My processes.

My process within an established design team follows key approaches with peer reviewing at each step (where appropriate).

Understand - Understand problem statement or task by examining the domain area, speaking to stakeholders, and researching existing similar solutions.
Document - Document dependencies, data requirements, and goals within a design file.
Create - Create modular wireframes as a scaffold for design, understanding the page hierarchy and most important visual aspects (usually the primary CTA).
Design - Mock up using existing components - making designs grayscale and removing graphics to keep focus on the task at hand, not visuals.
Prototype - Integrate with existing or new user flows—creating clickable prototypes if appropriate.
Review and test - Conduct peer reviews and refinement through discussions covering usability, requirements, development feasibility, and business requirements.
Rinse and repeat until approved.
Document for handover - Using modular design methods to suit business timescales - providing MVPs not just for full pages, but for modules of pages or processes, delivering components that work out of the box from a design system, plus adaptations for improved usability and visuals, considering scalability and reuse across the system.
Handover - Handover with three amigos and provide support throughout sprint cycles.

What I do