The project focused on creating a new business process to manage the service provider's orders in areas where it do not have the infrastructure. This included a process for communicating the client's various APIs and an application for mapping products, updating them and planning changes, which the business would use.
The main users of the application are Product Catalogue Specialists. The main problem identified by the client was the dispersed knowledge in different areas of the organization and the difficult and time-consuming manual entry of information in the spreadsheets, which was prone to a large number of errors.
✔️ gathering findings and requirements from the client
✔️ mapping of the process
✔️ preparing lo-fi and hi-fi wireframes of the application
✔️ preparing documentation, which included:
This stage was combined with Define stage, because we agreed to discuss the proposed processes on the wireframes and work on them iteratively - I got to know how the process looks like from the engineers perspective and I tried to translate these processes into the language of the GUI. Of course, the start was not easy, because the process was very complicated, but after a few meetings with the Product Catalogue Specialists (the business), Solution Architect and Business Analyst on the Client’s side we managed to agree on some fundamentals for the app. The wireframes had 3 versions until they were finally accepted.
<aside> ℹ️ Sometimes we needed more time because it turned out that the client needed to develop a process on their side and get along internally.
</aside>
<aside> ℹ️ We alerted the client that their branding colors, which we had to incorporate into the design, do not fulfill accessibility requirements in terms of the contrast, but they accepted that.
</aside>

Mapping of the products - Service provider to the other infrastructure operator.
After summarizing all acceptance criteria during the meetings, I prepared documentation of the product in Figma and Confluence. To do this, I used the guidelines provided by Autentika, because our company didn’t have any documentation template standarized yet. As for documentation, I first prepared:
<aside> ℹ️ We decided to use Carbon Design System without any specific visual corrections. We found out that this DS has a pretty extensive section about data presenting. Nevertheless, I had to do some additional changes, which was in general a bit too time-consuming.
</aside>
Because the business didn’t have any comments or questions after 1-1,5 months (we were updated on this information), engineers started to prepare the development environment. I prepared all the tasks in our Jira and made some subtasks to them. To be consistent with the use case specification and processes presented on wireframes, I used Figma to Jira plugin, so all the flows had its task in Jira.
<aside> ⚠️ During the beginning of this phase we discovered a problem. While waiting for the acceptance of the documentation the business started questioning it, because they didn’t understand it entirely.
We decided to take a step back ↩️ and go to the discover & define phase. In the end, the client decided to modify the process and add a few additional features, which resulted in significant changes to the processes and, at the same time, to the mockups and documentation. These had to be partially created from scratch.
</aside>
<aside> ℹ️ So I used this time to make some changes to the mockups and to the documentation. I gave up on diagramming user flows, because they appeared to be super difficult to understand and interpret. Instead, I created use case specification, which one of my company’s business analysts suggested to do. It contained main, side and alternative user scenarios.
</aside>
During making updated documentation and wireframes, the project changed it’s main IT Project Manager and Business Analyst on the client’s side, so again, time for having everything accepted was also consumed. Finally, in January after few rounds of comments with client’s specialists the documentation was accepted. I was still monitoring the whole development, giving feedback or opinion to the engineers who were coding (usually these were minor shortcomings).