Product development is hard.
The Product Thinking Playbook by Connected is here to help.
Consisting of various tactics, techniques and milestones borrowed from Design Thinking, Agile Development, Lean Product Strategy, and Jobs-To-Be-Done Theory, the Product Thinking Playbook helps facilitate conversations around what you will and (just as importantly) will not do to achieve your product goals.
A Playbook exercise has two goals. The first is to create alignment through dialogue about what will and will not be done to achieve the desired outcome. The second is to generate a physical artifact that represents the execution strategy that can be referenced—and modified—throughout the life of the project.
Tactics cards represent a set of methods and strategies that can be sued to accomplish desired outcomes.
Milestone cards are used to update or demonstrate progress at the conclusion of critical tactics.
Technique cards specify how you will execute against your chosen tactics in greater detail.
Cards labeled with the Discovery track are geared toward learning and validation while Delivery-labeled tactics are geared toward design and development.
Release software updates regularly and in short cycles to iteratively improve the capabilities and functionality of an existing product in the market.
Define system-level components and interactions, including technical requirements and domain boundaries, resulting in a technical vision and plan for execution.
Deploy iterative design techniques to validate and deliver assets in tandem with software development cycles. Activities include synthesis, ideation, user experience design, and visual design.
Test the desirability of a proposed strategy, concept, or feature against the problem or opportunity it is intended to address. The goal is to ensure that the solution addresses a real, observed struggle…
Generate, define, and evaluate multiple product concepts that leverage key insights and areas of opportunity uncovered through research.
Beginning with a validated solution backlog, QA analyzes product requirements, design specifications, and system interactions to validate accuracy, comprehensiveness, and testability…
Establish multiple options for the software architecture—following commonly defined patterns—and validate which approach will be the most effective and extensible solution.
Determine the technical feasibility of a concept or prototype given project constraints, available technologies, and business requirements.
Illustrate a story or sequence of events to explore the beginning, middle, and end of how a user interacts with a product, service, or AR/VR experience. In some cases, storyboards may be translated into concept videos…
Complement an early-stage prototype with human elements during testing to more realistically simulate the proposed solution, revealing more representative behaviours from the users testing it.
Release of a pre-market version of the product to a select group of users. This allows for the testing and validation of many of the assumptions made during development prior to releasing to market.
An in-depth demonstration of the product in its working-code version, along with a presentation of the technology and overall design philosophy.
A shareout of key insights based on research synthesis. These will inform the the design and development of product concepts and recommend a clear direction on product strategy.
A meeting between stakeholders and team members to define project and product success and secure overall alignment. Topics covered include business goals, relevant technologies, existing research, and the overall execution plan…
A formal presentation of a product’s strategy that may include the product vision, value proposition, key objectives, measures of success, and/or a design and development roadmap.
"*Required" indicates required fields
Like the products we work on, the Product Thinking Playbook is always evolving. By sharing it with others, we hope to spark conversation on how to build better.