GuideOSGuideOS™

ORGANIZATION SETUP GUIDE

GuideOS Setup Guide

Your complete guide to installing the Leadership Behavior Operating System. Follow each step in order to move from observation to full governance.

Level 1

Observer

Define what winning looks like and understand who your leaders are under pressure.

1

Step 1: Define Winning

Navigate to: GuideOS System > Clear Winning > Score & Guardrail

What you will do:

  • Choose the one primary result metric (the Score) that settles arguments
  • Choose the one boundary metric (the Guardrail) that constrains how you chase the Score
  • Lock the Score and Guardrail as the official measures of success

Why it matters: Without a locked Score and Guardrail, every leadership conversation devolves into opinion.

Done when: The Score & Guardrail page shows a green "Locked" status.
2

Step 2: Reveal Identity

Navigate to: GuideOS System > Leadership Installs > Identity

What you will do:

  • Complete your own GuideType behavioral assessment
  • Invite your leadership team to complete their assessments
  • Review results: behavioral archetype, pressure defaults, communication tendencies

Why it matters: You cannot govern behavior you do not understand. Identity is the foundation of all behavioral standards.

Done when: At least one leader has a completed GuideType profile.
Level 2

Practitioner

Install the behavioral mechanics that make leadership inspectable.

3

Step 3: Lock Leadership Checks

Navigate to: GuideOS System > Leadership Installs > Behavior

What you will do:

  • Define 3 to 5 binary yes/no questions leaders answer weekly
  • Write each check as a clear, observable behavior
  • Examples: "Did I have a documented 1:1 with every direct report?" or "Did I address a performance issue within 24 hours?"

Why it matters: If leadership behavior is not inspected weekly, tolerance expands silently.

Done when: You have 3-5 active Leadership Checks defined.
4

Step 4: Define Tolerance

Navigate to: GuideOS System > Leadership Installs > Tolerance

What you will do:

  • Conduct a Tolerance Audit: identify where your organization has silently accepted sub-standard behavior
  • Name each tolerance item specifically
  • Categorize by severity and assign ownership

Why it matters: Drift not named is drift tolerated. The Tolerance Audit forces you to name what has quietly eroded.

Done when: At least one tolerance item is identified and documented.
5

Step 5: Lock Standards

Navigate to: GuideOS System > Leadership Installs > Standards

What you will do:

  • Create Stop commitments: behaviors that must cease immediately
  • Create Start commitments: new behaviors that must begin
  • Create Protect commitments: behaviors that are working and must be defended

Why it matters: Standards not explicitly declared are not standards; they are preferences.

Done when: At least one commitment in each category (Stop, Start, Protect).
Level 3

Certified

Establish the weekly governance rhythm that keeps the system alive.

6

Step 6: Lock Weekly Governance (MMI)

Navigate to: GuideOS System > Weekly Governance > MMI Cadence

What you will do:

  • Set your MMI (Monday Morning Implementation) cadence
  • Choose your facilitator type (internal or external)
  • Run your first full MMI session through the 6-step process
  • Commitments from each session become tracked action items

Why it matters: If nothing changes Monday morning, nothing changed. The MMI prevents the operating system from becoming shelf-ware.

Done when: You have completed at least one full MMI session.
Level 4

Install Leader

Verify the system is self-sustaining and producing results.

7

Step 7: Confirm Performance

Navigate to: GuideOS System > Performance > Org Diagnostic

What you will do:

  • Run the Organizational Diagnostic to assess system health
  • Review indicators: green (healthy), yellow (at risk), red (needs attention)
  • Confirm all prior steps are complete and the MMI cadence is active

Why it matters: Performance is the proof that governed behavior produces results.

Done when: The Organizational Diagnostic confirms all systems are healthy.

The MMI Session: Weekly Governance Loop

The Monday Morning Implementation is the heartbeat of the operating system. It follows this structured process every week:

0

Review Last Week’s Commitments

Review outstanding commitments from previous sessions. Mark complete or carry forward.

1

Score Review

Did we win this week? Review the primary result metric.

2

Guardrail Review

Did we win the right way? Check the boundary metric.

3

Leadership Checks

Review weekly yes/no behavioral checks. Any "No" triggers a recovery conversation.

4

Drift Identification

Name what drifted this week. Be specific.

5

Recovery

Name the drift, restate the standard, declare recovery, reset tolerance.

6

Recommitment

Each leader makes one observable behavioral commitment for the coming week.

Ongoing Governance Rhythms

Weekly

  • Run the MMI session
  • Track and complete commitments
  • Use Recovery Protocol when drift occurs

Monthly

  • Review the Tolerance Audit
  • Review Leadership Checks
  • Review Stop/Start/Protect commitments

Quarterly

  • Review the Score and Guardrail
  • Update the Strategic Plan
  • Run the Organizational Diagnostic

Key Principles

GDD is an operating system, not a philosophy. It governs behavior through structure, standards, and weekly inspection.

The Score settles arguments. If you cannot point to one number that defines winning, every conversation is opinion.

The Guardrail constrains how you win. Winning the wrong way is not winning.

If behavior is not inspected weekly, tolerance expands silently.

Drift not named is drift tolerated.

If nothing changes Monday morning, nothing changed.

Recovery is not punishment. Recovery is discipline.

Guide, Don't Drive. The Leadership Behavior Operating System.