The problem with A beautiful process

A system can look perfectly sensible on paper and still be abandoned by Tuesday afternoon.

This is especially true in founder-led businesses, where the person at the centre is often energetic, instinctive and highly capable, but not naturally drawn to routine. They may understand the need for structure in principle while resisting it in practice. They may want the business to feel more ordered while continuing to work in ways that are fast, verbal, deadline-led and difficult for other people to follow.

The mistake is to treat this as stubbornness.

Sometimes, of course, it is. People are people, and even the most elegant workflow is no match for a founder who has decided that the real system is “just ask me”. More often, though, resistance is a sign that the process has been designed for an imaginary version of the business, rather than the one that actually exists.

Start with behaviour, not aspiration

Good operational design has to begin with reality. That means paying attention to how people behave under pressure, not how they promise they will behave once the new system is in place.

A founder who has never updated a project board consistently is unlikely to become a different person because the board has acquired better columns. A team that has spent years waiting for verbal instruction will not suddenly act with confidence because a workflow has been saved in a shared folder.

The problem is rarely that no process exists. Many businesses have plenty of documents, spreadsheets, templates and tools. The more useful question is whether any of them are used when the work becomes urgent, complicated or politically awkward.

A useful system has to survive contact with real people

That is where many systems fail. They are created in a moment of good intention, then quietly ignored as soon as the old operating rhythm returns. The founder goes back to voice notes, the team goes back to checking everything twice, and the business continues to rely on memory, interruption and last-minute recovery.

A good system does not require everyone to become a different kind of person overnight.

That does not mean lowering standards. It means designing around behaviour with enough honesty to make the system usable. A founder who thinks aloud needs a way of turning spoken context into decisions, actions and ownership. A business driven by deadlines needs visible milestones before the moment of panic. A team that avoids documentation needs a process light enough to maintain and useful enough to justify its existence.

Most small businesses do not need heavier machinery around them. They need a clearer route through the work they already have.

That may mean reducing the number of places people have to look for information. It may mean clarifying the handover between sales and delivery. It may mean agreeing who can make which decisions without returning to the founder. It may mean replacing a heroic spreadsheet with something less impressive and more likely to be used.

Less theatre, more function. Always a relief.

Capability is not the same as consistency

There is also a human element that is often missed. People who dislike systems may still crave order. They may be exhausted by the consequences of their own working patterns, even while finding structure difficult to sustain.

A founder can be excellent with clients, fast in a crisis and unusually good at spotting opportunities, while still leaving behind unfinished decisions and unclear follow-up. A team can be intelligent and committed, while still becoming passive if responsibility has never been properly handed over. A business can be commercially strong and structurally fragile.

These contradictions are not unusual. They are often the point at which informal working has reached its limit.

The work is to understand the pattern before trying to fix it.

The right question

When Callisto looks at a business, the first question is rarely, “What system should this company have?”

The better question is:

“What structure would this business actually use, given how its people behave when things are busy?”

That shift matters because it moves the conversation away from neatness and towards usefulness. A process is not valuable because it exists. It is valuable because it helps the right work happen with less confusion, less repetition and less dependence on one overloaded person.

Good structure should make the next step easier to see. It should make ownership visible. It should allow information to move without being carried in someone’s head. It should give people enough confidence to act without asking for permission every time.

Designing something that will last

Businesses that resist systems rarely need more process language. They need someone to observe how work really moves, identify where it breaks down, and build something proportionate enough to last.

That is the difference between imposing structure and designing it properly.

A system for people who hate systems has to meet them where they are, while still helping the business move beyond the habits that are holding it back. It should respect the intelligence in the room without pretending that good intentions are enough.

The aim is not to create perfect process.

The aim is to make the business easier to run.

References and further reading

Lucy Suchman, Plans and Situated Actions
Wanda J. Orlikowski, “Using Technology and Constituting Structures: A Practice Lens for Studying Technology in Organizations”
B. J. Fogg, Fogg Behavior Model
Peter M. Gollwitzer and Veronika Brandstätter, “Implementation Intentions and Effective Goal Pursuit”
Amy Edmondson, “Psychological Safety and Learning Behavior in Work Teams”
Everett M. Rogers, Diffusion of Innovations
Donella H. Meadows, Thinking in Systems
Atul Gawande, The Checklist Manifesto
Wendy Wood, Good Habits, Bad Habits
Eric Barends, Denise Rousseau and Rob Briner, Evidence-Based Management: The Basic Principles