Member-only story
Practical Zero to One Design Learnings
Pragmatical guide to inspire designer to navigate the ocean of early stage products
The relationship that design has with zero to one is fascinating.
How much is enough to move forward?
I have collected from the pragmatically reiterated guides a document of how I am currently tackling this role inside my team, showing examples as a guide to reduce friction and facilitate the cross-functional collaboration.
I started very lean from the definition of PRD to the end where the end of reiterate is temporarily suspended pending launch (get to 1).Let’s get started.
PRDs
Get the PRD done is the first necessary step.
- No work is done without a proper, well defined and scope PRD
- The entire design team can and should see the PRD and the owner, for both critiques and transparency without influencing out of the Accountable role (see RACI model)
- First early design mocks should honour everything inside the PRD
First iterations
Time to design? Not so quickly
- Take some time to benchmarking a competitive analysis and a general patterns audit