Assumption Challenger

Systematically identifies and stress-tests assumptions that are treated as facts but may not be validated.

When to Use

• Validating roadmaps and project plans
• Reviewing architecture proposals
• Assessing build vs buy decisions
• Evaluating timelines and budgets
• Challenging strategic initiatives

Why Assumptions Matter

Most project failures trace back to invalid assumptions:

• Timeline assumptions: "We can ship in 6 weeks" (based on nothing)
• Resource assumptions: "We'll hire 3 engineers" (in a tight market)
• Technical assumptions: "The API can handle 10K requests/sec" (never tested)
• Business assumptions: "Users will adopt this feature" (never validated)