Context Gap, Memory Gap, and Decision Gap: the 3 gaps draining margin

Why separate the three

Amnésia Operacional is the category. The three gaps are the instances. Treating the category as a single thing leads to generic solutions — "let's buy a better CRM", "let's train the team" — which fail because they attack the wrong symptom.

The three gaps are causally independent. You can have low [Context Gap](/glossario/context-gap) and high Decision Gap. You can have zero Memory Gap and high Context Gap. Each has its own instrumentation, its own measurement, and its own treatment.

Context Gap: the memory that doesn't travel

Definition

Context Gap is the distance between the knowledge the company already has about the customer and the knowledge that actually reaches the point of the next interaction.

Operational Signals

• The customer repeats information already provided previously.
• The agent opens the interaction with "catch me up."
• The handoff between SDR and salesperson (or salesperson and CS) resets the relationship.
• Different people in the company give inconsistent answers to the same customer.

How to measure

Sample 30 to 50 conversations completed in the last quarter. For each one, count:

• How many pieces of information the customer had to repeat between handoffs.
• How many of those pieces of information already existed in some company system before the handoff.

[Context Gap](/glossario/context-gap) (%) = (repeated information that already existed / total information exchanged in the handoff) × 100.

Healthy operation: below 15%. Critical: above 35%.

How to attack

Context Gap is solved with a Crachá de Contexto: an artifact that carries the customer's full context to any person or agent entering the cycle. It lives in the overlay layer, not in the CRM. It updates in real-time with each new interaction.

Memory Gap: the memory that was never created

Definition

Memory Gap is the volume of conversations that happened and never turned into structured and recoverable data.

Operational Signals

• Notes in notebooks, personal spreadsheets, or private WhatsApp.
• Audios and calls without transcription.
• Meetings without structured minutes.
• Salesperson goes on vacation and the customer "disappears" from the radar.
• There is no recoverable history of objections, promises, preferences.

How to measure

For the same sampling period:

• Total conversation hours (call + meeting + messages).
• Hours with structured and recoverable records in a central system.

Memory Gap (%) = ((total - registered) / total) × 100.

Healthy operation: below 20%. Critical: above 50%.

How to attack

Memory Gap requires automated capture (call transcription, message thread summarization) and the habit of having every relevant interaction feed the central system. It's not training ("fill out the CRM!") — it's instrumentation.

Decision Gap: the memory that doesn't decide

Definition

Decision Gap is the percentage of operational decisions (which cadence, which offer, which channel, which message) that are made while ignoring the available context.

Operational Signals

• Standard cadence for everyone, regardless of archetype.
• Email sent after the customer requested WhatsApp.
• Template offer for an account that requested customization.
• Re-approach by SDR of a customer already in conversation with a salesperson.

How to measure

Sample 30 to 50 operational decisions (sending a message, scheduling, changing cadence). For each one:

• Was there available context that should have informed this decision?
• Did the decision made respect that context?

Decision Gap (%) = (decisions that ignored available context / total decisions) × 100.

Healthy operation: below 20%. Critical: above 40%.

How to attack

Decision Gap is solved in the MCI Decision Plan: explicit rules, recommendations generated by the engine (Conversation Score + archetype) that appear at the point of decision, not in a retroactive report.

The right order to attack

If you have all three critical gaps (which is common), there is an order that minimizes effort and maximizes return:

1. Memory Gap first. Without memory, there is no context to travel or to decide. Solving Memory unlocks the other two.
2. Context Gap next. With existing memory, the work is to get it to the right point. Crachá de Contexto solves this.
3. Decision Gap last. With context traveling, the work is to train the decision engine to use that context well. This is where Conversation Score, archetype, and suggested next action come in.

Inverting this order (attacking Decision Gap first) is the most common mistake. Without Memory and without Context, any engine recommendation operates in the dark.

Estimated financial impact

Each percentage point reduction in each gap has a measurable effect:

• 1 point less of Memory Gap = ~0.3% reduction in cycle time.
• 1 point less of [Context Gap](/glossario/context-gap) = ~0.5% increase in conversion per state.
• 1 point less of Decision Gap = ~0.4% increase in LTV/CAC.

The numbers are averages observed in pilots; they vary by sector and ticket. The direction is stable.

The point

The three gaps are not elegant synonyms for each other. They are distinct phenomena with distinct instrumentation, measurement, and treatment. An operation that measures the IAm as an aggregate number, without decomposing it, ends up investing in the wrong gap — and discovers, months later, that the IAm hasn't dropped.