Clay Tech

"clay-works make things real"

translated from clazytech.com

Field Knowledge Matters As Much As The Numbers

As a textbook convention in business plans, the pattern of “improving operational efficiency,” “efficiency gains and labor cost reduction,” and “therefore the market value is…” comes up often. None of that is wrong, and plenty of people simply won’t engage in conversation without it, so by all means get it in order.

But here I want to talk about the small hidden side that everyone runs into after that. This isn’t some grand revelation I’m building up to — it’s something anyone runs into after taking one or two steps forward with a business.

Let’s imagine a B2B business as an example. Say you target some service industry and pitch it as “We built a software tool (let’s call it App A) that improves operational efficiency by this much!” You immediately approach the person in charge of operations, or someone in the department with authority to decide on adopting outside tools (let’s call him Section Chief B). You build connections aiming to reach the person who actually holds decision-making authority, and eventually you succeed. He (let’s call him Division Head C) really likes it.

Division Head C tells you he’s decided to bring it to the board meeting, and you wait eagerly for the result. After a while, Section Chief B proposes a plan to first trial it at some of their sites for evaluation. A so-called PoC. Naturally you get paid a one-time fee. You’re overjoyed and immediately start preparing for deployment. But be careful. At this stage you’re still completely in the red.

Division Head C’s request is this: “Show us with numbers that operational efficiency improves the way you say it will. If you can do that, we’ll roll it out to all our sites.” This PoC will decide the fate of the company. You head into the field full of energy, but here you’re extremely likely to run into several classic pitfalls.

  1. The field staff haven’t been told

Division Head C tells Section Chief B “I’ll leave the rest to you,” and the section chief talks to Manager D, who controls the site (the person responsible for the facility or department). Up to this point the message might still get through to some degree, but at minimum Manager D’s level of understanding looks like this:

Section Chief B > Division Head C >> Manager D

All Manager D has really “heard” is roughly what the PoC is meant to do, with no idea what goal Division Head C has actually set, but as a manager’s duty, he tells Field Leader E about a month before deployment. Field Leader E may barely even remember your company’s name or the name of the tool being tested. The field is busy every single day. A meeting on how to use the tool gets set up two or three weeks beforehand, and Field Leader E finally understands properly who you are. But he still doesn’t understand the goal or the point of the PoC. You painstakingly explain how to use the tool in careful detail, but Field Leader E keeps wearing a puzzled expression the whole time, thinking “what is this even for?”

So, will this PoC go well? The answer is no.

  1. You get pushback from the field

The field is busy, no matter what. The team assigned to test new tools tends to be fixed at most companies. But they are not a team set up for this — they have their regular work. Now they’re made to learn an unfamiliar tool, made to read through documentation on top of their regular work, made to fill out surveys at the end of it all. It would be strange if they didn’t push back. To them, you are the enemy itself. Field Leader E might say something like “well, just bear with it” to his team members, but the outcome still tends to tilt in an unfavorable direction.

  1. It turns out the field doesn’t actually welcome this

And this is the biggest tragedy. You start to feel disgust toward the field staff pushing back. “We built such a convenient tool — why won’t you use it more comfortably!” “You’re just using it wrong!” “At least read the manual before touching it!” — and so on. But look carefully and observe them. Take a case like this. Their work rarely has them sitting at a desk during the day, and they spend very little time looking at a PC screen. What screen time they do have is for things like checking schedules, checking email, processing slips — minor clerical tasks that make up only a tiny fraction of their overall workload. Your tool may be very convenient and might shorten the time they spend at their desk, but —

what’s the point of shortening something that’s already short?

Their actual pain point was rather something like “please do something about the situation where we almost never get to sit at a desk and work calmly.”

You could have grasped this fact immediately just by visiting the site and sitting there for half a day. Only here do you finally understand that juggling numbers on paper means nothing.

A simulation like this is somewhat abstract (that’s intentional), but as stated at the outset, it’s the small hidden side that everyone runs into. “The small space just behind the screen” might be a more accurate way to put it.

How can you avoid situations like this? It’s extremely simple.

That’s it. Even startups that ultimately achieved spectacular success very often tell stories like “back then we ended up building a service the field never needed at all.” Everyone does something like that once or twice, regrets it, and corrects course next time. Having read this, I hope you’ll take the chance to reexamine your own situation from square one.

A good keyword for systematically understanding this situation is as follows:

“Understand that stakeholders span many layers.”

Executives are satisfied by improved numbers. A division head is satisfied if it looks like they can deliver numbers that will please the executives. A section chief is satisfied if results look likely to align with their own mission. A site manager just hopes, above all, that no complaints come up from below. A leader says “can’t be helped, it’s an order from above” while actually thinking it’s unnecessary if it doesn’t benefit their own team. Members are busy no matter what, and are constantly pleading for someone to do something about that. The moment their workload increases even slightly, they show immediate rejection. The recipient of the service (the client) wants the best possible service at the lowest possible cost.

Each of them is thinking something completely different, and their values differ too. Yet you need to satisfy all of them cleanly. When working out a business plan, there’s an inevitable tendency to only consider the interests of people above a certain layer. That’s correct in a sense (securing the person with decision-making authority is the most basic basic of negotiation), but you need to know that this alone is far from sufficient.


Author Profile

Yuichiro “kuz” Kuzuryu Engineer / Executive Has experience falling into all manner of deep valleys, from launching new businesses at major Japanese corporations to Silicon Valley startups. CEO, Founder, ClayTech Inc. Director, EYS-STYLE Inc. Director, 144Lab Inc. Visiting Professor, Tohoku University Also serves as technical advisor to several other companies https://twitter.com/qzuryu https://www.facebook.com/qzuryu https://www.linkedin.com/in/yuichiro-kuzuryu-kuz-27b92838/

Originally published in Japanese at https://clazytech.com/2019/10/265/. Translated with LLM assistance and reviewed before publication.