1. Resist the urge to immediately start sketching

   It's tempting to start sketching right away, but it's important to first really understand the problem and the user's needs. Nevertheless, i often blatantly disregard this rule, if only to offload the ideas in my head.

2. Empathize

   Empathizing is researching. Getting to know the user. Understand their needs, motivations, and pain points. Possibly create user personas to keep them in mind throughout the design process. Collect all available data, such as analytics, user feedback, and stakeholder input.

3. Define the problem statement

   Based on the insights gathered, define a clear problem statement that outlines the main challenge to be addressed. Create an overview of the current challenges, insights, and opportunities. I also look at the competition and the market.

   

4. Validate with colleagues & stakeholder(s)

   Share the problem statement (and user personas if necessary) with colleagues and stakeholders for feedback and validation.

5. Create a baseline

   Use Miro to facilitate a brainstorming session (e.g. using sticky notes) and create a baseline for the solution. it is possible that not even a single pixel is designed at this stage.

   

6. Creating wireframes

   Use Figma to create wireframes that outlines the structure and layout of the solution. Lots of collaboration here is needed with different departements, especially copy.

   

7. Validate with colleagues, stakeholders, users... As many as possible

   Share the wireframe with colleagues and stakeholders for feedback and validation. If possible, conduct an early test with users to gather feedback on the wireframe and identify any usability issues. N.B. Testing for me is also asking my wife & daughters what they like the most. in an agile environment, I would give demos on a 2 weekly basis

8. Iterate. Iterate some more and Iterate again

   Iterate on the wireframe based on user feedback and continue to refine the design. Conduct usability testing with users to validate the design and identify any remaining issues.

9. Finalize high-fidelity design

   Create a high-fidelity design in Figma that incorporates the final visual and interactive elements.

   

10. Handoff to developers

    Document the design specifications and interactions for developers to implement the design.

These rules are not set in stone. Nor is the order in which they are executed. It's also really dependant on the project, the team and the way-of-work.

Approval also depends on the project and the organization's UX maturity. In some cases, a simple thumbs-up from the product owner in teams may suffice. In other cases, a more formal review by multiple stakeholders is wanted. However, it's crucial to engage stakeholders early and frequently. I also consider it essential to build consensus among team members by actively involving them in the process and regularly sharing progress. This could be in a dedicated chat, a weekly design-sync or a bi-weekly demo.