Differences

This shows you the differences between two versions of the page.

--- playbook:start [2025/05/16 01:29] – created marcel
+++ playbook:start [2025/12/08 08:47] (current) – marcel
@@ Line 1: / Line 1: @@
-===== 📘 Company Playbook =====
+====== Chenla Playbook ======
-This section defines the strategic principles, escalation paths, and coordinated responses for high-impact decisions and recurring operational patterns. It is not about step-by-step procedures, but **how we think, decide, and act consistently across the company**.
+The Playbook is the shared reference for how Chenla works: the expectations, rituals, and systems that help the team operate with clarity and autonomy. It is not a rulebook. It is a living map of how we collaborate, make decisions, and maintain coherence across distributed work.
-----
+===== Purpose =====
+  * Give every team member a clear understanding of how Chenla operates.
+  * Provide reusable structures for communication, planning, and feedback.
+  * Reduce coordination overhead by making expectations explicit.
+  * Support autonomy: people know what “good” looks like without waiting for instructions.
-==== 🧭 Core Playbook Entries ====
+===== How to Use This Playbook =====
-  * [[playbook:escalation_paths|🚨 Issue Escalation Paths]] (to be created)
+  * Read sections as needed; they are modular.
-  * [[playbook:decision_making|🎯 How We Make Decisions (Decision-Making Protocols)]] (to be created)
+  * When improving a process, update the relevant page (or propose changes).
-  * [[playbook:communication_rhythm|📅 Weekly & Monthly Communication Rhythm]] (to be created)
+  * Keep the Playbook concise — remove redundancy, elevate essentials.
-  * [[playbook:client_escalation|📞 Client-Facing Escalation Protocols]] (to be created)
+  * Treat it as a tool for clarity, not bureaucracy.
-  * [[playbook:crossborder_projects|🌐 Cross-Border Project Playbook (Cambodia–Thailand)]] (to be created)
-----
+===== Sections =====
-==== 🎓 Cultural Principles & Behavior ====
+**Branding**
-  * [[playbook:values_in_action|💬 Company Values in Action]] (to be created)
+Guidance for how Chenla presents itself publicly.
-  * [[playbook:what_good_looks_like|🏆 What “Good” Looks Like – Quality Benchmarks]] (to be created)
+  * [[playbook:branding:linkedin_banners|LinkedIn Banners]]
-  * [[playbook:trusted_judgment|🧠 Developing Trusted Judgment]] (to be created)
-----
+**Communication**
+Shared norms and expectations for how we communicate, especially in a distributed environment.
+  * [[playbook:communication:introductions|Introductions]]
-==== 📄 Templates ====
+**Remote Work**
-  * [[templates:decision_log|📝 Strategic Decision Log Template]] (optional)
+  * [[playbook:remote_work:start|Remote Work]]
-  * [[templates:escalation_map|🚦 Escalation Flowchart Template]] (optional)
-  * [[templates:_template|🧾 SOP/Playbook Page Template]] (shared)
-----
+**People**
+Rituals and structures that support growth, alignment, and onboarding.
+  * [[playbook:people:onboarding_milestones|Onboarding Milestones]]
-==== 📚 Resources ====
+**Performance**
-  * [[meta:contributor_guide|🛠 Contributor Guide]]
+Lightweight structures for evaluating progress without micromanagement.
-  * [[meta:dokuwiki_syntax|📖 DokuWiki Syntax Guide]]
+  * [[playbook:performance:kpis|KPIs]]
-----
+**Principles**
+The deeper reasoning behind how we operate — the lenses that shape decisions.
+  * [[playbook:principles:deep|Deep Principles]]
-**Next Steps:**
+**Rituals**
-- Begin by writing one or two key escalation scenarios your team faces regularly
+Recurring practices that maintain clarity, alignment, and momentum.
-- Add actual cases where a decision path worked well (or failed), and what was learned
+  * [[playbook:rituals:office_transition|Office Transition]]
-- Link to SOPs, policies, or communications that support these protocols
-----
+**SOPs**
+Operational guides and templates for consistent execution.
+  * [[playbook:sop:start|Standard Operating Procedures]]
-{{tag>index playbook escalation strategy decision-making}}
+===== Contributing =====
+  * Use simple, direct language.
+  * Keep pages short unless depth is required.
+  * Prefer structure over narrative.
+  * When unsure where something belongs, add it temporarily and we will refactor as needed.
+This Playbook evolves with the company. When the system improves, the Playbook improves.