What I Look for When I Enter an Organization
By Joe Cozart
There is one room I am always interested in entering.
It is your conference room.
If I were working with your company, I would begin there, although perhaps not in the way you would expect. I would not arrive assuming that your company is broken. I would not begin with a predetermined framework looking for places to impose itself. I would not assume that the people who have spent years building the organization somehow understand it less because someone from outside has entered the room. That would be both arrogant and analytically useless.
I would listen.
Not passively. Not politely while waiting for my opportunity to speak. I would listen for architecture.
Every organization has one.
There is the company described on its website, the company represented in presentations, the company contained in financial statements and strategic plans, and then there is the company that actually exists in the accumulated decisions people make every day. Those versions frequently overlap. They are rarely identical.
I would want to know where they separate.
I would listen to the language people use when they explain what the company does well. I would listen even more carefully when they explain what cannot be changed. I would pay attention to the sentences that begin with “We have always,” “Our customers expect,” “The industry requires,” “That won’t work here,” and perhaps the most consequential phrase in organizational life: “Everybody knows.”
“Everybody knows” is where I become interested.
Not because consensus is necessarily wrong. Most of the time, there are perfectly good reasons why intelligent people have arrived at the same conclusion. I become interested because the assumptions least likely to be examined are often the ones that no longer feel like assumptions.
They have become facts without remembering when they became facts.
Expertise creates an interesting vulnerability here. The more thoroughly we understand a system, the more difficult it can become to distinguish what the system actually requires from what experience has taught us to expect. Expertise is enormously valuable. I would never substitute an outsider’s novelty for the accumulated knowledge of people who understand their business.
But familiarity has a peculiar way of converting yesterday’s explanation into today’s reality without requiring the explanation to prove itself again.
That is the organizational problem that interests me.
I am rarely most interested in what a company does not know.
I am interested in what it knows that may no longer be true.
Those are very different problems.
An information problem can often be solved by obtaining more information. Hire the specialist. Commission the study. Purchase the data. Conduct the survey. Bring another dashboard onto another screen.
An assumption problem behaves differently.
More information can actually make it worse.
If the underlying question is wrong, additional data may simply allow the organization to answer the wrong question with greater precision.
That is where I begin working.
Before recommending what your company should do next, I want to understand how it decides what matters now. Which variables have been given authority? Which measurements actually predict the outcome you care about? Which measurements remain because they are familiar? Which processes exist because they solve a current problem, and which survive because removing them would require someone to acknowledge that the problem they were designed to solve no longer exists?
I am listening for noise that has acquired institutional status.
Every organization has some.
Success creates it as readily as failure.
In fact, successful organizations can be particularly vulnerable because yesterday’s correct decision possesses evidence on its side. It worked. The company grew. The strategy succeeded. The market responded. The executive was promoted. The process became institutionalized.
Then circumstances changed.
The process remained.
Eventually nobody remembers the circumstances that created it.
They remember only the process.
This is why one of the simplest questions I can ask an organization is also one of the most revealing.
What are we actually trying to accomplish?
It sounds elementary.
It almost never is.
Organizations accumulate secondary objectives with astonishing ease. Protect the department. Preserve the reporting structure. Maintain the relationship. Avoid embarrassing the person who proposed the initiative. Satisfy the metric. Defend the budget. Continue the program. Produce the presentation demonstrating that the strategy remains on course.
None of these necessarily begins as deception. Most begin as perfectly understandable human behavior.
But slowly an organization can begin optimizing the preservation of its own explanations rather than the achievement of its original objective.
That is when I become useful.
Not because I know your company better than you do.
I shouldn’t.
You know things about your company I could never know from the outside.
My advantage is different.
I am not carrying its history.
I did not propose last year’s strategy. I am not protecting the organizational chart. I do not need the previous forecast to have been correct. I am not seeking promotion from the executive whose assumption may need to be questioned. I have no emotional investment in preserving a sentence merely because that sentence appears in twelve previous presentations.
I can stand at a slightly different distance.
Distance does not make me right.
It makes certain things easier to see.
Those are not the same proposition.
If I confused them, I would become precisely the kind of consultant I would never want advising me: the outsider who mistakes unfamiliarity for insight and confidence for clarity.
My work therefore does not begin by telling you what I see.
It begins by testing whether what I think I see survives what you know.
That is where the conversation becomes interesting.
I might ask a question that initially seems almost embarrassingly simple. Someone in the room answers it. Another person adds context. A third person explains why the answer is more complicated than the question suggests.
Good.
Now we are getting somewhere.
I ask another question.
And another.
Not because I already know where the questions lead, but because I want to discover where the explanation begins requiring protection.
That moment matters.
There is usually a point in a complicated system where explanation changes character. Before that point, people describe what happens. After that point, they begin explaining why what happens must happen.
I listen very carefully there.
Because somewhere near that boundary, an assumption is often hiding.
Perhaps the assumption is correct.
Then it survives.
Perhaps it was correct five years ago.
Then we ask whether the conditions that made it correct still exist.
Perhaps nobody remembers where it came from.
Then we have found something worth examining.
And perhaps, occasionally, the assumption collapses almost immediately once somebody finally says it aloud.
Those are remarkable moments.
Nothing physical has changed.
The company has the same employees, customers, assets, liabilities, contracts, technology and competitors it had sixty seconds earlier.
But the room is different.
A sentence that had been carrying authority has lost it.
Possibility enters through the space it leaves behind.
That is the moment I work toward.
Not disruption for its own sake.
Not novelty.
Not the theatrical pleasure of telling intelligent people that they have been wrong.
Clarity.
The removal of something that was unnecessarily limiting the field of view.
And then comes the part consulting often gets backward.
I do not want you dependent upon me for the answer.
I want the organization capable of seeing the question.
Because an answer solves one problem.
A better way of seeing changes what happens when the next problem arrives.
That is the distinction between advice and clarity.
Advice says: Do this.
Clarity asks: Why does this appear to be the thing we should do?
Then it keeps going.
What would have to be true for this decision to work? Which of those things do we know? Which are assumptions? Which can we test? What happens if the assumption fails? What are we measuring? Why are we measuring it? What aren’t we measuring because we decided long ago that it did not matter?
And perhaps the most uncomfortable question of all:
What would we have to discover before we were willing to change our minds?
That question changes rooms.
Because now we are no longer defending a strategy.
We are examining it.
We are no longer asking whether we can produce enough evidence to support what we already believe.
We are asking whether what we believe deserves to survive.
There is an enormous difference.
If I were working with you, I would not promise that I would walk into your conference room and discover something everyone else had missed. Sometimes the organization is right. Sometimes the strategy is sound. Sometimes the assumptions survive examination precisely because they are good assumptions.
That is useful too.
Clarity does not require a surprising answer.
It requires an examined one.
This is not a hypothetical method I reserve for essays. It is the work I do. I enter complicated systems without needing them to be broken. I listen long enough to understand the architecture that produced them, and then I begin looking for the distance between what an organization knows and what it has simply stopped questioning.
Sometimes that distance is insignificant.
Sometimes an entire strategy is hiding inside it.
But if something does not survive examination, I want to know.
So should you.
Because somewhere inside every organization there are things everybody knows.
Most of them are probably true.
A few may not be.
And sometimes the distance between those two categories is the distance between the company you have and the company you could have.
That is the room I want to enter.
——— GMJoe™ ———
Clarity. Strategy. Sovereignty.
Books by Joe Cozart are available at: amazon.com/author/joecozart
GMJoe.org
Joe Cozart is a writer and consultant based in North Dakota. His work explores the intersection of political performance, cultural clarity, and the architecture of power. He is the creator of the GMJoe™ consulting voice and author of several longform essay series exploring sovereignty, institutional systems, industrial civilization, and the recursive tensions shaping the modern age.