Week 38 Day 7: Assignment: Take One Company Goal and Define Three Team Behaviors

Choose one company goal that your team influences. Define three behaviors -- recurring actions with a specific frequency, owner, and output -- that will contribute to achieving that goal. The behaviors should be things the team does differently starting next week, not things the team is already doing.

Here is the assignment process. Step one: select the company goal. Pick the company goal that your team most directly influences. If you are not sure which goal your team influences most, use the profit equation from Week 37 Day 1 -- the goal most connected to your team's value creation is the right one. Step two: identify your team's lever. What does your team control that affects this goal? Be specific. Not 'we affect customer retention' but 'we affect the reliability of the payment system, which is the third most cited reason for customer churn in our exit survey data.' Step three: design three behaviors. For each behavior, specify: what the behavior is (the specific action), who owns it (the person responsible for making it happen), when it occurs (the frequency and the specific time), what it produces (the tangible output), and how it connects to the goal (the causal chain from behavior to lever to goal). Behavior example: 'Every Friday at 3pm, the on-call engineer reviews the week's alerts and identifies the top 3 by frequency. For each, they file a noise reduction ticket if the alert is not actionable, or a reliability improvement ticket if the alert indicates a real issue. The output is posted in the team Slack channel. This connects to the reliability goal because reducing alert noise by 30% frees on-call capacity to focus on real incidents, reducing MTTR.' Step four: install the behaviors. Put them on the calendar. Notify the team. Run them for two weeks before evaluating. Step five: measure and adjust. After two weeks, check: did the behaviors happen consistently? Is the lever moving? If the behaviors happened but the lever did not move, the behaviors might be targeting the wrong root cause -- adjust. If the lever moved, you have a validated behavior-goal connection. Document it. Add your company goal translation and three behaviors to your Leadership Operating Manual under 'Strategic Alignment.'

The three-behavior design implements what Fogg (2019) calls the 'Tiny Habits' methodology applied to organizational change -- the principle that behavior change succeeds when the new behavior is specific (not vague), anchored to an existing routine (not free-floating), and small enough to be sustainable (not ambitious enough to require willpower). His research found that behavior designs meeting all three criteria had an 89% adoption rate after 5 days, compared to a 10% adoption rate for behavior designs that were vague, unanchored, or too ambitious. The two-week evaluation window before adjustment implements what Deming (1993) calls the 'Plan-Do-Study-Act' cycle at a cadence appropriate for behavioral interventions. Research by Langley, Moen, Nolan, Nolan, Norman, and Provost (2009) on improvement science found that 2-week PDSA cycles produced faster organizational learning than either shorter cycles (insufficient time for behavior effects to materialize) or longer cycles (delayed feedback reduces learning rate). The lever-to-goal validation step implements what econometricians call 'instrumental variable analysis' (Pearl, 2009) -- verifying that the intermediate variable (the lever) is causally connected to the outcome variable (the goal), rather than merely correlated. This validation prevents the common organizational failure of investing in behaviors that move a metric without moving the outcome the metric is supposed to represent.