Name one behavior this week that demonstrates each value — if you can't, the articulation lacks operational specificity
For each articulated value, specify one concrete behavior you will perform this week that demonstrates the value—if you cannot name the behavior, the articulation lacks operational specificity and needs revision.
Why This Is a Rule
Define values so an observer could predict your behavior — operational specificity, not dictionary definitions established that values need operational definitions specific enough to predict behavior. This rule tests that specificity with the hardest possible criterion: can you name one concrete behavior you will personally perform this week that demonstrates the value? Not "I could do..." but "I will do [specific action] on [specific day]."
The test works because abstract values are compatible with zero-action weeks. "I value learning" is compatible with a week where you learned nothing — the value is too abstract to generate specific behavioral commitments. "I value learning, defined as: I allocate 5+ hours weekly to deliberate skill development" either generates a specific behavior this week ("Tuesday and Thursday evenings, I'll work through chapter 3 of the statistics textbook") or reveals that the value isn't operational enough to drive action.
The weekly timeframe is deliberate: it's concrete enough to name a specific behavior but broad enough to accommodate scheduling variation. "This week" creates immediate accountability — not "someday" but "in the next 7 days." If you can't name the behavior, the value definition needs revision (Define values so an observer could predict your behavior — operational specificity, not dictionary definitions), not the behavior — the problem is in the articulation, not in your discipline.
When This Fires
- After articulating values with operational definitions (Define values so an observer could predict your behavior — operational specificity, not dictionary definitions)
- During weekly planning when connecting values to concrete actions
- When values feel abstract and disconnected from daily behavior
- When you suspect a value is aspirational rather than operative (Write a disqualification test for each value — what evidence would prove it's aspirational rather than operative?)
Common Failure Mode
Naming vague intentions instead of concrete behaviors: "I'll practice my value of integrity this week by being more honest." This doesn't name a behavior — it names a state. A concrete behavior: "Tuesday's team meeting: I'll share my actual concern about the timeline instead of agreeing that it's fine." This is specific, time-bound, and demonstrably either performed or not.
The Protocol
(1) For each articulated value, ask: "What is one concrete, specific behavior I will perform this week that demonstrates this value?" (2) The behavior must be: Specific (not "be more X" but "do Y at Z time"), Observable (an external observer could confirm it happened), Scheduled (when this week will it happen). (3) If you can name the behavior → the value is operationally specific. Follow through. (4) If you cannot → the value articulation is too abstract. Return to Define values so an observer could predict your behavior — operational specificity, not dictionary definitions and revise until a concrete weekly behavior becomes nameable. (5) At week's end: did you perform the behavior? If yes → the value is operative. If no → either the commitment was unrealistic or the value isn't as important as you stated.