The APEN Method

Most operations advice fails for the same reason. It hands you someone else’s system and tells you to run it.

I have built or rebuilt operations for more than twenty five organizations over fifteen years. Founder-led companies, nonprofits, multi-vertical firms, ministries. What I learned across all of them is that the tools are almost never the problem. The order is.

APEN is the method I built out of that. Four steps: Audit, Prepare, Execute, Niche. It works because it refuses to let you skip ahead to the part that feels productive.

Here is what each one actually means.

A: Audit

Look at what is actually happening, not what the org chart says.

Every organization has two versions of itself. There is the documented one, with roles and processes and a tidy diagram. And there is the real one, where a decision quietly routes through one person because that is how it has always worked, three people are doing the same task without knowing it, and the most important process in the company lives in somebody’s head.

The audit is where I find the second one.

That means asking people what they actually do, not what their title says. Following a piece of work all the way through and watching where it stalls. Looking at the tools you pay for and finding the ones nobody opens. Naming the thing everyone works around instead of fixing.

This step is uncomfortable and people want to rush it. Don’t. Almost every failed operations project I have seen was solving a problem that was not the real problem.

P: Prepare

Build the structure, the sequence, and the people before anything moves.

Preparation is the step organizations skip most, and it is the one that determines whether any of this survives.

Structure means deciding what the new system actually is before you start building it. Sequence means knowing what has to happen first, because operations work has dependencies and doing step four before step two costs you the whole thing. People means the humans who will live inside this system every day.

That last one is where projects die. You can design a flawless workflow and watch it get abandoned in six weeks because nobody asked the person who would run it whether it made sense. Adoption is not something you handle at the end. It is something you build in from the beginning by involving the people who will carry it.

Prepare is also where you decide what you are not doing. A system that tries to fix everything fixes nothing.

E: Execute

Build it alongside the team, not on top of them.

There is a version of consulting where someone hands you a deck and leaves. I do not do that, because a plan is not infrastructure. A plan is a document about infrastructure.

Execution means being in the build. Setting up the CRM, writing the SOPs, migrating the data, testing the workflows before anyone else touches them. It also means being there when the first thing breaks, because something always breaks, and the difference between a system that sticks and one that gets abandoned is usually whoever was in the room during week three.

Executing alongside the team does something else too. It transfers the knowledge. When I leave, the system does not leave with me. That is the entire point.

N: Niche

Tailor it to the organization it belongs to. Then keep tailoring it.

A process that works everywhere in general works nowhere in particular.

This is the step that makes the difference between a template and a system. Two nonprofits of the same size with the same budget will need different infrastructure, because one has a founder who reads every email and the other has a board that needs monthly reporting. Same tools. Completely different build.

Niche means fitting the system to the actual organization: its size, its people, its rhythm, its constraints, the way its leader thinks.

And it does not stop at handoff. Organizations change. The system that fit you at four people will strain at twelve. So this step loops. You reassess what is working, you refine what has drifted, and you adjust. Operations is not a project with an end date. It is a practice.

Why the order matters

You can find plenty of people who will do one of these steps. The value is in the sequence.

Audit without Prepare gives you a diagnosis and no treatment. You now have a very clear document about your problems.

Prepare without Audit gives you a beautiful system built for a company you do not actually run.

Execute without Prepare is the most common failure I see. New tool, real enthusiasm, no sequencing, and six weeks later everyone is back in the spreadsheet.

And skipping Niche gives you something that technically functions and that nobody uses, because it was built for a generic organization instead of yours.

Who this is for

APEN is built for founder-led and mission-driven organizations. Companies where one person is holding too much, where growth has outpaced the systems, or where there was never a system to begin with.

It works whether you have an operations team or you are the operations team.

If any of that sounds like where you are, that is the conversation I have every day.

Let’s talk!