The phrase to be designed signals a moment of intentional planning where ideas, constraints, and user needs are clarified before any execution begins. This phase is critical for projects that demand thoughtful architecture, brand alignment, and technical feasibility.
By treating to be designed as a deliberate checkpoint, teams can surface risks early, align stakeholders, and build solutions that are both usable and maintainable.
| Project Phase | Key Activities | Primary Owner | Decision Output |
|---|---|---|---|
| Discovery | Stakeholder interviews, user research, competitive audit | Product Manager | Problem statement, success metrics |
| To Be Designed | Requirements synthesis, journey mapping, architecture sketching | Design Lead | Design specifications, prioritized backlog |
| Build | Prototyping, development sprints, asset production | Engineering Lead | Working MVP, tested components |
| Validate | User testing, analytics review, iteration planning | Product Manager | Usability report, launch readiness |
Define Scope And Objectives
During the to be designed phase, teams translate high-level goals into a clear scope. Objectives, constraints, and acceptance criteria are documented so that everyone shares the same understanding of what comes next.
This work includes mapping user journeys, identifying touchpoints, and prioritizing features that directly support measurable outcomes for the product or service.
Key Outcomes
Defining scope reduces ambiguity, aligns cross-functional teams, and establishes a baseline for estimating effort and timeline.
Conduct User Research And Analysis
Effective design starts with real user needs. Research activities such as interviews, surveys, and contextual observation feed insights that shape the to be designed artifacts.
Analysis of this data reveals pain points, unmet expectations, and opportunities that may not be visible through business assumptions alone.
Insights To Actions
Synthesizing research into personas, jobs-to-be-done statements, and task analyses ensures that the design decisions remain user-centered and evidence-based.
Develop Architecture And Design Specifications
With scope and insights defined, teams move into structuring information architecture and interaction models. This stage transforms concepts into concrete design specifications.
Details such as navigation flows, component libraries, accessibility standards, and performance targets are recorded for engineering handoff.
Blueprint Deliverables
Wireframes, flow diagrams, and design systems documentation produced during to be designed activities provide a shared reference throughout implementation.
Align Stakeholders And Governance
Complex initiatives require clear governance, sign-off processes, and alignment across legal, compliance, and business functions.
During to be designed, teams clarify responsibilities, review constraints such as budget and regulation, and establish communication rhythms to keep the project on track.
Plan And Execute With Clarity
Treating to be designed as a disciplined phase enables teams to move forward with confidence, minimizing rework and maximizing value delivery.
Strong specifications, aligned stakeholders, and user-informed decisions form the foundation for successful execution.
- Document clear objectives, scope, and acceptance criteria early
- Leverage user research to inform design decisions and prioritize features
- Produce detailed specifications and architecture diagrams before build starts
- Establish governance, roles, and sign-off checkpoints with stakeholders
- Iterate with engineering through validation, but finalize core design commitments during to be designed
FAQ
Reader questions
What specific deliverables are expected during the to be designed phase?
Expect design specifications, user journey maps, component libraries, prioritized backlogs, and documented acceptance criteria that guide development.
How does to be designed differ from the discovery phase?
Discovery focuses on understanding problems and user needs, while to be designed translates those insights into a concrete plan and specifications ready for execution.
Can to be activities overlap with development sprints?
Yes, iterative approaches allow design validation alongside development, but core specifications and architecture decisions should be solidified during to be designed to reduce rework.
Who owns responsibility during to be designed activities?
Design Lead typically owns deliverables, Product Manager aligns priorities and stakeholders, and Engineering contributes feasibility input to ensure realistic solutions.