The Core Idea
Most business problems are easier to solve once they are mapped at the right level.
Sometimes the problem is micro: a project keeps drifting, a handoff fails, or a recurring task creates rework.
Sometimes the problem is middle: a team lacks ownership, meetings are unclear, or a department needs better rhythm.
Sometimes the problem is macro: the business has outgrown founder memory, informal decision-making, and scattered operating structure.
PROGRESS works across all three levels because the same questions apply: what is happening now, what is blocking movement, what are we trying to accomplish, what should this work give back, what support is missing, where is the work fragile, why does this matter, and what should happen next?
Why This Happens
Founder-led companies often try to fix problems at the wrong level.
A founder sees a missed deadline and assumes the project needs better follow-up. The real issue may be unclear ownership.
A founder sees a team member hesitate and assumes they lack initiative. The real issue may be decision rights.
A founder sees messy delivery and assumes the company needs SOPs. The real issue may be invisible standards and weak review rhythm. PROGRESS slows the diagnosis down enough to see the pattern before choosing the fix.
The PROGRESS Lens
The same eight prompts can zoom in or out.
What is actually happening right now?
What is blocking progress?
What is this work supposed to accomplish?
What useful return should this create for the founder, team, client, or business?
What people, tools, context, or support are missing?
Where is the work fragile or dependent on one person?
Why does this matter strategically or personally?
What should happen next?
Mini Case
A slipping workflow may need a smaller, more accurate fix.
A founder notices that a client delivery workflow keeps slipping. The first instinct is to create more SOPs.
Using PROGRESS, the team maps the issue differently. Present: work is moving, but client context is scattered. Roadblocks: the handoff from sales to delivery is unclear. Resources: the delivery team lacks a reliable source of truth. Exposures: client promises live in messages and founder memory.
The next step becomes a simple handoff map, decision rules, and weekly review rhythm before writing a full SOP library.
What To Do Next
Use the framework to map before you move.
Choose the level you are mapping.
Start with a project, workflow, team, department, or the whole company.
Write the present reality.
Name what is happening without trying to solve it yet.
Separate symptoms from roadblocks.
Look for the constraint underneath the visible frustration.
Define what the work should accomplish.
Clarify the outcome before choosing the operating fix.
Identify resources and exposures.
Find what support is missing and where the work is fragile.
Choose the next step.
Select the action that creates the most movement with the least unnecessary complexity.
Common Mistakes
The framework works best when it stays practical.
Using PROGRESS only at the company level
It can also diagnose a single project, handoff, meeting rhythm, or workflow.
Jumping to Steps too quickly
The first action is often wrong if Present and Roadblocks are unclear.
Treating Roadblocks as complaints
Roadblocks are constraints that need to be named accurately so the fix can be sequenced.
Ignoring Exposures
Hidden risk often explains why the business still depends on the founder.