Behavior-First Meeting Inventory and Cadences

What this is

Three linked pieces from Ch.7. First, the book's three-plus-three framing of behavior-first leadership. Second, the Meeting Structure Inventory, a four-part audit of a recurring meeting. Third, three behavior-focused cadences (weekly, monthly, quarterly) that the book describes a financial services organization using alongside its existing performance rhythms.

Use when / Do not use when

Use when: dashboards are green but the leader is not seeing the ways of working the process was designed to produce (the book's opening case), or when meetings are mostly results reporting. Do not use when (addition): no one has named the behaviors that drive value. Step 1 of behavior-first leadership comes first; the inventory asks about "behaviors we want to see" and needs them named.

The Instrument

A. Traditional versus behavior-first (book's lists)

Traditional performance leadership: 1. Setting clear outcome expectations. 2. Tracking progress against metrics. 3. Addressing shortfalls or recognizing achievements. Behavior-first adds: 1. Identifying and naming the specific behaviors that drive value. 2. Creating visibility into behavior patterns, not just outcomes. 3. Reinforcing effective behaviors through attention and response.

Book's three practice shifts: From Status Updates to Behavior Observations; From Performance Reviews to Behavior Pattern Recognition; From Problem-Solving to Environment-Shaping.

Book's behavior examples (a technology company's engineering organization): escalating potential issues before they affected deadlines or dependencies; challenging requirements that would not deliver customer value; exploring technical debt implications before committing to approaches; sharing emerging solutions early enough for meaningful feedback; balancing immediate delivery with system evolution.

Book's sample observation lines: "I saw the platform team raise integration concerns early in the planning process, which gave us time to address them before they affected the schedule." / "I noticed the mobile team challenging some of the feature requirements based on user data, which helped us focus on what would actually deliver value." Pattern recognition lines: "You consistently explore technical implications before committing to approaches, which has prevented several potential architecture problems." / "You've developed a pattern of sharing early solution concepts, which has significantly improved our ability to integrate effectively across teams." Environment-shaping questions: "What would make early escalation the easiest thing for teams to do, not something that requires courage?" / "How might we structure our planning process so that challenging requirements based on user value happens automatically?"

B. Meeting Structure Inventory

Review each meeting you lead or participate in regularly and assess:

1. Visibility Focus

• What outcomes receive attention in this meeting?
• What behaviors receive attention in this meeting?
• What's the ratio between outcome visibility and behavior visibility?

2. Language Patterns

• How much discussion focuses on what happened vs. how it happened?
• Do we have specific language for describing the behaviors we want to see?
• Do we name behavior patterns when we observe them?

3. Response Patterns

• How do we react when outcomes are on track but behaviors are concerning?
• How do we react when behaviors are excellent but outcomes are still developing?
• What receives more attention: outcome deviation or behavior deviation?

4. Environmental Focus

• How much discussion focuses on solving immediate problems vs. shaping conditions?
• Do we explore what makes desired behaviors easy or difficult?
• Do we adjust structures based on behavior patterns we observe?

What the book says the inventory often reveals: most meetings focus heavily on outcome visibility with minimal attention to behaviors; language for results is specific while language for behaviors is general; outcome deviations trigger immediate response while behavior concerns get limited attention as long as metrics stay on track.

Redesign elements the book reports a healthcare leadership team adopting (illustration, unverified, not for ROI or proof claims): a "behavior observation" section in each leadership meeting; standardized language for the key behaviors to reinforce; equal response protocols for outcome and behavior deviations; regular discussion of environmental factors that shape behavior patterns.

C. Three behavior-focused cadences (as described in the book)

How to run it (Performance Lab suggested practice)

1. Pick one recurring meeting. Answer the twelve inventory questions in writing, from memory first, then check against the next occurrence.
2. For "ratio between outcome visibility and behavior visibility", count agenda time or speaking turns on each (the method is an addition; the book names the ratio but gives no way to measure it and no target).
3. List the behaviors you want to see, in observable terms, before running the cadences.
4. Choose which cadence to start with. The book does not say to start with any one or to adopt all three at once.
5. Use the Five-Minute Behavior-Oriented Conversation for individual conversations that follow from an observation.

Record sheet (Performance Lab suggested practice)

• Meeting / date:
• Outcomes that got attention:
• Behaviors that got attention:
• Ratio (how counted):
• Specific language we have for behaviors / language we lack:
• Our response when outcomes are fine and behavior concerns; when behavior is excellent and outcomes lag:
• Environment change to try: