Clay Tech

"clay-works make things real"

translated from clazytech.com

Rigor Clashes Split Contract Workers From Product Teams

As discussed in another section, gathering people with shared context is highly effective when speed matters. Here I want to touch on character as culture.

Where exactly does cultural conflict arise in the first place?

Of the many cases I’ve seen, one typical pattern is “conflict over rigor.”

For example, people who have built their careers largely doing contracted work tend to hold a high standard of rigor around specifications and contracts. Overturning a specification formally agreed with a client later on is extremely costly, and it’s far from rare for someone to stumble onto an exceptional clause buried in a contract and end up in litigation over it. People whose careers have mostly involved shipping their own company’s products as one-off efforts, on the other hand, often arrive at this point having paid little attention to preserving specifications or, in some cases, even design data. What complicates things further is that someone with the former kind of career sometimes joins a company believing “this time it’s the latter,” and someone with the latter kind of career sometimes joins believing “this time it’s the former.” Left alone, these gaps in perception rarely resolve themselves naturally.

Clear leadership is therefore required. Someone has to set direction, build the right structures, and have experienced members model the right behavior. How rigor should be understood is up to each company. There’s no single right answer for development processes, internal approval workflows, or client communication. But laying out a clear policy — “here’s how we think about this” — can keep it from turning into a major problem.

The next pattern I often see might be called “conflict over the reach of information.”

That’s a slightly clunky way of putting it, but essentially it’s the conflict that arises from differing senses of how far, and in what way, information discussed among executives or the progress of a special project “should” circulate within the company.

J, who was my boss back in my America days, hated having large numbers of people CC’d on emails, and every time he replied to one, the CC list would often end up shorter than before. I once asked him why, and his answer was, “First, because it’s unnecessary. Also because it becomes unclear who it was sent to and who it wasn’t.” J used to work at Apple, where he reportedly oversaw the MacBook development project.

One classic pattern where the circulation of information turns into a headache, on the other hand, is “when someone leaves the company.” A handoff naturally becomes necessary, and when both the person leaving and the people around them are accustomed to this kind of transition, things tend to go smoothly — but even then, some omission or oversight usually occurs. Workplaces that already maintain a high degree of information circulation naturally reduce this risk. Likewise, in situations like “when part of a project is in crisis,” sharing information within the company early and pooling collective wisdom helps prevent things from getting worse. The longer information sharing is delayed, the worse things get.

Because this kind of conflict mostly surfaces through individual, day-to-day behavior, it can be hard to spot and hard to address. And because each individual instance seems trivial, none of them get taken seriously on their own. But these conflicts gradually produce small distortions, and at some point, somewhere, they can form a major pitfall. It won’t necessarily always happen that way, but judgment is needed on how much of that risk to factor into actual hiring decisions.

For what it’s worth, in America I occasionally came across people who deliberately cut off the flow of information from their own hands. I understand this as a form of self-defense. In other words, they build a small silo of their own to protect their position. People like this have no habit of keeping information organized day to day, so once they’re actually leaving, they scramble to pull together a summary at the last minute. Naturally, it’s riddled with gaps. This can be a major risk factor, so care is needed when hiring.

The content of this post is an excerpt (original text) from the following book. If you’re interested, please consider purchasing it.

The Shape of a Happy IoT Startup

The Shape of a Happy IoT Startup


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