Recommended resources
The freely available resources this lesson will direct you to.
Hello. Last time, you wrote a positioning statement that distinguishes an agent workflow from the collection process a buyer would otherwise continue using. That statement is your internal anchor. Today you will make it easier to use: you will build a message hierarchy that keeps the buyer’s problem, your different approach, the evidence, and the business outcome connected—even when you change what you emphasize in a conversation.
Plan on about 40 minutes for the short videos, reading, and a working draft. By the end, you should have a compact reference you could use before speaking with a head of operations or head of collections.
Give each part of the message a distinct job
A positioning statement has to compress several ideas into a sentence or two. A hierarchy gives those ideas room to do their separate jobs. The buyer’s problem explains why change is worth considering. Your approach explains what changes. Proof explains why the buyer should believe you. The outcome explains what improvement matters.
Henry Wang’s How to Build Positioning & Messaging demonstrates how to start with a customer’s existing workflow rather than a product feature, then communicate the resulting value in different ways.
How to Build Positioning & Messaging (by an ex-Google PMM)
Watch Henry Wang’s “How to Build Positioning & Messaging” for a practical distinction between the underlying message and the way you lead with it.
Watch the mapping of customer workflow, frustrations, solution, and benefits. Then watch message variations: Wang shows how the same material can be presented problem-first, solution-first, or benefit-first. Focus on keeping the underlying claims consistent when their order changes; his example concerns education, not lending.
The pyramid below is another way to picture the relationship. Its lower levels include key messages and proof points; its upper levels include broader statements of value and position. You do not need to fill all six labels to complete today’s task. Use it as a reminder that a broad promise needs specific support beneath it.
For your current position, begin with one buyer problem, not every challenge in collections. Suppose the problem supported by your interviews is that routine, policy-eligible follow-up consumes collector time and some eligible cases wait in a queue. The alternative is the prospect’s actual current process, which may already include automation. Your differentiated approach must identify the remaining work your agent workflow handles differently—not merely say that it “uses AI.”
Connect the claim to the work that changes
Pam Didner’s How to Create a Messaging Framework is useful here because it separates a customer challenge, a message about how the product addresses it, a feature, and a user benefit. That separation prevents a technical capability from being mistaken for a business result.
How to Create a Messaging Framework (Including Templates!)
Watch Pam Didner’s “How to Create a Messaging Framework” to see how to express a buyer challenge and translate a product feature into a benefit.
Watch buyer challenges, paying attention to how a message addresses a specific difficulty. Continue with features and benefits; notice that naming a system is not the same as explaining what becomes easier for its user.
Here is a hypothetical hierarchy built from the positioning example in the previous lesson. It is a model for organizing claims, not a description of your product’s verified capabilities or results.
| Layer | Illustrative message |
|---|---|
| Buyer problem | Routine, policy-eligible follow-up uses collector time, while eligible cases can wait for attention. |
| Differentiated approach | Agents handle approved follow-up steps within defined rules and present exceptions for staff review, rather than requiring staff to initiate each of those steps. |
| Supporting evidence | A workflow demonstration and event records show which approved steps agents completed and which cases were routed for review. Comparable queue records would be needed to establish a change in coverage or staff time. |
| Business outcome | The intended result is more eligible cases receiving timely follow-up per collector hour, with staff attention available for exceptions. A measured improvement can replace “intended result” only when comparable records support it. |
Read the rows as a test of one another. If the problem is collector capacity, proof only that agents can send a message is insufficient: you also need evidence about staff time or capacity before claiming a productivity improvement. If the outcome is better recovery, records of follow-up coverage alone do not establish it. They show that work happened, not what borrowers paid.
This is also where precision about control matters. “Agents handle approved steps and route exceptions” is meaningful only if those boundaries describe the actual workflow. Do not add “staff retain control,” “compliant,” or “lower cost” as automatic consequences. Each is a distinct claim requiring an appropriate explanation or evidence.
Make proof proportionate to the outcome
Create a Messaging Framework That Sticks, from The Starr Conspiracy, describes a messaging framework built around core positioning, supporting messages, proof, and adaptations for different audiences. Read its sections on architecture and proof with a practical question in mind: Which evidence belongs immediately beside each claim?
Create a Messaging Framework That Sticks
Read The Starr Conspiracy’s “Create a Messaging Framework That Sticks” for a compact model of how positioning, supporting messages, and proof fit together.
In “Step 3 - Build Your Messaging House Architecture,” read the architecture, from the list of four levels through the example of adapting a pillar for different buyers. In “Step 4 - Develop Proof Points That Actually Prove,” read the proof guidance, from the three evidence types through the warning against generic claims. Finally, in “Step 5 - Create Application Guidelines for Different Contexts,” read the adaptation guidance. Focus on preserving one core position while changing what you emphasize for a particular buyer.
For an agent workflow, distinguish evidence that a capability exists from evidence that a business outcome occurred. A demonstration or event log may establish that approved actions were executed and exceptions surfaced for review. To support “more eligible cases covered per staff hour,” you would need consistent definitions of eligible case, covered case, and staff hour, plus a credible comparison with the prior process. Even a measured reduction in hours spent on that queue is not automatically a cost saving: staff may be redeployed rather than removed from expense.
This distinction does not make an early message weak. It makes it usable. Where you have demonstrated a workflow but not yet measured its effect, state the outcome as a target to validate. Where you have comparable results, state the observed result and its scope. Keep a visible gap rather than filling it with a confident adjective.
The same hierarchy can serve both senior buyers without becoming two conflicting stories. An operations leader may want to understand capacity across the team; a collections leader may ask first about eligible-case coverage and how exceptions are handled. You can lead with either concern if discovery confirms it matters, while retaining the same description of the workflow and the same limits on your proof.
Assemble a one-page working hierarchy
Bring forward the positioning statement you drafted last time. Beneath it, write four short entries: buyer problem, differentiated approach, supporting evidence, and business outcome. Aim for one or two sentences per entry, using the hypothetical table as a structure, not as copy to adopt. Beside the evidence, mark whether it is a demonstration, a customer report, or a comparison against a defined baseline. If the outcome has not been measured, label it “to validate.”
Then read the four entries without the positioning statement. They should still describe one coherent account of how work changes and why that change matters. If you could swap in any collections software without changing the approach entry, sharpen the operational contrast. If the proof does not establish the stated outcome, narrow the outcome or identify the missing measurement.
Keep this as an internal guide, not a script to recite. It should let you start with the problem in a discovery meeting, with the outcome in an executive discussion, or with the approach during a demonstration—without quietly changing the claim.
What to carry forward
A usable message hierarchy ties a recognizable buyer problem to a specific change in the workflow, then pairs each claim with suitable evidence and a business outcome stated at the level the evidence permits. It makes your positioning more flexible without making it less precise.
This completes the module’s work on product–market fit and the core message. Next, you will examine a prospect’s current collection workflow in detail. That operational map will help you replace broad contrasts with the specific activities, handoffs, bottlenecks, and cost drivers needed for a credible comparison and ROI case.