The working concepts behind the practice.
Eight ideas, defined once, in one place. Each grew out of a real engagement, not a whiteboard session, and each names a specific way a customer journey breaks. Together they're less a list of essays and more one way of looking at the same underlying problem: a company organizes its work vertically, by function, while the customer experiences all of it as one continuous, horizontal system.
How they connect
The diagram below isn't decoration, it shows how these ideas genuinely relate: three form a throughline, the rest attach to specific points along it. Plenty of people can hand you a framework. Knowing which one applies to what you're dealing with, and how it connects to everything else in play, is the harder part.
Position reflects how directly a concept connects to the core progression, not how developed it is as a framework.
Customer Journey & Onboarding
4 FRAMEWORKSConvergence
DIAGNOSTIC LENSThe discovery that separate teams, describing their work in different internal language, are already solving the same customer problem without realizing it.
Teams rarely disagree about what's true. They describe it in function-specific language optimized for getting a budget line approved, not for revealing overlap with someone else's project. A journey map works as a translation device: it forces every internally-named project onto the same axis, not whose roadmap it's on, but which moment of the customer's experience it touches. What looked like three unrelated initiatives turns out to be three descriptions of the same gap.
Sequencing Debt
DIAGNOSTIC LENSThe compounding cost created when customer-facing touchpoints are individually complete but collectively delivered at the wrong time or in the wrong order.
Like technical debt, it's rarely visible inside any single team's own reporting. Each team can point to a touchpoint that works correctly on its own terms; the failure only exists in the sequence between them. It's a distinct problem from whether any individual step is well-designed, which is why a team can fix every piece and still deliver a broken experience.
Drift
DIAGNOSTIC LENSThe gap between what a journey map says is true and what customers are actually experiencing.
A workshop is a founding event, not a maintenance plan. The business keeps changing after the map is built, and nothing in most processes is built to notice when reality has moved past what the map describes. Drift isn't one problem; it splits into distinct types depending on which layer broke.
Process layer. Two workstreams solving the same customer moment without knowing it, a smaller, earlier version of the Convergence pattern.
Positioning layer. The map is accurate about what exists and wrong about who owns it.
Setup Absorption Model
APPLIED METHODReady State: the earliest point at which a product is configured enough for a meaningful task and a real result. Not every setting. Just useful enough to begin.
Most onboarding teams measure whether setup was completed. The better question is whether the product became ready, and who did the work to get it there. The model applies six treatments, in order, to every step standing between signup and Ready State.
Does this need to happen at all?
Can we determine this safely from what we already know?
Can we prevent a blank-state decision?
Can the system complete this safely?
Must this happen before value?
Why must the user do this?
Cross-Over Insights
1 FRAMEWORKVoicing
APPLIED METHODVoicing: rearranging the same core message so it lands correctly with a specific buyer, without changing what the message actually claims.
Borrowed from how a chord keeps its identity no matter which note is voiced on top. Teams get this wrong in two directions: unison, the same pitch for every buyer, which reads as generic; or dissonance, a genuinely different chord for each one, which collapses under comparison. Voicing is the third option, built in three moves.
Write down the two to four proof points that aren't allowed to move.
Pick three or four buyers you're actually voicing for, not twelve personas.
Decide which pillar leads for each register. The pillars themselves don't move.
Lifecycle Marketing Strategy
1 FRAMEWORKThe Three Jobs of Friction
CLASSIFICATION MODELNot all friction is a problem to remove. A taxonomy for telling the difference, and treating each type correctly instead of optimizing every pause out of the journey by default.
Remove it.
Asks the customer to perform work that adds no value.
Preserve it.
Exists because the customer still needs to determine whether the product can meet the requirement.
Design it in deliberately.
Requires customer and vendor to define the conditions for the purchase to produce value.
Measurement & Analytics
2 FRAMEWORKSThe Four Levels of Marketing Measurement
CLASSIFICATION MODELA maturity model distinguishing four measurement approaches by the specific question each can answer, not by which is newest or most sophisticated.
Can tell you whether one ad outperformed another. Can't tell you whether it created incremental value.
Can tell you which touchpoints appeared along the path. Can't reliably tell you which ones changed the outcome.
The cleanest direct evidence that a channel caused a result, via treatment and control groups. Too costly to run on everything.
Estimates each channel's contribution from aggregate data, without tracking individuals. Only as trustworthy as the assumptions built into it.
These aren't eight separate problems. They're one system, examined from different angles.
The Diagnostic is where I find out which of these is happening in your organization, before assuming it's the one you already suspect. The Workshop is where we apply the relevant framework directly to your systems.