Why Some of Your Projects Succeed and Others Don't (And What's Really Going On)

This document covers:

• Why small businesses end up here, and why there was never a right moment to fix it
• A checklist to spot the signs of an undefined process in your own business, across seven different areas
• What inconsistent delivery is actually costing you, in time, quality, people, and growth
• On request: five places to start, and the bigger picture on what a defined process actually gives you

You've probably noticed it. One project runs smoothly, the team knows what they're doing, the client is happy, things get delivered on time. The next project, similar in size and scope, somehow feels like a struggle from start to finish. Deadlines slip, things get missed, and nobody can quite explain why.

It's tempting to put it down to the individuals involved, or the client, or just bad luck. But in most cases, when I speak to people who have worked in and with small businesses, the same underlying cause comes up: there is no defined process for how projects get delivered. Nobody has ever written it down, agreed on it, or made it available in a way that people can actually use.

That absence, quiet and unremarkable, easy to overlook, is usually the real reason your project outcomes are inconsistent.

What "No Defined Process" Actually Looks Like

Most small businesses don't think of themselves as lacking a process. Things get done. Projects get delivered. There is a way things work, it's just not written down anywhere.

In practice, it usually looks like one of these:

• New team members get shown how things are done by someone more senior, informally, verbally, on the job. What they learn reflects that person's experience and habits, not a shared standard.
• There might be a document somewhere, a checklist, a template, an old process guide, but it hasn't been updated in years and doesn't reflect how things actually work now. People try to follow it and hit dead ends, so they give up and improvise.
• Everyone broadly knows the goal but makes their own decisions about how to get there. Some of those decisions are good. Some aren't. And because nothing is standardised, the outcome varies depending on who happens to be leading the work.

None of this feels like a crisis from the inside. It feels like normal. But it creates a business that is only as consistent as its most experienced person, and that's a fragile foundation to build on.

Why Small Businesses End Up Here

There was never a right moment to formalise it

When a business is small and the founder is involved in everything, a formal process feels unnecessary. Everyone knows what's happening. Communication is easy. Then the business grows, more people join, and suddenly the informal knowledge that worked for five people doesn't stretch to fifteen. By then, formalising the process feels like a big project in itself, one that always gets pushed back in favour of more immediate work.

The knowledge lives in people, not in the business

In many small businesses, the process is essentially one or two experienced people who know how things should be done. That works until those people are unavailable, overstretched, or leave. At that point, the business discovers that what it thought was institutional knowledge was actually personal knowledge, and it walked out the door.

Written guidance exists but can't be applied

Some businesses do have written processes, but they were created at a different point in time, by someone who no longer works there, and haven't kept pace with how the business has evolved. People try to follow them, encounter steps that no longer make sense, and either ignore the document entirely or waste time trying to work around it. Outdated guidance can actually be more damaging than no guidance at all, because it creates confusion and erodes trust in any future process.

Nobody has been given the time or brief to fix it

Process development rarely gets prioritised because it doesn't feel urgent. There's no client deadline attached to it. It doesn't appear on anyone's job description. So it stays on the to-do list, perpetually deferred, while the inconsistency it causes quietly costs the business time, quality, and people.

The Signs That a Defined Process Is Missing

These are the day-to-day signals that point to an undefined or unusable project delivery process:

In how people talk about their work

• You hear "we've always done it this way," but nobody can tell you exactly what "this way" means.
• Post-mortems after a project goes wrong stay vague: "things just fell through the cracks," with nobody able to point to where or why.

In how the business is structured

• Two people in the same role deliver projects in noticeably different ways, and both think they're doing it right.
• There's nobody whose job it is to own or maintain how projects get delivered, it's simply not on anyone's brief.

In the day-to-day work itself

• Onboarding a new team member takes far longer than it should because there's nothing written down to hand them, only shadowing and picking things up as you go.
• When a key person is on leave, things slow down or stop, because nobody else knows the full picture.

In your outcomes

• Clients get a different experience depending on who is managing their project.
• Your best people are constantly being pulled in to rescue projects because they're the only ones who know what to do.

In your knowledge base

• What you'd call "institutional knowledge" is really just personal knowledge sitting in one or two heads, ready to walk out the door.
• Any written guidance that does exist was created by someone who's since left, and nobody has touched it since.

In how it's governed

• Nobody checks whether two teams are actually delivering projects the same way.
• The same issues keep recurring project after project, and nothing structural ever changes as a result.

In what it's costing financially

• You can point to real hours lost to unclear ownership, missed steps, or rework on recent projects.
• Client retention or repeat business has been affected by an inconsistent delivery experience.

If several of these sound familiar, the issue probably isn't your team. It's the absence of a clear, shared framework for how projects get done.