Ritual
Counter hour ritual
Stuck behind one big blocker in your Gqeberha ops? Book a Counter Hour, call it, and reset the pace with your team.
When to start a Counter Hour
You call this ritual when work stalls behind a single stubborn issue, think Sizwe’s Custom Joinery in Gqeberha waiting on a supplier quote to finish three jobs, or Thandi’s Tuition Corner in Albert Park chasing a VAT201 resubmission. The telltale signs? WhatsApp group silence, half-finished checklists, or team mates rehashing the same old problem at the kettle again. As soon as that one snag blocks more than just payroll or the month-end numbers, it’s time. The best trigger is a Monday morning review or a Friday wrap-up, but it works any day when the team feels gridlocked and the regular cadence just isn’t shifting things.
What to do, step by step
A Counter Hour ritual has a strict script, one hour, one priority. The aim is to move the blocker forward just enough to make progress inevitable. In Gqeberha, local teams often use this rhythm to push past port delivery headaches or utility account standstills. Here’s the rhythm with the Counter Hour Charm and Chaos Reset kits handy:
- Set the timer for 60 minutes and all phones on silent but one. That one phone is for emergencies, load-shedding Stage 5, or a client cheque clearing.
- Quick round: Name the single biggest blocker (5 minutes). No long stories, just the facts.
- Nominate a lead (the person closest to the issue) and a scribe (note-taker). Everyone else picks a smaller related task or brings reference info.
- Go deep: Gather documents, emails, supplier notes, screenshots, dump everything linked to this blocker into one shared folder (15 minutes).
- Map three possible moves. Not five, not ten. Three. Choose one as the next step (20 minutes).
- Assign action: Lead takes the main move, scribe types clear follow-up notes, others chase up what’s needed or book supplier calls (15 minutes).
- Wrap: Review actions, set a check-in time for the next move, could be tomorrow’s breakfast, or Friday 3pm before load-shedding bites again (5 minutes).
- Everyone gets copies of the notes and checklist. If no progress by next check-in, reset and run the ritual again.
Roles in a small ops team
In a team of two to ten, mix roles by experience. The founder (in Gqeberha, maybe it’s Nomsa managing a sports shop’s new lease) calls the ritual and books the hour. The lead owns the main next step; the scribe captures everything on the checklist. Others might be an admin, bookkeeper, or ops coordinator. If you’re running this from Vereeniging, the same rules work, just make sure the right supplier is on call if needed. Each person should leave knowing exactly what’s next, not just for themselves but for the team.
SA traps and how to close it out
South African teams hit a few classic traps: getting sidetracked by load-shedding schedules, dropping the ritual because of a single team absence, or letting WhatsApp group chat swallow real follow-up. The other is skipping the finish, just because you’re out of time doesn’t mean you’re done. The last five minutes must always recap action points, set the next check-in, and file the follow-up notes. Store them in your shared cloud drive or even just in a labelled A5 notebook (seen alot of those at supplier hubs in Sandton). If the next step stalls again at the next check-in, consider a chaos reset or bring in a new pair of eyes. For more ideas on making operational rituals stick, check out the wider rituals library or see the one-blocker, one-hour guide.
