Ch3 02: Three Dimensions of Direction Quality: The Stress Test That Saves You#
A direction can pass two out of three tests and still kill your company. Nobody warns you about that part.
We celebrate directions that feel strong — obvious user need, elegant solution, large market. But “feels strong” and “is structurally sound” diverge more often than founders want to admit. The most dangerous directions aren’t the ones that fail every test — those are easy to discard. The dangerous ones pass almost every test, generating a “we’re so close” conviction that keeps teams pushing into territory that was never going to work.
This chapter hands you the three-dimensional stress test that separates survivable directions from attractive-looking dead ends.
The Three Dimensions#
Every viable direction must satisfy three conditions simultaneously. Not sequentially. Not approximately. Simultaneously.
| Dimension | Definition | Core Question |
|---|---|---|
| Rigidity | The demand is non-optional for the user | “Does the user have to solve this, or choose to solve this?” |
| Independence | The demand exists without preconditions | “Does this demand require other things to be true first?” |
| Directness | Your solution resolves the demand in one step | “Can the user go from problem to resolution without intermediate dependencies?” |
Think of these as a multiplication equation, not addition. Rigidity × Independence × Directness = Direction viability. If any factor is zero, the product is zero — regardless of how strong the other two are.
Dimension 1: Rigidity#
Rigidity measures whether the user’s need is a requirement or a preference.
Rigid demand: A logistics company must track shipments in real time or face contractual penalties. Not optional. Failure has measurable, immediate consequences.
Non-rigid demand: A consumer wants to organize digital photos more efficiently. Annoying but consequence-free. The user can — and usually does — tolerate it indefinitely.
The Rigidity Spectrum#
| Level | Description | Example | Startup Risk |
|---|---|---|---|
| Mandatory | Legal, regulatory, or contractual requirement | Tax filing, safety inspections | Low — demand guaranteed |
| Operational | Business cannot function without it | Payment processing, inventory management | Low-Medium — demand stable |
| Efficiency | Improves performance but isn’t required | Analytics dashboards, workflow optimization | Medium — must prove ROI |
| Preference | User wants it but doesn’t need it | Photo organization, habit tracking | High — must create demand |
Most consumer startups operate at the “Preference” level and compensate with volume. Most failed B2B startups operated at “Efficiency” and couldn’t prove ROI fast enough.
The False Rigidity Trap#
Some demands appear rigid but aren’t. Common pattern: the founder identifies a genuine operational bottleneck that’s only painful at scale. For the startup’s initial customers — typically smaller organizations — the bottleneck doesn’t exist yet.
An HR tech startup built automated onboarding for companies with 50+ hires per month. Rigid demand at that scale — absolutely. But companies with 50+ monthly hires represent less than 2% of the market. For the other 98%, manual onboarding worked fine. The rigidity was real but applied to a customer segment too narrow to sustain the business.
Diagnostic question: Is the rigidity universal across your target segment, or concentrated in a sub-segment that may be too small?
Dimension 2: Independence#
Independence measures whether demand stands on its own or depends on external conditions being true.
Independent demand: Businesses need to process payroll every two weeks. Regardless of market conditions, technology trends, or policy changes. No “if-then” required.
Dependent demand: “If autonomous vehicles reach Level 4 adoption, fleet management software will need real-time rerouting.” Real if the precondition materializes. But the precondition is outside your control, timeline, and possibly reality.
The Dependency Chain Test#
Map the assumptions your direction requires. Write each as an “if-then” statement.
| Dependency Type | Example | Risk Level |
|---|---|---|
| Zero dependencies | “Businesses must comply with tax law” | ✅ Independent |
| Market dependency | “If remote work remains prevalent…” | ⚠️ Conditional |
| Technology dependency | “When 5G coverage reaches 90%…” | ⚠️ Conditional |
| Policy dependency | “If regulation X is enacted…” | 🔴 Fragile |
| Behavioral dependency | “Once users adopt crypto wallets…” | 🔴 Fragile |
Each dependency is a load-bearing assumption. More dependencies = more failure points you don’t control.
Case: The Policy-Dependent Collapse#
A B2B SaaS company built compliance automation for a specific environmental reporting regulation. Excellent product. Rigid demand (regulatory requirement). Direct solution (one-click report generation). Two out of three dimensions: perfect.
Independence: zero. The entire model depended on one regulation remaining in force. When a new administration deprioritized enforcement, reporting requirements softened. Within eight months, renewal rates dropped from 92% to 41%. The product still worked. The regulation still technically existed. But enforcement uncertainty destroyed the demand’s rigidity retroactively.
The company didn’t fail because of execution. It failed because its direction had a single point of dependency it treated as permanent.
Dimension 3: Directness#
Directness measures the number of steps between the user’s problem and your solution’s value delivery.
Direct resolution: User has problem → uses your product → problem resolved. One step. No training, no integration, no behavior change.
Indirect resolution: User has problem → learns your platform → integrates with existing tools → changes team workflow → trains staff → begins seeing value. Six steps. Each step is a dropout point.
The Indirectness Tax#
Every intermediate step imposes a tax:
| Step Count | Conversion Impact | Time to Value | Churn Risk |
|---|---|---|---|
| 1 step | Baseline | Immediate | Low |
| 2–3 steps | 30–50% dropout | Days to weeks | Moderate |
| 4–5 steps | 60–80% dropout | Weeks to months | High |
| 6+ steps | 85%+ dropout | Months | Very high |
These aren’t theoretical — they’re patterns observed across dozens of enterprise software deployments. Each additional step doesn’t just reduce conversion; it compounds the reduction.
Case: The Integration Dependency#
A data analytics startup built a powerful visualization tool for e-commerce companies. Genuinely superior product. Rigid demand (data-driven decisions are operational necessities at scale). Strong independence (e-commerce isn’t going away).
Directness failed. To use the tool, a merchant needed to:
- Export data from their existing platform
- Clean and format data to match the tool’s schema
- Set up API connections for ongoing sync
- Learn the tool’s custom query language
- Build their first dashboard
Average time to first value: 23 days. By day 10, most trial users had stopped logging in. The product solved a real problem — after a three-week obstacle course most users never completed.
The fix wasn’t a better product. It was a direct Shopify integration that reduced the path from five steps to one: install the app, see your dashboard. Conversion tripled the quarter after the integration shipped.
The Cross-Dimensional Stress Test#
Real diagnostic power comes from testing all three simultaneously. Most dangerous directions pass two and fail the third — creating a “nearly there” illusion that consumes resources.
The Two-Pass, One-Fail Matrix#
| Passes | Fails | What It Looks Like | What Actually Happens |
|---|---|---|---|
| Rigidity + Independence | Directness | “Huge stable market, but adoption is painfully slow” | Death by churn — users need it but can’t reach the value |
| Rigidity + Directness | Independence | “Users love it and onboard instantly, but demand depends on one external factor” | Death by context shift — one policy change wipes out demand |
| Independence + Directness | Rigidity | “Easy to use, always relevant, but users can live without it” | Death by indifference — low willingness to pay, high competition from free alternatives |
Each failure mode produces different symptoms. Founders who don’t test all three often misdiagnose the cause of death — blaming sales when the problem is directness, or blaming timing when the problem is rigidity.
Applying the Framework: A Worked Example#
Consider a startup building AI-powered contract review for mid-size law firms.
Rigidity test: Law firms must review contracts. Errors carry legal liability. Associates spend 60% of billable hours on review tasks that could be partially automated. Rigidity score: high — operational, bordering on mandatory.
Independence test: Contract review demand exists regardless of market conditions, technology trends, or policy changes. Law firms have reviewed contracts for centuries. No “if-then” dependencies. Independence score: high.
Directness test: To use the AI tool, a firm needs to: upload documents (easy), review AI suggestions (moderate learning curve), integrate with existing document management (significant IT involvement), get partner approval for AI-assisted review (organizational change). Directness score: moderate — three steps, one outside the product’s control.
Diagnosis: Two strong, one moderate. The direction isn’t dead, but the directness gap is the primary risk. Strategic response: reduce the partner buy-in barrier by starting with low-stakes contracts (NDAs, vendor agreements) where AI augments rather than replaces human review. Reduce integration by offering a standalone upload interface before pursuing deep integration.
This is what dimensional analysis does — it doesn’t just tell you good or bad. It tells you where the specific weakness is and what to do about it.
Common Pitfalls#
Pitfall 1: Scoring generously because you want it to work. If you’re debating whether demand is “operational” or “preference,” it’s probably preference. Rigid demand doesn’t require internal debate — it’s obvious to the user, not just to you.
Pitfall 2: Treating future directness as current directness. “Once we build the integration, it’ll be one-click.” That’s a roadmap, not current state. Score directness on what exists today. Users churn on today’s experience.
Pitfall 3: Confusing your passion for market rigidity. You care deeply about this problem. Admirable — and irrelevant to dimensional analysis. Rigidity is measured at the user’s end, not yours.
Direction Pressure Test #2#
Score your direction. Be ruthless.
| Dimension | Score (0–2) | Evidence | Weakest Link? |
|---|---|---|---|
| Rigidity | What consequence does the user face if this stays unsolved? | ||
| Independence | List every “if-then” assumption your demand requires. How many? | ||
| Directness | Count the steps from “user encounters problem” to “user experiences value.” |
Which dimension are you least confident about?
That’s the one most likely to fracture under real-world pressure. It’s not the dimension to ignore — it’s the one to obsess over. Because in a multiplication equation, the smallest factor determines the product.
A direction that scores 2 × 2 × 0 = zero. A direction that scores 1 × 1 × 1 = one — modest, but alive. The math doesn’t care about your pitch deck.