PDP Cheat Sheet
PDP Cheat Sheet
CHEAT SHEET
Meet the 12 steps that changed the way digital products are built!
Directly to you, from our Product Design Process Book.
• Workshop with the team (usually one to four hours) to present the vision and the
goals of the project and clarify all necessary business requirements.
Assures that the whole team is working on the same page and with all the relevant
information to start the project.
1 / RESEARCH
User Research • Explore the user profiles with the product stakeholders;
• Define target user profiles (Personas), clearly identifying the users’ motivations and
goals for using the product.
Guarantees product usefulness and effectiveness from the users’ point of view.
User • Map the ideal user experience, describing the main steps performed by the user;
Journey • Write and validate the user scenarios.
Provides a vision of the global user experience, ensuring its consistency and fluidity.
Serves as a base to establish the product requirements.
Provides an indispensable basis for the project development plan ensuring that,
even under time and cost constraints, a viable product can be developed.
Wireframes • Draw the skeleton of the screens covered by PDP, defining the pages structure and
navigation flow.
Improves interface usability and reduces design time by baselining the core
information architecture.
Mood Board • Scout the product’s “mood” through a collection of pictures, words, and other
visual elements.
Assures that the product’s look & feel conveys the desired user experience and is
aligned with the user profile and market strategy.
PHASE STEP DESCRIPTION
Style Guide • Baseline the graphic interface styling: color palette, fonts, image style, input fields,
buttons and other page elements.
Assures the consistency throughout the application, baselining the visual coherence
of different graphic interface elements.
3 / EXECUTION
Graphic User • Execute the end-looking screens by applying the Style Guide to the Wireframes.
Interface Provides stakeholders with the final aspect of the product’s screens in order to
Design
obtain approval before moving to the implementation.
Prototype • Develop a click-through Prototype, accessible online and shareable with other
devices and users through a link and password.
Allows the navigation from screen-to-screen, facilitating the feedback intake either
from stakeholders or from potential users and investors.
High-level • Develop the technical design with the ideal balance between complexity and
4 / TECHNICAL ASSESSMENT
Architecture reach;
• Identify the external dependencies from third party providers (e.g. Stripe,
Facebook, Amazon).
Details how the product is going to be built, identifying baselines for the needed
technologies and skills to build it.
Project Plan • Define the major milestones, providing a general understanding of the project’s
structure, phases, intersections and interdependencies.
Allows a good understanding of how to build the product, how much effort it will
require and the expected costs for each product phase.
Sounds useful?
We have a whole book about it!
A manual for digital product design based on a
multidisciplinary approach that unites product
owners, designers, developers and managers.
A proven step-by-step process that helps to avoid
the waste of resources and to succeed in a quick
market launch.