artifacts/standard-named

Rendered from markdown source. Open raw source on GitHub.

Continuity in Practice — Manager Training Outline

Purpose

Equip managers to support a Continuity-enabled environment without creating friction, bottlenecks, or loss of autonomy.

This training focuses on how to:

• Maintain trust while increasing clarity
• Respond to 🜬 breach signals constructively
• Encourage 🜹 witness without creating bureaucracy
• Translate principles into team norms

---

Format

• 60–90 minute session
• Discussion-heavy
• Scenario-driven

---

0. Opening (10 min)

Goal

Set tone: this is not about control, it’s about better leadership in complex systems

Key Message

Managers are not being asked to:

• approve more
• monitor more
• control more

They are being asked to:

help their teams stay in control without things becoming invisible

---

1. What’s Changed (10 min)

Goal

Create shared understanding of why this matters now

Key Points

• Work now spans tools, AI, people, and policies simultaneously
• Decisions propagate across systems
• Small actions have larger downstream effects

Insight

Most issues are not bad decisions — they are invisible ones

---

2. The Manager’s New Role (15 min)

Old Model

• approve decisions
• review outcomes
• step in when things go wrong

New Model

• enable good decisions at the edge
• reinforce clarity
• interpret signals (🜬, 🜹)

Core Shift

From decision authority → to clarity stewardship

---

3. The Four Signals (Manager View) (15 min)

🝚 Boundary

Where access or scope may be unclear or too broad

🝁 Consent

Where usage or transformation may be inappropriate

🜬 Breach

Where something “feels off” or crosses a line

🜹 Witness

Where actions are made visible and understandable

Manager Role

Not to police these — but to:

• recognize them
• normalize them
• guide responses

---

4. Responding to 🜬 (20 min — critical section)

Goal

Prevent shutdown or fear

Bad Responses

• “Why did you do that?”
• “You should have asked first”
• Overreaction

Good Responses

• “Thanks for flagging that”
• “Let’s walk through it together”
• “What made this feel off?”

Principle

A breach signal is a success, not a failure

---

5. Encouraging 🜹 Without Bureaucracy (15 min)

Goal

Avoid over-logging / over-reporting

Key Message

Witness is not reporting — it is leaving context

Examples

• Slack note
• Comment in doc
• Short async message

Anti-pattern

• requiring formal logs for everything

Principle

If it matters, it should not disappear — but it should stay lightweight

---

6. Preserving Autonomy (10 min)

Goal

Avoid cultural backlash

Key Message

Continuity strengthens trust — it does not replace it

Reinforcement

Managers should continue to say:

• “Use your judgment”
• “Solve problems”

But add:

“Make it understandable when it matters”

---

7. Team Norms (10 min)

Goal

Translate into team-level behavior

Suggested Norms

• It’s okay to flag 🜬 without blame
• It’s normal to leave 🜹 traces
• Not everything needs escalation

Optional

Define where “witness” lives for the team:

• Slack channel
• docs
• tickets

---

8. Calibration Discussion (10–15 min)

Prompts

• Where does your team currently lose visibility?
• Where do people hesitate to raise concerns?
• Where would lightweight witness help most?

---

9. Close (5 min)

Reinforce

Managers are not responsible for controlling everything

They are responsible for:

helping the system remain understandable over time

Final Line

“Don’t require permission. Require clarity.”

---

Outcome

Managers leave able to:

• support autonomy without chaos
• respond constructively to uncertainty
• reinforce lightweight visibility
• reduce hidden risk without adding friction

---

Positioning

This is not management training.

This is:

How to lead when systems are too complex to fully see — and still need to be trusted.