Redesign and prototype of the Requirements Application Platform.
Context
My role:
Improving user flow as an interface designer for service UI specification document requirements, creating UX solutions for UI specifications. The main goal of me as a designer is to create a service where document requirements can be created quickly and easily.
Client:
Startup platform for creating all documents and all requirements before the project. It provides users a tool for working with requirements for mobile and web projects with a target audience for small teams for creating documents with the support of UI specifications with the ability to use AI. The main goal of the project is to create a service where document requirements can be created quickly and easily.
Problem:
According to feedback from users and the client, the platform's interface is the main feature UI specifications are a very oversaturated screen and when users sit there and don't understand how it works. Users don't notice and don't understand how to still generate text with AI.
Task:
Change user flow, conduct an audit of the app, provide UX solutions in an interactive prototype and update the design of the interface.
The developers did their best and launched the app, which already has some useful features. The client and I did a discovery of the project. We discussed the existing application interface, its problems and the tasks that the project is facing. We fixed everything in the technical documentation.
The main tasks and problems were:
1) The page interface is too oversaturated. Users don't understand how to reach their queries when they take advantage of the interface features.
2) Users don't notice or understand how else to generate text using artificial intelligence.
3) Request to change or improve the user flow
4) The navigation is not user-friendly. It's not clear how to go back a step or what page you're on now.
Solutions and proposed timeline and estimation:
Research: 2 days; ~8 hours
Audit the current system interface: specs and project analysis.
Building new solutions. *Relatively quickly, as I have already encountered and had an overview of such decisions.
Wireframes: 2 days; ~16 hours
Wireframe for default page
Wireframe for UI specifications page product
Final: 1 day; ~8 hours
Present the solution and show this in a clickable prototype. Create a clickable prototype
Reviews and revisions
Transfer of screens to development
UX Wireframes
After agreeing with the client on the project's next stage- the wireframes' development. Now we will focus on creating detailed wireframes and prototypes that will reflect the updated structure and design of the application interface.
Concept solutions
Requirement descriptions play a crucial role in the decision-making process at all stages of development for the entire team, and improving your requirements can help the manager send it to the team earlier and automate writing requirements from scratch
This product is here to help and it's very easy to get started. Just provide a few details about your UI Element or the keywords you want to rank for in search engines, and the tool will automatically generate requirements for you right on the requirements settings page in your product admin.
Present the solution and show this in an interactive prototype
An interacive protype shows how the application interface will look and function, allowing users to interact with it, navigate between screens, and perform basic actions. It provides a realistic view of the user experience and helps to identify and fix possible problems in the early stages of development.
UI specifications page product
To describe the document requirements and reduce the time for specification descriptions to the selected element, a solution of text generation by keywords was added.
Results
The presentation of the solution with an interactive prototype has improved the service's navigation. The result is a new UX design solution and new navigation on the platform.
I spent just ~32 hours and 5 days on the project as a designer. This, along with meeting calls and a quick analysis of competitors.
Since I unfortunately didn't have access to potential customers, at the initial prototyping and pattern analysis stage, I suggested that the customer team interview potential users to see if the solution helped them. The team listened and hopefully did a couple of iterations.
