Business Constraints
Module 02 · Business Constraints
Businesses rarely need more work. They need the right constraint removed.
Overview
Businesses do not stop growing because every part of the business fails at the same time.
Growth usually slows because one or two constraints begin limiting progress.
These constraints change as the business evolves.
Some belong to operations.
Some belong to finance.
Some belong to leadership.
Rundown exists to identify and reduce a specific category of constraints related to communication, credibility and digital presence.
Understanding this distinction is essential.
It defines both our value and our boundaries.
Core Principle
Every business has a limiting constraint. Sustainable growth depends on identifying and reducing the right one.
Businesses often describe symptoms.
Our responsibility is to identify the underlying constraint.
Business Reality
The problem a client presents is rarely the problem they actually have.
Examples include:
| Client Says | Possible Underlying Constraint |
|---|---|
| "We need a new website." | The current website no longer reflects the business. |
| "We need a rebrand." | The market perception no longer matches the company's position. |
| "We need better brochures." | Sales lacks credible communication assets. |
| "Our competitors look better than us." | The business has fallen behind market expectations. |
| "We need more leads." | The issue may be credibility rather than traffic. |
The requested deliverable should always be treated as a starting point—not the diagnosis.
The Constraint Categories
Not every constraint belongs to Rundown.
Our role is clearly defined.
Constraints Rundown Owns
- Communication clarity
- Brand positioning
- Digital credibility
- Website effectiveness
- Brand consistency
- Presentation quality
- Sales enablement assets
- Visual communication
These are our primary area of expertise.
Constraints Rundown Supports
- Lead generation
- Marketing performance
- Customer experience
- Sales conversion
We may influence these outcomes, but we do not claim ownership.
Constraints Rundown Does Not Own
- Product quality
- Operations
- Finance
- HR
- Manufacturing
- Legal
- Product-market fit
- Leadership
If these are the primary bottlenecks, another specialist should lead the engagement.
Rundown Standard
RD-002 · Identify the constraint before proposing the capability.
Every recommendation must be linked to a clearly identified business constraint.
Deliverables are never recommended in isolation.
Instead, proposals should follow this sequence:
Business Context
↓
Constraint
↓
Recommended Capability
↓
Deliverables
In Practice
Before preparing a proposal, confirm:
- What constraint is limiting progress?
- Is that constraint within Rundown's expertise?
- Can Rundown materially reduce it?
- Can success be measured?
If any answer is "No", reconsider the engagement.
Operator Notes
A client may request a website.
That does not automatically mean the website is the problem.
Continue asking questions until the underlying constraint becomes clear.
Good discovery replaces assumptions with evidence.
The Rundown Test
Before recommending any solution, confirm:
If these conditions are not met, continue discovery before presenting recommendations.
Related Modules
Previous
- Module 01 · Business Evolution
Next
- Module 03 · Buyer Psychology
Supports
- Qualification
- Discovery
- Product Strategy
- Proposal Structure
- Pricing