Put the Play Into a Real Work Rhythm

Build the play into the moment so the workplace helps people call it, use it, and improve it.

A good play does not have to begin in a classroom.

A leader can notice a recurring problem during a customer call, an assignment, a handoff, or an ordinary Tuesday meeting. They can recognize that the moment matters because what happens there affects something the team or unit is trying to achieve. They can study the familiar response, think carefully about what it produces, and design a different play worth testing.

That is already playmaking.

The next challenge is making the play easy to call when the critical moment returns.

This is where a real work rhythm matters. A rhythm gives the play a recurring place. A cue helps people recognize when to call it. Supporting conditions make the response easier to perform. Repeated use then produces evidence that helps the players improve the play.

The objective is not to make people remember another model.

It is to make the workplace help them do what matters.

Before the guest reaches the front desk

Years ago, I visited a resort where guests often booked months before arriving. That gave the staff something unusual: time to know who was coming.

Before guests reached the property, employees could learn their names and become familiar with their faces. This mattered because the resort wanted the arrival to feel personal rather than transactional.

At the front desk, the staff had a simple play. When an arriving guest came into view, smile. When the guest came within about five feet, greet the person by name. Then offer the welcome refreshment.

Nothing about that play was complicated.

But it was not left entirely to memory.

Near the front desk, staff could see a simple reminder of the expected response: smile, greet the guest by name, offer refreshment. The cue was close to the place where the critical moment occurred.

That matters.

Imagine depending instead on a training session held several months earlier. The employee may remember that hospitality is important. They may remember being told to personalize the guest experience. But when three families arrive together, the phone is ringing, and another guest is asking about a room, broad intention has to compete with immediate work.

A visible cue reduces that competition.

It tells the employee, this is the moment; call the play.

Plays can be born in the workplace

It is easy to imagine this sequence:

A facilitator teaches a play in a workshop. Participants practise it. Then managers are responsible for transferring it back to work.

That can happen.

But it is only one way plays are created.

A supervisor can notice that every difficult assignment comes back to them and design a different response. A service manager can notice that the same routine customer exceptions keep waiting for approval and test a new decision play. A team leader can notice that meetings repeatedly end with vague commitments and change the way the last five minutes are handled.

The workplace is not merely the place where a finished play gets deployed.

It is where plays can be discovered, designed, tested, and improved.

Training can help people become better playmakers. A facilitator can help leaders slow down, examine a critical moment, and design a responsible bet. But leaders do not need to wait for the next workshop before they begin improving recurring moments in their own work.

The critical moment is already there.

The question is whether somebody can see it.

A rhythm is where the critical moment keeps returning

The word rhythm can create another misconception. People may imagine a Monday huddle, a Friday review, or a weekly meeting.

Those are rhythms.

They are not the only rhythms.

A real work rhythm is the recurring pattern in which a critical moment naturally comes back and gives the play another chance to be called.

For the resort staff, the rhythm was every guest arrival.

For a supervisor, the rhythm might be every meaningful assignment.

For a sales team, it might be the handoff from signed agreement to operations.

For a customer-service employee, it might be every request that falls near the edge of their authority.

For a project team, the rhythm may be every decision meeting where ownership needs to leave the room clearly.

The important question is not, “Where can we schedule time to practise the play?”

Ask instead:

Where does this critical moment already happen in the normal flow of work?

That is usually the best place to put the play.

If the moment happens during assignments, install the play there. If it appears in customer exceptions, make the customer process call it. If it happens during handoffs, put the cue at the handoff.

Do not make people leave the work merely to remember how to do the work differently.

A reminder asks. A rhythm calls.

Organizations often try to sustain new behavior through reminders.

Send another email.

Put up a poster.

Mention the program in the Monday meeting.

Ask managers to remind everyone.

Reminders can help, but they still place most of the burden on memory. The employee has to remember that a general instruction applies to this particular moment.

A well-designed rhythm does something more useful.

A reminder asks people to remember the play. A rhythm helps the work call the play when the moment arrives.

Consider a supervisor who wants employees to retain ownership when they encounter a blocked decision. Sending a weekly message saying “Remember to take ownership” will probably have little effect.

Instead, change the interaction itself.

Whenever blocked work returns to the supervisor, the first questions become familiar:

“What decision is blocking you?”

“What are the reasonable options?”

“What do you recommend?”

Now the critical moment itself calls the play.

The employee begins to anticipate the questions. The supervisor does not need to deliver a mini-lesson every time. Over repeated use, the language becomes part of the way work moves.

That is very different from remembering a training model.

Make the cue easy to see

People have limited attention, especially when work becomes busy.

That is why cues matter.

A cue can be a small card near the workstation. It can be a prompt on a whiteboard. It can be a short line in the system people already use. It can be a manager question. It can be a peer prompt. It can even be a physical object placed where the moment normally happens.

The form matters less than the job.

The cue should help people recognize the moment and recover the play without requiring them to search through a handbook or reconstruct a workshop from memory.

At the resort, a simple front-desk reminder could carry the essential play:

Smile. Greet by name. Offer refreshment.

That is enough because the reminder sits close to the moment.

The same principle could work for a project meeting:

Owner. Next move. Timing. Proof.

Or for a supervisor assigning unfamiliar work:

Win. Boundary. First move. Checkback.

The cue does not replace judgment. It lowers unnecessary memory load so judgment can be used where it actually matters.

Make the play easier to perform, not merely easier to remember

A visible cue does not solve everything.

Return to the resort.

Greeting guests by name becomes difficult if the employees do not know the guest’s name confidently. The challenge becomes even more obvious when a foreign guest has a name unfamiliar to the staff. An employee may see the reminder, recognize the moment, want to use the play—and still hesitate because they are unsure how to pronounce the name.

That tells us something important.

The arrival play may need another play before it.

Perhaps the reservations or sales team prepares the receiving staff before the guest arrives. They share the names of arriving guests, help people recognize the guests, and practise unfamiliar pronunciations.

Now we have two connected plays:

Prepare for the guest → welcome the guest

The front-desk play becomes easier because an earlier play prepared the conditions for it.

This happens throughout organizations.

A delegation play may depend on an earlier conversation that clarified decision boundaries.

A customer-recovery play may depend on employees having access to the right information.

A handoff play may depend on the sending team completing specific information before the receiver ever sees the work.

A meeting-ownership play may depend on decision makers having the evidence they need before the meeting begins.

When a play is repeatedly difficult to use, do not automatically add another reminder.

Look upstream.

Another critical moment may need its own supporting play.

Design away avoidable excuses

Execution becomes fragile when the desired response requires heroic effort every time.

If employees have to find a document in a hidden folder, ask three people for information, remember a five-step model, and guess whether the manager will support the decision, the organization should not be surprised when the familiar play returns.

Good execution design asks a practical question:

How can we make the desired response easier to use at the moment it matters?

That does not mean removing judgment or making everything automatic. Some critical moments genuinely require thought.

It means removing unnecessary friction.

Put the cue where people already look.

Provide the information before it is needed.

Clarify the authority before the exception arrives.

Give people the language they need for a difficult conversation.

Make the manager’s response predictable enough that the employee does not have to guess whether using the new play will be punished.

A play should still demand good judgment.

It should not demand unnecessary struggle.

Repetition is how a beta play learns

A Minimum Lovable Play is a bet.

That remains true after it enters the workplace.

Putting the play into a rhythm does not mean the organization has declared, “This is now the correct way forever.”

The rhythm gives the beta enough real repetitions to teach us something.

Suppose the resort staff uses the arrival play with twenty guests over several days. Leaders can now ask better questions.

How often did you use the play?

Where did it feel natural?

When was greeting by name difficult?

What happened when several guests arrived together?

Were there names people were unsure how to pronounce?

When did offering the drink feel too early or too late?

What did guests appear to appreciate?

What should we change?

Those questions do more than check compliance.

They invite the people closest to the critical moment to become co-designers of the next version.

That matters because the original play builder cannot see everything from a meeting room. Real use reveals timing, awkward language, missing information, exceptions, workload pressures, and unexpected opportunities.

The rhythm does not merely repeat the play. It gives the players enough experience to improve it.

Counting reps is not the same as measuring success

It can still be useful to ask how many times the play was used.

But the number has to serve the right purpose.

If five employees had fifty opportunities to call the play and it appeared only twice, that tells us something. Perhaps the cue is weak. Perhaps the play is awkward. Perhaps the moment is not being recognized. Perhaps another condition is blocking it.

If the play was used thirty times, we now have enough repetitions to ask what people learned.

But thirty uses do not automatically prove the play works.

Repetition produces evidence. It is not proof by itself.

The bigger question remains: what changed nearby?

Did the greeting feel more personal?

Did customer waiting decrease?

Did blocked decisions return less often to the manager?

Did handoffs become cleaner?

Did employees feel more able to act?

Did the play create an unintended problem?

The purpose of observing use is to make the next decision wiser: continue, adjust, strengthen, or stop.

Managers do not need to reteach the play

Managers are important to work rhythm, but their job is not necessarily to become trainers.

Often the most useful thing a manager can do is consistently call the cue and help people learn from the next repetition.

A supervisor does not need to explain the full logic of ownership every time blocked work arrives. They can ask the questions that call the play.

A hotel front-desk leader does not need to conduct a hospitality lecture before each shift. They can make sure the staff knows who is arriving, keep the cue visible, observe real interactions, and ask what the team is learning.

A project leader does not need to repeat a workshop on accountability every Friday. They can refuse to let important work leave the meeting without an owner and next move.

Managers make a play normal by using the operating environment to support it.

When that happens, the language stops sounding like training language.

It becomes simply how we handle this moment here.

Use the Rhythm Install

Once you have a play worth testing, give it a place to live.

You can use four questions.

1. Where does the critical moment naturally return?

Find the actual work rhythm.

Do not choose a weekly meeting simply because a weekly meeting exists. Find where the situation that calls the play really happens: assignment, customer interaction, handoff, checkback, approval, coaching conversation, review, or another recurring point in the work.

Put the play as close to that moment as possible.

2. What will call the play?

Choose the cue.

It might be a visible card, a system prompt, a manager question, a peer phrase, or another reminder already located where the work happens.

The cue should make recognition easier:

This is one of those moments. Use the play now.

3. What must be ready before the play can work?

Look at support.

Does the employee need information?

Authority?

A prepared list?

A pronunciation guide?

A clear boundary?

A tool?

A manager response?

An upstream play?

Make enough support available that the desired response does not lose simply because the familiar response is easier.

4. What will the next few reps teach us?

Decide what you want to learn.

Track enough use to know whether the play is entering practice. Ask players what feels useful or difficult. Watch the nearby result. Notice recurring exceptions.

Then improve the play, the cue, the support, or the placement.

The first installation is still a test.

Make the workplace carry the play

Choose one Minimum Lovable Play you want to test.

Then leave the training room in your imagination.

Where does the critical moment actually happen?

Stand there.

Look at what the employee sees.

What is competing for attention?

What information is available?

What would remind the person that this is the moment?

What would make the desired response easier?

What happens just before this moment that may need its own play?

What can the people who actually perform the work teach you after ten or twenty repetitions?

Build around those answers.

A play becomes part of execution when people do not need a facilitator standing beside them to call it.

The workplace begins carrying the play.

And the players begin making it better.

When the workplace still teaches the old play

Sometimes you can do all of this and the familiar response still wins.

The play has a clear critical moment. People know the cue. The reminder is visible. The information is available. The manager is prompting the response.

Yet employees still escalate.

Managers still rescue.

Teams still hide risks.

Meetings still produce vague commitments.

At that point, adding more reminders may solve nothing.

Something in the surrounding work may still be rewarding the old response more strongly than the new play.

That is the next question.

Continue with Remove the Routine That Rewards the Old Behavior to examine the approval rules, measures, incentives, routines, tools, manager signals, and other conditions that may be teaching people to return to the familiar play.

If you need to go back one step, Design One Minimum Lovable Play explains how to build the beta response itself. If the situation you are trying to improve still feels like a general problem rather than a business-critical point in the work, return to Find the Moments Where Strategy Must Show Up.

For the larger execution system, begin with Make Execution Daily.

Find where the critical moment returns. Put the play there. Make it easy to call. Give it enough real repetitions to learn—and let the people doing the work help build the next version.