Most project management content on the internet was written for a 50-person SaaS company in San Francisco. It assumes pre-existing tooling budgets, predictable internet, and a workforce that all sit in the same time zone. African agencies don't operate that way — and the playbook needs to be different.
This is what we've learned from talking to studios, growth agencies, and software shops across Lagos, Nairobi, Accra, and Cape Town: how the best ones plan their work. Steal what fits.
1. Default to async — but defend the standup
Power cuts, traffic, multi-office teams. Trying to enforce 9-5 synchronous standups burns out the team and excludes the best talent (who often work odd hours to leverage US/EU client overlap). Default to async updates in writing.
BUT — defend a 30-minute weekly sync where everyone is video-on. Async kills informal mentorship. The weekly sync is where junior team members hear how senior ones think.
2. Plan in cycles, not quarters
Quarterly planning works at companies with 18-month roadmaps. Most African agencies don't have those — they have a 6-week pipeline and a 3-month wishlist. Plan in 2–4 week cycles instead. End each cycle with a retro that drops anything not delivered, and add new work from the backlog.
This is exactly why Prozari's sprint cycles default to 2-week cycles, not arbitrary quarter blocks. Built for the reality.
3. One tool, one source of truth
Most agencies we've seen have: client work in a Trello, internal work in a Notion, marketing campaigns in a Google Sheet, and design assets in a WhatsApp group. Each handoff between those tools is a place where work falls through the cracks.
Consolidate. Pick one tool that can hold engineering tasks, marketing campaigns, content calendar, asset library, and team docs in the same workspace. The cost of a slightly more expensive tool is way less than the cost of work falling between four free ones.
4. Track WIP, not "Done this week"
The default agency planning report is "what did we ship this week." It's a vanity metric. The number that actually matters is WIP (work in progress): how many cards are sitting in your "Doing" column right now.
If WIP is high and rising, your team is overloaded — work is starting but not finishing. If WIP is low and rising, you're under-utilised. The healthy state is WIP that stays roughly flat over a 2-week cycle.
Prozari shows WIP per list directly on the board, with WIP limits you can configure. Crossing the limit highlights the column red.
5. Document decisions, not just tasks
The biggest knowledge loss in agencies happens when a senior person leaves: every decision they made walks out the door with them. Why did we pick that vendor? Why did we shape the campaign that way? Why did we deprecate that integration?
Run a lightweight "decision log" — a single doc page per quarter with one-paragraph entries: Date, Decision, Why, Who decided. Three minutes per decision, infinite value when the next person inherits the project.
(Prozari Docs has an ADR template that's good for this; one of the more loved features for engineering teams.)
6. Bill in naira, plan in naira
If you're invoicing local clients in naira but paying for tools in dollars, your margin shifts every time the rate moves. Whenever possible, match your cost currency to your revenue currency. It's not glamorous; it's how agencies keep margins predictable.
7. The "two-week-from-now" rule
Plan only what you can confidently commit to two weeks from now. Anything beyond that goes in a "Maybe" backlog, not a hard plan. This sounds obvious but most agencies still try to plan eight weeks of work, watch reality diverge by week 3, and then re-plan in a panic.
Two weeks of confident planning + a maybe-list beats eight weeks of fictional planning every time.
The takeaway
Agency planning isn't about copying methodologies from Silicon Valley playbooks. It's about matching the rhythm of how your team actually works to the tooling you use. Build the rhythm first; pick the tool that fits the rhythm second.