41 Things Your Business Needs to Do

Ask any business owner what their company does and they'll rattle off the obvious: sales, marketing, accounting, customer support, maybe HR. Push a bit harder and they'll add project management, some kind of IT function, and whatever compliance box they last had to check. That gets you to maybe 10 or 12.

The real number is 41. Not 41 tasks. Not 41 job titles. Forty-one distinct areas of work, what our catalogue calls operational domains, that every business needs to manage whether it has five employees or five hundred.

This isn't about creating more work. It's about seeing work that already exists. Right now, someone in your organisation is handling vendor relationships, probably the same person who handles procurement, who also somehow became the person everyone calls about IT issues. Someone is managing knowledge, or more accurately, knowledge is living in people's heads and disappearing every time someone leaves.

Someone is handling compliance, in the sense that nobody has been fined yet. These functions exist whether you've named them or not. The question is whether they're being handled deliberately or by accident.

Mapping the operational anatomy of businesses across different industries has left us with a conviction: the ones that run smoothly aren't necessarily bigger or better funded. They are simply aware of more of these areas. They have made conscious decisions about each one, even if that decision was "we're not going to invest in this yet."

Deciding not to invest in one of them yet is a choice. Not knowing it exists is a surprise waiting for a Tuesday afternoon.

Forty-one areas sounds overwhelming until you organise them. Each one falls into one of eight groups. Think of the groups as the major organs of your business. Some are visible and get constant attention (sales, finance). Others work quietly in the background until something goes wrong (governance, the machinery underneath everything else). Together, they keep a business alive.

Here's the framework, group by group.

Any one of these, left unowned, is manageable. You can survive without a formal knowledge system. You can get by without tracking vendor contracts in a structured way. You can operate without a business continuity plan, right up until you can't. The real damage is the accumulation: fifteen or twenty of these areas, unowned at the same time.

Think about what happens in a typical week at a growing business where this work belongs to nobody. Monday: a new hire spends three hours looking for a process that was never written down. Tuesday: a client escalation bounces between two people because there's no clear ownership. Wednesday: someone manually re-enters data from one system to another because the tools aren't connected. Thursday: a vendor invoice gets approved without anyone checking it against the original quote. Friday: a compliance deadline passes because it wasn't in anyone's calendar. None of these are crises. All of them are waste. And they happen every single week.

This is the compound effect. It doesn't show up as a dramatic failure. It shows up as a persistent drag: slower growth, higher costs, more stress, and a team that's always busy but never on top of things. The businesses that break through this ceiling are the ones that stop treating operations as something that just happens and start treating it as something that gets designed. That starts with seeing the full map.

Knowing the 41 areas exist is step one. Knowing which ones matter most for your specific business, and in what order to address them, is step two. A logistics company and an accounting firm share the same map, but their priorities within it are completely different. That's why a static checklist isn't enough. What matters is which of these areas carry your advantage, and that has to be worked out one business at a time.

Most of what comes out of that will be ordinary, and ordinary is worth buying rather than building. Sorting the ordinary from the part that is actually yours is the decision the whole exercise is for. A medical equipment business we worked through this with ended up changing nothing inside their bought software and building only the two things that did not exist.

That work is done with people, not by a form. Going through the map with a business is how the ordinary parts get told apart from the part that actually wins the work. What comes out is a sequence to build in, with specific tools and a specific order, rather than a score.

Think of it as the difference between a doctor saying "you should be healthier" and a doctor handing you a treatment plan with your name on it.