Business
Professionalizing is not bureaucratizing
Every time someone proposes putting processes into a small company, the same objection shows up:
"I don't want us to become like the big companies."
I get it. We've all worked somewhere where asking for a chair took three signatures.
But I've spent years watching that objection — which comes from something legitimate — end up justifying the mess.
And mess and agility are not the same thing. Not even close.
The train tracks
A train goes incredibly fast. And it runs on tracks, the most rigid constraint you can imagine: it can't turn wherever it wants, it can't wander off.
An off-road truck can go anywhere. And that's exactly why it goes much slower and gets stuck.
Neither is better. It depends on what you're doing.
But notice this: the train doesn't go fast IN SPITE of the tracks. It goes fast BECAUSE of the tracks. Without them it couldn't run at that speed without flipping over.
Structure, done right, doesn't slow you down. It lets you go faster without derailing.
A five-person company with written quoting criteria almost always beats a twenty-person company where every quote is a meeting.
What you're actually afraid of
Let's split it, because the fear mixes two different things. And sometimes it mixes a third: control.
Bureaucracy is process that exists to protect itself. Three signatures for the chair. Forms nobody reads. Meetings to prepare the meeting. It adds steps and it doesn't add value.
A system is information sitting where it should so decisions can get made without asking anyone. It removes steps.
They're opposites. Not the same road with different mileage.
The test to tell them apart is simple: does this process make people ask for more permission, or less?
If the answer is "less," it's a system. If it's "more," it's bureaucracy and you have to kill it.
There's a second test, more uncomfortable, because it points at you.
Does this process exist so the team can move without you, or so you can sleep knowing nobody moves unless you sign?
The second one is control dressed up as order. And that's how small companies get slow without ever getting big.
The original fear wasn't of rules, either. It was of losing what made you special when there were four of you and everybody knew everything.
That dies on its own. At eight people nobody knows everything anymore, whether you write it down or not. The difference is whether you replace it with a system or with WhatsApp and faith.
What happened when we professionalized
When we finally put structure into Bolteam, my fear was exactly that: that we'd get slow and stiff.
I already told the part where every lead fell into the follow-up hole. What I didn't tell is what I FELT when we fixed it.
The opposite happened. And in hindsight it was pretty obvious.
Before, every quote was an internal negotiation. How much do we charge? Who handles it? What do we promise? Each one was a decision from scratch, with a debate.
After, with defined stages and written criteria, most cases already had an answer. Debate was reserved for the weird ones, which is where it's actually worth debating.
We stopped spending energy deciding what we had already decided.
That isn't bureaucracy: it's stopping yourself from reinventing the wheel fourteen times a week.
What DID happen — and this has to be said — is there were a few uncomfortable months where everything felt SLOWER. Because we were learning the new way while still running the old one.
Two paths at once. The written process. And the usual WhatsApp, "just this once."
Those startup months are the price. There's no way around them. If someone sells you professionalizing with no valley, they're selling you a slide.
The valley ends the day the old path dies. Not the day you write the document.
And if every exception still comes up to you — "send it to Jorge" — you didn't professionalize. You added a step in front of the same bottleneck.
The right moment to start
The question every growing business owner struggles to answer is WHEN.
My advice, after crashing into this more than once: when the same mistake happens twice.
Not the first time. The first time can be bad luck, a weird case, a bad day.
The second time is already a pattern. And the pattern is what you fix with process.
The truth is it feels uncomfortable. As an owner, sometimes we don't want to look at what's in front of us, because it feels exhausting to fix things that seem obvious.
That rule protects you from both extremes: you don't go paranoid documenting things that happened once (because you never finish), and you don't let a recurring problem become part of the scenery.
And it works the same for the good stuff: if something went well twice, write down how it was done. Over time you improve it. You don't guess it.
If YOU are in every quote, every exception, every "hold on, let me check," you're already late. The two-times rule is for the process. The bottleneck is you, and that clock is already running.
At GAMBI I saw it from the other side. When you're already fifty or sixty people, changing the culture hurts a different kind of hurt. Work orders on paper. Colored post-its. People signing N orders a day just to give a notice.
That started as a system: in writing, with a name, with a signature. Until size turned it into bureaucracy. The paper didn't expire. The process did.
That's why the advice to start small isn't romance. Getting an eight-person team to change is a different war than moving a culture of sixty. I've been there.
At Apunto we already had that knowledge. We already had, as they say, a stripe on the tiger.
Thanks to what we learned at Bolteam and at GAMBI, we started professionalizing with a work rhythm. That's something you really need for the business to take shape.
Rules for putting structure in without killing the business 🛠️
One process at a time, the one that hurts most. Not a reengineering. One. The one that already ate your Friday.
Start with what you already do well. Just write it down. It's easier to document something that works than to invent something new. And it gives the exercise credibility.
If it doesn't fit on one page, it's wrong. Nobody reads and remembers a 30-page manual. Not even you. (Same rule as the partner agreements: if it doesn't fit, it doesn't exist.)
The person who does the work writes the process, not the boss. The person doing it knows the real exceptions. This is where people get uncomfortable, because they think writing their process is so you can replace them. The reality is different, and YOU have to make that clear with your team: we write it so the business doesn't depend on that person not getting sick.
Every process has a review date. Six months. If it no longer serves, you kill it. A process with no expiration date is how bureaucracy starts. Always. GAMBI's paper orders were that: they helped, and then they were the problem.
Ask what it removes, not what it adds. If a new process doesn't take work off anyone, it probably shouldn't exist. Same as with automating: if nobody lets go of the spreadsheet, you didn't install anything. You duplicated.
The system enforces the process, not the people. If your process depends on someone remembering to follow it, it isn't a process. It's a good intention with an elegant name.
Point 7 is the one that ties together the rest of what I've been writing. A written process nobody follows is worse than not having one, because it also gives you the illusion that it's solved.
The information has to live in one PLACE. Not in someone's head. Not in the chat. I already said it when the message gets stuck across six apps.
What professionalizing actually means
It isn't a suit. It isn't a committee meeting. It isn't the weekly that informs and never decides, or the report nobody reads.
(Careful: rhythm is not theater. A partners' meeting that decides is not bureaucracy. A meeting to prepare the meeting is.)
It's this, and it's much simpler than it sounds:
- That the information lives in one place and not in someone's head.
- That the repetitive decisions are already made.
- That you can tell what happened without asking anyone.
- That the business still runs on a Tuesday when two people are out.
That's it. None of that makes you corporate: it makes you a business, instead of a group of talented people running in the same direction out of habit.
And the part you don't touch
An honest close, because the original fear had a point.
There are things you do NOT systematize. And you have to defend them on purpose:
- The hard conversation with a client.
- The judgment to know when to break your own rules.
- The decision to go into something new.
- The human relationship.
If you write a script for the hard conversation, you didn't professionalize. You hid.
The system exists so those things have room. If your process eats judgment, you built bureaucracy. If your process frees time and headspace to use judgment where it matters, you built a system.
The difference isn't in how many rules you have. It's what they're for.
Bolteam was another MOTIVATOR. The one about putting structure in without going stiff.
That's when I understood that a company's communication can't stay as talk. It has to turn into actions. And those actions, into processes that are already in place. The ones that still run on a Tuesday when two people are out.
That's what we put inside Actiun. Professionalizing through the process. Not through another meeting.
The valley I told you about — the document and the WhatsApp of “just this once” — doesn't end the day you write the process. It ends when the process lives where the team already works.
💡 Say it out loud
What are you afraid of when it comes to putting structure into your business?
Write it to me as it is. Almost always, once you say it out loud, the fear was about something else.
Write me at hola@jorgenajera.com or on LinkedIn.
If you're at that point where the business is growing and you're afraid to put order in because you don't want to "go corporate," let's talk. Most of the time the problem isn't the structure. It's that you still can't tell which kind.