Some links on this page are affiliate links — if you buy through them we may earn a commission, at no extra cost to you.
The 90-Minute Values-to-Behaviors Translation Framework
A values-to-behaviors translation workshop is a 90-minute structured working session that converts abstract corporate principles into observable, non-negotiable workplace actions. It guides teams through four structured phases: Context Framing (15 minutes), Divergent Mapping (35 minutes), Friction Testing (25 minutes), and Operational Commitment (15 minutes). Running this framework eliminates interpretive ambiguity, giving managers clear criteria for daily operations and objective performance reviews.
Without operational definitions, corporate values create cynicism rather than alignment.
+---------------------------+
| 1. Context Framing |
| (15 Minutes) |
+---------------------------+
|
v
+---------------------------+
| 2. Divergent Mapping |
| (35 Minutes) |
+---------------------------+
|
v
+---------------------------+
| 3. Friction Testing |
| (25 Minutes) |
+---------------------------+
|
v
+---------------------------+
| 4. Operational Commitment |
| (15 Minutes) |
+---------------------------+
Why Abstract Values Break Teams
Most culture statements fail because single words invite conflicting interpretations. In Patrick Lencioni’s landmark analysis for the Harvard Business Review, generic value statements often alienate employees and create management cynicism when daily incentives contradict them. According to Gallup’s workplace research, only 23% of employees strongly agree that they can apply their organization’s values to their daily work.
When a leadership team selects "Collaboration," an engineering lead interprets it as consensus-driven architecture reviews that take 3 weeks. A sales director interprets that same word as fast, unblocked client concessions delivered in 2 hours. Neither definition is wrong in isolation. Because neither was defined as a set of physical actions, the two leaders clash during product delivery.
Ambiguous values turn performance management into a political battle. When a manager evaluates a direct report on "Integrity" or "Excellence," the evaluation reflects the manager’s personal biases rather than a shared corporate standard. To build alignment across peer groups, teams use structured formats like a 90-Minute Leadership Agenda (With Facilitation Script) to establish shared definitions before conflict emerges.
The Translation Standard: The Observability Test
The engine of this workshop is the Observability Test.
Friction testing is a structured evaluation method where teams stress-test proposed workplace behaviors against high-pressure business scenarios, such as missed deadlines or quarterly budget cuts, to see if the standards hold under real operational stress.
To pass the Observability Test, every proposed behavior must satisfy one rule: a video camera mounted on the office wall or recording a remote call must be able to record the action occurring.
- Mindset (Fails the test): "Show customer empathy."
- Observable Behavior (Passes the test): "Acknowledge client-reported software bugs within 15 minutes of ticket creation."
- Mindset (Fails the test): "Foster psychological safety in meetings."
- Observable Behavior (Passes the test): "Ask the most junior engineer in the room for their technical input before the team lead speaks."
Applying this standard prevents values from turning into vague personality assessments. If an action cannot be filmed, timed, or counted, you cannot hold an employee accountable to it.
+-------------------------------------------+
| OBSERVABILITY FILTER |
+-------------------------------------------+
| Input: Abstract Value |
| Example: "Customer Obsession" |
+-------------------------------------------+
|
v
+-------------------------------------------+
| Test: Can a video camera record this? |
+-------------------------------------------+
| |
NO YES
| |
v v
+-------------------+ +-------------------+
| Mindset Statement | | Concrete Action |
| "Care about user | | "Review 5 user |
| pain points" | | session replays |
| (Unenforceable) | | every Tuesday." |
+-------------------+ +-------------------+
The 4-Phase Session Structure
The 90-minute framework runs on a strict visual countdown timer to prevent theoretical debates and force behavioral output.
Recommended gear
Secura 60-Minute Visual Countdown Timer
A 60 minute mechanical timer showing remaining time as a coloured segment, keeping short timed exercises on track without a screen.
Affiliate link
1. Context Framing (15 Minutes)
The facilitator establishes the rules, presents the core company value under review, and demonstrates the Observability Test. The group reviews examples of empty platitudes versus concrete behaviors. If your organization is undergoing broad structural changes, running a 60-Min Change Workshop Agenda (With Script) prior to this session helps clear operational backlog first.
2. Divergent Mapping (35 Minutes)
Participants work silently on sticky notes or a digital board. They write down 2 "Always Do" behaviors and 2 "Never Do" behaviors for the chosen value. Silent generation stops dominant voices from steering the room. The facilitator clusters similar notes into 3 to 5 behavior categories.
3. Friction Testing (25 Minutes)
The group pressure-tests the top-voted behaviors against realistic operational constraints:
- "Does this behavior hold when we are 2 weeks behind on a launch date?"
- "What does this action look like when an executive pushes an unplanned feature request?"
- "Will this behavior break our budget constraints?"
Similar to the decision clarity created in an Agile Delegation Poker Workshop Agenda (60-Min Template), this phase strips away aspirational wish-lists and leaves only non-negotiable operational minimums.
4. Operational Commitment (15 Minutes)
The team selects a maximum of 3 positive behaviors and 2 negative boundaries ("We will not…"). Each participant states aloud which existing operating document, onboarding checklist, or quarterly review rubric will house these behaviors by Friday at 5:00 PM.
Frequently Asked Questions
How many values should we translate in one 90-minute session?
Focus on exactly one core value per 90-minute session. Attempting to translate three or four values at once produces superficial bullet points that fail the Observability Test. Run separate 90-minute blocks spaced across two weeks to translate a full cultural rubric.
Who needs to attend this workshop?
Keep the working group between 6 and 10 cross-functional contributors, including frontline operators and people managers. If you are dealing with deep legacy misalignment across teams, review these 10 Town Hall Scripts for Toxic Culture (Word-for-Word) before convening frontline staff.
How do we prevent the behaviors from becoming obsolete?
Embed the concrete behaviors directly into your 30-60-90 day onboarding plans, promotion packets, and weekly peer reviews. Review the behavioral statements every 6 months during leadership retrospectives.
Now that the structural framework is clear, review the exact facilitator script and room prompts required to run Phase 1 without letting the room derail into semantic arguments.
Key Takeaways
- A 90-minute structured workshop converts vague corporate values into 3 to 5 observable daily behaviors.
- Pairing positive behaviors with explicit anti-behaviors eliminates ambiguity and prevents weaponized values.
- Breakout groups of 3 to 5 participants produce the highest consensus during behavior drafting exercises.
- Drafted behaviors must be embedded into 1-on-1 templates and review rubrics within 14 days.
Table of Contents
- The 90-Minute Values-to-Behaviors Translation Framework
- Pre-Workshop Preparation and Setup Requirements
- The 4-Stage 90-Minute Agenda Breakdown
- The Core Translation Tool: The ‘Looks Like / Doesn’t Look Like’ Matrix
- Facilitator Script: Word-for-Word Prompts and Intervention Guides
- Your Copy-Paste 90-Minute Facilitator Guide and Workbook Template
- Sources & Further Reading
Pre-Workshop Preparation and Setup Requirements
Behavioral anchoring is the management practice of defining specific, observable daily workplace actions that demonstrate an abstract company value. It converts vague concepts like "integrity" or "customer first" into clear operational rules that employees can measure and evaluate during performance reviews.
A workshop fails when participants spend the first 30 minutes arguing about meeting rules or sitting in departmental silos. Setting up the room and aligning participants beforehand ensures the 90-minute session delivers actionable output.
Participant Selection and Grouping
Limit table groups to 3 to 5 people. A table with more than 5 participants reduces individual speaking time and allows disengaged attendees to hide.
Build every table with cross-functional representation. Place one software engineer, one product manager, one sales executive, and one customer support representative at the same table. In a study published in the Harvard Business Review, Boris Groysberg and his co-authors found that cultural alignment drops by 44% when individual business units interpret company values in operational silos.
Separating functional peers stops departmental echo chambers. It forces a support manager to explain what "customer obsession" means to a backend engineer who never speaks directly to clients.
Material Checklist
Prepare the physical or digital room at least 45 minutes before the session starts. For in-person workshops, set up the following physical supplies at each breakout station:
- Self-adhesive easel pads: Place 2 pads (minimum 25 x 30 inches) on the wall space behind each table.
Recommended gear
3M Post-it Easel Pad, 20 x 23 in, White, 2 Pack, Command Strips included
Self-adhesive 20 by 23 inch sheets that stick to a wall and reposition cleanly, so a workshop map survives the whole session.
Affiliate link
- Color-coded sticky notes: Provide 3 distinct colors (3 x 3 inches) per table. Designate Green for "Target Behaviors", Yellow for "Edge-Case Scenarios", and Red for "Anti-Behaviors".
- Fine-point permanent markers: Provide 2 black markers per person to ensure written notes remain readable from 6 feet away.
- Whiteboard partitions: Position mobile partitions between tables to absorb audio spill and give teams dedicated vertical charting space.
- Printed core value prompt sheets: Place 1 one-page brief on each chair containing the company’s official value statements, existing definitions, and zero commentary.
Pre-Work Expectations (48-Hour Distribution)
Send the pre-work email exactly 48 hours before the workshop. Keep the instructions under 150 words to guarantee completion.
Ask each participant to bring 2 real workplace moments from the past 90 days:
- One situation where a team member demonstrated a core value under pressure.
- One situation where an abstract value created confusion, friction, or poor decision-making.
Collecting these moments in advance removes a 15-minute brainstorming delay at the start of the session. Participants arrive with concrete material ready to map into observable behaviors.
Which Path Fits Your Workshop Setup?
If your company has fewer than 50 employees and values are still informal…
Run a single cross-functional group with founders, department heads, and frontline staff in the same room. Use our 60-Min Change Workshop Agenda (With Script) to build initial consensus on company-wide standards before attempting granular job-level behavioral definitions.
If your organization suffers from severe inter-departmental friction…
Pair direct department rivals at the same tables (such as Sales and Operations or Marketing and Product). Pair this workshop setup with the tools in our guide on 10 Peer Department Head Conflict Scripts (With Matrix) to manage live table pushback effectively.
If you are running this exclusively for Director-level and VP leaders…
Structure the tables by operating scope rather than function to define executive baseline expectations across business units. Refer to our 90-Minute Leadership Agenda (With Facilitation Script) for governance-specific facilitation prompts.
Once the physical room and participant rosters are locked, the next step is running the clock through the minute-by-minute facilitator script below.
The 4-Stage 90-Minute Agenda Breakdown
A corporate value remains an empty slogan until you bind it to observable daily work. A 2023 Gallup report found that only 23% of U.S. employees strongly agree they can apply their organization’s values to their everyday work.
This 90-minute agenda translates abstract corporate values into explicit baseline behaviors, following the time-boxed structure used in the 90-Minute Leadership Agenda (With Facilitation Script).
00:00 - 00:15
Alignment Kickoff
|
v
00:15 - 00:50
Divergent Behavioral Mapping
|
v
00:50 - 01:15
Convergence & Anti-Behaviors
|
v
01:15 - 01:30
Operational Anchoring
Stage 1: The Alignment Kickoff (00:00–00:15)
Open the session by defining why the workshop exists. State the commercial risk of vague principles: when values lack definitions, employees interpret them based on personal preference rather than operational necessity.
Establish explicit ground rules for psychological safety. Amy Edmondson of Harvard Business School defines psychological safety as a shared belief that the team is safe for interpersonal risk-taking, which is critical when debating past leadership missteps.
Set a physical timer for 15 minutes to keep the opening brisk. Tell participants that the goal is not to rewrite the company values, but to document exactly what those values look like during trade-offs, client negotiations, and delivery deadlines.
Stage 2: Divergent Behavioral Mapping (00:15–00:50)
Split the room into cross-functional pairs. Assign one corporate value to each pair and give them 35 minutes to generate concrete actions.
Direct participants to focus on high-pressure moments. Ask: "What does this value demand we do when a release is delayed, a budget is cut, or an account escalates?" For instance, if the value is "Accountability," a concrete behavior is using the steps to admit failure without losing authority rather than deflecting blame to another department.
Every submitted behavior must pass the "camera test": if a video camera cannot record an employee physically doing it or saying it, rewrite the statement. "Be proactive" fails the test. "Send a weekly blocker list to engineering by 4:00 PM every Thursday" passes the test.
Practical Scenario: Calibrating “Extreme Ownership” Across Engineering and Product
Consider a mid-sized team that adopted "Extreme Ownership" as a core corporate value, only to watch cross-functional handoffs stall. Product managers assumed the value meant they should override technical roadmaps, while engineering leads interpreted it as permission to block releases indefinitely without consulting business stakeholders.
To resolve the impasse, the facilitator ran this 90-minute translation workshop:
- Stage 1 (Setup): The facilitator established that the session would not judge past missed deadlines, but instead map daily operational handoffs.
- Stage 2 (Divergence): Mixed pairs wrote explicit actions required during release delays. When engineers wrote "take responsibility for code quality," the facilitator pushed them to rewrite it as "publish a test summary report before requesting staging deployment."
- Stage 3 (Anti-Behaviors): The group identified that "Extreme Ownership" was being weaponized to micromanage peer tasks. They drafted the guardrail: "Ownership never means making architecture changes without peer review."
- Stage 4 (Anchoring): The teams agreed on three release behaviors and assigned the VP of Product and Lead Architect to audit the new protocol during sprint reviews.
Within several release cycles, cross-department blame disappeared from weekly triage meetings, and pull request reviews moved through the pipeline without executive escalation.
Stage 3: Convergence and Anti-Behavior Pairing (00:50–01:15)
Spend the next 25 minutes narrowing the longlist into core patterns and defining boundaries.
Anti-behavior pairing is the deliberate practice of defining what a corporate value explicitly does not permit, preventing employees from using positive principles to justify toxic workplace behavior.
For every positive behavior agreed upon, document its toxic counterpart. Patrick Lencioni notes in The Advantage that unclarified values produce organizational politics when leaders weaponize corporate language against each other.
| Core Value | Operational Behavior | Weaponized Anti-Behavior |
|---|---|---|
| Integrity | Surface budget deficits within 24 hours of discovery. | Publicly shaming peers for minor calculation errors. |
| Speed | Ship minimum viable updates within 2-week sprint cycles. | Skipping mandatory data validation checks before launch. |
| Collaboration | Seek cross-functional input during initial project scoping. | Requiring unanimous consensus before taking any basic action. |
If you encounter deadlock between department leads over conflicting priorities, apply the alignment protocols from the 60-Minute Strategy Meeting Agenda (With Script) to force a crisp operational compromise.
Stage 4: Operational Anchoring (01:15–01:30)
Dedicate the final 15 minutes to codifying the outputs into team operations. Reduce the mapped list to exactly 3 primary behavioral statements per corporate value.
Assign a specific departmental owner to embed each statement into existing performance reviews, quarterly retrospectives, and onboarding rubrics. A behavior without an assigned owner defaults to an unmeasured suggestion.
Review the facilitator script in the next section to see the exact opening lines, transition prompts, and pushback responses needed to lead this agenda without losing the room.
The Core Translation Tool: The ‘Looks Like / Doesn’t Look Like’ Matrix
A behavioral anchor is a specific, observable workplace action used to evaluate performance or demonstrate a company value, replacing subjective impressions with clear evidence that any observer can independently verify.
Without clear anchors, corporate values remain decorative. In a study of corporate culture across CultureX data by Donald Sull and Charles Sull published in MIT Sloan Management Review, researchers found zero statistically meaningful correlation between a company’s published values and how employees evaluate corporate culture in practice. Gallup’s workplace analytics back this up, finding that only 23% of employees strongly agree they can apply their organization’s values to their everyday work.
The ‘Looks Like / Doesn’t Look Like’ matrix solves this gap. It forces teams to divide values into concrete everyday evidence: observable actions on one side, and anti-patterns or passive non-compliance on the other.
[Value Statement]
│
▼
[Video Camera Test]
│
┌───┴───┐
▼ ▼
[Action] [Breach]
To build an effective matrix, run every proposed phrase through the Video Camera Test. If a third party cannot see the action or hear the words on a video recording, the statement is an attitude, not a behavior. Statements like "think proactively" or "respect others" fail this filter. Rewrite them into verifiable operational habits, such as "flags production blockers within 2 hours" or "does not interrupt colleagues during design presentations."
This structure separates three distinct tiers of conduct: unacceptable breaches, baseline compliance, and high-standard positive actions. Pair this exercise with your broader 90-Minute Leadership Agenda (With Facilitation Script) to establish clear operating baselines across your team.
When facilitating this exercise on an easel pad or a virtual whiteboard, push participants beyond generic professional courtesy. Teams frequently default to listing baseline contractual duties—like arriving to work on time—instead of defining how the value alters daily trade-offs.
| Core Corporate Value | Weak Translation (Non-Verifiable) | "Looks Like" (Binary, Observable Action) | "Doesn’t Look Like" (Observable Breach) |
|---|---|---|---|
| Customer Obsession | "Always put the customer first in everything we do." | Shares user feedback snippets directly in the sprint review deck before presenting new roadmap items. | Ships a UX update that alters user workflow without running 5 recorded user test sessions. |
| Speed & Agility | "Act quickly and embrace changes in direction." | Delivers a working software prototype within 48 hours of product requirements document sign-off. | Delays engineering feedback past the agreed 24-hour review window while waiting for a formal meeting. |
| Radical Candor | "Be honest and transparent with teammates." | Challenges flawed assumptions in cross-functional syncs using documented project data. | Withholds critical project timeline risks in sync meetings and vents concerns in private 1-on-1 chats. |
| Extreme Ownership | "Take full accountability for project outcomes." | Submits a post-incident review within 24 hours of an outage, listing 3 preventive countermeasures. | Blames external vendor downtime or cross-department delays without proposing an immediate fix. |
Calibrating these examples prevents department heads from interpreting corporate culture through individual biases. When cross-functional teams define boundary conditions together, conflict resolution becomes objective, which mirrors the tactical alignment found in 10 Peer Department Head Conflict Scripts (With Matrix).
Now that your matrix has converted abstract corporate values into observable daily habits, the next step is pacing your session so participants complete the calibration within the allocated 90 minutes.
Facilitator Script: Word-for-Word Prompts and Intervention Guides
A behavioral indicator is an observable, measurable workplace action that demonstrates whether an employee is upholding or violating a specific organizational standard during daily operations.
Without clear indicators, corporate values remain abstract slogans on a lobby wall. In an analysis of 1.2 million Glassdoor employee reviews across the Culture500 dataset published in MIT Sloan Management Review, Donald Sull and Charles Sull found a correlation of -0.02 between official company values statements and how employees actually experience everyday culture. Gallup research similarly shows that only 23% of employees strongly agree they can apply their company values to their daily work.
Use the verbatim scripts below to open the session, redirect vague output, and handle pushback. You can adapt these prompts into a broader 90-Minute Leadership Agenda (With Facilitation Script) for your management team.
Opening Monologue: Setting the Room and Defusing Cynicism
Deliver this 3-minute opening standing at the front of the room before breaking into table exercises:
"Welcome, everyone. We have 90 minutes today to do one job: translate our company values from broad concepts into observable daily behaviors.
Most values initiatives fail because they stop at slogans like ‘integrity’ or ‘customer focus.’ When values stay vague, two well-intentioned people define them differently, leading to friction in code reviews, client handoffs, and performance evaluations.
We are not here to debate whether our values are pretty. We are here to agree on what they look like on a Tuesday afternoon when a release deadline slips or when a peer challenges your proposal in a meeting. If a behavior cannot be seen, heard, or evaluated in a review, it does not go on our output sheet today. Let’s get to work."
Keep the agenda moving visibly using a table-top timer.
Real-Time Intervention Prompts: Eliminating Generic Corporate Speak
During breakout exercises, teams often write vague platitudes like "collaborate better" or "show respect." Walk the room, review post-its, and use these exact verbal redirects:
- When a table writes "Communicate transparently":
"Make that observable. If I were a fly on the wall in your sprint retrospective, what specific sentence would I hear you say that proves you are communicating transparently?"
- When a table writes "Put the customer first":
"Give me the tradeoff. What is something you are actively choosing not to do or delay so the customer wins? Write the boundary, not the wish."
- When a table writes "Be accountable":
"What is the consequence when an agreed delivery date slips? Specify who gets notified, through what channel, and within how many hours."
- When a table writes an attitude instead of an action (e.g., ‘Have a positive mindset’):
"A camera cannot film a mindset. Rewrite that as an action. What does an employee do with their hands, voice, or calendar when that mindset is active?"
If peer disputes surface during these small group debates, draw from 10 Peer Department Head Conflict Scripts (With Matrix) to keep functional leads focused on shared operational handoffs.
De-Escalation Scripts for Past Violations and Cynicism
Participants often bring up past leadership failures where stated values were ignored. Acknowledge the breach directly without letting the session derail into a complaint forum. If the friction stems from historical management behavior, pair this intervention with principles from Admit Failure Without Losing Authority (4-Part Script).
- When a participant says: ‘Leadership never follows these values anyway’:
"You are pointing out a real breakdown. When leadership behavior does not match the wall poster, trust drops. Today’s exercise is the fix for that gap: we are creating the explicit standard against which leadership behavior will be evaluated. Let’s write the exact standard you want leadership held to."
- When two participants lock horns over a contentious value definition:
"We have hit a genuine trade-off. Table this definition for 60 seconds. Column A says this value means speed to market; Column B says it means zero defects. Let’s write both down as distinct situational rules instead of forcing a false compromise."
- When a participant claims: ‘This is just HR fluff that takes away from real work’:
"Unclear expectations waste more billable hours than any workshop. When we disagree on what ‘good collaboration’ means, project sign-offs stall for days. This 90-minute session establishes the exact operating criteria so you spend less time negotiating interpersonal friction later."
Practical Scenario: Converting ‘Ownership’ from a Slogan to an Operational Rule
Consider a mid-sized product development team that suffers from delayed cross-functional handoffs. The organization lists "Ownership" as a core corporate value, yet features routinely stall between quality assurance and deployment because neither team claims responsibility for release verification.
The facilitator begins the 90-minute session by dividing the engineering and product leads into mixed tables. When prompted to define "Ownership," Table 1 drafts the statement: "Take pride in your deliverables and help teammates when needed."
The facilitator intervenes immediately using the action-testing prompt: "Take pride is an internal feeling, not an operational action. What does the engineer do when a staging build fails at the end of the day?"
The table debates the question and rewrites the indicator into a two-part observable standard:
- The engineer who opens a pull request remains the designated owner until the feature passes automated integration testing in staging.
- If a build fails after 4:00 PM, the owner posts a status update in the team release channel before leaving, specifying the root cause and next triage step.
Skipping the facilitator redirect would have produced another abstract slogan that failed to resolve the deployment bottlenecks. By forcing the team to describe the physical action and the channel used, the handoff process was standardized, and deployment blockers were documented without requiring emergency status meetings.
Review the post-workshop integration matrix in the next section to convert these raw table outputs into your quarterly performance appraisal templates.
Your Copy-Paste 90-Minute Facilitator Guide and Workbook Template
A behavioral matrix is a structured grid that maps high-level corporate values to specific, observable actions and counter-examples that employees can demonstrate during everyday work. Without this translation layer, corporate values remain abstract slogans.
Gallup’s State of the American Workplace report found that only 23% of employees strongly agree that they can apply their company’s values to their everyday work. Furthermore, research led by Donald Sull published in MIT Sloan Management Review analyzed corporate values across 500 large firms and discovered no statistically meaningful correlation between published corporate values and how employees actually experience company culture.
This 90-minute agenda turns abstract corporate ideals into concrete daily actions. You can use it alongside a broader 90-Minute Leadership Agenda (With Facilitation Script) or as a standalone working session for leadership teams.
WORKSHOP FLOW
│
▼
00-15m: Context & Anti-Patterns
│
▼
15-45m: "Looks Like / Doesn't Look Like"
│
▼
45-75m: Matrix Drafting & Scoring
│
▼
75-90m: Operational Commitments
Facilitator Run-of-Show (0 to 90 Minutes)
Keep the room focused by placing a tabletop timer where everyone can track the working blocks.
Recommended gear
Original 12" Visual Countdown Timer
A 12 inch dial that shows remaining time as a shrinking coloured disc, so a room can read the clock without being told.
Affiliate link
00:00 – 00:15 | Module 1: The Translation Mandate
- Slide Cue: Slide 1 (Workshop Purpose) & Slide 2 (The Abstract vs. Concrete Gap).
- Setup: Distribute the Participant Workbook. Seat attendees in cross-functional pairs or trios.
- Facilitator Script:
"Values on a wall do not change how we ship code, resolve cross-team friction, or prioritize budget. Today, we are taking our stated core values and defining the exact workplace behaviors that support them, as well as the common behaviors that violate them. By the end of this 90 minutes, we will have an operational behavioral matrix ready for onboarding, hiring, and performance reviews."
- Instructions: Share one real example of a value behaving badly. For instance, show how "Speed" without definition leads to skipping security checks and burning out junior engineers. Give teams 3 minutes to read the baseline value statements in their workbooks.
00:15 – 00:45 | Module 2: The "Looks Like / Does Not Look Like" Brainstorm
- Slide Cue: Slide 3 (Matrix Mechanics: Action Verbs Only).
- Setup: Open digital whiteboards or supply breakout tables with physical cards.
- Facilitator Script:
"For each value, you must write two items: what it looks like when done well, and what it looks like when done poorly. You cannot use passive words. Do not write ‘Be transparent.’ Write ‘Post weekly project status updates in the public Slack channel by Friday at 4:00 PM.’ Do not write ‘Poor communication.’ Write ‘Makes architecture changes without notifying downstream service owners.’"
- Instructions: Assign one core value to each breakout group. Direct participants to generate at least 6 positive behaviors and 6 negative behaviors per value. If you are managing multiple teams at once, this structure mirrors the breakout mechanics used in our 60-Min Change Workshop Agenda (With Script).
00:45 – 01:15 | Module 3: Matrix Drafting and Friction Testing
- Slide Cue: Slide 4 (The Stress-Test Rubric).
- Setup: Display the master matrix grid on the main screen.
- Facilitator Script:
"Now we stress-test these behaviors. A behavior is only valid if it helps an employee make a tough trade-off when two priorities collide. If a behavior statement can be interpreted in three different ways by three different people, revise it immediately."
- Instructions: Each group presents their draft behaviors. Use Patrick Lencioni’s core-versus-accidental framework from his book The Advantage to strip out baseline expectations (like "shows up on time") and isolate genuine cultural differentiators. Edit the entries live into the master workbook.
01:15 – 01:30 | Module 4: Voting, Scoring, and Operational Sign-Off
- Slide Cue: Slide 5 (Operational Commitments).
- Setup: Distribute 5 voting dots or activate digital polling.
- Facilitator Script:
"Review the final list of behaviors. You each have five votes. Place your votes on the behaviors that will have the strongest daily impact on how your teams execute. The top 3 positive behaviors and top 2 anti-patterns per value become our official team standard."
- Instructions: Run a 5-minute silent voting period. Tally the top results, confirm verbal consensus from department leads, and assign the 14-day rollout owners.
Copy-Paste Participant Workbook
Print or duplicate this layout for each participant.
========================================================================
PARTICIPANT WORKBOOK: VALUES-TO-BEHAVIORS TRANSLATION MATRIX
========================================================================
CORE VALUE ASSIGNED: ___________________________________________________
EXERCISE 1: THE TRANSLATION GRID
Rule: Use observable, third-party verifiable actions (verbs, outputs, timelines).
------------------------------------------------------------------------
WHAT IT LOOKS LIKE (Observable Actions) | WHAT IT DOES NOT LOOK LIKE (Anti-Patterns)
------------------------------------------------------------------------
1. [e.g., Shares unpolished project | 1. [e.g., Delays reviews until work
drafts at the 30% milestone] | is 90% complete to avoid critique]
|
2. _________________________________ | 2. _________________________________
|
3. _________________________________ | 3. _________________________________
|
4. _________________________________ | 4. _________________________________
------------------------------------------------------------------------
EXERCISE 2: BEHAVIORAL SCORING RUBRIC
Score your top 3 drafted behaviors on a 1-to-5 scale:
- Specificity: Can a manager observe this happening without guessing intent? (1-5)
- Trade-off Power: Does this clarify what to do when time or budget is tight? (1-5)
- Measurability: Can this be evaluated in a quarterly review? (1-5)
BEHAVIOR 1: _____________________________________ Total Score: ____ / 15
BEHAVIOR 2: _____________________________________ Total Score: ____ / 15
BEHAVIOR 3: _____________________________________ Total Score: ____ / 15
========================================================================
14-Day Operational Integration Checklist
A values matrix loses relevance within 30 days unless inserted directly into existing operational workflows. Complete the following rollout sequence over the next two weeks. For delegating these integration milestones across team leads, use the structured responsibility levels outlined in the Agile Delegation Poker Workshop Agenda (60-Min Template).
Days 1 to 3: Documentation and Master Formatting
- Facilitator cleans up workshop matrix notes and standardizes phrasing across all values.
- Distribute the final one-page matrix to executive sponsors for written sign-off within 48 hours.
- Publish the finalized behavioral matrix in the central company documentation repository (such as Notion or Confluence).
Days 4 to 7: Hiring and Interview Integration
- Select the top 1 anti-pattern and top 1 positive behavior per value to build into structured interview scorecards.
- Replace generic cultural questions (like "Are you a team player?") with behavioral scenario questions based directly on the matrix.
- Train hiring managers to evaluate candidate answers against the "Looks Like / Does Not Look Like" criteria. More on structured selection frameworks can be found via the Society for Human Resource Management.
Days 8 to 10: Performance Management and 1-on-1 Updates
- Paste the translated behaviors into quarterly performance evaluation templates as standard rating rubrics.
- Instruct managers to select one positive behavior to reinforce in every bi-weekly 1-on-1 check-in.
- Provide managers with scripts to address identified anti-patterns before they become formal performance issues.
Days 11 to 14: Operational Ritual Embedding
- Add a 3-minute matrix review into weekly team tactical meetings or engineering stand-ups.
- Highlight one peer demonstration of a target behavior during monthly all-hands meetings.
- Schedule a 30-minute review at the 90-day mark to audit the matrix against real workplace incidents and update out-of-date behaviors.
Try This Today: Pull your organization’s primary stated core value right now. Open a blank document, write "Looks Like" on the left and "Does Not Look Like" on the right, and draft exactly two concrete, observable workplace actions for each column.
Sources & Further Reading
Behavioral anchoring is a measurement technique that defines specific, observable workplace actions required to demonstrate an abstract competency or organizational value across different performance levels.
Translating abstract corporate ideals into discrete daily habits requires rigorous structural design rather than open-ended morale discussions. Research published by Gallup in their 2023 State of the Global Workplace report revealed that only 23% of employees strongly agree they can apply their organization’s core values to their day-to-day work. When values remain unanchored slogans, cross-functional alignment collapses. In a landmark study of 7,600 managers across 262 companies published in Harvard Business Review, researchers Donald Sull, Rebecca Homkes, and Charles Sull discovered that only 28% of leaders could accurately list three of their company’s strategic priorities.
A physical tabletop visual countdown clock keeps participants strictly accountable to the 5-minute and 10-minute micro-sprints built into the translation exercises.
The methodologies underpinning this 90-minute workshop framework draw directly from organizational psychology, leadership theory, and empirical culture research.
- Schein, Edgar H. (2010). Organizational Culture and Leadership (4th ed.). Jossey-Bass. Establishes the three levels of culture—artifacts, espoused values, and basic underlying assumptions—proving that values only influence organizations when translated into observable artifacts and daily behaviors.
- Lencioni, Patrick M. (2002). "Make Your Values Mean Something." Harvard Business Review, 80(7), 113–117. Defines the distinction between permission-to-play, core, aspirational, and accidental values, providing the diagnostic foundation for eliminating hollow corporate slogans.
- Sull, Donald, and Sull, Charles. (2020). "The Strategy and Culture Strengths Index." MIT Sloan Management Review. Demonstrates that the gap between corporate value statements and daily employee experience directly correlates with attrition rates and project failure.
- Gallup. (2023). State of the Global Workplace: 2023 Report. Gallup Press. Supplies global benchmark data showing that fewer than one in four workers understand how company values apply to their specific roles.
- Latham, Gary P., and Wexley, Kenneth N. (1994). Increasing Productivity Through Performance Appraisal (2nd ed.). Addison-Wesley. Introduces the Behavioral Observation Scales (BOS) methodology used during the workshop’s rubric-generation segment.
Featured image by cottonbro studio on Pexels