What is 10-80-10?
The 10-80-10 Framework is a project management mental model used by engineers, filmmakers, product teams, and classroom builders alike. It breaks any project into three distinct phases — each requiring a different kind of thinking — so that every hour of work is as productive as possible.
Most project failures share the same root cause: teams skip the first 10% and jump straight into building. They end up working hard in the wrong direction, then scrambling at the deadline. This framework prevents that by structuring how and when you think.
Phase 1 — The First 10%: Vision & Alignment
Before a single line of code is written or a single brick is placed, the best teams spend time getting aligned. This phase is about setting the vision, defining success, and identifying constraints before the clock starts burning.
What happens in the first 10%
Set the vision. Define the goal in one sentence. List your constraints — time, tools, and team. Answer the five W’s so everyone is pointed in the same direction.
Key questions to answer
- What exactly are we building?
- Who is it for?
- What does “done” look like?
- What are our constraints (time, tools, budget)?
- What could go wrong?
Phase 2 — The Middle 80%: Execute
This is where the actual work happens. Build it. Code it. Make it. The 80% phase is the engine of the project — but it only runs well when Phase 1 set the direction correctly. Protect this time aggressively: no major changes to the plan, no scope creep.
Rules of execution
- Stay focused on the defined goal — resist the urge to change the vision mid-build
- Make decisions quickly — stalling is more expensive than an imperfect choice
- Document as you go (code comments, sticky notes, quick voice memos)
- Ask for help early, not at the end when there’s no time left to fix it
Phase 3 — The Last 10%: Review & Deliver
Step back. Look at what you built with fresh eyes. Does it match the vision from Phase 1? The last 10% is where you polish, present, and collect feedback. It is not about building more — it is about making sure what you built is ready to land.
Review checklist
10-80-10 In the Wild
The same framework shows up in every professional field. The ratio and the phases are consistent — only the subject matter changes.
🚀 NASA Moon Landing
- First 10% — Vision
- Years of mission planning, trajectory math, crew selection, and safety protocols. Every variable defined before liftoff.
- Middle 80% — Execute
- Building the Saturn V rocket, training astronauts, running simulations, launching, and navigating 240,000 miles of space.
- Last 10% — Deliver
- Post-mission review, scientific data analysis, congressional debriefs, and lessons documented for the next mission.
💻 Building an App
- First 10% — Vision
- Wireframes, user stories, tech stack decisions, and a clear definition of the MVP before a single line of code is written.
- Middle 80% — Execute
- Writing code, designing screens, integrating APIs, and testing features in sprint cycles with regular check-ins.
- Last 10% — Deliver
- Beta testing with real users, squashing bugs, writing App Store copy, and submitting for review.
🎬 Making a Movie
- First 10% — Vision
- Writing the script, building storyboards, casting actors, scouting locations, and locking the shooting schedule.
- Middle 80% — Execute
- Principal photography, set direction, and the edit — weeks or months of assembling the raw footage into a story.
- Last 10% — Deliver
- Test screenings, focus group feedback, sound mixing, color grading, and the final cut submitted for distribution.
Why Students Skip the First 10%
Most project failures happen because teams skip the first 10% and jump straight to building. The urge to start doing is powerful — but without a clear goal, that energy is wasted on the wrong thing.
“A goal without a plan is just a wish.”— Antoine de Saint-Exupéry
Common mistake: “I’ll figure it out as I go.” This approach leads to wasted effort when you build something that misses the brief, missed goals when the deadline arrives and the core feature isn’t done, and last-minute panic when there’s no buffer left for the unexpected. Spending 6 minutes planning a 60-minute project is not wasted time — it is the multiplier that makes the other 54 minutes count.