They did not act like one.
When he inherited the engineering organization, he expected challenges. What he found surprised him. Multiple groups, each doing their own version of the same work. Different tools. Different standards. Different definitions of what good looked like. Overlap nobody knew about and nobody had mapped.
Nobody had failed. Nobody had made a single bad decision that caused it. The organization had simply drifted. Over years and leadership changes and shifting priorities, the groups had stopped acting like parts of a whole and started acting like independent teams who happened to share a name.
The result was an organization that had lost the respect of the people it was supposed to serve.
He could have addressed the symptoms. Consolidated tools. Standardized processes. Shuffled responsibilities. But he had seen that approach before. It fixes the surface without touching what caused the drift.
The real problem was not process. It was clarity.
Nobody could answer the same questions the same way. What does this organization exist to do? How does each group’s work connect to the others? What does each person own and where does their responsibility end and someone else’s begin?
So he started there.
He built an architect team and led it himself. Not to do the work for everyone else but to build the shared picture the organization had lost. Vision first. Direction second. Standards third. Then clear roles for each group, and finally clear responsibilities for each individual within them.
And then he repeated it. In every meeting. In every one on one. Every time a decision got made or a question surfaced about how something should work. He said the same things until they stopped needing to be said because the organization had internalized them.
Eighteen months later the engineering organization was recognized as one of the best in the industry.
Not because the people changed. Because the clarity did.
Here is why this matters for every new technical leader reading this.
The same drift that happened to that organization can happen inside a single team. When individuals start solving their own problems their own way, without a shared picture of what the team exists to do and how each person’s work connects, the team quietly stops being a team. It becomes a group of people who happen to share a manager.
The new leader almost never sees it coming. They were rewarded their entire career for independent excellence. Deep focus. Personal output. Nobody told them that their job now includes building and sustaining the shared picture that keeps everyone connected.
That is the job. Not just the technical work. The clarity underneath it.
Clarity is not a one-time announcement.
It is a daily practice.
If your team is starting to drift, the clarity conversation cannot wait. dieleconsulting.com.