Tech Lead Handbook
  • 👋Introduction
  • People
    • Space for Growth
    • One on Ones
    • Manage Conflicts
    • Deal with Passive Aggressive
    • Give Feedback
    • Performance Management
    • Manage Up
    • Talent Matrix
  • Engineering
    • Pair Programming
    • DCI Framework
    • Code Ownership
    • ADR
  • Leadership
    • Leadership Competencies
    • The Communication Pyramid
    • Anti Patterns
  • Prioritisation
    • Types of Decisions
    • Pros and Cons
    • Decision Matrix
  • Hiring
    • Hiring Process
    • Prepare a Hiring
    • Position Description
    • Shortlisting
    • Case Study
  • Product
    • Working with Product Managers
    • Assumptions Mapping
    • Decision Making
    • Practice vs Process
    • Nemawashi
    • OKRs
    • Consensus vs Consent
  • Project
    • The Triple Constraint
  • Strategy
    • Tech Strategy
  • Communication
    • Use Positive Language
  • Shortlist
  • ...
Powered by GitBook
On this page
  • The What
  • The How
  • Tips
  1. Product

Assumptions Mapping

PreviousWorking with Product ManagersNextDecision Making

Last updated 8 months ago

The What

Assumptions Mapping is used to find and check assumptions based on desirability, feasibility, and viability. It helps teams focus on testing high-risk assumptions, lowers uncertainty, and improves decision making.

The How

Access the hypotheses: Desirability: Does the market want this idea? Feasibility: Can we deliver at scale? Viability: Is the idea profitable enough?

Map out Evidence vs Importance

Verify the top right quadrant where critical assumptions with little evidence are found

Not all hypotheses are equally important; some may not be critical to the business idea's success

Tips

📜
https://www.strategyzer.com/library/how-assumptions-mapping-can-focus-your-teams-on-running-experiments-that-matter
https://www.producttalk.org/2023/10/assumption-testing/