Prompt: Create an operations playbook for a 50-person tech company in Johannesburg. Cover: daily/weekly/monthly rhythms, key meetings, escalation paths, and the 5 most important operational KPIs to track.
As you are requesting a comprehensive operational plan, I recommend structuring the output using several distinct sections to ensure clarity and immediate usability for a management team.
I will structure this response by:
- Analyzing the context (Geographic/Company Size).
- Defining core process domains (People, Process, Platform).
- Generating the specific weekly, monthly, and quarterly rhythms.
- Listing the crucial KPIs.
Here is the proposed Operational Playbook for a company of your structure.
*
🚀 Operational Playbook: 50-Person Tech Company (Johannesburg Focus)
Objective: To standardize operational rhythms, ensure cross-functional visibility, and scale processes to support 150% headcount growth without commensurate increases in process debt or operational friction.
Contextual Assumptions:
- Team Size: $\approx 50$ employees (Engineering, Product, Operations/Marketing, Sales).
- Location: Johannesburg, South Africa (Implying local labor laws and market dynamics).
- Stage: Growth Stage (Moving from scrappy founding to repeatable, scalable processes).
1. Foundational Pillars (Operational Domains)
All operations must be governed by these three integrated pillars:
| Pillar | Focus Area | Key Goal | Ownership |
| :--- | :--- | :--- | :--- |
| People (HR/Culture) | Talent Acquisition, Onboarding, Performance Management, Culture fit. | Maintain high employee engagement and low regrettable attrition. | HR / People Lead |
| Process (Product/Sales) | Workflow efficiency, Customer Journey mapping, Feedback loop closure. | Reduce cycle time from idea inception to customer value delivery. | Product / Sales Lead |
| Platform (Tech/Ops) | Infrastructure stability, Tool consolidation, System reliability, Security compliance. | Ensure the technology backbone scales linearly with user/employee growth. | CTO / Engineering Lead |
2. Operational Cadence (The Rhythm)
Consistency is built through predictable meetings that serve a defined purpose.
📅 Daily Rhythms (Tactical & Execution Focus)
- Daily Standups (Team Level): Short (10-15 min). Focus: What did I do yesterday? What will I do today? What is blocking me? (High signal-to-noise ratio).
- "Scrum of Scrums" (Cross-Functional): 30 mins (For Leads/Managers). Focus: Highlighting shared dependencies between Engineering, Product, and Ops. (Key: Proactively identifying dependencies before they break).
🗓️ Weekly Rhythms (Alignment & Prioritization Focus)
- All-Hands / Company Update (All Employees): 45 mins. Focus: Executive vision updates, celebrating wins, articulating the "Why" behind recent pivots. (Culture reinforcement).
- Product/Strategy Deep Dive: 90 mins (Product & Key Stakeholders). Focus: Inspecting the next 2-4 weeks increment. Reviewing recent feature usage data. (Deliverable: Updated, signed-off, prioritized backlog).
- 1:1 Meetings (Manager/Report): 45–60 mins. Focus: Career development, roadblocks, psychological safety, and gathering qualitative feedback (This is where most actionable managerial intelligence is gathered).
📊 Monthly Rhythms (Review & Accountability Focus)
- Business Reviews (Leadership Team): Half-day session. Focus: Deep dive into key metrics (see Section 3). Reviewing departmental budgets, operational expenditure variances.
- Customer Success Review: Dedicated half-day. Focus: Analyzing churn reasons, top feature requests (Voice of Customer), and defining the top 3 improvements for the coming month.
- People Pulse Check: HR-led Workshop. Focus: Gathering anonymous feedback on morale, process friction, and culture health. (Output: One actionable, measurable process change championed by HR).
📈 Quarterly Rhythms (Strategic & Scaling Focus)
- Quarterly Business Review (QBR): Entire executive team. Focus: Hard ROI assessment for the last quarter. Determining if current processes are sustainable for the next 3x growth. Setting OKRs (Objectives and Key Results) for the next 90 days.
- Process Retrospective: Cross-functional workshop. Focus: STOP/START/CONTINUE. Identifying a major process that is broken (e.g., Handoff from Sales $\rightarrow$ Ops $\rightarrow$ Product) and designing a permanent fix.
- Market Benchmarking: Ops/Leadership. Focus: Understanding how successful competitors (in SA and globally) are operating, pricing, and acquiring customers.
3. Key Performance Indicators (KPI Dashboard)
KPIs must be grouped by the pillar they measure to provide actionable insight rather than just rearview mirror reporting.
$\text{People KPIs (Health)}$
- eNPS (Employee Net Promoter Score): Measures internal advocate strength. (Target: Above 40).
- Time-to-Productivity: How long does a new hire take to contribute independently? (Goal: Decrease quarterly).
- Voluntary Attrition Rate: High vigilance required in a competitive local market.
$\text{Process KPIs (Efficiency)}$
- Sales Cycle Length: Time from first contact to signed contract. (Must trend downward).
- Feature Adoption Rate: Percentage of target users who use a new core feature within 30 days of release.
- Support Ticket Resolution Time (TTR): Measures the efficiency of the support backend.
$\text{Platform KPIs (Stability \& Growth)}$
- MTTA (Mean Time To Acknowledge/Respond): For critical systems and customer outreach.
- System Uptime/SLAs: Core platform reliability (Target: 99.9%+).
- CAC Payback Period: How quickly does a customer's revenue cover the cost of acquiring them? (Crucial for financial runway assessment).
*
Summary Action Items for Leadership:
- Institute the 1:1 structure immediately; it is the lowest-overhead, highest-yield meeting for leadership.
- Define the Objective and Key Results (OKRs) template and lock it in for all teams by the end of the current month.
- Audit the current tech stack against the "Platform Pillar" to identify three outdated tools that can be eliminated or consolidated by next quarter.