playbook:start [Chenla Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Chenla Playbook ======

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.

===== How to Use This Playbook =====
  * Read sections as needed; they are modular.
  * When improving a process, update the relevant page (or propose changes).
  * Keep the Playbook concise — remove redundancy, elevate essentials.
  * Treat it as a tool for clarity, not bureaucracy.

===== Sections =====

**Branding**  
Guidance for how Chenla presents itself publicly.  
  * [[playbook:branding:linkedin_banners|LinkedIn Banners]]

**Communication**  
Shared norms and expectations for how we communicate, especially in a distributed environment.  
  * [[playbook:communication:introductions|Introductions]]

**Remote Work**  
  * [[playbook:remote_work:start|Remote Work]]

**People**  
Rituals and structures that support growth, alignment, and onboarding.  
  * [[playbook:people:onboarding_milestones|Onboarding Milestones]]

**Performance**  
Lightweight structures for evaluating progress without micromanagement.  
  * [[playbook:performance:kpis|KPIs]]

**Principles**  
The deeper reasoning behind how we operate — the lenses that shape decisions.  
  * [[playbook:principles:deep|Deep Principles]]

**Rituals**  
Recurring practices that maintain clarity, alignment, and momentum.  
  * [[playbook:rituals:office_transition|Office Transition]]

**SOPs**  
Operational guides and templates for consistent execution.  
  * [[playbook:sop:start|Standard Operating Procedures]]

===== 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.