For much of my working life, I had more questions than answers.
This was not always convenient. I worked in a world that valued certainty, speed and solutions. A problem arrived and an answer was expected: a new process, a revised structure, a dashboard, perhaps another workshop. Questions were welcome as long as they led quickly to something that could be presented in a meeting.
I often lingered before that point.
Why had the problem appeared now? Why had earlier attempts failed? Why did two teams describe the same workplace so differently? Why did the official process bear so little resemblance to the way work moved? Why were capable people waiting for permission? What had they learnt about acting without it?
I did not have a name for this way of working. I only sensed that the question placed before me was often one fragment of a larger story.
Over time, I came to think of it as organisational seeing.
The question beneath the question
Most organisational problems arrive dressed as practical requests.
A founder wants a dashboard. A leadership team wants greater accountability. A growing company needs a new structure. Decisions take too long, meetings multiply and work keeps returning to the same few people.
The request is valid, though it may not reveal enough.
A dashboard may expose the absence of agreed goals or useful measures. An accountability concern may have less to do with attitude than with authority. A communication issue may begin with competing priorities. A founder struggling to delegate may be surrounded by people who lack the context, confidence or permission to exercise judgement.
The visible difficulty is sometimes one sign of a wider condition.
Organisational seeing is the practice of noticing those connections. It examines how structures, habits, relationships, histories and assumptions influence what happens each day. It is interested in the workplace as lived, rather than only as described in plans, charts and policies.
Seeing with more than the eyes
Seeing, as I understand it, involves more than looking.
We perceive through conversation, attention, memory and the senses. A pause before someone answers can carry information. So can the atmosphere of a meeting, the repetition of a phrase, the absence of disagreement or the change in a room when a senior leader enters.
Language offers its own map.
Leaders may speak about ownership while their teams speak about permission. One group may call an initiative transformation; another may experience it as disruption. Words such as urgency, alignment and accountability acquire local meanings, often far removed from their dictionary definitions.
Listening to these differences helps me understand how people experience the place in which they work. Language can reveal where trust sits, which subjects are safe to raise and which realities have become difficult to name.
I also pay attention to movement.
Where does information travel easily, and where does it stop? Which decisions rise to the top despite formal delegation? Who connects groups that the organisation chart keeps apart? Where does progress rely on memory, personal influence or repeated acts of rescue?
These currents rarely appear in official documents. Yet they often determine whether the work moves at all.
The tree and the forest
A struggling tree can be studied as an isolated object. We can examine its leaves, prune its branches or support its trunk. Some of this may help.
But the tree belongs to a forest.
Its growth depends on the soil, light, water, neighbouring roots and the wider ecology around it. Treating the tree without examining those conditions may improve its appearance while leaving the cause of its struggle untouched.
A similar relationship exists within organisations.
A manager cannot be understood entirely apart from the leadership environment around them. Their performance may be affected by vague authority, competing demands or decisions repeatedly overturned from above. A process may fail because it crosses boundaries that teams have never learned to work across. Behaviour labelled as resistance may be a sensible response to previous experience.
This asks us to move beyond “What is wrong with this person, team or process?” towards a different line of enquiry:
What surrounds it? What does it depend on? Do those conditions allow it to grow?
The tree matters. So does the forest. Seeing requires us to hold both in view.
Staying with the difficulty
Organisations are rewarded for responding quickly.
A problem appears, a solution is proposed and an initiative begins. Software is introduced. A role is created. A procedure is documented. Another dashboard joins the quiet cemetery of dashboards nobody trusts.
Action creates a comforting impression of progress. Yet moving too quickly can prevent a company from understanding what it is trying to change.
Some situations need to be sat with.
- What keeps happening?
- When did it begin?
- Who experiences it differently?
- What tends to happen just before the work stalls?
- Where does practice depart from procedure?
- Which decisions are postponed, returned or quietly avoided?
- What conduct is rewarded, despite what leaders claim to value?
A quick answer may be plausible, tidy and insufficient. Remaining with the enquiry gives less obvious details time to surface.
The intention is never to make a straightforward matter seem complicated. It is to understand enough of the situation to respond with greater precision.
The organisation on paper and the one people inhabit
Every organisation has a formal version of itself.
It can be found in reporting lines, job descriptions, policies, strategic plans, processes and governance forums.
There is also the organisation people inhabit: the colleague everyone consults before deciding, the meeting where the real agreement occurs, the knowledge stored in one person’s memory and the senior figure whose approval is still sought despite having no formal part in the matter.
The first describes how work is meant to happen. The second shows how it travels.
A chart may distribute authority among several leaders while daily habits continue to draw decisions towards the founder. A process may assign ownership clearly while incentives encourage each function to protect its own interests. A strategy may declare three priorities while leadership attention communicates twelve.
The difficulty here cannot be repaired through better documentation alone. The formal design and everyday reality have drifted apart.
Informal arrangements often arise because the official machinery cannot carry the work. A trusted employee becomes an unofficial coordinator because no other connection exists between teams. A founder stays close to minor decisions because few shared principles guide them. Staff develop workarounds because the prescribed route no longer fits what they encounter.
What appears dysfunctional from one vantage point may once have been an intelligent adaptation.
The task is to understand why it arose, what purpose it serves now and what it may be costing the organisation.
How I practise seeing
My own approach begins with curiosity rather than a ready-made framework.
I ask questions and observe before translating what I hear into familiar consulting language. Each organisation has its own vocabulary, history and internal logic. Learning those matters.
Origin stories are particularly revealing because old choices leave traces.
Close founder oversight may once have protected quality. Hiring through personal networks may have supported speed and trust. A weekly meeting created for five people may survive as an exhausting ritual for fifty. Arrangements endure long after the circumstances that produced them have disappeared.
I watch how leaders work with their teams: what they invite, interrupt or ignore; which decisions they retain; how they respond when somebody disagrees; whether people leave a conversation with greater agency or further dependence. Leadership is communicated through such moments long before it appears in a statement of values.
Resistance also deserves attention. It can point to fear, threatened status, poor incentives, weak trust, limited capacity or the memory of initiatives that vanished without explanation. Treating every hesitation as unwillingness is an efficient way to misread people.
From there, I follow the friction.
Does it originate in the structure, the culture, the technology or the relationships between people? Are employees missing skill, information, time or authority? Has a question of capability been mistaken for one of motivation? Does the difficulty belong to a single part of the business, or does it arise when several parts meet?
Experience helps, although it carries its own danger. Familiarity with certain problems can tempt us to recognise them too soon. Seeing demands that I remain open long enough for this particular organisation to contradict what I think I know.
A practice still in development
I am still learning to see.
That matters because no one stands outside an organisation with a complete and impartial view. Each person perceives it from a particular position, influenced by role, history, loyalty, incentives and experience. A consultant has a position too.
Any interpretation I form begins as a proposition to be tested. It must be held against different accounts, evidence from the work and the consequences people experience.
A single conversation can alter the picture. Someone described as resistant may reveal a constraint others have missed. A convincing explanation may fail because human systems remain more contradictory than the diagrams built to contain them.
Seeing develops through returning, listening and revising. It calls for enough confidence to name what may be happening and enough humility to be changed by what appears next.
Perhaps this is why having more questions than answers no longer feels like a professional weakness to me. The right question can loosen an explanation that has hardened into fact. It can make familiar arrangements visible again. It can help people recognise that what they accepted as inevitable was, at some earlier point, a choice.
From attention to action
Observation alone changes little. What is noticed must eventually inform what is done.
The response may involve clarifying authority, roles or accountability. It may require a different flow of information, knowledge or work. Sometimes leadership habits must change because they keep recreating the very conditions a new structure was intended to remove.
Usually, several elements are involved. Redrawing the chart while leaving behaviour untouched merely gives the old organisation new boxes to occupy.
A useful response asks:
- What needs to become clearer?
- What must people be able to do that they cannot do today?
- What should no longer depend on memory, heroic effort or quiet influence?
- What conditions would allow this part of the organisation to grow?
- What needs to change in the surrounding forest?
The aim is to help an organisation become better able to notice, decide and adapt without remaining dependent on an outsider.
Organisational seeing begins with the possibility that the first question is an entrance rather than a conclusion.
Redesigning a structure requires attention to how authority already travels. Changing behaviour means considering what people have learnt from their surroundings. Automating a process calls for an understanding of the judgement and human exchange held within the work. Tending to the tree begins with the forest in which it is trying to grow.
For me, this remains a developing practice. Its purpose is not to arrive with more answers than everyone else, but to ask questions that help an organisation see itself more fully: what it has become, what no longer serves the work and what might still be possible.