Clay Tech

"clay-works make things real"

translated from clazytech.com

Temporary fixes by owners hide a company's true costs

It’s a common story for a business owner or management team to fill in operational gaps. This is especially true in organizations with limited funds and staff, like small businesses and startups. It’s all the more common when the gap shows up inside some innovative activity.

Operations and innovation aren’t opposing concepts. There are small innovations within operational work, and plenty of operations buried within innovative work.

Now, the scene described above — the business owner filling the gap — is proof that operations aren’t running smoothly, at least temporarily.

Here lies the demon of “temporary.”

What kind of situations does “temporary” assume? A staff member calls in sick, an urgent delivery comes in, trouble at a site outside the office pulls staff away, or some task shows up that nobody’s been assigned to. It’s common for several of these to happen at once.

If a company owner fills in every single time a staff member calls in sick, something’s wrong, and the staffing needs rethinking. If it’s just an urgent delivery, the existing staff can surely push a lower-priority delivery to tomorrow and get through it. If it’s just a case of staff being pulled to an external site, other departments can surely shift people around. If it’s just some nitpicky task that’s come up, that sort of thing happens often enough that a position like “general affairs” or “secretary” should exist, with a system in place so that staff member handles it.

But when these things happen simultaneously, they become unmanageable, and the business owner ends up dragged into operational work as a result.

Even so, it’s a common story.

The real trouble starts when the interpretation of “temporary” keeps expanding, bit by bit, with an attitude of “well, today just happened to be like this,” “these things happen,” “I guess this time was like that too…”

That’s when real caution is needed.

It means the cost you’re assuming is wrong. Or it means your company is actually running a loss. Or your company’s loss is bigger than you think. Or your company’s profit is smaller than you think. What’s really needed is more spending on labor costs or system development. Skipping that just creates the appearance of cost savings. In other words, it’s a slow bleed.

What the business owner should actually be doing is reviewing the operational workload and either increasing staff to match it, or reviewing the operational flow and department structure. Based on that, they’ll need to adjust future funding plans, bonuses, procurement funds, sales plans, and business strategy. Nobody other than the owner or management can decide this on their own. Putting their minds to that is their job.

Just when it’s finally their turn to step up, that’s not the moment to be out on the floor doing operational work, breaking a good sweat, and enjoying a refreshing beer afterward. That laziness will come back to strangle the employees down the line.

That said, this story gets murkier with the pattern mentioned earlier — operations within innovative work.

Countless operational tasks exist within any innovative process. Beyond that, encounters with the seeds of innovation often happen while grinding through operational work. Back when I was in the US, I drew up my own business plan, designed and prototyped, built everything from hardware to the web application, presented at exhibition booths, and even handled the explanations myself. A French-American friend was pretty astonished and asked, “Are you really doing all of that by yourself?”

On the whole it was innovation, but it was packed with operations inside. In the US, where division of labor is far advanced, it’s not common for one person to handle everything end to end like that.

In a similar vein, an Indian colleague once told me, “Kuz, you do the design work and you pick up the soldering iron too? That’s unusual.”

That said, this “operations within innovation” idea is, in most cases, just wordplay. Most of daily life is filled with activity that isn’t innovative. This depends on the job, the position, and of course the individual. But taken as a whole, most of daily life is operational. This isn’t a pessimistic observation. The reason you can get a rice ball at the convenience store every day, the reason vending machines reliably dispense hot coffee, and the reason trains run exactly on schedule, is precisely the high quality of operations.

Long live operations.

But a society can’t run on operations alone. Someone needs to think about making convenience store delivery systems more efficient, someone needs to come up with a system to predict vending machine stockouts, someone needs to develop IoT devices to monitor train drivers’ health. Someone needs to build financing plans for those projects, and someone needs to dream up the business and hustle to launch it in the first place.

Coming back to the opening case: a business owner or management team is precisely the party that has to provide some kind of answer to the fact that a society can’t run on operations alone.

So in most cases, it’s simply not praiseworthy for an owner to be doing operational work.

I had my own younger days, of course, my days as a junior staffer — and it wasn’t all that long ago — nights spent hunched over an oscilloscope debugging, nearly in tears while grinding through endless CAD revisions, trying every idea I could think of and measuring over and over when I had no good plan for noise countermeasures. Honestly, it was fun.

I know the taste of ramen eaten in the middle of a late-night work session, and I remember the pleasant rush of dopamine staring down a mountain of tasks.

Sometimes I even think I’d like to go back to that.

But I can’t forget that, at this point, that mindset isn’t something to be praised.

There’s other work to do. I’m in my current position precisely because I wanted that.

Of course there are times for emergency operational response. But it should never be done with any swagger. It’s entirely normal to get no praise for it, perfectly fine not to be thanked, and one should be careful never to act proud of it, or let others perceive it that way, and it has to be done with an awareness of getting back to one’s real job as quickly as possible.

In a culture like Japan’s, which strongly demands homogeneity, this tends to get romanticized as “what a warm company, where the higher-ups get out onto the floor.”

This is a big mistake.

What needs to be said is: “No, you’re just slacking off on your actual job.”


Originally published in Japanese at https://clazytech.com/2022/09/1486/. Translated with LLM assistance and reviewed before publication.