Lore

Behavior Design Framework for Team Environments

Overview

A practical starting point for redesigning a team's environment: specify concrete, observable desired behaviors instead of vague values like "empowerment" or "data-driven." Once a behavior is specified, diagnose what's blocking it along four dimensions:

• Competency — do people know how to do it?
• Accessibility — do they have what they need (time, tools, access) to do it?
• Social reinforcement — is it rewarded and modeled, or punished and ignored?
• Replayability — can people practice it repeatedly and improve, or is it a one-shot, high-stakes action?

This turns a slogan like "we want more empowerment" into a diagnosable, fixable design problem.

Related

• Making a Game: Co-Designed vs. Political Work Environments
• Hollow Empowerment Declaration (Abdication Mistaken for Empowerment) — the failure mode this framework is meant to prevent

Four-Part Behavior Diagnostic

When a desired behavior isn't happening, Cutler suggests checking four factors, in order, before assuming a talent or competency problem:

1. Competency — do people actually have the skill? (Usually not the real blocker, per Cutler.)
2. Accessibility — can people actually reach what they need (tools, information, access) to perform the behavior?
3. Social reinforcement — is the behavior talked about, modeled, and rewarded, or does it go unnoticed?
4. Replayability — can someone attempt the behavior, get it wrong, and revise without lasting penalty?

Cutler explicitly downplays competency as the usual culprit — see Context Removal Reveals Suppressed Creativity for a related case where perceived skill/prioritization deficits turned out to be environmental rather than personal.

Why 'Be More Data-Driven' Initiatives Fail

The framework implies that "we want to be more data-driven" (or similar culture mandates) usually fails for reasons other than a skill gap: the actual blockers are typically accessibility (can people easily get to the data/behavior in question) and social reinforcement (is doing the behavior rewarded or noticed), not competency. Leaders default to explaining failure as a training or skill problem, which is rarely the true bottleneck.

Из тем: The Product Operating Model