The 8-Question Positioning-vs-Operations Diagnostic

When an operational fix keeps not holding, the question is whether the cause is on the operational layer at all. Here are eight yes-or-no questions that answer it in fifteen minutes, and how to read the result.

The short answer

Run the eight questions below and count your yeses. Zero to two yeses means the symptom is most likely on the operational layer, and the workflow fixes you have been running are the right work. Three or more yeses means the cause most likely sits a layer up, in pricing, commercial design, or who the firm is selling to, and another operational pass will produce diminishing returns. The number tells you which layer the symptom is on. The identity of the yeses tells you which layer-up lever to start with. The whole thing takes about fifteen minutes and needs no investigation you cannot do from your own desk.

When to run this

You have decided the operational symptom is recurring. You have sat with the cost of another round of fixes that may not hold. The honest read is that you are somewhere between "let us tighten the workflow one more time" and "let us reopen a question we have not reopened in a while."

Pause for fifteen minutes and run the eight questions. The output is not a score band. It is a binary read on which layer the symptom is most likely sitting on, and that read changes the next move from "another operational pass" to "the layer-up question we have been deferring," or from "we should reopen pricing" to "no, the operational work is genuinely the right work."

Both outputs are useful. The expensive thing is not being on the operational layer. It is being on the wrong layer for too long. The instinct, when a symptom recurs, is to do the next SOP, the next hand-off template, the next capacity model. Each step is a reasonable response to the pressure. But operational work has fast feedback, the vendors around the firm sell operational work, and the layer-up question asks the founder to revisit a strategic decision they have already answered once. So the operational lane stays attractive past its useful life. This diagnostic interrupts that by asking the layer question directly, before the next round of work begins.

The 8 questions

Each question maps to a different signal. Answer each yes or no from where you sit today.

1. The recurrence test

Has the symptom recurred after at least one full round of operational fixes?

Workflow tightened, hand-off documented, capacity adjusted, and the symptom returned within two quarters. If the operational fix worked and held, the symptom was operational. If it returned, the operational layer probably is not the cause. Walk the date stamps of the last three fixes against the dates the symptom reappeared. If recurrence is the pattern, this lands as a yes.

2. The peer-language test

When you describe the symptom to a founder you respect, do they ask a workflow question back, or a pricing-and-positioning one?

"How are you priced?" "Who exactly are you selling to?" "What is in the proposal template?" When peers reach for commercial questions before they reach for workflow questions, that is outside signal that the symptom reads as a layer-up problem. Describe it to two peer founders this week. Do not lead. Listen for which questions they reach for first. Both reaching for layer-up questions is two for two.

3. The concentration test

Is the symptom concentrated in a specific client segment, service line, or engagement size?

Capacity stretch on every engagement is an ops question. Capacity stretch on the engagements under $40k while the larger ones run clean is a pricing or scope question. Hand-off failure on every project is workflow. Hand-off failure only on the newer clients, clean on the legacy ones, is client-fit drift. Split the symptom by segment, service line, and engagement size. If it concentrates anywhere, that concentration is the clue.

4. The pricing review test

Has your pricing been reviewed in the last 18 months against your actual delivery cost?

Not "have you raised rates." Reviewed against fully loaded delivery cost, including senior consultant time, founder time, and the rework loops. If the answer is no, capacity stretch may be margin compression wearing an ops costume, and adding workflow leverage to an under-priced engagement still produces an under-priced engagement that takes a little less time. Name the date of the last pricing-vs-cost review. More than 18 months ago lands as a yes.

5. The client-fit test

Has your ideal-client definition been re-articulated in the last 18 months against the clients you actually want more of?

Firms drift. The clients who close fastest are not always the clients who deliver cleanest, and the marketing surface gradually attracts a slightly different buyer than the firm is built to serve. If the ideal-client doc is older than 18 months, hand-off and scope friction may be the firm trying to deliver a service that has quietly become a different service. Name the date of the last re-articulation. More than 18 months ago, or no doc at all, lands as a yes.

6. The proposal-template test

Is the proposal template promising scope the engagement is not sized to deliver?

Walk one closed proposal from the last 90 days against the engagement that followed. Did the proposal commit to deliverables, timelines, or revisions the engagement could not comfortably hit? If yes, the delivery slip is a commercial-design problem, because the proposal is the product specification, not an operational one. Pull one proposal, walk it against the work that followed. A meaningful gap lands as a yes.

7. The founder-in-the-loop test

Are the sign-off and revision loops the symptom, or the way clients use the firm?

A founder in every quality review may be a workflow problem. A founder in every quality review because the senior team cannot credibly defend the work to clients without you is a positioning problem. The cure for the second is not a quality-review SOP. It is a re-priced engagement where founder time is a billed line, or a repositioning that builds the senior team's authority. Ask the senior team whether clients accept their work as final without you present. A consistent no means this is the way clients use the firm, not a workflow gap, and it lands as a yes.

8. The thought-experiment test

If you reset the symptom by changing the engagement, re-priced, re-scoped, or aimed at a different client, would the operational pressure ease?

Not an action. A thought experiment. If the same workflow ran against a 1.4x-priced engagement with a tighter scope and a sharper-fit client, would the capacity stretch, the hand-off failure, or the delivery slip materially improve? If yes, the symptom depends on the engagement, which depends on pricing, scope, or commercial design. Sit with the question for two minutes. Most founders know the answer the moment they ask it. The discipline is asking it.

How to read the result

Count your yeses across the eight. This is not a score band. It is a binary call.

0 to 2 yeses: the symptom is most likely on the operational layer. The fixes you have been running are probably the right work. The next move is the sequencing tree from week 22, or the hire-readiness gate from week 20 if a senior hire is in the picture. The diagnostic has done its job by ruling itself out, and that is a useful answer in its own right. Continue with the operational work, with the confidence that the layer is correctly identified.

3 or more yeses: the symptom is most likely a layer up. The pattern suggests the operational fixes are treating downstream effects of a pricing, commercial-design, or positioning decision the firm has not reopened in a while. Continuing to apply operational fixes will produce diminishing returns and carry meaningful opportunity cost over the next two to four quarters, because the firm is spending operational energy against a layer that is not the cause.

At three or more yeses, the next move is not another workflow pass. It is reopening one of the three layer-up questions, in the order that runs cheapest to most expensive: pricing first, because it is cheapest to test and gives the fastest signal; commercial design second, the proposal-template walk; positioning third, the deepest and slowest, but the right move when the first two confirm the misalignment is upstream of both.

The count tells you which layer the symptom is on. The identity of the yeses tells you where to start. A yes on Q4 and Q3 points at pricing first. A yes on Q5 and Q3 points at positioning first. A yes on Q6 and Q7 points at commercial design first.

Why eight questions

Each question draws on a different signal source. Q1 is the firm's own history. Q2 is outside signal from peers. Q3 is internal segmentation. Q4 is pricing posture. Q5 is client-fit posture. Q6 is commercial-design posture. Q7 is the founder's relationship to client trust. Q8 is the thought experiment that integrates the rest.

Eight separates the signals cleanly. Fewer and the layers blur. More and the diagnostic stops being something you can run in fifteen minutes between two meetings. The point is not the count. The point is that "the operational fix is not holding" is really a small portfolio of layer questions, and the firm's next move depends on which signals are landing.

What to do this week

Run the eight questions tonight, on the symptom you named at the start of the week. Write the yeses down, do not just tally them in your head, because the identity of each yes is the part that tells you where to start.

If you land at 0 to 2, treat that as a confirmation worth having and keep running the operational work. If you land at 3 or more, block 90 minutes this week to rough out the cheapest layer-up check the result points you toward, almost always a pricing-vs-cost walk on your three most painful recent engagements. Thursday's post walks through exactly what that produces and how to do a rough version yourself.

The diagnostic exists because the most expensive operational decision in a founder-led firm is not a wrong fix. It is a right fix on the wrong layer, applied repeatedly across quarters, against a cause that was never on that layer.

Continue the series

This is part 3 of a 5-part series on What's Hiding Behind Your Operational Problem. The full arc:

• Monday: When the Operational Fixes Don't Move the Needle
• Tuesday: What It Costs to Keep Diagnosing the Wrong Layer
• Wednesday: The 8-Question Positioning-vs-Operations Diagnostic (this post)
• Thursday: What a Positioning Audit Actually Surfaces
• Friday: Why "Ops Is Broken" Is the Most Expensive Misdiagnosis in Founder-Led Firms

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.