I worked on many different projects. Some of them had clients that already had grader information from users. He just wanted to upgrade the old version of the app. Also, he has known very well his client. He knows what he wanted. I didn't have design system. The client ask for colorfull pallette, bacause his clients was portugalize. I had to design all form skrech. The specifications were clear. That's what I talk about was project for Transision Technology. I worked for Smart Agency. It was web application. Other three apps I design using company brand colours. They didn't have design system. I use a design system for another project. Cool stuff. It makes my work more efficient and effective.
Writing down requirements
Small projects
Websites and small apps like mobile apps have different approach. The client usually gives it to me and the project moves on. How do I handle it? I just try to communicate well with clients and I ask questions. I cannot provide you with a ready-to-go recipe because I am simply asking for things that I do not understand. Every project is different from the last. Usually, the product owner arranges a meeting with me and the client, and we talk. I'm an IT engineer, so my questions are more about the client's preferences and his users. When the client can't answer my questions on the meting, they just send me the answer later.
Big apps
Larger projects are often more complex. I need to understand business needs, clients and the user. Strange? There are projects that the client is not a user. I try to answer questions like:
- What's the problem?
- Are there any expectations for the product now?
- What do you want to achieve?
Moreover, I am interested in learning as much as possible about the competition. What are the ways we compete with them? Why do our clients choose us instead of our competitors? Does the client know this? I write down the requirements once at the beginning, and they are possibly verified on an ongoing basis during the design process. Competition analysis can also be done in cycles. Unless I can be in constant contact with the client’s team. I start build user persona.
Outcome: I make notes. I can prepare an PowerPoint, Figma or Exel file for a competitive audit.
Analyse the current condition of the product (UX audyt).
Usually, I ask the client if they want this or not. It is a painful task as I will list the errors committed by both the current PJM, PO and previous designers. Regrettably, every project that I have worked on since I began my career as a UX/UI designer has been a disaster. Sometimes the designer is responsible, and sometimes the client is responsible.
Outcome: I make notes. I prepare a PowerPoint file with comments and print screens.
UX reserch.
It's a tool for me. If clients wants to, I can share with him my notes. I don't make a big deal about it. I use this tool when I need to clarify something. It's not taking me weeks or months. I don't have time for it. I'm trying to be flexible with it. When I need to recommend something or see if there are any alternatives.
Outcome: Notes, links, print screens.
Making use cases.
Define future, expected behavior of the system and describe solutions to critical errors (consultations with developers at meetings).
This step can be repeated. It will show up before we start planning new features.
Outcome: I make notes. Moreover, it can be described with comments in the flow or mockup.
Doing flow.
A verbal description (a sketch) is the first thing I do. Then I start with flow.
At this stage, consultation with the team is important to me. I would like to hear your opinion, what you think about it, and how you view the real implementation of the model. Am I missing something that should be included? I use wireframes as a quick form of a sketch and notes from consultations.
Customers would rather not see this stage. They often argue that they don't understand what they're looking at. Meeting notes/screenshots are what the result is.
What are the reasons this step is significant to me? Creating high-quality mock-ups takes a lot of time. Due to the current stage, I want to save time, as well as avoid a million corrections and a delayed implementation deadline.
It's very usefull for big projects. Sometimes, one future is designed in one file and it is necessary to have a main file with links. An example you can see below - mobile app
The clients seem to think they don't need it at all. Then they are surprised that something is not working properly. Apps can have separated features but still, there is one point like a menu that connects them. I understand the future is even a little thing hidden under one icon. Even those need to be described like this or by words (list or step by step description).
Outcome: FigmaJam, Miro or notes.
Wireframes that's nobody uderstand but only UX/UI designer do.
Here should be wireframes that's looks like this:
The clients seem to think they don't need it at all. Then they are surprised that something is not working properly. Apps can have separated features but still, there is one point like a menu that connects them. I understand the future is even a little thing hidden under one icon. Even those need to be described like this or by words (list or the 'step by step' description).
Outcome: Figma, skeches on paper or tablet.
Mock-ups and prototypes.
You can say finally! How long I should wait for the most important part. No. It's not the most important. The most important is to understand the business, competition, target and end users. The mockup is just a nice picture with a description.
Mock-up as my recommendation and design of the finished product. It is also a point of reference. I believe that it should be implemented. Good practices are exhibited through references. That's fine if the customer doesn't agree with it. I will make changes and make a note in the documentation. The customer takes responsibility for it.
The mock-ups are described by me and have equivalents in flow. Complex functionalities can be hidden under a given icon. For example, a simple save is presented on the mock-up as a save icon and the developer writes more than one line of code.
This part can be tested. Do you know what other designers say about tests? You know how the product works when the users use it. Before you can design across good practices that's already tested by years of experience and described by other designers. But some features can be implemented in about 300 hours by developers. Now it's too risky if I will not test it.
Please see examples in portfolio tab.
Small websites and apps can also have more interactive mockups. Some parts of mockups should be interactive to show the client and developer how it works. I did mockup that contain only table.
Below you can find simple example for mobile app.
To see more detail view, please hover on prototype below and find full-view option.
Here you can register, login, open menu and search.
The client can decide if this step is the last and implement the prototype or ask for more fixes.
Outcome: Figma.
Improving the interface.
In my opinion, everything can be improved, even small brand and one page. I know that mobile apps are done once and the team moves to another project. It's up to the client, not my decision.
I will accomplish this by conducting user testing.
The cycle is like this:
- Implementation of the mockup.
- Testing
- Or testing a prototype if I think the risk is too high. What are my definitions of risk? For example, you think a given implementation will last 300 hours. It's a big risk for me, so I like to test it first and then give it to the implementation.
- Changing the layout. (Figma file)
- Consultations, prototype tests, etc.
The cycle begins again.
Communication
Yes. It's an important aspect of the design process. Not everyone has this skill at a high level. For me, it's important to know whether everything is okay or not. If in 6 sprints everything is fine, I should know this each time. On the 10th, something could change.
Clarifying expectations is also important. After 6 months of cooperation, it can be changed. However, please let me know what you think about my work and keep me informed.
What is the ideal design process?
Flexible.
It doesn't always take the same amount of time for every step. Sometimes it's just a few days or a week. I began my career as a UX/UI designer with websites. More than ten stand alone, web apps or plugins.
That's how my product design process looks in 2024. What will happen in the upcoming years? I don't know. I'm sure I'll improve it to do my job better. I'm interested in taking another course or reading books that might aid in this process.
Some examples are in my portfolio.
Mobile apps:
Web apps:
Back to all Articles
