I built operational systems for large-scale law enforcement long before digital tools existed to support them. Major operational commands ran on processes and disciplines I wrote — not because technology enabled them, but because the thinking underneath was sound.
When a national health crisis required border management built from scratch, I designed and commanded it: more than a million travellers screened, no existing infrastructure, no tolerance for failure. The intelligence architecture that came next, inside a state-level command environment, existed so frontline operators could act on information while it still mattered. Along the way I led the implementation of major technology projects, from the business case through to rollout.
Then the private sector, leading law enforcement partnerships for a retail intelligence technology company — sitting between what police need and what a technology business can actually deliver, proved across every Australian state and territory.
That order matters. Operational practice came first, before the tools existed. Then a seat inside a technology business, watching which products got used and which got bought and shelved. It is why I review a vendor proposal the way I do — not on the demonstration, but on whether the proposal will hold in practice.
Today, through BW Advisory, I work with organisations of every size, from growing businesses to local government and national operators, on what keeps them running: how the operation works, the technology decisions behind it, and the privacy and governance that come with them.
The problems look different. The fundamentals are the same.