Working rule

The “timing” question is really three different diagnoses in disguise — too early (the market is not ready), too late (the market is saturated by better-known alternatives) or just confusing (customers cannot see where the product fits in their existing mental categories, so they read a positioning problem as a timing problem). Each diagnosis has a different fix — a pivot for too-early, a differentiation move for too-late, a repositioning for just-confusing — and running the wrong fix against the right symptom wastes the runway that a correct diagnosis would have preserved. Before pivoting or shutting down on a “timing” answer, run the three-diagnosis framework in writing with cohort evidence for the chosen diagnosis.

Why “timing” is really three different questions

When a founder says “our timing might be off”, they are usually collapsing three different questions into one. Too early means the market is not ready — early adopters may love the product, but the early majority is not paying attention and the sales cycles from mainstream buyers are unpredictable. Too late means the market has saturated around alternatives — customers already have a solution they know, and switching costs plus incumbent trust make the challenger’s growth expensive. Just confusing means the product is positioned in a way customers cannot decode — they cannot slot it into their existing mental categories, so their reaction reads as market timing rather than as their own confusion. The three diagnoses share the same surface symptom (slow adoption, mixed feedback, unclear traction) but require different fixes.

Geoffrey A. Moore’s Crossing the Chasm frames the too-early diagnosis in adoption-curve terms — the gap between enthusiastic early adopters and the pragmatic early majority is where startups mistake early-adopter praise for broader market signal. April Dunford’s Obviously Awesome reframes many “timing” or “market” problems as positioning problems: customers cannot buy what they cannot understand, and lack of understanding is often diagnosed as market immaturity when it is actually the founder’s positioning failing.

The three-diagnosis framework does not tell the founder which diagnosis applies; it insists that the founder pick one deliberately, produce evidence for the pick, and act on that diagnosis rather than the abstract debate. Steve Blank’s Harvard Business Review 2013 essay on the lean start-up argues that timing questions are hypothesis-tests — testable with cohort experiments rather than resolved through introspection.

The three-diagnosis framework

The framework below is an editorial synthesis of Moore’s chasm work, Dunford’s positioning discipline and the Startup Genome Global Startup Ecosystem Report ecosystem view. Every diagnosis has a signature signal, a required evidence type and a specific fix that is different from the other two.

Too early — market not ready

The too-early diagnosis fits when early adopters buy enthusiastically but their behaviour does not generalise — the pragmatic majority either does not engage or asks questions about certifications, references and integrations the product does not yet have. The signature signal is asymmetric feedback: five customers love it, twenty pragmatic buyers ask about compliance and enterprise-readiness the product cannot deliver. Moore’s chasm framing is exact for this diagnosis: the startup is on the wrong side of the chasm and treating early-adopter behaviour as market signal. The fix is not a pivot; it is either a bowling-alley strategy (win a specific narrow segment completely before crossing) or waiting for the market to mature with a smaller footprint. Pivoting away from a working early-adopter segment usually destroys the one thing that was working.

Too late — market saturated by better-known alternatives

The too-late diagnosis fits when the market clearly exists (buyers know the category, know what they want, are already spending money) but the startup’s product is meeting resistance framed as “we already have that”. The signature signal is objection consistency — buyers name the same three incumbents in every conversation, and even the ones who like the product ask “why should we switch from X”. The fix is a differentiation move — a specific wedge segment where the incumbents underperform, a positioning that makes the switch look small rather than large, or a business-model shift that changes the buying calculation. Just building a better version of the incumbent product is expensive and rarely wins the switching decision.

Just confusing — positioning problem masquerading as timing

The just-confusing diagnosis fits when feedback varies wildly by conversation — some customers “get it” immediately, others cannot place the product at all, and the same demo produces enthusiasm from one buyer and blank confusion from the next. The signature signal is inconsistency: reactions differ by buyer without a pattern that maps to segment. Dunford’s Obviously Awesome is exact for this diagnosis — customers cannot slot the product into their existing mental categories, so they read the confusion as timing or market fit when it is actually the positioning. The fix is a repositioning exercise: name the alternative buyers use today, name what makes the product genuinely different from that alternative, name the buyer for whom that difference matters most. The product does not change; the frame around it does.

DiagnosisSignature signalFix that worksFix that wastes runway
Too early — market not readyAsymmetric feedback — early adopters love it, pragmatists ask for capabilities you don’t haveBowling-alley strategy — win narrow segment completely before crossingPivot away from working early-adopter segment
Too late — market saturatedObjection consistency — same three incumbents named in every conversationDifferentiation move — wedge where incumbents underperform + small-switch positioningBuild a better version of the incumbent product
Just confusing — positioning problemFeedback varies wildly by conversation without segment patternRepositioning — name alternative, name difference, name buyer who caresRebuild product or pivot before addressing positioning

Visual slot: three-diagnosis flowchart — signature signal → fix that works → fix that wastes runway. Replace this block with the final visual.

Crossing the Chasm applied to the timing question

Moore’s chasm is a useful lens for the too-early diagnosis in particular. Innovators and early adopters are motivated by newness and are willing to endure incompleteness; the early majority is motivated by references and complete solutions and will not adopt on the same signals. When a startup gets warm reception from ten early adopters and cold or absent reception from the next fifty prospects, the temptation is to conclude the market is wrong. The chasm framing suggests the market is right — the second group is a different market with different requirements, and crossing requires either winning a beachhead in that group’s world or accepting that the current product is an early-adopter product for now.

The bowling-alley strategy Moore proposes — win one specific pragmatic-majority segment completely, then use that credibility to attack adjacent segments — is a middle path between “wait for the market” and “pivot away from what’s working”. It requires narrowing scope temporarily to expand credibility, which is often the opposite of what a founder feels the round demands.

The born-global academic view

Oviatt and McDougall’s 1994 Journal of International Business Studies paper established that some ventures are born global — they operate internationally from inception rather than expanding sequentially from a home market. Knight and Cavusgil’s 2004 Journal of International Business Studies paper extended the theory to show that innovation and organisational capabilities determine which firms can operate globally at inception. The timing implication is direct: timing decisions are bounded by the team’s capabilities, not only by external market conditions. A founding team without global-from-inception capability that treats the timing question as purely about the market will diagnose “too early” when the honest diagnosis is “capability-limited”.

Sarasvathy’s 2001 Academy of Management Review effectuation paper reinforces the point: founders should start from means they control, and timing decisions that require capabilities the team does not yet possess are structurally suspect. Shepherd & Gruber’s 2020 Entrepreneurship Theory and Practice consolidation treats each timing diagnosis as a hypothesis — the founder’s job is to test which of the three diagnoses fits the current evidence rather than resolve the timing debate philosophically.

Positioning as the confusion-fix

Dunford’s Obviously Awesome is the clearest operator playbook for the just-confusing diagnosis. Positioning, in Dunford’s framing, has five components: competitive alternatives (what customers use today), unique attributes (what your product has that others do not), value the attributes enable, characteristics of the customer who values that most, and the market category that frames the product. When any of the five is missing or wrong, customers cannot decode the product — and their inability to decode reads to the founder as “market timing off”.

The repositioning fix is a written exercise, not a design or messaging exercise. Working through the five components as prose statements — “customers today use X; our product uniquely has Y; that unlocks value Z; the customer who cares about Z the most looks like W; the market category that frames this is V” — usually surfaces the positioning gap that was being read as timing. If the exercise produces a coherent five-part statement and customers still cannot decode the product, the diagnosis was not just-confusing after all.

Visual slot: Dunford five-component positioning template — competitive alternatives / unique attributes / value / customer / market category — with one-line examples per box. Replace this block with the final visual.

Startup Genome ecosystem context

Startup Genome’s Global Startup Ecosystem Report tracks 350+ ecosystems over 14 years and documents that startup ecosystems differ materially by region — meaning the timing signal a founder reads in one ecosystem may not transfer to another. A “too early” diagnosis in one ecosystem might be “just right” in another where the buyer segment is further along the adoption curve. Startup Genome’s reports show significant concentration of value in specific ecosystems, particularly in the AI era.

The corollary for the timing diagnosis is that ecosystem-specific evidence beats generic market signal. A founder in Istanbul reading Silicon Valley articles about market timing is reading signal from a different ecosystem with different buyer expectations, different capital availability and different competitive density. Startup Genome data is a reminder that timing is ecosystem-conditional; the PitchBook-NVCA Venture Monitor similarly provides US-specific pacing context that should not be transferred to other ecosystems without adjustment.

Sixty-day timing-audit scenario

Assume a hypothetical early-stage startup receiving mixed customer feedback — some enthusiastic “we love it but not yet”, some dismissive “we already have that”, and some baffled “we don’t get what this does” — with the founder unsure whether the answer is to pivot, wait or reposition. The scenario is illustrative — no real company or founder is named, no specific market data is invented, and every output expectation is expressed as a diagnosis type rather than a target number.

Days 1–14 — feedback triage. The founder categorises the last thirty customer conversations by feedback pattern — enthusiastic-but-not-yet, already-have-that, and don’t-get-it. The distribution is the first evidence: if 70% are enthusiastic-but-not-yet, the diagnosis leans too-early; if 70% are already-have-that, it leans too-late; if the distribution is mixed with no dominant pattern, it leans just-confusing. Segment characteristics for each pattern get noted — who says what, from which industry, at which stage.

Days 15–35 — hypothesis test per diagnosis. For each candidate diagnosis, the founder designs a short experiment — bowling-alley test for too-early (pick a narrow segment, sell only into it for four weeks), differentiation-message test for too-late (rewrite the sales conversation around the switch objection), positioning rewrite for just-confusing (write the five-component Dunford statement and test with three fresh buyers). The output at day thirty-five is a diagnosis with cohort evidence, not a founder-opinion.

Days 36–60 — commit to the fix. The confirmed diagnosis drives the fix. Too-early triggers a narrower go-to-market — smaller footprint, longer horizon, defensible early-adopter revenue. Too-late triggers a differentiation move — new positioning around the wedge segment where incumbents underperform. Just-confusing triggers a repositioning — new sales conversation, new deck, new website, no product change. The fix is committed to for at least ninety days before revisiting the diagnosis.

The point of the sequence is not a promised traction outcome. The output at day sixty is a diagnosis with cohort evidence and a committed fix — not a decision to pivot or shut down based on ambiguous “timing” feedback.

Visual slot: 60-day timing-audit sequence — three phases with entry criteria, exit artifact and diagnosis-to-fix mapping. Replace this block with the final visual.

PhaseEntry criteriaExit artifactOwner
Days 1–14: feedback triageLast thirty customer conversations recordedFeedback distribution by pattern + segment characteristicsFounder + head of growth or product
Days 15–35: hypothesis test per diagnosisFeedback distribution in handDiagnosis with cohort evidence — not founder opinionFounder + advisor + small experiment budget
Days 36–60: commit to fixConfirmed diagnosisCommitted fix + 90-day plan against the diagnosisFounder + team

When to pivot versus when to hold

Pivot triggers versus confusion signals

A pivot decision is warranted when the three-diagnosis framework produces a diagnosis (too-early, too-late, just-confusing) and the fix for that diagnosis fails after ninety days with cohort evidence — not before, and not on abstract timing debate. A too-early diagnosis whose bowling-alley test fails triggers a segment pivot; a too-late diagnosis whose differentiation move fails triggers a category pivot; a just-confusing diagnosis whose repositioning fails suggests the product actually lacks a value the market recognises, which triggers a product pivot. Teece’s 2010 Long Range Planning paper on business models reinforces that pivots should reference the model design, not chase surface symptoms.

A confusion signal — mixed feedback, unclear conviction, board pressure — is not a pivot trigger. Founders who pivot on confusion signals usually pivot from a working segment to an unknown one and lose the diagnosis window entirely. The three-diagnosis framework’s discipline is precisely to convert confusion into diagnosis before pivoting decides anything.

Five timing-diagnosis mistakes to skip

The five mistakes below appear repeatedly in early-stage startups whose founders skipped the three-diagnosis framework and acted on “timing” as a single question. Each mistake has a specific rewrite.

  • Treating chasm-side feedback as market rejection. Early-adopter enthusiasm followed by early-majority silence is the chasm, not market failure. Rewrite: apply the too-early diagnosis and design a bowling-alley test before considering pivot.
  • Treating positioning confusion as timing problem. Wildly variable feedback usually signals positioning failure. Rewrite: run Dunford’s five-component positioning exercise before diagnosing timing at all.
  • Transferring ecosystem signals without adjustment. Silicon Valley timing signals do not transfer to non-SV ecosystems. Rewrite: use ecosystem-specific evidence (Startup Genome for ecosystem context, local buyer data for product-market signal).
  • Chasing “first-mover” without capability match. Being first is only advantageous when the team has the capabilities to sustain the lead. Rewrite: check Knight & Cavusgil’s capability-match against born-global claims before betting on first-mover timing.
  • Pivoting on three-customer feedback without cohort evidence. Three enthusiastic customers or three dismissive ones is not a diagnosis; it is anecdote. Rewrite: require thirty conversations minimum before running the three-diagnosis framework, then design a bounded experiment.

Sources and evidence

Every source below was verified during the current production run and is used in the visible body of the article.

Diagnose the timing question before you act on it

Before pivoting, shutting down or spending the next round of runway on a “timing” answer, run the three-diagnosis framework in writing — feedback triage over the last thirty customer conversations, hypothesis test for the candidate diagnosis (bowling-alley for too-early, differentiation-message for too-late, five-component repositioning for just-confusing), then commit to the diagnosis-specific fix for at least ninety days before revisiting. A confirmed diagnosis with cohort evidence outperforms a founder-opinion pivot on every horizon that matters.

Circulate the diagnosis document — feedback distribution, candidate diagnosis, evidence, committed fix, ninety-day horizon — as the artifact the team, board and advisors all reference. A pivot after a confirmed diagnosis fails is a coherent decision; a pivot on ambiguous timing feedback is throwing the working parts of the business away with the confusing parts. Ecosystem-specific signals (Startup Genome for the region, cohort evidence for the buyer) beat aspirational transfer of another market’s timing signals.

Two rounds of this discipline separates founders who navigate timing questions coherently from founders who mis-diagnose them repeatedly and burn runway on the wrong fixes. Diagnose the timing question before you act on it — the diagnosis takes sixty days, the fix takes ninety, and the wrong action taken quickly costs more runway than the right action taken deliberately.

Visual slot: common-timing-mistakes dashboard — mistake, failing diagnosis, safer rewrite, signal to watch. Replace this block with the final visual.

Ready to run the three-diagnosis framework against your current timing question before the next investor conversation?

A marketing audit engagement runs the three-diagnosis framework against your last thirty customer conversations, designs the hypothesis-test experiment per candidate diagnosis with your team, and returns a written diagnosis document you can use to commit to a fix or defend a pivot decision. No timing predictions, no market-size guarantee, no pivot recommendation — a diagnosis brief that separates the working parts from the confusing parts.

Skip the three-diagnosis framework and the pivot decision usually gets made on ambiguous feedback rather than on cohort evidence.

A timing-diagnosis engagement scores your feedback against the three diagnoses, designs the per-diagnosis hypothesis test and hands back a diagnosis document your team can use to commit to a fix. Timing predictions: none. Market-size guarantee: none. Pivot recommendation: none.

FAQ

How do I know whether my feedback is chasm behaviour or genuine market rejection?

Chasm behaviour looks like enthusiastic early adopters followed by pragmatic-majority silence or specific capability questions (compliance, references, enterprise-readiness) the product does not yet meet. Genuine market rejection looks like consistent objections across all buyer types — “we don’t need this at all”. Moore’s Crossing the Chasm reads the first as a chasm crossing challenge, not a rejection; the fix is bowling-alley, not pivot.

How is “just confusing” different from “too early”?

Too early has a segment pattern — early adopters yes, pragmatic majority not yet. Just confusing has no segment pattern — the same demo produces enthusiasm from one buyer and blank confusion from the next of the same type. If you can predict who will get it and who will not based on segment, you have a chasm; if you cannot predict at all, you have a positioning problem.

What if my “too late” diagnosis is actually correct — should I shut down?

Not necessarily. Too-late markets are still winnable through differentiation moves — a wedge segment where the incumbents underperform, a positioning that makes the switch look small, a business-model shift that changes the buying calculation. Shutting down without running the differentiation experiment leaves potential value on the table. Only shut down when the differentiation experiment fails after ninety days with cohort evidence.

How much customer conversation data do I need before running the framework?

Roughly thirty conversations minimum, distributed across buyer types you actually want to sell into. Three enthusiastic customers or three dismissive ones is anecdote, not diagnosis. Thirty gives enough distribution to see whether the feedback has a segment pattern (too early), objection consistency (too late) or wild variance (just confusing).

Does born-global timing apply to my regional startup?

Not necessarily as-is. Oviatt & McDougall 1994 and Knight & Cavusgil 2004 established that some ventures are born global because their team has capabilities to operate internationally from inception. If your team lacks those capabilities, treating the timing question as “we should launch globally” invites a capability-mismatch that reads as timing failure. Test capability match honestly before betting the timing on international expansion.

Where does this article stop and market research begin?

This article is educational context on the operator decision behind timing diagnoses — the three-diagnosis framework, the evidence patterns per diagnosis, and the fix that fits each. Specific market sizing, region-specific competitive analysis, and regulated-industry timing considerations require dedicated market research from a qualified firm and, for regulated industries, jurisdiction-specific legal and compliance advice. Use the operator brief to structure the diagnosis question, then extend it with rigorous market research where the diagnosis requires quantification.