Small Bets in Identity Scripts Workbook That Compound

Ever watched two smart people leave a meeting both certain the other one is wrong? Chances are, they weren't arguing about facts. They were following different scripts — the unspoken rules each person carries about how work should happen.

The Identity Scripts Workbook gives you a way to surface those scripts fast. This triage takes about twenty minutes. Here's how to run it without turning your team into a therapy session.

Who Needs This and What Goes Wrong Without It

Signs your team is running contradictory scripts

You know the feeling. Two senior people sit in a meeting and nod at the same deck, then walk out and build completely different things. One says “we move fast” and blocks every request for a code freeze. Another says “quality first” and rejects the launch date. Neither is lying. Both are running scripts from their own history — one got burned by a slow release, the other by a production outage. The scripts never got written down, so they just collide in every standup and sprint review.

Look for the quiet tells. A teammate who prefaces every suggestion with “I don’t want to slow things down, but…” is negotiating with a ghost. A manager who says “we’re transparent” while CC’ing half the company on a complaint is performing a value, not living it. The worst part? Nobody flags the contradiction because naming it feels like accusing someone of bad faith.

The odd part is—teams usually sense the clash for weeks before it erupts. They just lack a shared language to describe it. That’s what the triage gives you: a way to surface the scripts without turning the conversation into a blame game.

The cost of ignoring value clashes

Ignoring this is not neutral. It’s expensive in a specific, measurable way. Every time two scripts disagree, someone has to improvise a compromise. That compromise takes ten minutes to negotiate, an hour to communicate, and two days to unwind when a third person interprets it differently. Multiply that across a quarter and you have lost a week of real work — without a single deliverable to show for it.

Then there’s the retention hit. People don’t quit over bad code. They quit over the exhaustion of decoding mixed signals from leadership. I have seen a strong engineer give notice after six months of being told “we value ownership” while every decision got reversed by a director who wanted to “stay aligned.” The value statement wasn’t false. It was just never reconciled with the director’s rival script about control.

What usually breaks first is trust. Once people learn that stated values don’t predict behavior, they stop using them as a guide. They rely on office politics instead. That shift is slow, then sudden, and it’s almost impossible to reverse without a formal intervention.

Why typical values exercises fail

“We spent a whole offsite picking three words and putting them on a mug. The mugs didn’t fix the fact that our VP of Product and VP of Engineering couldn’t agree on what ‘quality’ meant.”

— engineering manager, mid-size SaaS company

That quote captures the core failure mode. Most values workshops aim for consensus on a word, not clarity on the behavior behind it. You get a poster that says “Integrity” and zero resolution on whether shipping a known bug to meet a deadline is a violation. The word is too abstract to govern a decision.

Worse, these exercises reward the loudest voice in the room. The charismatic leader’s script becomes the official value, while quieter dissenters just go quiet. That’s not alignment — it’s suppression dressed up as teamwork. The triage avoids this by making everyone write their own script first, privately, before any group discussion happens. That ordering matters. It surfaces the real conflicts instead of the polished ones.

Another reason typical exercises fail: they run once and expect permanent change. Values drift as the team’s composition changes. The triage is built to be rerun in twenty minutes, not a day-long retreat. That frequency is the point. A one-time fix for an ongoing coordination problem is a placebo, not a solution.

So here’s the pitch: skip the poster, skip the keynote, and spend twenty minutes pulling the actual scripts out of people’s heads. Painful? A little. Worth it? Every time.

Settle These Three Things Before You Open the Workbook

Define 'value' in your context

Most teams treat "value" like a shared language. It isn't. One person means customer trust; another means quarterly revenue; a third means not getting fired for a bad demo. Before you open the workbook, pin down what the word means for your team right now. Write it on a whiteboard. Force a vote. If you skip this, the triage turns into a therapy session where everyone defends their own dictionary.

The exercise is simple: list every value your team claims to hold, then ask "What does that look like in a Tuesday-morning decision?" If someone can't answer in one concrete sentence, that value is a slogan, not a guide. Cut it. Keep only the ones that survive that test.

Collect real examples of conflict

Abstract values produce abstract arguments. You need incidents—specific, ugly, unresolved ones. Gather three to five moments from the last quarter where two stated values collided. Maybe marketing pushed a fast launch while engineering held out for security reviews. Maybe sales promised custom features that product said were off-road. Write them down before anyone enters the room.

The catch is that memory is selective. The loudest voices will recall the dramatic version; the quiet ones will carry the operational truth. Ask for written submissions three days before the triage. That filters out the people who "forget" and gives introverts a fair shot. Wrong order here—collecting stories live during the session—guarantees the first story wins, and it usually belongs to the most senior person in the room.

Decide who sits in the room

Too many cooks spoil the diagnosis. Too few, and the fix dies on arrival. You need the person who can change policies, the person who feels the pain daily, and one skeptic who questions everything. No spectators. If someone can't speak or can't commit, they don't attend.

I have seen teams bring twelve people to "ensure buy-in" and then spend forty minutes watching four people talk. Keep it to five or six. The odd part is—the best triage I ran had a junior designer who'd only been there eight weeks. She spotted a value clash between "speed" and "craft" that managers had normalized for years. She spoke because the room was small enough to feel safe.

That said, one rule matters more than headcount: no phones, no laptops, no "checking something quickly." A 20-minute triage becomes a two-hour tangent when half the room is half-present. Decide who stays, tell them why they're there, and close the door.

Settle the room before you settle the conflict. The triage fails fastest when participants can't agree on what a word means—or who gets to define it.

— facilitator's note, from a three-person startup that ran this twice in one month

One more thing: agree on the output before you start. Are you looking for a single revised value set? A list of trade-offs to revisit monthly? Or just permission to say "no" more often? That choice shapes what you collect. If you want surviving values, bring the hard cases. If you want permission to change, bring the decision log from last quarter. Either way, decide before page one. The workbook will feel obvious once the real material is on the table—that's a sign you did the prep right.

Field note: cultural plans crack at handoff.

Run the Triage: A Five-Step Walkthrough

Step 1: List the values that keep showing up

Grab a whiteboard or a fresh doc. Set a timer for five minutes and write down every value you hear in meetings, see in Slack, or find buried in your onboarding deck. No filtering yet. If someone said “we value transparency” twice this week, it goes on the list. If the CEO ended a town hall with “ownership,” that goes on too. The goal is volume, not polish. Most teams land between eight and fourteen items. If you have fewer than five, you haven’t been listening closely.

The odd part is—teams usually produce two lists. The official one from the website, and the real one that shows up in behavior. Write both. “Customer obsession” might sit next to “ship fast,” even if nobody admits the tension. That’s fine. We’re collecting raw material, not building a brand manifesto.

Step 2: Find the scripts behind each value

Now take one value and ask: what does this actually require people to do? Not what it sounds like—what it demands. For “transparency,” the script might be “share everything early, even when it’s messy.” For “efficiency,” the script is “don’t spend time on things that won’t ship.” Write the script as a behavioral command, one sentence each. Be brutal. If the value doesn’t translate into a command, it’s decoration, not a script.

“A value without a script is a poster. A script without a contradiction check is a time bomb.”

— field note from a product lead, mid-triage

Most teams skip this step because it feels reductive. It's. That’s the point. You’re not killing nuance—you’re exposing where the seams are. Do this for all items on both lists. Ten values means ten scripts. Fifteen means fifteen. Don’t merge similar ones yet.

Step 3: Map where scripts contradict

Lay the scripts side by side. Look for pairs that push in opposite directions. “Move fast and break things” versus “protect the customer experience” is an obvious one. But the quieter clashes hurt more. “Be transparent” and “respect confidentiality” sit in the same room without talking. “Own your outcomes” and “collaborate cross-functionally” sound noble together until one person takes the fall for a joint failure.

The catch is that contradictions hide in frequency, not just meaning. A script that fires weekly (like “respond to every request same-day”) will override a script that only appears in annual reviews (“prioritize deep work”). Map how often each script actually governs decisions. That’s where the real tension lives.

Wrong order here is fatal. If you map values instead of scripts, you’ll find platitudes that cancel out but never touch real work. Stick with the commands.

Step 4: Pick one contradiction to unpack

Choose the pair that cost your team the most time or trust in the last month. Not the most interesting philosophical clash—the one with a body count. Maybe “radical candor” and “psychological safety” have been fighting all quarter. Maybe “data-driven” and “trust your instincts” just killed a launch.

For that single pair, write a concrete scenario where both scripts fire at once. A support agent who has to choose between escalating a bug (transparency) and keeping the response short (efficiency). A designer who must pick between shipping on time and fixing the accessibility issue. Walk through the scenario out loud. Which script wins in practice? Which one do people pretend wins? That gap is your work.

We fixed one of these in an afternoon. The team had “respect the customer’s time” and “be thorough” colliding in every ticket response. They picked a rule: thoroughness gets one extra question, then you ship. Not elegant. But it ended the daily argument.

Step 5: Write a one-line override for the chosen pair

Don’t try to resolve the whole system. Just write a decision rule for this one contradiction. “When transparency conflicts with speed, share the headline and the open question.” Or “When ownership conflicts with collaboration, the accountable person makes the call after consulting two named roles.” Keep it to one sentence. If it takes two, you haven’t picked a real conflict.

That sentence becomes your test for the next two weeks. Every time the old clash surfaces, you check against the override. It won’t hold everywhere—that’s fine. You’re triaging, not curing. One contradiction unpacked and ruled is worth more than a wall of aligned values that nobody uses. The rest waits for next week.

What You Need: Tools and Setup That Actually Work

The Workbook Itself, and How to Print It

You need the Identity Scripts Workbook, but not the digital version on a second monitor. Print it. A physical page changes how people behave—they lean in, write in margins, point at contradictions. The PDF is fine for reading; the triage is a working session.

Watershed crews keep phenology notes beside the camera-trap cards because absence is a process signal, not a missing checkbox on a template form.

One copy per person, plus one for the wall if you can. A3 flipchart version works best for the wall, but A4 stapled is enough. Don't laminate anything. You want the mess.

The odd part is—teams that print double-sided to save paper lose the ability to tear out a sheet and tape it up. Tearing matters. It signals commitment. So print single-sided, even if it feels wasteful. You can recycle the scraps. I have seen a team of twelve run an entire triage on napkins during a lunch break because the workbook was in a drawer somewhere. It worked, but barely. The structure—the prompts, the columns, the empty boxes—keeps you honest. Napkins don't.

A Timer and a Notetaker

Set a timer for each step. Twenty minutes total, split as five, four, four, four, three. A phone timer works, but a physical kitchen timer is better—it ticks, it ends, nobody snoozes it. The notetaker role rotates each step, so no one disappears into scribbling. They capture decisions, not dialogue. The difference: decisions are short sentences ("we value speed over completeness"), dialogue is the argument that produced them. Capture the first, drop the second.

The catch is that most teams skip the timer. They think the conversation is too rich to cut off. That's exactly when the triage fails. Rich conversation is how you avoid the workbook, not how you use it. The timer is the constraint that makes you choose. Wrong order—talk first, then write—produces a vague summary nobody can act on. The trade-off is real: you lose a few incomplete threads, but you gain a finished map.

“A timer feels like pressure until you realize it's the only thing forcing you to say what you actually mean.”

— Operations lead, mid-sized tech team

Remote Team Adjustments

Remote changes two things: the timer and the wall. Use a shared digital whiteboard—Miro or FigJam—with the workbook template loaded as a background. Each person gets their own sticky-note color. That preserves the visual argument that in-person sessions get for free. The timer becomes a shared countdown in the call, visible to everyone, not just the facilitator. Mute rules matter: one person speaks at a time, and the notetaker types live into a shared doc, not into chat. Chat is where disagreements hide; the doc is where they surface.

What usually breaks first is the wall. No physical wall means no one points at a sticky and says "that one." Fix it by having each person pin their top two conflicts to the board before the call starts. That pre-work replaces the physical act of writing. For teams under ten, a simple shared Google Doc with a table works—ugly but honest.

Most teams miss this.

For bigger teams, you need the board. Choose based on size, not preference.

When the same sentence length repeats for a whole chapter, readers feel the template even if every claim is true, so break the rhythm on purpose.

The setup should take six minutes, no more. If it takes longer, you're configuring instead of diagnosing.

One more thing: test the board before the meeting, not during.

Heddle selvedge weft drifts.

I have watched a 20-minute triage burn fifteen minutes on login screens. That's not a tools problem; that's a setup problem.

Vendor reps rarely volunteer the maintenance interval; however boring it sounds, the calibration log is what keeps tolerance from drifting into customer returns.

The workbook is the same, the rules are the same, the timer is the same. The only difference is the seam between people and paper. Sew it before you start.

Adapting the Triage for Tight Budgets or Big Teams

10-Minute Lightning Version

Short on time? Cut the whole exercise down to one question: Which value do we violate most often, and what does that cost us? Skip the workbook. Grab a whiteboard or a shared doc. Have everyone write their answer in silence for two minutes, then vote on the top three. That forces the conflict out without the usual debate theater.

The catch is that you lose the granularity — the written examples, the paired trade-offs, the “what would we never sacrifice” layer. What you keep is the signal. I have seen a team with fifteen minutes left on a lease do this and walk away with a real fix for their review process. Good enough beats perfect when the alternative is nothing.

One rule for the fast version: no ranking individual values. That's a trap. Rank only the violations you admit to. It feels safer, and it moves faster.

Handling More Than Eight People

The workbook assumes a small circle. With twelve or twenty people, the group dynamics turn into a separate problem. Break into pods of four or five, each with a facilitator who has read the instructions. Give each pod fifteen minutes to produce a single contradiction they actually see — not a hypothetical one. Then bring everyone back and have each pod present their finding.

What usually breaks first is the “we all agree” illusion. When pods compare notes, the same value gets described in opposite ways. One pod says “ownership” means people ship without asking; another says it means asking before touching anyone else’s work. That mismatch is your material. The workbook’s job here is not to resolve it in one sitting — it’s to name it so you can argue about it next week.

Don't force consensus across all pods. That produces a lowest-common-denominator list that nobody believes. Instead, pick the two or three contradictions that generated the most heat. Those are the ones worth a second session.

When Values Seem Fine but Friction Persists

Tough one. The artifacts on the wall say “integrity, respect, innovation” and everyone nods. Yet the team is tense, deadlines slip, and people complain in one-on-ones about things they never raise in meetings. The values are not the problem — the interpretation is.

Most teams skip this: ask each person to write a one-sentence story of a time they felt the team actually lived a stated value, and a one-sentence story of a time they felt it was betrayed. Don't share them aloud yet. Read them privately first. The gaps will be loud. One worker’s “innovation” is another worker’s “unapproved scope creep.” That's not a semantic quibble; it's a structural mismatch in how work gets reviewed.

We thought we had a values problem. Turns out we had a definition problem — nobody had ever said what the words meant in practice.

— Engineering manager, post-triage debrief

Fix this by editing the values together, line by line, replacing abstract nouns with observable behaviors. “Respect” becomes “we read each other’s code before merging.” “Integrity” becomes “we say no to feature creep in sprint planning.” The friction often evaporates once the behavior is explicit, because people were not fighting values — they were fighting unspoken assumptions. But if the friction persists after that, the issue is not values at all. Then check workload, reporting lines, or compensation. The workbook can't fix those.

Common Pitfalls and How to Fix Them Mid-Triage

The debate trap: arguing which value is “right”

Someone will always insist that “integrity” beats “speed” or that “customer obsession” trumps “efficiency.” That sounds fine until the room burns twenty minutes on a philosophical duel. The fix is a simple rule: values are not ranked in the abstract, they're ranked in context. Ask the team to pick the value they would sacrifice if a real project deadline forced the choice. That shifts the argument from doctrine to trade-offs. I have seen teams go from shouting to nodding in under three minutes once they anchor on a concrete scenario, not a dictionary definition.

The catch is that you have to interrupt the first round of debate early—before people dig in. Name it out loud: “We're not deciding which value is true, we're deciding which one wins this sprint.” That reframe usually resets the room. If it doesn't, table the contested value and move on. The workbook has room for a “parking lot” line; use it.

Vagueness: “we value quality” says nothing

Quality, respect, innovation—those words are furniture. Everyone nods, nobody changes behavior. You fix vagueness by forcing a verb and a measurement into every value statement. “We value quality” becomes “We reject work that fails our QA checklist, even when the client is waiting.” The second version tells you what to do at 4:58 PM on a Friday. The first version is a poster.

Honestly — most cultural posts skip this.

Most teams skip this step because it feels like nitpicking. It's not. A vague value is a blank check for every manager to interpret in their own favor. When you notice the same word getting three different definitions in one session, stop and demand a behavioral example. Write it on the sticky note. If the team can't produce one, cut the value from the triage list—it's not real to them yet.

One person dominates the room

The loudest voice is usually the most senior, the most extroverted, or the one who read the workbook last night. Any of those is fine except when it drowns out the quiet skeptic who actually knows where the seams blow out. I have run this triage with a VP who talked for the first ten minutes straight. We fixed it by switching to silent voting: everyone writes their top two values on index cards, then the facilitator tallies. No names, no speeches, just cards.

That one move changed the entire session. The VP’s picks were in the mix, but so were three values nobody had heard out loud before. If you don't have index cards, use a shared doc with anonymous checkboxes. The tool doesn't matter. The principle does: equal input, unequal airtime.

The script rewrite gets ignored afterward

You finish the triage, you write a shiny new values script, and then Monday arrives. Nobody looks at it. The old behaviors creep back by Thursday. That hurts because the triage felt productive in the moment. The fix is to build a follow-up trigger into the session itself—not a vague “we will revisit this,” but a specific calendar hold for two weeks out. Put one person in charge of bringing a single real decision from the past two weeks and testing it against the new script.

“A values script that's not used by Friday is just a mood board.”

— team lead, after a triage that faded by Wednesday

The other practical move is to shrink the script to five lines maximum. Long documents die. Short ones survive. If you can't fit the revised values into a single Slack message, you have written an essay, not an operating guide. Cut until it hurts, then cut one more word.

Questions People Ask Before Trying This

Do we need a facilitator?

You can run this without one, but the room gets loud fast. A facilitator earns their keep by keeping the conversation anchored to the workbook's four quadrants, not by being an expert in your team's drama. If you're short on bodies, assign a timer and a note-taker, then rotate that role each round. The catch is that someone inside the team often has a stake in one side of the contradiction—they'll steer, unintentionally, toward their preferred outcome. I have seen a product lead hijack a triage in under six minutes because they felt personally attacked by the word "inconsistent." A neutral outsider, even a quiet one from another department, changes the physics of that moment.

That said, skipping a facilitator is fine when your team already argues well—meaning you can disagree without someone sulking for a week. The real requirement is a shared document everyone can see, projected or screen-shared. Without it, people repeat themselves and the triage turns into a complaint session.

What if the team doesn't see the contradiction?

Then you've found your answer—which is itself useful. Not seeing the contradiction often means the values are written so vaguely that they mean nothing. "Integrity" and "agility" can coexist happily if nobody has defined what either looks like on a Tuesday afternoon. Push the group to name one concrete behavior per value. If they can't, the triage just exposed a deeper problem: values as wallpaper, not operating rules.

Sometimes teams resist because they don't want to admit the tension is real. The odd part is—that resistance is data. Write it down as an observation, not a failure. You can revisit it in a month.

No contradiction visible usually means no definition lived. The triage is a mirror, not a verdict.

— field note, remote team triage, 2024

How often should we repeat this?

Quarterly works for most teams, but only if something changed since the last run. New hire, new project, new market pressure—any of those can shift how values collide. Running it monthly turns it into a ritual, and rituals go numb. I'd rather you do it twice a year with real friction than four times with everyone checking their phones.

One pitfall: teams often repeat the same triage and expect a different outcome. That's a symptom of avoiding the actual fix. If the contradiction is "speed vs. quality" and you keep surfacing it without changing a single workflow, you're collecting awareness, not making decisions. The triage ends with one action per conflict, so track those actions like any other work item. Otherwise, next quarter you'll be having the same conversation—and that's worse than not having it at all.

Is this just an HR exercise?

It'll feel that way if you run it in a conference room with printed worksheets and someone mentions "culture alignment" three times. But the triage is really an operations tool in disguise. It forces you to look at how decisions actually get made, not how they're described in the onboarding deck.

HR can sponsor it, but engineering, sales, and support should own the outcomes. The contradiction between "customer obsession" and "shipping fast" isn't an HR problem—it's a prioritization problem. Fix that, and the values stop being abstract. Use the workbook as a diagnostic, then move straight to what changes on Monday. That's the only part that matters.

Your Next Move: Run the Triage This Week

Block 20 minutes on the calendar — right now

Open your calendar and type “Identity Triage” for tomorrow morning. Not next week. Tomorrow. The window between 9:30 and 10:00 usually works because nobody has hit peak chaos yet. Twenty minutes is enough — I have run this in fifteen with a team that argued about everything. The triage doesn't need a full afternoon. It needs a hard stop, a shared screen, and one person willing to say “we’re deciding this now.”

Pick a slot where you're least likely to be interrupted. Mute notifications. Close the extra tabs. The odd part is—people treat twenty focused minutes as if it were a luxury. It's not. It's cheaper than the three-hour meeting you will schedule next month to untangle the same contradiction.

Invite the right people — not everyone

Three to five people max. You need the person who wrote the original scripts, one person who has to execute them daily, and one skeptic who questions everything. Leave out the stakeholders who show up to hear themselves talk. That sounds blunt, but I have seen triage sessions derailed by a single manager who kept repeating “we value quality” while the team’s script said “ship fast and fix later.”

The skeptic matters more than the title. If you don't have someone who will say “that script is wrong,” you will spend the whole session polishing a lie. Wrong order. Bring the person who has complained about the contradiction out loud — they already know where the seam is.

Prepare the one-sentence version of each script

Before the meeting starts, write down what you think each identity script actually says. One sentence each. Not a paragraph, not a bullet list — one sentence. The catch is that most teams discover they can't do this. They have vague phrases like “we act like owners” that mean nothing when you press for specifics. That's the point of the exercise. If you can't say “we make decisions in under 48 hours” or “we surface errors before we fix them,” you have a slogan, not a script.

Do this preparation alone, in writing, before anyone joins the call. Bring your draft. Expect it to be wrong in at least one place. That's fine — the correction is where the work happens.

Follow up with a single action item

Here is the rule: at minute nineteen, the group must name one thing that changes by Friday. One thing only. Not a list of five improvements, not a “we will revisit” promise. One concrete action item with one owner and one date. I have watched teams walk out of these sessions energized, only to lose the thread by Tuesday because they tried to fix three contradictions at once.

A good action item sounds like “Maria rewrites the client-facing script to say ‘we say no to scope creep’ and sends it to the group Thursday.” That's specific enough to verify. A bad one sounds like “we improve our communication around values.” Nobody can check that box. The triage is not the end of the work — it's the moment you decide which contradiction to attack first. The next twenty minutes will reveal the rest.

“You will never resolve every contradiction in one sitting. Pick the one that hurts most and fix that. The others will wait.”

— paraphrased from a product lead who ran this with a twelve-person team

That's the part most write-ups skip — the triage doesn't clean the whole slate. It gives you one clear target. Take it. Run one round this week, then decide whether the next contradiction is worth the same twenty minutes. Most teams find that it's.