Latest

Notes, insights and practitioner essays

What we learn while consulting, marketing, building and running events — written for people who have to decide.

Strategy documents rarely fail because the thinking is wrong. They fail because nobody owns the first ninety days.

Roughly half of what a business asks an ERP to fix is a handover problem, not a software problem.

Reach, engagement and impressions are diagnostics. The report your finance team reads has one line.

Consistency beats production value. Here is the weekly rhythm we hand to clients.

Tenant isolation, module switches and a sync server — the decisions that made one code base serve four very different organisations.

A tour guide needs today’s itinerary and a way to report an incident — not the operations menu on a small screen.

Events5 min read

The event is the middle of the campaign. What happens the week after decides whether it paid off.

Events6 min read

Large religious and community events are logistics problems first. The plan has three layers.

Before choosing a use case, know where your data, processes and people actually are.

Two design rules make AI assistants deployable in real operations: every answer has a source, every action has an approver.

Most repetitive work is rule-shaped. Use a model only where documents or judgement vary.

Company4 min read

No result claims without a baseline; no logos without permission; no case studies without the client’s sign-off.

A brand that only works on a laptop screen fails on launch day.