Short session with the founder or team to define goals, product vision, and success metrics Identify key user segments and assumptions to test later

SWOT Analysis - Summary of competitor and market findings organised by: Strengths: What current solutions do well Weaknesses: Common usability or accessibility gaps Opportunities: Areas where the MVP can differentiate or simplify Threats: External factors or design trends that may limit adoption Opportunity Map Visual summary connecting user pain points to areas for innovation or simplification

1. Concept Sketches Low-fidelity sketches or whiteboard frames exploring multiple layout and flow options Focused on solving top tasks identified in research 2. User Flow Diagrams Visual maps showing how each persona moves through key interactions Includes decision points, system responses, and potential friction areas

Purpose To develop the core structure and layout of the MVP through wireframes and mid-fidelity designs that define the product’s flow, hierarchy, and functionality before adding visual polish. This stage focuses on usability, clarity, and alignment with user goals rather than final styling. What’s Involved Translating user flows into detailed wireframes for key pages and interactions Exploring multiple layout variations to test information hierarchy Designing mid-fidelity screens that show spacing, structure, and interaction intent Ensuring layouts follow accessibility and responsive design principles Reviewing flows internally to confirm logic and usability before moving to high-fidelity UI Deliverables Complete set of low- and mid-fidelity wireframes in Figma Annotated notes explaining layout logic and interaction patterns User flow diagram updated to match designs PDF summary linking design rationale to research insights Optional clickable prototype for structure validation

Purpose To review and test the wireframes and mid-fidelity designs internally with the team before involving real users. The goal is to confirm that the proposed flows make sense, align with business goals, and can be built efficiently. What’s Involved Team walkthrough of each core flow to verify logic and usability Feedback sessions with founders, product, and developers Checking consistency across screens and alignment with requirements Identifying unclear interactions, missing states, or technical blockers Prioritising refinements before moving to high-fidelity design or development Deliverables Internal review notes and feedback summary Updated wireframes or mid-fidelity designs reflecting agreed changes Issue log with priorities and owners Validation summary outlining next steps for final design or prototype build

Organised Figma file with labelled pages, flows, and components Final designs approved by the team Design tokens or style references for colours, typography, and spacing Handoff checklist confirming accessibility, responsiveness, and completeness Optional walkthrough session to clarify functionality and answer developer questions Figma make prototype