General Lesson Instructions
Click to Expand General Instructions
Click to Collapse
Coach's Note
Preamble: The Critical Distinction
Roles vs. Functions
Welcome to Lesson 1. You've successfully completed the foundational quiz and the prerequisite Guardrail Excavation work. Our mission now is to take the Active Rules you created and convert your defensive Guardrails (Active Rules) into positive Core Standards, mapping them to the four Functional Engines to build your complete code of conduct.
Reminder: Your changing emotional Roles (The Driver) must be supported by the fixed, objective Functional Archetypes (The Engines: Executive, Professional, Personal, Aspirational).
Why this matters now: Your stress and burnout are a signal that your Roles are overloading your Engines. Our task today is to define the non-negotiable Core Standards for each Engine. We do this by reverse-engineering them from the Guardrails you already set. These Standards act as the ultimate boundary required to protect your Resource-Holding Capacity (RHC) and keep your system running optimally.
1
Mapping Your Roles to Standards
Finding Your Core Values
In your Prerequisite work, you established Guardrails (The Active Rules): these were reactive boundaries set to prevent a violation. Now we're going to reverse-engineer your Core Values from these rules.
Step A: Identify the Stress Result (The Pain Type)
Start by looking at one of your Active Rules (Guardrails). Ask yourself: "If I were to break this rule right now, where would I experience the immediate, measurable stress (the RHC drop)? What is the result of that failure?"
Step B: Determine the Engine (Mapping the Pain)
Use the Engine Mapping Validation Table below to match your identified Stress Result to the corresponding Functional Engine.
Step C: Name the Standard
With the Engine anchored, ask: "What fundamental state (or condition) does this Rule protect me from losing in that specific Engine?" The single word or short phrase that answers this is your Core Value (Standard).
Part 1: Guardrail Translation
Click to Expand Guardrail Translation Instructions
Click to Collapse
How to Use - Part 1 General Translation Form
Active Rule
Your Active Rules (Guardrails) from the prerequisite lesson are automatically inserted; you can also add a new active rule manually by pressing the ADD RULE button.).
STEP A: Stress Result (The Pain Type)
Document the immediate, measurable drop in performance or capacity that breaking this rule would cause (the RHC Drain Signal). This is the tangible result of the failure (e.g., feeling scattered, chronic irritability, delivering late).
Ask Yourself: "If I were to break this rule right now, where would I experience the immediate, measurable drop in performance or capacity?"
STEP B: Engine (Functional Archetype)
Objectively match the identified Stress Result (RHC Drain Signal) to the corresponding Functional Engine. The four fixed Engines are Executive, Professional, Personal, and Aspirational.
Ask Yourself: "Which Engine is protecting my Focus, my Excellence, my Rest, or my Legacy?"
STEP C: Core Value (The Standard)
With the Engine anchored, identify the single, fundamental state or condition that this Rule permanently protects you from losing in that specific Engine. This single word or short phrase is your Core Standard (e.g., Sovereignty, Excellence, Focus).
Ask Yourself: "What single, fundamental state does this Rule permanently protect me from losing in that specific Engine?"
Part 1: Guardrail Translation
▼
For each Guardrail (Rule), identify the Stress Result, determine the Engine, and name the Core Value (Standard)
Active Rule 1
- Your Guardrail (From Prerequisite work)
- Your Guardrail (Manually Inserted)
X
I'm a paragraph. Click here to add your own text and edit me. It's easy.
You have reached your maximum core values for this Engine.
Click the expand icon (▼) to view, edit, manually add, or save your active rule translations.
NO DATA MESSAGE
Coach's Note: Those words you just wrote in the Core Value column? Those are your first authentic Core Values! We didn't choose them from a list; we derived them from the rules you set to protect yourself from stress
Part 2: The Two-Week Stress Test - Filling the Gaps
Click to Collapse
Click to Expand Two Week Stress Test Instructions
We need 3 to 5 Core Values per Engine to ensure the entire system is stable. If you haven't filled out an Engine yet, use the Two-Week Stress Test to find the missing standards.
NOTE: For a true, reliable "Fixed Operating System" diagnosis, having at least three Core Values defined for all four Functional Engines is the most rigorous and necessary constraint.
The Stress Test Protocol (Your Human Litmus Test)
Ask yourself this question about any potential new value:
"If I completely ignore this standard for two weeks, will it cause immediate, measurable stress or burnout (a drop in my RHC)?"
If the Engine Fails: Its a Core Value
If the Engine Runs Fine: Its a nice goal, not a critical standard
How to Use Part 2: Functional Engine & Standard Map (Stress Test)
The goal of this phase is Operational Assurance by building a resilient, redundant system of Standards. You need 3 to 5 Core Values per Engine to ensure comprehensive systemic stability and prevent the "Single Point of Failure" that occurs when an Engine relies on only one or two standards
Review Gaps
The workbook will display all the Core Values you identified in Part 1 for each Engine. It will highlight where you have fewer than the minimum of three standards required per Engine.
Use the Stress Test Protocol:
For any Engine with fewer than three standards, you can add more by pressing the + ADD STANDARD button. This will take you nack to the prior form to manually add additional data. You will need at least 3 entries for each engine.
Use the following question to determine if a potential new standard is critical or merely a preference:
"If I were forced to completely ignore this standard for two weeks, would it cause an immediate, measurable drop in performance, anxiety, or burnout (a drop in my RHC) in the corresponding Engine?"
Action
If the answer is Yes, the standard is critical and a Core Value that must be included. If the answer is No, it is a preference and must be discarded.
Complete the Map:
Continue this process until you have at least 3 (and up to 5) Core Values per Engine.
Part 2: The Functional Engine & Standard Map
▼
Complete your Core Value Map with 3-5 non-negotiable standards for each Engine.
Click the expand icon (▼) to view your Core Values, grouped by Functional Engine.
NO DATA MESSAGE
-
Engine Title
-
Engine Count
Value Name Slot
Part 3: The Initial Conflict Scan - Your Core Conflict
Click to Collapse
Click to Expand the Initial Conflict Scan Instructions
How to Use Part 3: The Initial Conflict Scan (Assignment)
With your stable system of Standards defined, this final assignment isolates the single most critical point of systemic friction that is driving most of your RHC drain.
Engine Conflict Pair
Identify the two Engines that are currently battling the most for your finite time and energy. Look for the most frequent source of internal guilt or stress. (e.g., Professional vs. Personal )
Standard Clash 1 (From the first Engine)
Select the one specific Core Value from your first chosen Engine that is in direct, frequent conflict with a value from the second Engine. (e.g., Responsiveness from Professional)
Standard Clash 2 (From the second Engine)
Select the one specific Core Value from your second chosen Engine that is in direct conflict with the first value (when you satisfy one, you immediately fail the other). (e.g., Deep Rest from Personal)
Working Hypothesis (Diagnosis)
Formulate the conflict clearly and objectively into a concise statement. This is the single, specific problem that Lesson 2 will solve. (e.g., "The conflict between my Professional Archetype's value of Responsiveness and my Personal Archetype's value of Deep Rest is causing chronic burnout.")
Example Conflict Hypothesis: "The conflict between my Professional Archetype's value of Responsiveness and my Personal Archetype's value of Deep Rest is causing chronic burnout."
After you submit teh Hypothesis, you will see a Lesson Complete window appear just below summarizing your data in an organzied table and paragraph. Yiu will aslo see next steps.
Part 3: The Initial Conflict Scan (Complete Part 2 First!)
Identify your primary Engine conflict and formulate your Working Hypothesis.
First Conflicting Engine
Second Conflicting Engine
ERROR TEXT
Lesson Complete
Conclusion: Setting the Stage for Change
Great work! You've just completed the most foundational step of this entire process.
-
You went from Rules to Standards: You took your reactive Guardrails (Rules) and reverse-engineered the authentic Core Values (Standards) that these rules were trying to protect.
-
You mapped your Fixed System: You finalized your Functional Engine & Standard Map, defining the 3-5 non-negotiable operating standards for your four engines.
-
You identified the Core Conflict: You developed a Working Hypothesis that names the two Engines and the specific Standards that are clashing most often.