Content, Pattern, Relationship Feedback
Escalate repeated feedback from the incident to the pattern and working relationship
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 100%
Cohn's CPR framework moves a feedback conversation through content, pattern, and relationship. Content is the concrete behavior, such as a product leader failing to share information with peers. If the manager keeps repeating the same request and the behavior returns, the conversation must shift to the pattern: the employee agrees, improves briefly, and then stops. The manager names that sequence and asks what is going on rather than issuing the instruction again. The discussion then addresses the working relationship and the strategies needed for reliable change, such as recurring peer meetings, calendar reminders, or more one-on-ones. The manager offers help but makes clear that forgetting cannot continue. This reframing turns repeated correction into diagnosis, commitment, and accountability.
Origin
Extracted from The Tim Ferriss Show; Cohn explicitly names the framework content, pattern, and relationship, abbreviated CPR.
Core principles
- 01Repeating the same request turns a manager into a nag
- 02A repeated incident is evidence of a pattern
- 03The pattern conversation should uncover what blocks change
- 04Support and accountability can coexist
How to run it
- 1
State the content
Describe the observable behavior and the business impact without broad character judgments.
Pro tip Use a recent concrete example.
- 2
Name the pattern
Summarize the prior requests, the employee's agreement, and the fact that any improvement did not stick.
Pro tip Ask what is going on instead of repeating the instruction.
Watch out Do not remain trapped at the content level.
- 3
Address the relationship
Clarify that the manager will help while the employee must take responsibility for changing the repeated behavior.
- 4
Install a strategy
Choose practical mechanisms such as calendar reminders, recurring coordination meetings, or one-on-ones.
Pro tip Match the mechanism to the reason the employee gives for the pattern.
- 5
Follow up
Review whether the behavior changed and escalate the performance conversation if it did not.
Watch out Do not let another verbal agreement reset the history of the pattern.
In the wild
A vice president of product repeatedly failed to proactively update sales, marketing, and engineering. Instead of asking again, the CEO could name the pattern: requests produced a day or two of improvement but no lasting change. They could then choose recurring peer meetings or calendar reminders.
→ The conversation targets the cause of the recurring behavior and creates a durable coordination mechanism.
Common mistakes
Repeating the content
Restating the same instruction ignores evidence that agreement alone is not producing change.
Accepting apology as a plan
Acknowledgment matters, but the employee still needs a concrete strategy that prevents recurrence.
Is it for you?
Best for
It is best for managers who have already given the same actionable feedback more than once.
Not ideal for
It is not ideal for a first minor incident that has not yet formed a pattern.
From the transcript
“i like to give people a framework which is content pattern and relationship”
“i'm seeing this pattern which is that i ask you to do it and maybe you get better for a day or two but it…”
“whatever it takes but i can't have you keep forgetting if that's what's going on”
From the episode
#539: Alisa Cohn on Prenups for Startup Founders, How to Reinvent Your Career, the Importance of "Pre-Mortems," and the Three Selves
Alisa Cohn