About
Hi, I’m Anita.
A little about how I think, and why I build the way I do.
Where it started
I began in human resources, though what actually drew me in was people.
Long before I had language for it, I was interested in why some teams worked and others did not. Human resources gave me a place to study that up close. It put me next to hiring, performance, structure and the quiet systems that decide whether an organisation runs well or simply gets by. That was the real pull. Not the field itself, but what it let me see.
The more I looked, the wider the questions became. Understanding people led me to understand how they learn, which led me into training and the design of learning that genuinely changes how someone works. Building those programmes meant building the tools and systems around them, and that carried me into digital systems, websites and the way information moves through a business.
From there the thread kept extending. If I could help a business teach, I could help it communicate, so I moved into marketing and commercial content. If I could help it communicate, I could help it run better, so I moved into business improvement. At some point the pattern was obvious. I was not changing careers. I was following one question through different rooms.
Eventually I stopped only improving other people’s organisations and started building my own. The ventures came from the same instinct as that first role: see how something works, understand why it struggles, and build a better version of it.
How I think
For as long as I can remember, I have wanted to understand how things work.
Not in a technical sense so much as a structural one. The quiet habit of taking something apart in my head to see why it behaves the way it does. When I come across a business, a process, a project or an idea that lacks structure or direction, my first instinct is not to rush in and change it. It is to understand it. Only once I can see how the pieces actually fit do I begin thinking about how they might fit better.
Structure matters to me, probably more than it should. Confusion, disorganisation and wasted potential all bother me in the same way. I build systems because structure is generous: it lets people see what they are doing, work without second-guessing themselves, and make better decisions with less effort. A good system does not box people in. It gives them room.
On moving between things
People sometimes assume I move between fields because I get bored. It is closer to the opposite.
The same way of thinking turns out to work almost everywhere. Understand the problem, find the structure it is missing, and build the thing that makes it work. That approach is as useful for a hiring process as it is for a hotel’s marketing, a training programme, or a room that does not yet function.
So each new discipline I have learned was never really about adding a skill to a list. It was about gaining another way to look at a problem. Recruitment taught me one thing about people. Design taught me another. Building ventures taught me something else again. I hold on to all of them not because I like collecting them, but because each one occasionally turns out to be exactly the lens a particular problem needs.
How I work
Whatever the problem, the approach is the same.
For all the different kinds of work, there is really one method underneath it. It barely changes, whatever the field.
01
Understand
I start by learning how the thing actually works, not how it is meant to. The real problem is rarely the one described first.
02
Find what is missing
Underneath most problems is a piece of structure that was never put in place. I look for that, not the symptom on the surface.
03
Design the structure
Then I work out the system that would make the outcome dependable, built around how people really behave rather than how we wish they would.
04
Build it properly
I build it to a standard, so it holds without someone holding it together. If it only works when I am in the room, it is not finished.
05
Prove and refine
Finally I watch it work, keep what does, and quietly improve the rest. Most things get better once they meet reality.
What I’ve come to believe
A few things I have become fairly sure of, mostly by paying attention to what works.
I believe people do their best work when they have clarity, and that much of what looks like underperformance is really just confusion no one has taken the time to remove. I believe businesses grow when good systems are placed underneath good ideas; an idea without structure tends to stay an idea. I believe learning should leave people more capable, not simply more informed. If it changes what someone can do, it worked; if it only changes what they can recite, it did not. And I believe an opportunity means little on its own. It becomes real when someone has quietly done the work of being ready for it.
It is also why I enjoy improving things as much as making them. Taking a business, a page or a process that is almost working, and finding the few changes that make it click, is to me just as satisfying as starting from a blank page.
Beyond work
Away from any particular project, I am simply curious. I read and learn across fields that have little obviously in common, partly for its own sake and partly because that is usually where the useful ideas come from. Most of my spare attention returns to the same quiet question that runs through my work. How do businesses, people and systems actually work, and how might they work a little better?