Five values for how value-first work is taught.

Single Source of Truth

Version: 1.0 Effective Date: May 6, 2026 Owner: Chris Carolan, Founder Governance: All Value-First content referencing TEACH Values must align with this reference

Purpose

This document establishes the official, canonical definitions for the five TEACH Value pairs that constitute the operating posture of the Value-First Team. Any document, resource, content, or communication that references TEACH must use these exact pairs, structures, and definitions.

When in doubt, check this document.

What is the TEACH Values Framework?

The TEACH Values Framework is the set of five interdependent value pairs that define how anyone — human or AI — shows up while doing work inside Value-First. TEACH is not methodology (what we do) and not philosophy (what we believe). TEACH is operating posture — how participants conduct themselves while the methodology and philosophy are being applied.

The framework can be expressed in two complementary framings:

• Brand-facing framing (live on valuefirstteam.com/about): "Building Transformation Through Interdependent Relationships." TEACH describes how relationships generate transformation when both halves of each pair are held simultaneously.
• Protocol-stack framing (per the VCP Positioning Paper): TEACH is "the operating posture of anyone — human or AI — working inside the stack." Every relationship between an organization and any stakeholder sits somewhere on each of the five axes.

Both framings describe the same five pairs. Use brand-facing framing in client and public-facing contexts; use protocol-stack framing in technical and AI-native ecosystem contexts.

Why Value Pairs Matter

Most organizations treat values as standalone virtues to display on walls and mention in meetings. But transformation doesn't work that way. Real change happens through reinforcing relationships where strengthening one dimension naturally amplifies its partner.

The TEACH framework recognizes this reality: values exist in dynamic tension that creates momentum. When you build transparency, trust deepens. When trust deepens, transparency becomes safer. This creates virtuous cycles that accelerate growth and multiply impact across our entire team constellation.

Each pair is held simultaneously, not sequentially. Neither half is foundational to the other; both are foundational to the relationship between them.

The Five Value Pairs: Official Definitions

1. Transparent ↔ Trust

Theme: Foundation for genuine collaboration

How We Live This: Open sharing of what works and what doesn't — no manufactured authority through information gatekeeping. Public celebration of wins and honest discussion of challenges.

In Client Relationships: Honest assessment of organizational readiness before selling transformation. Transparent pricing and clear deliverables. Real talk about complexity without manufacturing dependency.

What This Creates:

• Better knowledge transfer through authentic communication
• Faster problem resolution through open collaboration
• Stronger team constellation through trust-enabled sharing
• The speed of trust replacing the friction of guardedness

2. Empathetic ↔ Empowered

Theme: Understanding deeply, acting confidently

How We Live This: Active listening to what people actually need, not what we assume they should want. Supporting individual growth paths rather than forcing standardized journeys.

In Service Delivery: Understanding client constraints before prescribing solutions. Building client capability so they own transformation, not depend on us.

What This Creates:

• More effective transformation through genuine understanding
• Better client outcomes through empowered action
• Stronger team collaboration through respect for different styles
• Enhanced problem-solving through diverse perspectives

3. Agile ↔ Adaptable

⚠ PROPOSED — PENDING CHRIS APPROVAL Content below is drafted by V based on the conceptual framing established in the 2026-04-19 conversation. The live website has not yet been updated for this pair. Chris should review and edit before this canon doc moves to v1.0 finalized status.

Theme: Moving quickly while reshaping form

How We Live This: Building and shipping based on what we know now, then reshaping the form as patterns reveal what good actually looks like. We move quickly, but we don't lock in what we're moving toward — speed without willingness to reshape just sprints us through the wrong shape faster.

In Service Delivery: Engagements that ship working capability quickly rather than perfect plans slowly. When evidence shows the form was wrong, we reshape it openly — the rework is the work, not a deviation from it. Methodology evolves with practice, not with quarterly ritual.

What This Creates:

• Faster value delivery through quick action that adapts as it moves
• Methodology that evolves with evidence rather than locking in past assumptions
• The freedom to reshape without abandoning momentum
• Reduced risk of optimizing the wrong shape at speed

4. Confidence ↔ Conviction

Theme: Clarity that creates action

How We Live This: Operating from earned certainty about what works and what doesn't — built through patterns, not assumptions. Bringing clarity to conversations that enables others to close themselves. Saying no to misalignment, "almost" fits, and impressive-sounding distractions. Making decisions easier by knowing which questions actually matter.

In Client Relationships: The outcome isn't answers — it's clients who know they're right and can act on it. We give people the confidence to understand they can do most of what we're talking about until they prove they can't. When clients say "they gave us confidence to know how to impact change within our organization," that's the testimonial we're building toward. Not "they did it for us" — but "now we know how."

What This Creates:

• Faster decisions through clarity rather than endless analysis
• Sustainable transformation through client conviction, not consultant dependency
• Scalable impact because confidence transfers to everyone we work with
• The freedom to focus on what matters by releasing what doesn't

5. Humble ↔ Hungry

Theme: Learning continuously while driving forward

How We Live This: Active learning culture where everyone shares discoveries. Innovation encouraged through safe experimentation without fear of failure.

In Client Engagement: Continuous methodology refinement based on implementation learning. Regular feedback seeking from clients and team members.

What This Creates:

• More effective transformation through ongoing discovery
• Better client outcomes through fresh approaches
• Stronger team development through mutual learning
• Enhanced methodology through collective intelligence

Quick Reference Card

THE TEACH VALUES

T - Transparent ↔ Trust         — Foundation for genuine collaboration
E - Empathetic ↔ Empowered      — Understanding deeply, acting confidently
A - Agile ↔ Adaptable           — Moving quickly while reshaping form
C - Confidence ↔ Conviction     — Clarity that creates action
H - Humble ↔ Hungry             — Learning continuously while driving forward

Pattern: [Capability A] ↔ [Capability B]
Each pair held in productive tension, not hierarchy.

Living the Framework

Individual Level

Regular self-assessment: Which value pairs am I strengthening? Where am I creating friction instead of flow? Personal development planning based on honest gaps, not aspirational thinking. Building pattern recognition until clarity emerges naturally — confidence earned through practice, not claimed through assertion.

Team Level

Coordination aligned with value pairs — our constellation model embodies these principles. Contribution-based engagement respecting different strengths and working styles. Shared conviction about what matters accelerates decisions across the team. We express conviction without arrogance — helping collaborators find their own clarity.

Client Level

Service design reflecting interdependent values throughout every offering. Relationship development built on trust and transparency from first contact. The goal of every engagement is clients who know they're right and can act on it. Success measured by how decisively clients move forward, not by how much they need us afterward.

Usage Rules

Naming Conventions

DO Use:

• The ↔ symbol (Unicode U+2194) between pair halves — indicates interdependence
• Full pair names on first reference (e.g., "Transparent ↔ Trust")
• "The TEACH Values" or "the TEACH framework"
• The acronym order: T, E, A, C, H

DO NOT Use:

• "vs", "and", "/", or "→" between pair halves (these change the meaning)
• "TEACH method," "TEACH model," or "TEACH system" (it's a framework of values, not a method)
• Standalone halves as if they were independent values (e.g., "we're transparent" without "trust" implied)
• A different ordering of the pairs

When Referencing Pairs

1. Full reference on first mention — Use complete "X ↔ Y" format (e.g., "Confidence ↔ Conviction")
2. Short reference after introduction — Can use the pair name as shorthand, but never split the pair
3. Never invert — "Confidence ↔ Conviction" not "Conviction ↔ Confidence"
4. Never substitute — Don't replace one half with a synonym

When Discussing the Framework

1. Emphasize productive tension — Both halves are simultaneously true; neither precedes the other
2. Honor the pair structure — Avoid framings that treat the halves as separate values
3. Connect to operating posture, not methodology — TEACH is how we show up, not what we do
4. Use brand-facing or protocol-stack framing based on context — see "What is the TEACH Values Framework?" above

Common Errors to Avoid

Naming Errors

Wrong:

• "TEACH stands for Transparent, Empathetic, Accessible, Confident, Humble" — these are halves of pairs, not standalone words
• "Transparent and Trust" — uses "and" instead of ↔, loses the productive tension
• "Confidence/Conviction" — uses "/" instead of ↔, looks like alternatives rather than interdependence
• "Conviction ↔ Confidence" — wrong order

Right:

• "Transparent ↔ Trust"
• "The TEACH framework consists of five interdependent value pairs"

Conceptual Errors

Wrong:

• "First we build transparency, then trust follows" — implies sequence; the pair is held simultaneously
• "Confidence is more important than conviction" — implies hierarchy; both are simultaneously load-bearing
• "TEACH is our methodology" — TEACH is operating posture, not methodology
• "TEACH is our brand values" — TEACH is operating posture, which is broader than brand expression

Right:

• "Transparent and Trust reinforce each other in a virtuous cycle"
• "TEACH defines how anyone — human or AI — shows up while doing Value-First work"

Deprecated Pairs

The following pairs were used in earlier versions of the framework and should never appear in current content:

• Character ↔ Competence — replaced by Confidence ↔ Conviction (live on website)
• Accessible ↔ Authority — replaced by Agile ↔ Adaptable (finalized 2026-04-19; live website update pending)

When reviewing existing content, replace deprecated pairs with their current equivalents.

Governance Process

When Creating New Content

1. Check this reference before writing any TEACH content
2. Use the Quick Reference Card to verify exact pair names and themes
3. Reference brand-facing or protocol-stack framing based on audience
4. Honor the productive tension structure — don't separate pairs

When Reviewing Existing Content

1. Search for deprecated pairs (Character ↔ Competence, Accessible ↔ Authority) and replace
2. Verify ↔ symbol usage — replace "vs", "and", "/" between halves
3. Check ordering — TEACH order, both within acronym and within each pair
4. Note document and location of corrections for tracking

When Uncertain

1. Default to this document — it is authoritative
2. Default to the verbatim website content for the four established pairs (T, E, C, H)
3. Flag the proposed Agile ↔ Adaptable content if used in client-facing material before Chris finalizes
4. Ask Chris if this document doesn't address the question
5. Propose updates through proper channels (don't create variations)

Version Control

• This document may only be updated by Chris Carolan or with explicit approval
• All updates must include version increment and date
• Previous versions should be archived, not deleted

Changelog

Notes on Pending Updates (as of v1.0)

Live website state at canonization (May 6, 2026):

• valuefirstteam.com/about displays the deprecated Accessible ↔ Authority pair
• Update to Agile ↔ Adaptable is pending implementation
• All other content matches this canonical reference

This canonical reference reflects the finalized framework. When the live website is updated, the verbatim website content should be reconciled against the proposed Agile ↔ Adaptable content in this document — either the website matches what's here, or this document gets updated to reflect Chris's preferred final wording.

Related Documents

This canonical reference should be used alongside:

• VCP Canonical Reference (defines TEACH as protocol-stack operating posture)
• Five Core Beliefs Canonical Reference (philosophical foundation; TEACH is the corresponding operating posture)
• Value-First Brand voice and identity guidelines
• Contributor Engagement Guide (uses TEACH as foundational reading for new contributors)
• valuefirstteam.com/about live page (brand-facing rendering of TEACH)
• VCP Positioning Paper (May 2026; uses protocol-stack framing)
• Any client-facing material referencing how Value-First shows up
• Any contributor onboarding or constellation coordination material

When in doubt, check this document.

Value-First Team — Connect. Magnify. Multiply.