This edition connects Identify, Map, Prove, Align, Coordinate and Test. It helps turn a diagnosis into coordinated action and learning. Its usefulness must be examined through application.
Matrix can reveal a gap in a buying decision. The next task is to choose a response, coordinate the work and examine whether it helps.
IMPACT provides a working structure: Identify, Map, Prove, Align, Coordinate and Test.
Use it to connect customer understanding with evidence, consistent explanations and practical action. Keep the effort proportionate to the problem. Its purpose is to improve decisions and results, not to create a larger marketing process.
Start with a problem and an intended outcome.
Consider the fictional support-assistant purchase used in the Matrix exercise.
The customer could buy a product, build an internal assistant or continue with its current process. The support lead examines everyday usefulness. Engineering assesses technical fit and ownership responsibilities. A business owner considers the investment. An AI assistant helps research options but has no purchasing authority.
The Matrix suggests a specific gap:
Engineering cannot assess integration and escalation responsibilities from the existing feature page and demonstration.
That uncertainty also affects the business case. Without a credible account of implementation and ongoing work, the customer cannot compare the options fairly.
The intended improvement is an informed fit decision: engineering can explain whether the product meets its requirements, what the customer must do and what remains uncertain.
Publishing a guide is a possible intervention. It is not the outcome.
This example is illustrative. It does not describe a customer case or demonstrated results.
Identify: establish who matters to the decision.
Confirm the participants, their responsibilities and the authority they hold.
Who performs the technical evaluation? Who supplies the requirements? Who approves spending? Who will operate the chosen solution? If an agent participates, who delegates its task and checks its findings?
Do not infer authority from attendance at a demonstration or from a job title alone.
In the example, engineering needs input from the support lead to evaluate representative cases. Its findings must reach the business owner. Understanding those relationships helps establish who the response needs to serve.
Then identify the people inside your business needed to address the gap. A founder may hold several roles, but responsibility for technical accuracy, delivery and evaluation should still be explicit.
Output: a clear account of whose decision you are supporting and who will help address it.
Map: examine the gap and its dependencies.
Use Matrix to record the relevant decision tasks, questions and handoffs. Separate observations from assumptions.
For the support assistant, investigate:
- Which integration and escalation questions remain unresolved.
- What information the customer has already seen.
- What the customer needs to establish before proceeding.
- How the answers affect implementation effort and the business case.
- Whether the concern appears in other relevant evaluations.
Check existing materials before creating new ones. The information may be accurate but scattered, difficult to find or introduced too late.
The next step could be a focused investigation. A single conversation may justify learning more without establishing that every buyer needs the same response.
Output: one specific gap, its supporting evidence and the uncertainties that remain.
Prove: provide an appropriate basis for judgment.
“Prove” means giving the buyer evidence they can examine, with its conditions and limits visible.
In the fictional example, a focused evidence package might include:
| Buyer question | Possible evidence | What must be checked |
|---|---|---|
| Will it connect to our support system? | Supported-interface documentation and setup requirements | Supported configurations, permissions and dependencies |
| What happens when it cannot answer? | Escalation instructions and an evaluation task | Trigger conditions, limitations and failure handling |
| What remains our responsibility? | An implementation and ownership checklist | Customer configuration, documentation upkeep and ongoing oversight |
| Can we assess it against our needs? | Representative support cases and agreed evaluation criteria | Whether the cases reflect the intended use and what the evaluation cannot establish |
Describe capabilities that exist. If a requirement is unsupported, record that finding.
The response may need a product change, a narrower account of suitability or a decision to serve a different customer group. Marketing should make the limitation understandable.
A successful demonstration does not establish performance under every operating condition. Explain what the evidence supports and what requires further investigation.
Output: evidence matched to the buyer’s consequential questions.
Align: keep the offer consistent across explanations.
Different participants need different emphasis, but they should encounter the same product and responsibilities.
The support lead needs to understand how the workflow changes. Engineering needs to assess implementation and ownership. The business owner needs to evaluate the commitment and expected benefit.
Suppose the customer must configure escalation rules. The demonstration should make that clear. The technical guide should explain the work. The responsibility checklist should assign it. The cost comparison should allow for it.
Ask:
Could someone move from the product page to technical evaluation and then to the business case without encountering contradictory assumptions?
Revisit the competitive comparison too. Buying and building should be assessed against the same required outcome, operating period and expected level of service.
Output: explanations that address different responsibilities while remaining consistent.
Use the buy-versus-build comparison worksheet →
Coordinate: make the response usable.
Decide what needs to happen, who owns it and how the work reaches the buyer.
For the fictional example:
| Action | Responsible role | Dependency | Completion evidence |
|---|---|---|---|
| Confirm the evaluation questions | Customer-facing lead | Relevant buyer conversations and current materials | Recorded questions, sources and unknowns |
| Prepare and check the evidence | Product or engineering lead | Confirmed capabilities and requirements | Reviewed guide, ownership checklist and evaluation instructions |
| Align related explanations | Marketer or founder | Verified evidence | Consistent product page, demonstration and business-case assumptions |
| Introduce the material | Sales or founder | Suitable evaluation and materials ready | Record of what was provided, to whom and when |
| Review the intervention | Named evaluation owner | Baseline and observation plan | Findings, limitations and a next decision |
Assign a person and a realistic date to each action. If one person owns several actions, make that workload visible.
Start at a scale that lets you learn. The business could introduce the materials during a small set of suitable evaluations before deciding whether to use them more widely.
Assign maintenance responsibility too. Product changes can make an accurate guide misleading.
Output: a focused delivery plan with owners, dependencies and a review point.
Test: examine what improved and at what cost.
Set the observation plan before introducing the change. Identify the primary outcome, supporting evidence and possible adverse effects.
For this example, the primary outcome is an informed technical-fit decision. That is something to investigate through observable evidence, rather than an unexplained score.
| Evidence | What to examine |
|---|---|
| Understanding | Can evaluators explain the requirements, limitations and responsibilities accurately? |
| Decision basis | Can they explain their fit conclusion and identify unresolved questions? |
| Assistance required | What clarification and support do they still need? |
| Evaluation effort | What work and time does the evaluation require from the buyer and supplier? |
| Handoff quality | Do the technical findings inform a credible cost and responsibility assessment? |
| Confusion | Which instructions, claims or tasks are misunderstood or abandoned? |
Establish a baseline from comparable evaluations where possible. If records are inadequate, collect a starting point rather than inventing one.
Agree what would make the intervention worth retaining or expanding. Consider the cost of creating, delivering and maintaining it alongside the expected benefit.
Interpret the evidence carefully. Fewer questions may indicate understanding or disengagement. A longer evaluation may reflect unnecessary work or more careful examination. An earlier rejection may reveal a genuine mismatch or a confusing explanation.
Record differences in requirements, buyer experience, product version and sales assistance that could affect the result. Early observations may guide a next step without establishing that the intervention caused an improvement.
Output: a reasoned assessment of what happened, what it may mean and what remains uncertain.
Follow the result through to the business.
Better evaluation should connect to outcomes the business values.
Over time, examine whether suitable opportunities progress, implementation surprises decline and customers receive the value they expected. Consider these outcomes alongside evaluation support effort and the cost of the intervention.
Conversion alone is insufficient. A higher rate could conceal poor-fit purchases; a lower rate could reflect unsuitable customers recognizing a mismatch earlier. Neither interpretation should be assumed.
Ask what changed in the decisions and experiences behind the number.
Make a decision at the review.
The review should lead to an action.
| Possible finding | Response to consider |
|---|---|
| Evaluators understand requirements more accurately with less repeated clarification | Retain the response and investigate whether wider use is justified |
| The same question remains unresolved | Revisit the explanation, evidence or evaluation task |
| Buyers understand the offer but need a capability it lacks | Reconsider the product, target customer or positioning |
| Engineering reaches a conclusion but the business case remains unclear | Improve the handoff and shared assumptions |
| The response adds effort without improving understanding | Simplify, replace or stop it |
| Evaluations differ too much to support a conclusion | Narrow the comparison or gather more relevant evidence |
These are hypothetical findings, not results claimed for the example.
Update the Matrix when you discover a missing participant, incorrect assumption or overlooked dependency. Record why you changed the response so the next person can understand the reasoning.
Use IMPACT as a loop.
The stages organize the work; they do not prescribe a rigid sequence.
Developing evidence may send you back to Map. Testing may reveal someone you missed during Identify. A new competitive alternative may require you to revisit the market context before continuing.
The method itself also needs scrutiny.
Does it help you choose a useful response? Does coordination improve delivery enough to justify the effort? Which steps add little in a particular situation? What does the structure fail to capture?
IMPACT is under development. Adapt its use to the problem and revise the method when evidence warrants it.
Prepare your first intervention.
Use this short brief:
| Field | What to record |
|---|---|
| Situation and alternatives | What the customer is deciding and what else they could do |
| Diagnosis | The Matrix finding, its evidence and remaining uncertainties |
| Intended outcome | What should improve for the buyer and the business |
| Response | The evidence, explanation or experience you propose to change |
| Ownership | Who does the work, checks accuracy and maintains the result |
| Dependencies | What must happen first and which handoffs matter |
| Evaluation | The baseline, observations, costs and criteria for deciding what follows |
| Review | When you will examine the evidence and who makes the next decision |
Keep the brief proportionate. If the diagnosis is still uncertain, the first intervention may be further investigation.
The useful result is a response you can explain, coordinate and assess—and a clear reason for what you do next.
Return to the Matrix exercise →
Read the Adaptive Marketing approach →
Revision history
Edition 1.0 — 15 November 2026
Initial method and worked example linking Matrix findings to evidence, consistent messages, coordinated activity and measurable outcomes.
Shared revision principle
We revise the method when evidence or practical experience warrants a change. For meaningful revisions, we explain what changed, why it changed and what readers using an earlier edition should reconsider. Earlier editions will remain available for reference.