Launching 4DX on a single team: a 30-day implementation guide

Pick the team

• Choose a team with stable membership for the 90-day cycle ahead. Float-heavy units, rotating residents, or temp-staff-dependent teams produce social accountability problems that undermine the cadence.
• Choose a team leader committed to running weekly Sessions for the full cycle. A half-committed leader is one of the most common reasons a launch fades.
• Choose a team where the relevant lag measure is something leadership cares about. A WIG on a metric leadership doesn't track produces a cycle that runs in isolation from the rest of the organization.

Pick the WIG

• Start from outcomes that matter most over the next 90–120 days, not what's most urgent right now. Urgency favors fire-fighting; importance favors WIG selection.
• Draft the WIG in "from X to Y by Z" form with hard numbers. "From 1.8 CLABSI events per 1,000 line days to 0.8 by [date]" is a WIG. "Reduce CLABSIs significantly" is not.
• Force-rank if multiple candidates emerge. "If we could only achieve one of these in 90 days, which?" Take the top answer.
• Get sponsor alignment before presenting to the team. Sponsor protection prevents the WIG from being diluted or replaced mid-cycle.
• Involve the team in the choice. The book's rule is that senior leaders can veto a team's WIG but shouldn't dictate it; a team that helped choose its WIG is more likely to own it. Once chosen, don't reopen it mid-cycle.

Design lead measures

• Generate candidate behaviors with the team. "What behaviors, if performed consistently, would most reliably move the lag?"
• Apply the three tests to each candidate: predictive, under team control, measurable weekly.
• Aim for 1–2 lead measures. Three is the edge of manageable.
• Identify the data source and owner for each measure before finalizing. If no one can own the weekly data pull, the measure will silently stop being tracked.
• Verify additivity. Prefer behaviors team members do ("complete bedside teach-back") over behaviors they avoid ("reduce rushed discharges").

Build the scoreboard

• Decide format: physical whiteboard, printed sheet, or digital display. Physical or screen-visible strongly preferred over login-required.
• Apply the five-second test: cover the scoreboard, ask a team member who wasn't involved "is the team winning?" — if they can't answer, simplify.
• Show the lag trend, the current lead vs target, and a winning/losing indicator. Nothing else.
• Test the data update process before Session 1. The scoreboard updates weekly; the update mechanism has to be operational before the cadence starts.
• Post the scoreboard where the team gathers before Session 1 — visible, not hidden in a system that requires login.

Schedule the cadence

• Pick a consistent day and time for the team's full 90-day cycle. Send recurring invites as protected blocks — not tentative.
• Pre-populate the agenda: (1) Account: report on last week's commitment, (2) Review the scoreboard, (3) Plan: make new commitments for the coming week.
• Give the team the commitment template before Session 1: "By [day], I will [specific action] for [specific recipient or scope]."
• Notify the sponsor of Session 1 date; share the WIG statement and scoreboard.

Run the first three Sessions

• Session 1 (around Day 15): introduces the format. Expect awkwardness and vague commitments while the team finds its feet.
• Session 2 (around Day 22): the first week of commitments has run; some were kept and some weren't. Coach specificity in the new commitments.
• Session 3 (around Day 29): the rhythm starts. Commitments are more specific and the scoreboard is becoming a shared reference. Keep the Session to 20–30 minutes.

Day-30 review

• Cadence: did every Session happen on schedule? A missed Session in the first month is a structural problem to fix before the cycle continues.
• Commitment quality: are commitments specific, behavioral and dated? Look for improvement from Session 1 to Session 3.
• Kept commitments: misses are normal early on. If most commitments are being missed, look at whether they are too vague, too big or not tied to the lead measure.
• Scoreboard accuracy: is the data updated every week? A stale scoreboard is an early sign the cadence is drifting.
• Lead and lag: it's too early to judge whether the lead measures predict the lag. Revisit that once you have several weeks of both.

What you'll discover

• The first WIG you picked may not be quite right. As the team learns, the WIG can be refined (not replaced) with numbers anchored more accurately.
• Lead measures that looked predictive may not be. Early data may show lead movement without lag movement; that's information, not failure. Step 6 of the basic process in the primer covers this calibration.
• Some team members find the Session format easier than others. Coaching and a consistent commitment template usually narrow the gap.

• Hold the Session at the same time every week, even in a bad week. If time is short, shorten it to 15 minutes rather than cancel it.
• Bring several weeks of lead and lag data to a Session around the end of the second month and decide together whether each lead measure is earning its place.
• Ask the sponsor for a short monthly check-in on Session status and the scoreboard. It costs them little and keeps the WIG protected.
• Close the cycle deliberately: record what moved, which behaviors seemed to drive it and what the team would change, then choose the next WIG.
• Add a second team only when the first one is running its Sessions without prompting.