Most projects kick off with optimism and assumptions, then hit reality somewhere around week three. By then, you've already committed resources, briefed stakeholders, and made promises. The Scope Check helps you surface those problems before you start, not after.
What is the Scope Check?
Scope Check is a two-session validation workshop that stress-tests project ideas before you commit resources. It's designed to expose untested assumptions, spot hidden risks, and create honest alignment across stakeholders all in under two hours total.
The template walks you through 10 focused sections that answer the critical questions most kick-off meetings skip:
Problem Check - Do we fully understand what needs solving?
Key Players - Who needs to support this work?
Technical Viability - Is the solution technically possible?
Change Capacity - Can we handle this change?
Value Check - Is this worth pursuing?
Resource Reality - Do we have what we need?
Red Flags - What could go wrong early?
Greenlight Check - Are we ready to proceed?
Success Signals - What does good look like?
New Normal - How will work change?
Who can use this Scope Check template?
This template works for:
Project managers starting new initiatives who need stakeholder alignment
Product managers evaluating whether a feature is viable before adding it to the roadmap
Business analysts validating requirements before diving into detailed specifications
Facilitators leading teams through alignment sessions
Cross-functional teams facing unclear scope, competing priorities, or misaligned expectations
Leadership teams who need to make go/no-go decisions on strategic initiatives
Best results come from sessions with 3-5 people who understand the space, including decision-makers, technical experts, and the people who'll actually do the work.
When to use this Scope Check template
Use Scope Check when:
You're starting a new initiative but stakeholders disagree on what problem you're solving
You're about to kick off a project but sense there are unspoken concerns
Stakeholders are excited about an idea but haven't stress-tested the assumptions
You need to expose risks and blockers before they derail the project
The team keeps debating scope without getting to clarity
You need a structured way to decide: greenlight, rework, or stop
Leadership is asking "are we ready?" and you're not sure how to answer
How to use this Scope Check template
Two-Session Flow
The template is designed to be run across two focused sessions with time between them for insights to settle.
Session 1: Brainstorm (60-75 minutes)
Work through sections 1-7 in 10-15 minute blocks per section. Use the starter questions, add stickies, and look for gaps—not consensus. Capture your top 3 insights per section.
Problem Check - What exact problem are we solving and why now?
Key Players - Who has the most to gain? Where's the resistance?
Technical Viability - What technical foundations need to be in place?
Change Capacity - What other changes are in progress? Can we handle this?
Value Check - What specific benefits would this deliver?
Resource Reality - What skills do we actually need? Where are the gaps?
Red Flags - Which assumptions need testing? What could derail this?
Between Sessions: Let it settle (1-2 days)
Give the team time to digest what surfaced. Honest conversations need time to sink in.
Session 2: Distill (30-45 minutes)
Work through sections 8-10 in 10-15 minute blocks. Narrow focus, assess readiness, agree on next steps. Aim for clarity.
Greenlight Check - What's still missing? Which risks remain unaddressed?
Success Signals - What metrics would prove success?
New Normal - Which roles need to change? What new skills must teams develop?
End with a decision: Greenlight, rework the approach, or stop.
What this Scope Check helps you accomplish
After two focused sessions, your team walks away with:
Exposed assumptions that would have caused problems later
Honest assessment of technical viability and resource gaps
Aligned stakeholders who've voiced concerns openly
Clear understanding of what success looks like
Documented risks and how you'll address them
A confident go/no-go decision backed by evidence
What's included in this template
Start Here Quick overview and instructions to get your team oriented
Workshop Cheat Sheet Preparation tips, ground rules, session timing, and post-workshop actions
Scope Check Canvas 10 structured sections with starter prompts to guide discussions
Worked Example Real sticky note demonstration using a lead scoring scenario so you can see what good looks like
Navigation Frame Quick links to jump between sections
Tips for facilitating with this template
Prepare before the workshop - Invite 3-5 people who understand the space. Ask them to bring key docs, blockers, and lessons learned. List known constraints or deadlines upfront.
Push for honesty over politeness - Problems hidden in kick-off meetings show up as disasters in delivery. Create space for people to voice concerns.
Ground rules that matter:
No wrong answers - Every perspective matters, especially uncomfortable ones
Evidence > opinion - "I think this will work" is different from "I've seen this work because..."
Be specific, avoid generalities - Instead of "users want better reports," say "managers spend 3 hours weekly fixing spreadsheets"
Spot assumptions - When you hear "probably" or "should," flag it as an assumption to test
Capture disagreements - When stakeholders disagree, that's a signal of risk. Document it rather than smoothing it over
Time-box discussions - Each section gets 10-15 minutes total (10 minutes discuss, 5 minutes synthesize top 3 insights). Set a visible timer.
Look for gaps, not consensus - Session 1 is about raising open questions, risks, and different perspectives. You're aiming for breadth, not agreement.
Let insights percolate between sessions - The time between sessions matters. People need space to process uncomfortable truths.
Use the worked example - If your team is new to this approach, walk through the example first so they understand the level of detail you're looking for.
Why this approach works
Traditional project kick-offs focus on timelines, deliverables, and optimism. Scope Check focuses on the uncomfortable questions that usually don't get asked until it's too late.
By running two short sessions with time between them, you give teams space to be honest about concerns they might not voice in a single high-pressure meeting. The result is a clear, confident decision backed by evidence rather than enthusiasm.
---
The Scope Check is part of a larger validation methodology, but works perfectly as a standalone tool for teams who need honest alignment before committing to a project.
Pragati Sinha
Founder & Facilitator @ Proof Sprint
Helping teams kill good ideas before they waste time solving the wrong problem.
