A Minimum Lovable Play is a small, useful bet for a critical moment—carefully designed, easy enough to try, and meant to improve through use.
People can know what good behavior looks like and still return to the familiar response when pressure arrives.
That is not surprising. The familiar response is already available. People have used it before. They know what it protects. It may even solve the immediate problem.
A different response has to compete with that.
This is where a Minimum Lovable Play becomes useful. You have identified a critical moment because what happens there can help or hinder something your team, unit, or organization is trying to accomplish. You have clarified what behavior should become visible. Now you need a response people can actually call when the moment returns.
Not a perfect response.
Not a universal best practice.
A carefully considered bet.
Given what matters in this critical moment, what different play is worth trying?
The deadline was real
Joel, an analyst, was finishing a report due that afternoon when he discovered two possible figures in the source files. Both looked reasonable. He did not know which one had already been approved.
He brought the report back to Mara, his manager.
“I’m not sure which figure to use.”
Mara looked at the clock. She had another meeting in ten minutes, and the report had to move.
She could stop and work through Joel’s thinking. She could send him back to investigate. She could tell him which figure to use. Or she could simply open the file and fix it herself.
Mara took the report.
For the next ten minutes, that was probably the fastest move.
The report moved. The deadline survived.
So did the dependency.
The next time Joel reached a difficult decision, returning the work to Mara became even more reasonable. The more Mara rescued the work, the more necessary the rescuing appeared.
It would be easy to call this a delegation problem or an ownership problem. But those are still broad topics. The more important question is why this particular moment matters.
Perhaps Mara’s team is expected to improve turnaround time, increase analyst ownership, and reduce work that repeatedly climbs back to managers. Perhaps the unit needs managers spending more time on customer and operational decisions rather than completing work their people could learn to own.
If so, this is not merely a moment that irritates Mara.
It is a critical moment because the repeated response can help or obstruct a result the unit needs to move.
That is where play design should begin.
Behavior tells you what should change. A play gives you something to do.
Suppose we have already clarified the desired behavior.
When Joel reaches a decision he can reasonably help solve, we want him to keep ownership of the work, think through the options, and bring judgment rather than simply returning the problem.
That is useful.
But imagine Mara standing there with ten minutes left before her meeting.
“Help Joel take more ownership” is still not much of a response.
Observable behavior tells us what good performance should look like. A play reduces the distance between that intention and the next action.
Mara needs something she can call.
Perhaps the play begins with one question:
“What decision do you need from me?”
Joel names the decision.
Then Mara asks:
“What are the reasonable options, and which one do you recommend?”
Joel has to think instead of simply transferring the uncertainty upward. Mara can confirm his recommendation, challenge it, or clarify the boundary for next time.
That small response does not solve every delegation problem. It does not turn Joel into an expert in one conversation. It does something more modest and more useful: it gives Mara and Joel a different way to handle a recurring critical moment.
That is a play.
Do not merely improve the familiar play
When people design solutions, they naturally ask how to do the current response better.
If managers explain too much, perhaps they should explain more clearly.
If people escalate slowly, perhaps they should escalate faster.
If meetings produce vague commitments, perhaps the team needs better meeting notes.
Sometimes improvement is exactly what is needed.
But not always.
A critical moment invites a more fundamental question:
Is the familiar response itself the play we want to keep?
Mara’s familiar play is taking the work back. We could help her do that more efficiently. We could create a faster correction process, improve the file system, or teach Joel how to package his questions more clearly.
Those changes might help.
But if the business need is stronger analyst judgment and less unnecessary managerial rescue, making the rescue more efficient may simply strengthen the old game.
The different play is not necessarily an improved version of the familiar play.
It may change who decides.
It may change what question gets asked.
It may move ownership.
It may remove a step.
It may replace explanation with a boundary.
It may replace escalation with a recommendation.
The design question is not, “How can we make the current response better?”
It is:
“Given what this critical moment contributes to the goal, what response is worth trying instead?”
That is a very different way to design execution.
A Minimum Lovable Play is a bet
The word play can make the idea sound more certain than it really is.
It should not.
A Minimum Lovable Play is a bet.
You are saying:
We have found a recurring critical moment.
We understand the familiar response and why people use it.
We can see what that response creates now and what it may cost later.
We believe this different response can make the desired result more likely.
So we will try it.
Then we will watch.
That makes the first version of the play a kind of beta. It should be good enough to use, but it is not sacred. Real work will reveal things the designer did not anticipate.
Perhaps Joel handles the play well when there are two clear options but struggles when the data itself is unreliable.
Perhaps Mara discovers that asking for a recommendation works with experienced analysts but overwhelms someone who joined last week.
Perhaps the play reduces unnecessary escalation but creates a new delay because the authority boundary is still unclear.
Good.
Now you are learning.
The purpose of the first play is not to prove that the designer was right. It is to create enough movement and evidence to make the next version wiser.
A play is not a better answer you have already proved. It is a different bet you are willing to test because this moment matters.
Minimum does not mean careless
There is a danger in the word minimum.
People may hear it as: do something quick, improvise a few steps, and see what happens.
That is not what Minimum means here.
The play may be small in execution and still deserve careful thinking before it is used.
Mara’s response with Joel might take ninety seconds. Designing that response well may take ten minutes of careful thought. A more complicated customer, safety, or operational moment may require several conversations, multiple scenarios, and a few hours before the first play feels responsible enough to test.
The amount of time is not the standard.
The quality of consideration is.
This is a form of slow thinking—not necessarily long thinking, but deliberate thinking. Instead of jumping from “we have a problem” to “here is the solution,” you stop long enough to examine the moment.
Why is it critical?
What result is at stake?
Why does the familiar play make sense?
What does it protect immediately?
What does it create later?
What different response might move the result?
Under what circumstances would that response fail?
What evidence would tell us to adjust it?
A thirty-second play may deserve ten minutes of design.
Sometimes it deserves much more.
Small execution does not require shallow thinking.
Use the Play Builder
This is why the Play Builder matters.
It is tempting to skip it once the new response sounds obvious. But the Play Builder creates a short period of deliberate thinking before a team turns an appealing idea into something people are expected to use.
You can work through it on paper, on a whiteboard, or in a conversation.
1. Why is this moment critical?
Begin with the result.
What team, unit, customer, operational, or business objective can this moment help or obstruct?
If you cannot trace the moment toward something that matters, question whether it deserves a new play at all.
Mara taking work back may matter because repeated rescue slows analyst development, keeps routine decisions with managers, and reduces the managerial capacity the unit needs elsewhere.
That gives the play a job.
2. What tells us the moment has arrived?
Name the cue.
A play becomes usable when people can recognize, “This is one of those moments.”
For Mara, the cue may be:
An employee returns work because a decision is blocking progress and asks the manager to solve the uncertainty.
That is much more useful than saying, “Use this play when delegating.”
The moment should be recognizable without opening a manual.
3. What is the familiar play?
Describe what people normally do without making them look foolish.
Mara takes the work back because the deadline is close.
Joel sends the work upward because using the wrong figure could create a larger problem.
The familiar play usually protects something. Speed. Safety. Authority. Customer confidence. Avoidance of error. A relationship.
Understanding that matters because the different play has to survive the same pressure.
4. What does the familiar play create?
Look one step later.
The familiar response may solve the immediate problem and still create dependency, rework, waiting, escalation, customer friction, risk, or managerial overload after repeated use.
That later effect is part of the reason the moment is critical.
If nothing important changes one step later, you may be trying to redesign an irritation rather than an execution break.
5. What different play are we betting on?
Now design the response.
Do not ask first whether it is more sophisticated or more impressive than the familiar play.
Ask whether it gives this critical moment a different path toward the result.
For Mara and Joel, the bet might be:
When work returns because a decision is blocking progress, keep ownership with the employee by asking for the decision needed, the reasonable options, and the employee’s recommendation before deciding what support is required.
That is different from taking the task back.
It changes the game of the moment.
6. What are the few moves that must survive pressure?
Reduce the play to two to four moves.
For Mara:
- Ask what decision is blocking the work.
- Ask for the reasonable options.
- Ask which option Joel recommends and why.
- Confirm, redirect, or clarify the boundary for next time.
That is enough for a first test.
The goal is not to capture every possible leadership behavior. It is to preserve the few actions that make the different response possible when the moment becomes noisy.
7. What conditions could change the play?
A good play preserves judgment.
Suppose Joel is brand-new and does not yet understand the data. Asking for a recommendation may still help, but Mara may need to provide more information.
Suppose the choice creates significant legal or financial risk. The authority boundary may require Mara to make the final decision.
Suppose the deadline is now two minutes away. The immediate play may be different, followed by a later review of why the decision arrived so late.
The play is not weakened because circumstances matter.
It becomes more useful because people know what result the play is trying to protect and can judge whether the moves still fit.
8. What proof will tell us what to do next?
Before using the play, decide what you will watch.
Does work return to Mara less often for routine decisions?
Does Joel begin bringing recommendations instead of unanswered questions?
Does decision time improve?
Does the quality of judgment remain acceptable?
Does Mara spend less time rescuing work?
The proof does not have to reach all the way to the annual business objective. It needs to be close enough to tell you whether this bet deserves another repetition.
That is what turns a play into learning.
“Lovable” means people feel why the play is useful
Lovable can sound like an unusual word for an execution method.
It does not mean entertaining.
A play becomes lovable when using it produces enough practical value that the people doing the work see a reason to reach for it again.
Joel may like the new play because he no longer has to guess what kind of question Mara expects him to bring.
Mara may value it because she can support Joel without automatically taking over the task.
A service employee may value a decision-boundary play because routine customer requests stop waiting unnecessarily for approval.
A project team may value a handoff play because fewer assignments bounce back for missing information.
The benefit should begin to appear in the work.
A play becomes lovable when the player feels its usefulness before the facilitator has to remind them to use it.
That does not guarantee the play is perfect.
It means the bet has earned another try.
A play is not the same as a checklist, policy, or script
A play may use all three, but they perform different jobs.
A policy tells people what is allowed, required, or prohibited.
A checklist helps people remember important steps.
A script can provide language when wording is difficult.
A play gives people a response to call in a recognizable situation so an important result becomes more likely.
Mara’s play might eventually include a small decision card. A customer recovery play may include a script. A safety play may rely on a mandatory checklist.
Those execution aids serve the play.
They are not the play itself.
Keeping that distinction matters because an organization can produce beautiful templates and still leave people uncertain about when to use them and why the response matters.
Test the play against reality
Before treating the first version as standard, run it through a few variations.
What happens when the employee is inexperienced?
What if the deadline is much shorter?
What if the manager disagrees with the recommendation?
What if the decision sits outside the employee’s authority?
What if the same situation happens with a strategic customer?
You are not trying to predict every possible exception.
You are looking for where the play bends, where it breaks, and which conditions matter enough to make visible.
Then use it in real work.
The most useful sentence you can hear after that is not:
“I understand the model.”
It is:
“I used the play when…”
Now you have something to examine.
What happened?
What moved?
What felt awkward?
What condition mattered?
What should remain?
What should change?
That is how the beta becomes better—not because the designer keeps polishing it in isolation, but because real use teaches the next version.
Build one play worth testing
Choose one critical moment.
Not simply a frustrating situation. Choose a moment where what happens can materially help or obstruct something your team, unit, customer, or organization is trying to achieve.
Write down the familiar play and what it protects. Then look one step later and name what repeated use creates.
Now use the Play Builder.
Design one different response.
Keep the execution small enough to try in the next real occurrence, but give the design enough careful thought that the bet is responsible. Decide what will tell you whether the play deserves another repetition.
Then run it.
Do not ask whether the play is already the final answer.
Ask whether it gives you a better way to learn from this critical moment.
Give the play another place to live
A useful first play still has one serious problem: people can use it once, appreciate it, and then return to the workplace rhythms that keep teaching the familiar response.
The next job is repetition.
Continue with Put the Play Into a Real Work Rhythm to decide where the play should be called again—in an assignment, huddle, customer conversation, handoff, checkback, coaching exchange, or review.
If you need to sharpen the steps before this one, return to Find the Moments Where Strategy Must Show Up to make sure the moment genuinely matters, or Turn One Strategic Priority Into Observable Behavior to clarify what should become visible before designing the response.
For the larger execution system, return to Make Execution Daily.
Find one critical moment. Understand the familiar play. Make a different bet. Build it carefully enough to try—and lightly enough to change when the evidence teaches you something new.