playbook:performance:kpis [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.
====== Cross-Team KPI Framework ======

This document defines a modular, department-specific KPI framework designed for clarity, delegation, and system scalability across all teams at Chenla Agathos Solutions.

===== Core Principles =====
  * KPIs must be measurable, actionable, and directly influenceable by the team.
  * Each KPI should align with a recurring ritual (weekly check-in, monthly reset, etc).
  * Ownership is decentralized: teams are responsible for tracking and reflecting.
  * KPIs evolve: archived when mastered, replaced with higher-leverage indicators.

===== Project & Construction Management =====
  * % of milestones delivered on time
  * Actual vs Estimated cost variance per project
  * # of client change requests or defect reports per project
  * # of weekly site reports submitted on time
  * % of lookahead tasks completed as forecasted
  * % of tasks delegated to site team vs self-performed

===== Quantity Surveying (QS) =====
  * % of cost deviations caught before procurement
  * Avg. # of days to submit BOQ or variation orders
  * # of approved variation orders per project/month
  * % of documents with complete backup evidence (e.g., DokuWiki uploads)
  * # of new or updated QS-related SOPs/month

===== Finance & Accounting =====
  * % of transactions recorded within 3 working days
  * % of accounting data entered into ERP vs external tools
  * # of corrections flagged by monthly review
  * # of published weekly/monthly internal finance reports
  * # of DokuWiki updates to accounting procedures or logs

===== HR & Administration =====
  * % of staff attendance records updated weekly
  * % of onboarding checklist completed per new hire
  * % of weekly admin summaries shared in internal channel or wiki
  * Avg. response time to internal support requests
  * # of administrative files created, cleaned, or updated monthly

===== CEO / Systems Leadership =====
  * % of recurring strategic decisions handled without CEO involvement
  * # of SOPs or systems created by team members
  * % of GPT-generated insights harvested and integrated
  * # of decisions embedded into playbooks or frameworks
  * Progress rating across 3 strategic objectives/month

===== Implementation Notes =====
  * Start with 3–5 KPIs per team.
  * Assign an owner per KPI to report or reflect, not to punish.
  * Review frequency:
    - Weekly for operational rhythm (e.g. standups)
    - Monthly for strategic adjustments
  * All KPIs should be tracked in an open, transparent format (e.g. Grist, Redmine, or DokuWiki dashboards).
  * Teams may propose to retire or evolve KPIs after sustained success or process maturity.