Part I — Better Teams and Operational Trust Glossary

Operational Trust Core

Operational Trust (OT Core)

Definition: A system where outcomes define what matters and emotional KPIs define how work is sustained, with privacy and fairness built into measurement and response.
Why it matters: It converts trust from “culture and luck” into a managed asset: signals → protections → repair → learning.
In Better Teams: Part III (protocols), Part IV (outcomes/fairness), Part V (Emotional KPI Systems).

Emotional KPI System (OT Core)

Definition: Governance infrastructure that makes wellbeing, cohesion, fairness, and repair visible and actionable, while preventing surveillance and misuse.
Why it matters: Without measurement, systems decay back into accidents and heroics; with the wrong measurement, you create bias and fear.
In Better Teams: Part V; Ch. 45–47.

Wellbeing Loop (OT Core)

Definition: A five-step operating sequence: Detect → Protect → Repair → Verify → Learn. A loop is real only if it closes (something changes).
Why it matters: It replaces “stress as noise” with a system that triggers protection early and prevents punishment for speaking up.
In Better Teams: Ch. 46.

Repair Loop (OT Core)

Definition: A minimum viable repair protocol that turns conflict or breakdown into structured dialogue, explicit requests, and recorded agreements.
Why it matters: “We talked about it” is not closure. Repair must result in changed behavior, reset norms, and verified completion.
In Better Teams: Ch. 45–46; conflict repair is also supported in earlier conflict chapters.

Distress Shield (OT Core)

Definition: A time-limited protection protocol that pauses negative performance consequences when distress is real and activates support so the person does not have to “prove legitimacy” while strained.
Why it matters: If reporting distress creates career risk, the system will produce silence; the shield makes early reporting rational and safe.
In Better Teams: Ch. 46 and Ch. 50.

Repair at Scale (OT Core)

Definition: A five-layer scalable loop: Signal → Shield → Support → Repair → Measure & Learn, designed so every actor has incentive to participate.
Why it matters: Teams can repair locally, but organizations need infrastructure so signals don’t die in silence and so repeated failures trigger governance.
In Better Teams: Ch. 50.

Anonymous Loops (OT Core)

Definition: Reporting and feedback mechanisms that surface strain and issues without exposing individual raw emotional data to management; used as input signals for repair systems.
Why it matters: Visibility without anonymity often becomes surveillance; anonymity without repair becomes a complaint sink.
In Better Teams: Ch. 50; measurement guardrails in Ch. 46.

Structural Shields (OT Core)

Definition: Organizational protections that prevent teams and individuals from being blamed while causes are investigated and corrected (workload, deadlines, scope, staffing, decision rights).
Why it matters: Many “personal” failures are system failures; structural shields enforce redesign, not scapegoating.
In Better Teams: Ch. 50.

Better Teams B5 revision 4 FINAL

Measurement and KPIs

Emotional Health KPI

Definition: A team-level measurement approach that makes strain and safety visible while explicitly guarding against individual surveillance and career bias.
Why it matters: If emotional data is tied to individuals, it invites biased interpretation (“not promotable”) and punishes honesty.
In Better Teams: Ch. 45.

Aggregation (team-level reporting)

Definition: Reporting emotional health and cohesion only at group level (with minimum group sizes) to prevent individual inference.
Why it matters: The system’s legitimacy depends on privacy: people must trust signals won’t be weaponized.
In Better Teams: Ch. 45–46.

Signals (state, event, structural)

Definition: Three input classes for detection: state signals (pulse checks), event signals (conflicts/grievances), structural signals (rituals, agreements, norms).

Better Teams B5 revision 4 FINAL

Why it matters: You cannot repair what you cannot see; but you must see it without surveillance.
In Better Teams: Ch. 46.

Verification

Definition: The step that checks whether agreed actions worked; if closure fails or issues recur, verification triggers escalation.

Better Teams B5 revision 4 FINAL

Why it matters: Prevents “theater loops” where teams meet, emote, and change nothing.
In Better Teams: Ch. 46 and escalation guidance.

Time-to-repair

Definition: Time from first signal to first meaningful protective or repair action.
Why it matters: Slow repair converts small issues into resentment and attrition.
In Better Teams: Ch. 45–46.

Repair ratio (raised vs. resolved)

Definition: The ratio of issues raised to issues closed with validated completion.
Why it matters: Teams that cannot close breaches become brittle: conflict goes underground.
In Better Teams: Ch. 45–47.

Cohesion as a KPI

Definition: Cohesion is tracked as a measurable bundle (bonding, commitment, coordination, repair) rather than “vibes.”
Why it matters: Cohesion predicts recovery under stress; it is the team-level proof that wellbeing loops are closing.
In Better Teams: Ch. 47.

Cohesion Dashboard

Definition: A pragmatic dashboard mapping cohesion dimensions to indicators, methods, and action triggers (measured quarterly, trends over snapshots).

Better Teams B5 revision 4 FINAL

Why it matters: It operationalizes “cohesion” into decisions leaders can act on without micromanaging individuals.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 47.

Boundaries and Digital Work

Boundaries (guardrails)

Definition: Explicit rules that protect time, attention, dignity, and fairness—so the team can perform sustainably under pressure.
Why it matters: Without boundaries, “always on” becomes invisible norm; people with fewer boundaries mask system flaws and burn out first.
In Better Teams: Ch. 48 and boundary-linked measurement.

Digital boundaries

Definition: Operating rules that keep tools in service of people (response-time expectations, urgent definitions, switch-off rituals).
Why it matters: Digital overload is often a structural fairness problem, not individual “discipline.”
In Better Teams: Ch. 48.

Always-on trap

Definition: The erosion pattern where pings and late messages blur work/life boundaries and make constant availability feel mandatory.
Why it matters: It corrodes wellbeing and trust by converting generosity into expectation.
In Better Teams: Ch. 48.

Tool segmentation

Definition: Assigning channels to clear purposes (collaboration vs async updates vs emergencies) so urgency becomes explicit and enforceable.
Why it matters: Mixed-purpose channels produce implicit pressure and misread intent.
In Better Teams: Ch. 48.

Right to disconnect

Definition: Policy and norm commitments to “off hours,” modeled in the book as part of digital boundary design.
Why it matters: It institutionalizes recovery and reduces hidden privilege for those able to be online 24/7.
In Better Teams: Ch. 48; Appendix 1 (legal context).

Digital Repair Loop

Definition: A repair loop for boundary breaches: Signal → Support → Repair → Measure → Distress Shield (if persistent harm).
Why it matters: Treats boundary breaches as system events to fix, not personal failures to shame.
In Better Teams: Ch. 48.

Rituals and Micro-protocols

Five-Minute Check-In

Definition: A meeting opener: each person shares one word/sentence; facilitator acknowledges without fixing or analyzing.

Better Teams B5 revision 4 FINAL

Why it matters: Creates equal voice, emotional visibility, and reduces misinterpretation before work begins.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 20.

Rapid retrospectives

Definition: Short, frequent reflection loops (weekly/biweekly or post-event) that generate time-bound actions, not ceremonial “lessons learned.”
Why it matters: Shrinks learning cycles; normalizes honest discussion of mistakes, supporting psychological safety.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 31.

Prioritization under uncertainty

Definition: A designed practice that forces explicit trade-offs (“what we will stop doing”) and revisits priorities rhythmically as reality shifts.
Why it matters: Hidden trade-offs destroy trust; overload destroys cognition and coordination.
In Better Teams: Ch. 30.

Conflict and Repair Skills

Conflict types (task / process / relationship)

Definition: A practical taxonomy: task conflict can be healthy; process conflict becomes corrosive if roles stay vague; relationship conflict is usually destructive if unmanaged.

Better Teams B5 revision 4 FINAL

Why it matters: Helps teams “shift conflict upward” from personal battles to visible debate about work.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. “Conflict by Design” section.

Structured discussion (NVC stem)

Definition: A guided sentence structure separating observation from judgment and turning feelings/values into requests (“When I see… I feel… because I value/need… would you be willing to…?”).

Better Teams B5 revision 4 FINAL

Why it matters: Prevents escalation; gives both sides a safe path to clarity and repair.
In Better Teams: Conflict-by-design chapter and Repair Loop steps.

Needs-mapping

Definition: A negotiation technique that maps positions to underlying interests/needs and then brainstorms options that respect both.

Better Teams B5 revision 4 FINAL

Why it matters: Shifts negotiation from “who wins” to “how we design an agreement that holds.”

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 24 (Negotiation by Design).

Fairness, Outcomes, and Hiring

Outputs vs outcomes (OT Core)

Definition: Outputs are countable artifacts (emails, reports); outcomes are the value created (e.g., accurate compliant reporting, stakeholder alignment).

Better Teams B5 revision 4 FINAL

Why it matters: Measuring outputs incentivizes activity theater; outcomes ground fairness and role clarity.
In Better Teams: Part IV (Outcomes and fairness).

Proxies

Definition: Indirect signals used as stand-ins for capability (prestige, pedigree, “years”), which often embed bias and weaken fairness.
Why it matters: Proxy-driven evaluation creates resentment and noise; outcomes-based systems create legitimacy.
In Better Teams: Part IV; also referenced in the Operational Trust synthesis.

Knowledge / Skill / Competence

Definition: Knowledge = understanding; Skill = observable application; Competence = independent responsible performance in context (sustained outcomes under real constraints).

Better Teams B5 revision 4 FINAL

Why it matters: It provides a structured, defensible language for capability that reduces bias in hiring and development.
In Better Teams: Part IV (roles and hiring by outcomes).

Part II — Psychological, Business, and Technology Terms

Psychological and organizational behavior terms

Psychological safety

Definition: A shared belief that it is safe to speak up, admit mistakes, and take interpersonal risks; treated as a core condition for learning and innovation.
Why it matters: Without it, measurement becomes fear; without it, conflict goes underground; without it, learning slows.
In Better Teams: Referenced throughout; explicit in trust and measurement chapters.

Stress

Definition: A predictable mind-and-body response to perceived demands exceeding resources/control; it reliably changes attention, judgment, and behavior.
Why it matters: Treating stress as “individual weakness” guarantees repeated breakdown; treating it as system signal enables repair.
In Better Teams: Ch. 46.

Burnout

Definition: A chronic depletion state linked to sustained job strain; used in the book as a high-cost failure mode predicting turnover and performance loss.
Why it matters: Burnout is a lagging indicator that the system failed to detect and protect early.
In Better Teams: Ch. 45–46.

Groupthink

Definition: A false “cohesion” pattern where dissent is suppressed; the book warns that high cohesion scores without dissent can indicate conformity, not health.

Better Teams B5 revision 4 FINAL

Why it matters: Teams that cannot disagree safely are fragile; they fail under novelty and pressure.
In Better Teams: Ch. 47 and conflict chapters.

Cognitive load (working memory limits)

Definition: The practical limitation that teams can only actively hold a small number of priorities at once (around 3–4 meaningful chunks), beyond which performance drops.
Why it matters: Overloaded plans produce switching costs, errors, and coordination collapse; prioritization becomes a trust practice.
In Better Teams: Ch. 30.

Loss aversion

Definition: The tendency to experience loss more intensely than equivalent gain; used to explain why teams cling to backlogs and legacy initiatives.

Better Teams B5 revision 4 FINAL

Why it matters: Teams must design “drop rituals” because psychology otherwise protects sunk cost.
In Better Teams: Ch. 30.

Business and operating model terms

KPI (Key Performance Indicator)

Definition: A metric that signals what leadership treats as real; in Better Teams, emotional health KPIs must be designed with privacy and anti-bias constraints.
Why it matters: KPIs shape behavior; “wrong KPI” turns stewardship into surveillance.
In Better Teams: Ch. 45–47.

OKR (Objectives and Key Results)

Definition: A goal-setting framework linking objectives to measurable results; the book references the idea of extending OKRs beyond delivery to include repair outcomes.

Better Teams B5 revision 4 FINAL

Why it matters: If goals measure only delivery, teams learn to hide strain; if goals include repair, you reward sustainability.
In Better Teams: Mentioned in negotiation + KPI context.

Better Teams B5 revision 4 FINAL

Stakeholder communication

Definition: Adapting message to audience without distorting truth; a team-level trust practice that protects credibility under pressure.

Better Teams B5 revision 4 FINAL

Why it matters: If the team speaks in “two voices,” stakeholders perceive chaos and trust evaporates.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 38.

Technology and modern work terms

Agile (General; referenced)

Definition: A family of iterative delivery practices emphasizing feedback loops and adaptation; treated in the book as an example of designed learning loops and resilience.
Why it matters: The key contribution is not speed; it is the institutionalization of reflection and course-correction.
In Better Teams: Ch. 30–31.

Scrum (General; referenced)

Definition: An Agile framework with time-boxed iterations and end-of-iteration retrospectives as a built-in learning ritual.

Better Teams B5 revision 4 FINAL

Why it matters: It provides a repeatable cadence for reflection, which supports psychological safety and learning.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 31.

Retrospective

Definition: A structured reflection practice that inspects what went well, what didn’t, and what to try next—kept lightweight so it can repeat endlessly.
Why it matters: Rare retros become performance theater; frequent retros keep learning concrete and low-stakes.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 31.

Slack / Microsoft Teams / WhatsApp (General; referenced)

Definition: Messaging channels treated in the book as boundary-risk surfaces that require explicit response norms and segmentation.

Better Teams B5 revision 4 FINAL

Why it matters: Without norms, they manufacture urgency and produce the always-on trap.
In Better Teams: Ch. 48.

Jira (General; referenced)

Definition: A work tracking tool referenced as part of “channel inventory” for digital boundary mapping.

Better Teams B5 revision 4 FINAL

Why it matters: Boundary design must cover where work actually flows, not just where leaders think it flows.
In Better Teams: Ch. 48.

ERP (Enterprise Resource Planning) (General; referenced)

Definition: Integrated systems that manage core business operations; referenced in the book via real workplace examples (rollouts and cross-functional friction).
Why it matters: ERP contexts amplify cross-functional conflict, reputation risk, and the need for coherent stakeholder messaging.

Better Teams B5 revision 4 FINAL

In Better Teams: Ch. 38; also referenced in outcomes examples.

CRM (Customer Relationship Management) (General)

Definition: Systems for managing customer interactions, accounts, and sales pipelines.
Why it matters: Useful context for readers; not a Better Teams concept.
In Better Teams: Not central (include for completeness).

HRIS (Human Resources Information System) (General)

Definition: Systems that manage HR administration (employee records, payroll, benefits, time, etc.).
Why it matters: Helps readers locate where “people data” typically lives, and why consent and privacy design matter.
In Better Teams: Contextual; the book focuses on governance rules more than specific systems.