1. Understand the business problem
We begin by discussing the intended users, the task they need to complete, and the constraints around delivery. Useful inputs include a current workflow, a short project brief, and sanitized examples of the information the product handles. Discovery separates confirmed requirements from assumptions. The goal is a shared understanding of the problem before a detailed commitment to features or timing.
2. Define scope and responsibility
The proposed scope identifies deliverables, exclusions, dependencies, and acceptance expectations. We discuss who supplies content, owns platform accounts, approves decisions, and supports the product after handover. Design exploration, production development, and ongoing maintenance are different activities. Their responsibilities and commercial terms belong in the project agreement.
3. Design the essential journeys
The interface should support complete user tasks, including error recovery and administrative work. Depending on the scope, design work may include navigation, page structure, prototypes, and interaction details. Review focuses on whether users can understand what to do and whether the proposed workflow matches the business rules. Illustrative screens are not presented as proof of production functionality.
4. Build and review against the scope
Development turns the agreed experience into working software. Reviews connect the implementation back to requirements and identify questions early. Integrations, permissions, and data handling need explicit attention when they are part of the product. Changes are assessed for their effect on scope and dependencies rather than quietly added to an unchanged delivery promise.
5. Validate and prepare release
Acceptance review considers normal workflows, invalid inputs, and meaningful failure scenarios. Device coverage, accessibility, and technical checks are selected for the product. Before launch, the release plan identifies the build, account ownership, documentation, and known limitations. External reviews and platform approvals remain the responsibility of their respective providers.
6. Handover and plan the next iteration
The agreed handover makes the product understandable to its owner. It may include setup and operating instructions, administrative guidance, source access, and dependency information. Support and maintenance coverage are agreed separately where applicable. Feedback from real use helps identify the next improvement, rather than assuming every possible feature belongs in the first release.