Skip to content

Ways of Work — Scope Document

Owner: CDO Date: 5 April 2026 Status: Scoping — for next session build Purpose: Map every Ways of Work document needed across Simpaisa, to be built in a dedicated session.

What "Ways of Work" Means

The Operating Model (OpModel repo) defines WHAT each function does. Ways of Work defines HOW they do it day-to-day: - Meeting cadences and agendas - Sprint/delivery rhythms - Communication norms (Slack channels, email, escalation) - Collaboration patterns (cross-functional, cross-market) - Decision-making protocols within teams - Onboarding checklists for new joiners - Tool usage standards (Jira, Confluence, Slack, Bitbucket, etc.) - Reporting obligations (what, to whom, when)

Documents Needed

Company-Wide (applies to all)

# Document Description Depends On
W-01 Company Operating Rhythm Annual, quarterly, monthly, fortnightly, weekly cadence for the whole company. What meetings exist at each level, who attends, what decisions are made. STD-GOV-135 (Execution Framework)
W-02 Communication Standards Slack channel naming, email protocol, when to Slack vs email vs call. Escalation norms. Meeting-free blocks. Time zone etiquette (staff across PK, BD, NP, IQ, AE, Dubai). —
W-03 Tool Standards Which tool for what purpose. Jira for X, Confluence for Y, Slack for Z, Bitbucket for code, Beads for architecture. No shadow IT. —
W-04 Cross-Functional Collaboration Playbook How divisions work together on cross-cutting initiatives. RASCI for common scenarios. Handoff protocols between CDO↔COO, CDO↔CFO, Commercial↔COO. STD-GOV-137 (Department Mandates)
W-05 New Joiner Onboarding Framework First day, first week, first month, first quarter. Per-division onboarding checklists. Access provisioning. Knowledge base orientation (Maerifa). —

CDO Division (Product, Security, Data, Technology)

# Document Description Owner
W-10 Engineering Ways of Work Sprint cadence, PR review process, CI/CD expectations, on-call rotation, incident response, code review standards, testing requirements. For all engineering teams (Pay-In, Pay-Out, Portal, DevOps, SQA). CTO
W-11 Product Ways of Work Product discovery process, requirement writing standards, backlog management, sprint planning, stakeholder reviews, release cadence. CPO
W-12 Security Operations Ways of Work SOC operations, vulnerability scanning cadence, pen test scheduling, incident classification, security review triggers, compliance reporting. CISO
W-13 Architecture Practice Ways of Work ARB cadence, ADR submission process, standards review, Confluence publishing, Maerifa maintenance. CDO (exists as STD-GOV-138, needs operational detail)
W-14 Data Team Ways of Work Data governance meetings, data quality monitoring, retention enforcement, analytics request process, dashboard maintenance. Data Lead (TBD)

COO Division (Operations)

# Document Description Owner
W-20 Operations Ways of Work Daily operations cadence, transaction monitoring, settlement process, partner escalation, SLA tracking, shift handover protocols. COO
W-21 Partner Management Ways of Work Partner onboarding process, monthly performance reviews, SLA enforcement, escalation to CDO for technical issues, partner offboarding. COO
W-22 Country Operations Ways of Work Per-country operational cadence. How country teams interact with central functions. Regulatory reporting obligations. Local incident response. Country Heads

CFO Division (Finance)

# Document Description Owner
W-30 Finance Ways of Work Month-end close process, settlement reconciliation cadence, treasury operations, financial reporting calendar, budget review cycle. CFO
W-31 Compliance & Regulatory Ways of Work Regulatory reporting calendar (per market), STR filing process, audit preparation, licence renewal tracking, compliance monitoring cadence. Global Head Regulatory

Commercial Division

# Document Description Owner
W-40 Commercial Ways of Work Sales pipeline management, merchant acquisition process, pricing approval workflow, quarterly revenue review, market development cadence. Commercial Head

HR

# Document Description Owner
W-50 People Operations Ways of Work Hiring process, performance review cycle, learning & development, offboarding, employee engagement cadence. Head of HR

Relationship to Existing Documents

OPERATING MODEL (OpModel repo)
  "What each function does, its mandate, its governance"
          │
          ▼
STANDARDS (Architecture repo)
  STD-GOV-135: Execution Framework (initiative lifecycle)
  STD-GOV-136: Performance Management (metrics, reviews)
  STD-GOV-137: Department Mandates (who owns what)
  STD-GOV-138: Architecture Practice Charter
          │
          ▼
WAYS OF WORK (to be built)
  "How each team actually operates day-to-day"
  Meeting cadences, sprint rhythms, tool usage,
  communication norms, onboarding checklists

Build Sequence

Priority Documents Rationale
1 W-01 (Company Operating Rhythm) Sets the heartbeat everything else syncs to
2 W-10 (Engineering) + W-11 (Product) CDO's own teams. Lead by example.
3 W-02 (Communication) + W-03 (Tools) Cross-cutting, affects everyone
4 W-04 (Cross-functional) + W-05 (Onboarding) Enables collaboration and scaling
5 W-20 (Operations) + W-30 (Finance) Other divisions
6 W-12 (Security) + W-14 (Data) CDO sub-teams
7 Everything else Commercial, HR, Country, Partner

Estimated Effort

Task Human CC
Company-wide docs (W-01 to W-05) 2 weeks ~2 days
CDO division docs (W-10 to W-14) 2 weeks ~2 days
Other division docs (W-20 to W-50) 2 weeks ~2 days
Review and refinement 1 week ~1 day
Total ~7 weeks ~7 days

Input Required

Before building, the next session needs: 1. Tool decisions — which tools does Simpaisa actually use? (Jira? Confluence? Slack? Teams? Something else?) 2. Current meeting cadence — what meetings already exist? Don't reinvent, document. 3. Sprint cadence — do engineering teams run sprints? What length? What ceremonies? 4. Country operations — how do PK, BD, NP, IQ, EG currently operate day-to-day?

These can be gathered from the operating model docs and the leadership team.