A good design cannot be achieved without a good design process. The below are the design process I follow in my team. The key is to continue learning from the users and iterate the design.
PROJECT LEVELS
Level 1
Level 1 projects include new products. Level 1 can also include a feature for an existing product that significantly increases functionality.
Level 2
Level 2 projects are new features that expand the functionality of an existing product. Level 2 also include expansion of an existing service/feature into additional localizations.
Level 3
Level 3 projects are minor enhancements and bug fixes in existing products.
MILESTONES
| |
| | |
| Optional
Connect with UX early on for a potential vision project | Before starting a vision document (OP1, PR/FAQ etc.) | PM Role: - Define business problems and opportunity - Define initial hypothesis we want to support/disprove - Identify related initiatives at Amazon that may impact this product, service, feature, etc. Design Role:
- Assist in generating design insights (design sprints, personas, journey maps etc.).
- Help PM prepare for vision share out by communicating needs & concerns.
Research Role: - Help identify research needs and gaps in current understanding.
- Report findings & data from survey & research (if applicable).
- Help team set up next steps. |
| CONCEPT DESIGN (Exploration) |
| | |
| Required for level 1 & 2
Consult with UX designer on the potential project | When starting a vision document (OP1, PR/FAQ etc.) | Initiator Role (PM):
- Fill out intake SIM .
- Sign up for UX office hour (if applicable).
UX Role:
- Review intake SIM.
- Request sign up for office hours if anything is missing to move forward. |
| Required for level 1 & 2
Discuss the project’s goals, expectations, and timelines | | Design Role:
Schedule kickoff meeting with PM, UX, Research and Dev (optional) after reviewing SIM.
---
Meeting Agenda (Duration 30 min.)
PM
Project Overview- What is it? What customer problem are we trying to solve? Who are the customers? What are our tenets? What does success look like and how will we be measuring it? General timelines (summary of SIM)
DESIGN
UX Process Overview- what to expect: review meetings, process, and artifacts like journey maps, personas, etc.
RESEARCH
How can research help and when in the process
ALL
General discussion, Q&A
Wrap up, and next steps |
| Optional
Explore different approaches and options to solve the problem | Based on timelines set at kickoff | Design Role:
- Drive the exploration design.
- Set up Concept design review, Design team review and Stakeholder design review to share progress and get alignment on designs with Business & Tech partners.
- Support defining business requirement.
- Connect with external partner teams to investigate potential collaboration or alignment.
PM Role:
- Provide data & business insights to help the team make informed decisions.
- Update PR/FAQ with details based on design progress.
Dev Role:
- Participant in check-in & reviews. Provide consulting for technical insights related to feasibility & scalability.
- Start tech investigation (if applicable).
Research Role:
- Provide data & insights to help the team make informed decisions.
- Conduct research to evaluate design explorations (if applicable). |
| Required for level 1 & 2
Review product & design direction and align on next steps. | Before or just after PR/FAQ approval | PM & UX Role:
Schedule wrap-up meeting with PM, UX, Research and Dev. |
| BUILD (front end, back end) |
| | | |
| Required for all levels
Build the chosen direction. | | Dev/QA Role:
- Drive development.
- Schedule bug bashes, take note of bugs and create issues in SIM.
- Schedule demos to share progress.
Work with UX and PM on issues implementing designs.
UX Role:
- Troubleshoot any CX issues during the implementation.
- Review work and provide feedback by create issues in SIM.
- Triage bugs.
- Participate in Bug Bashes.
PM Role:
- Troubleshoot any CX issues during the implementation.
- Review work and provide feedback by create issues in SIM.
- Triage bugs.
- Participate in Bug Bashes. |
| Required for all levels
Assess the implemented design. | When Dev. indicates implementation is near-final form | Dev/QA Role:
- Prepare build for demo/play-with session.
Participate in Bug Bashes.
PM Role:
- Review demo/play-with session build.
- Schedule demo/play-with session with stakeholders for final approval.
- Take notes on blocker and future tasks/bugs and create issues in SIM.
UX Role:
- Review demo/play-with session build.
- Participate in demo/play-with session. |
| Required for all levels
Final check-in to ensure and verify top quality before launch. | | PM/UX/Dev/QA Role:
- Sign-off on implementation for shipping. |
| |
| | |
| Required for all levels
Measure the successes and mistakes! Learn and iterate. | Post-launch after gathering required metrics & feedback | PM Role: - Set up retrospect meeting with Dev, UX & Research (if applicable). - Report findings & data to the team so the team can learn & iterate. Design Role:
- Drive design improvement & CX changes based on data.
Research Role:
- Report findings & data from survey & research (if applicable).
- Help team set up next steps. |
