The Moore Memorandum — Briefing 001

Moore briefing 001

0:00

/662.659184

1×

Recognition Without Procedure

Turning Financial Truth into Executable Operations

A recurring enterprise failure mode is straightforward: senior teams can name the symptom ("we need more revenue", "we need more customers", "we need higher retention"), yet cannot specify the procedure that makes the number true.

This briefing offers a disciplined walk-back--from financial statements to unit economics, from funnel arithmetic to frontline reality, from constraints to cadence--so that "we need more" becomes an executable plan.

Executive Summary

• Recognition is not a procedure. Financial statements surface the problem with speed and clarity; they do not specify next week's actions.
• The gap is predictable. Competent teams systematically underestimate coordination, time, and edge cases (planning fallacy) and over-trust their internal narrative (the inside view).
• The remedy is procedural. A walk-back method converts a financial gap into (i) quantities, (ii) conversion requirements, (iii) lead indicators, and (iv) on-the-floor constraints.
• The output is not a deck. The desired output is (1) an arithmetic chain the organization agrees to, and (2) a short list of binding constraints--each with an owner and a cadence.

1) The Pattern: Recognition Without Procedure

A board can read an income statement and see the truth in a minute. It cannot--by itself--tell you what to do on Monday.

This is how organizations drift into an odd equilibrium:

Everyone can say the correct sentence: "We need more revneue."

Very few can answer the next question with operational precision:

Exactly how many conversions, at what price, through which channels, at what acquisition cost, with what retention, by what date--and what must change in the customer experience to make that true?

When an organization confuses diagnosis with procedure, it produces rhetoric in place of execution.

2) Why this Happens (Without Armchair Psychology)

A) Planning Fallacy: Systematic Underestimation

Teams underestimate time, coordination, and complexity because the plan is written as a clean narrative rather than a decomposed procedure.

B) Inside View: The Story Feels Complete Before it is Complete

Teams default to their internal account of how the initiative will unfold, instead of running a base-rate check against comparable efforts (the outside view).

C) Unpacking Changes Judgements

When you require a plan to be stated in steps (not slogans), estimates move--because previously implicit work becomes visible, countable, and disputable.

D) Intentions do not Execute; Triggers Execute

Plans fail when they remain at the level of intention ("we should improve onboarding"). Execution improves when commitments become conditional procedures ("if X occurs, we do Y").

3) The Walk-Back Method

Treat this as an operating procedure, not a thought exercise.

Step 0 – State the Target in One Sentence, with Constraints

By DATE, we need +$X in incremental contribution margin (Or +Y customers/ +Z renewals) subject to constraints A/B/C.

Constraints are not decoration. Capacity, regulation, sales cycle length, staffing, inventory, and brand risk are frequently the true governing variables. If you do not state them, the plan quietly assumes them away.

Step 1 – Translate the Financial Gap into Unit Economics

If your target is incremental margin dollars, you need a unit-level margin figure (per customer, per member, per account, per renewal) over the relevant horizon.

Let:

• ΔCM = required incremental contribution margin (or gross margin dollars, if that is your operating convention)
• CM = contribution margin per customer/member over the same period

Then:

Net new customers required ≈ ΔCM / CM

If you do not know CM, your first action is not "run campaigns." Your first action is measurement: compute unit economics.

Step 2 – Convert Unit Economics into Funnel Arithmetic

Choose the dominant path you actually believe will carry the period. Do not average multiple incompatible funnels.

Example structure:

Exposure→ Visits → Leads → Qualified → Converted → Retained

Compute backwards:

• Conversions required = net new customers required (plus churn replacement, if applicable)
• Qualified leads required = conversions / close rate
• Leads required = qualified / qualification rate
• Visits required = leads / capture rate
• Top-of-funnel required = visits / click-through rate

At this stage, the "plan" becomes a set of implied requirements. If those requirements are impossible under stated constraints, you learn early – before the period is gone.

Step 3 – Define Lead Indicators and Cadence

Financial statements are lagging indicators. Execution requires lead indicators: operational precursors that move before revenue moves.

A practical minimum:

• 1 lag metric (e.g. net new members, renewals, incremental margin)
• 3 lead metrics tied to the arithmetic chain (e.g. qualified leads/week; activation within 48 hours; 30-day retention)
• Owners and cadence (weekly review; daily instrumentation when the system is new, unstable, or highly senstitive)

The purpose is governance: detect deviation early, while correction is still possible.

Step 4 – Reality-Test the Chain: Go and See

Most plans fail because the model was never tested against lived reality.

Run a disciplined observation pass:

• Watch 10 real prospects attempt the journey (or the equivalent in your context).
• Review 10 sales calls (or 10 support tickets) end-to-end.
• Trace one transaction across every handoff (marketing → sales → onboarding → billing → service).

You are looking for binding constraints:

• Where customers hesitate
• Where the organization drops them
• Where time-to-value fails
• Where conversion assumptions are friction

The point is not sentiment. The point is constraint discovery.

Step 5 – Turn Bottlenecks into If-Then Procedures

Intentions are not operational.

Replace "we should..." with conditionals:

• If a lead matches ICP and does not receive a response within two hours, escalation occurs.
• If a trial user does not activate within 24 hours, a defined intervention triggers.
• If a proposal stalls beyond X days, a specified follow-up sequence runs.

This converts execution from personality-driven heroics into repeatable process.

Step 6 – Run the Outside-View Check

Before you publish internal forecasts, run a base-rate sanity check:

• What do comparable organizations achieve for conversion, acquisition cost, sales cycle, and retention – without miracles?
• How long do comparable changes typically take to move the metric you are targeting?

This does not prohibit ambition. It prevents ambition from becoming self-deception.

4) A Worked Micro-Example (Generic Customer Case)

Assume:

• Target: +$150,000 incremental contribution margin over 12 months
• Contribution margin per customer/year: $300
• Net new customers required: 150,000 / 300 = 500

Now assume a plausible chain:

• Lead → customer conversion = 5%
• Landing page visit → lead = 10%

Then:

• Leads required = 500 / 0.05 = 10,000
• Visits required = 10,000 / 0.10 = 100,000

Now the only question that matters is unavoidable:

Where do 100,000 qualified visits come from – and what must change in the journey to make 10% become leads and 5% become customers?

The plan ceases to be sentiment. It becomes an executable chain of requirements.

5) What This Produces (The Two Outputs That Matter)

Done correctly, the walk-back yields:

1. An arithmetic chain the organization agrees to (not a narrative).
2. A short list of binding constraints – the few points where reality breaks the chain – each with:

• an owner
• a measurement instrument
• a weekly cadence
• an if-then procedure

That is what an executable plan is.

6) A Founder/Executive Checklist (Use This in the Room)

Before you leave the meeting, ensure you have:

• The target stated as ΔCM by DATE, with explicit constraints
• A defensible unit contribution margin over the same horizon
• A single dominant funnel with explicit conversion assumptions
• 1 lag metric + 3 lead metrics, each with an owner and cadence
• A short list of binding constraints, confirmed via "go and see"
• At least three if-then procedures that fire when reality deviates

Selected References

• Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the “planning fallacy”: Why people underestimate their task completion times.
• Journal of Personality and Social Psychology, 67(3), 366–381. https://doi.org/10.1037/0022-3514.67.3.366
• Kahneman, D., & Lovallo, D. (1993). Timid choices and bold forecasts: A cognitive perspective on risk taking. Management Science, 39(1), 17–31. https://doi.org/10.1287/mnsc.39.1.17
• Lovallo, D., & Kahneman, D. (2003). Delusions of success: How optimism undermines executives’ decisions. Harvard Business Review (July 2003).
• Tversky, A., & Koehler, D. J. (1994). Support theory: A nonextensional representation of subjective probability. Psychological Review, 101(4), 547–567. https://doi.org/10.1037/0033-295X.101.4.547
• Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493–503. https://doi.org/10.1037/0003-066X.54.7.493
• Kaplan, R. S., & Norton, D. P. (1992). The Balanced Scorecard—Measures that drive performance. Harvard Business Review (January–February 1992), 70(1), 71–79.
• Flyvbjerg, B. (2006). From Nobel Prize to project management: Getting risks right. Project Management Journal, 37(3), 5–15. https://doi.org/10.1177/875697280603700302
• Spear, S., & Bowen, H. K. (1999). Decoding the DNA of the Toyota Production System. Harvard Business Review (September–October 1999), 77(5), 96–106.