I strongly believe in the importance of process, and the following quote perfectly captures my perspective:
The process is the foundation of success. Trust it, embrace it, and let it guide you toward greatness.
~ John Addison
There are many processes—such as Design Thinking, Design Sprint, and Lean UX. However, not every process fits every project. Each company has its own unique way of designing and developing digital products. Since I began designing in 2019, I’ve adapted to new processes and approaches with every company change. This ability to embrace new methodologies reflects two key traits about me: my openness to learning and my flexibility in moving beyond personal preferences.
My Design Process
1. Understanding:
When it comes to projects, I focus on gaining clarity by asking the right questions to the right people. Typically, product managers (PMs) present me with the requirements. We usually have a kickoff meeting where the PM explains the problem and we brainstorm potential solutions together. Sometimes I agree with the proposed direction, and other times I raise questions to ensure everything is clear. If I have any doubts, I make sure to resolve them first. After that, I provide an estimated timeline for delivering the first design iteration.
2. Design:
The first iteration is intended to ensure alignment with the requirements and to allow for any necessary technical feasibility testing.
How long does it take to complete the first iteration? Honestly, it depends. In my current organization, we have a design system in place, so the process is more streamlined. However, in my previous company, where no design system was available, the design process took more time as I had to build everything from scratch.
3. Collaboration:
I collaborate closely with PMs, developers, QAs, and other designers.
Collaboration is essential in any product company. It acts as a bridge between design and development, ensuring smooth handoffs and alignment. In our organization, this collaboration happens in two key phases.
- Phase 1: After delivering the design, the PM organizes a kickoff call with the development team to ensure alignment.
- Phase 2: Once the developers complete the implementation, they provide a demo. At this stage, we review the design from a quality perspective and create tickets for any necessary changes. Some back-and-forth between design and development is expected at this point—it’s all part of the product cycle.
4. Gathering Feedback:
The process doesn’t end with delivery; feedback from users is crucial.
Once a feature goes live, we begin gathering feedback from customers. In the B2B space, we maintain close relationships with our customers to ensure a smooth user experience and to continuously improve our products.
Final note
This is the process I follow at my current organization, but every company has its own way of working. If your organization follows a different process, no problem—I’m open to adopting new approaches. As mentioned earlier, I value flexibility and learning.
Lastly, you’ll notice that I haven’t used complex UX jargon like user research, personas, or empathy maps. I believe in keeping conversations straightforward and discussing concepts in simple, easy-to-understand terms.