Most project plans get optimized at the margins — trim a week off the schedule, cut a little scope. 10x project management asks a different question up front: what would it take for this project to land ten times bigger, faster, or leaner than the default plan?
The idea
A 10x version of a project usually can’t be reached by working the same plan harder. It forces you to cut non-essential scope, automate or delegate work that doesn’t need a specific person’s attention, and rebuild the timeline around the new approach rather than the old one. The point isn’t that every project should literally 10x — it’s that asking the question surfaces waste and better options that incremental planning never surfaces.
When to use it
- Kicking off an ambitious or high-stakes project, before the plan is locked in.
- When a project is stuck making only incremental progress against its timeline or budget.
How to apply it
- Write down the default plan and its expected outcome.
- Ask what a 10x version of that outcome would require.
- List what would have to be cut, automated, or delegated to make that possible.
- Rebuild the schedule and resourcing around the new approach.
Watch out for
- Unrealistic scope if the exercise isn’t paired with a real capacity check.
- Using “10x” as a slogan rather than actually changing the plan.
Related models
- Critical path analysis — useful once the 10x plan needs sequencing.
- 10x Goal Setting — the same thinking applied to individual or organizational goals.
- Agile — an execution style that supports rapid replanning once scope changes.
Sources
General “10x thinking” as popularized by Dan Sullivan (“10x Is Easier Than 2x”) and Grant Cardone (“The 10X Rule”), applied here to project planning.