How does this actually work? I've asked that for 35 years.
Not how it's supposed to work. Not how the manual says it works. How it really works — when people are busy, information is scattered, and something always falls through the cracks. That question has run through every chapter of my career.
So what didn't change?
I've spent most of my working life trying to answer one simple question: how does this actually work? Not the version in the manual — the version that plays out when people are busy, information is scattered, processes have grown organically, and something inevitably falls through the cracks.
That question has followed me through almost every chapter of my career — from security operations to mining, from IT to digital marketing, and now into the work I do today, helping businesses build the knowledge infrastructure that makes everything else possible.
Where did I learn business from the ground up?
I started working in security in 1989. Over the years that followed I moved through roles in customer service, logistics, records, reconciliation, dispatch, supervision, investigations, operations and management.
I worked underground in mining, where procedures, standards, communication and accountability weren't theoretical concepts — they mattered every day. I eventually became an Area Manager responsible for more than 350 security officers, along with supervisors, vehicles, logistics, clients, investigations, reporting and business process investigations.
Somewhere along the way, I discovered something that has stayed with me ever since: most business problems aren't obvious from the outside. You have to go and see how the work actually moves.
Most business problems aren't obvious from the outside. You have to go and see how the work actually moves.
What changed how I looked at business?
In 2004, a client was experiencing significant losses. Management knew money was disappearing, but they couldn't identify exactly where. Rather than make assumptions, I asked for time to investigate the operation.
I followed the process from receiving raw materials, through stores and production, into storage, packing and finally dispatch — documenting what was happening at each stage. The problem turned out to be in the handover between the warehouse and the third-party logistics company. There were counts. There were scans. There were delivery notes. There were people doing their jobs. But there wasn't enough accountability between the different parts of the process.
We redesigned the controls around that handover. The client implemented the recommendations. The changes saved more than R1.6 million in losses year over year.
You can't fix what you haven't taken the time to understand.
Why am I obsessed with making information easier to use?
Another example was much less dramatic. At one company, important site documentation was being thrown into archive boxes. When someone needed something, they had to rummage through the box to find it.
I created a simple structure for the documents, putting the information people needed most where they could find it quickly. It was a small change. But it saved time, and the system was eventually adopted across the company.
That is the kind of problem I've always enjoyed solving. Not making things complicated — making complicated things easier to understand and use.
The tool changed. The instinct didn't
My career eventually moved into IT and entrepreneurship. I learned how computers worked from the hardware up, and became a certified PC technician. I worked with networks, backups, data storage, security, asset registers, incident records and troubleshooting.
Later I moved into digital marketing, analytics, databases, SQL, Python, data visualisation and automation. I've built websites, databases, applications and workflows. I've learned new technology whenever it became useful for solving a real problem. But technology was never the point. It was always the tool.
The same pattern, decade after decade
I find the moving parts. I understand how they connect. I identify where information, responsibility or process breaks down. Then I create enough structure to make the whole thing work better.
Security, operations and mining
Customer service, logistics, records, reconciliation, dispatch, supervision, investigations and management — including underground mining, where procedure and accountability were not optional.
Area management at scale
Responsible for more than 350 security officers, supervisors, vehicles, logistics, clients, investigations, reporting and business process investigations — including the R1.6 million process fix.
IT and technical foundations
Certified PC technician. Networks, backups, data storage, security, asset registers, incident records and troubleshooting — learning how the systems underneath a business actually work.
Digital marketing, data and automation
Analytics, databases, SQL, Python, data visualisation and automation — websites, databases, applications and workflows built to solve real, specific problems.
Business Knowledge Infrastructure
Helping knowledge-dependent businesses structure, document and operationalise what they already know — so automation and AI have something solid to stand on.
Why do businesses accumulate knowledge but rarely structure it?
Today, I help businesses do the same thing with their knowledge and information that I've been doing with processes my whole career. Because businesses accumulate enormous amounts of knowledge — some in documents, some in spreadsheets, some in software, some in emails and messages, and a surprising amount inside people's heads.
The problem isn't always a lack of information. Often, it's that the information has no useful structure. People can't find it. Processes aren't documented. Nobody is quite sure which version is correct. A critical task depends on one person remembering how to do it. And when the business grows, those little cracks become expensive.
Five steps. In this order.
Because technology applied to a messy business doesn't magically create order. It can simply make the mess move faster.
Structure
Understand what exists and how it fits together — before anything gets built or bought.
Documentation
Capture the important processes and knowledge so they don't remain trapped in people's heads.
Accessibility
Make the information easy for the people who need it to actually find and use it.
Better operations
Once people have clarity, processes become easier to improve, measure and manage.
Growth
Only then do we start asking where technology, automation and AI can create real leverage.
What's actually the biggest difference?
I don't want to walk into your business and immediately tell you what software you need. I want to understand what you're already doing. Where information comes from. Where it goes. Who uses it. Where things get stuck. What people have to remember. What gets duplicated. What gets lost. What nobody has documented. And what is quietly costing you time, money and momentum.
Then we decide what needs to change. Sometimes that means better documentation. Sometimes a simple process change. Sometimes a database. Sometimes automation. Sometimes AI makes sense. Sometimes it doesn't.
The business comes first. The technology comes second.
Which questions never change?
I've worked through the transition from paper records to computers, from local networks to cloud systems, from manual data handling to modern analytics and automation. The tools keep getting faster. The terminology keeps changing. There's always another platform promising to transform your business. But the underlying questions haven't moved.
- What do we know?
- Where is it?
- How does the work actually happen?
- Who is responsible?
- What happens when something goes wrong?
- Can someone else understand how this works?
- Can the business grow without everything depending on the people currently holding it together?
Can AI build this? I can.
The work I've been moving toward for decades
I help you take the knowledge, information and processes already inside your business and turn them into something structured, documented, accessible and useful — so your business isn't just working. It's becoming easier to understand, easier to manage and easier to grow.
Take the free Constraint Map Assessment →The problem didn't.
I'm Alistair Vermaak.
If your business runs on knowledge that only lives in people's heads, spreadsheets, and scattered documents — that's exactly the kind of problem I've spent 35 years learning to solve. Start with the free assessment and see where your own constraints actually sit.
Take the Free Constraint Map Assessment → Free · 10 minutes · No obligation