Leadership listening is a design skill

Listening is part of designing an organisation that can execute. Leaders need to understand how people interpret a proposed direction, which constraints shape their choices, and where the intended change conflicts with the work. Without that information, a clear presentation can still produce several incompatible versions of the same strategy.

In my EA 878 paper on strategic communication, I argued that architecture leadership must help people develop shared understanding. Executives, delivery teams, operations, and governance partners may hear different implications in the same proposal. The leader’s job includes discovering those differences while the design can still change.

Ask people to describe the work

A general question such as whether someone supports the strategy often produces a general answer. A more useful conversation asks what they would do differently next week, which decision they would need to make, and what might prevent them from acting. The explanation reveals the practical meaning they have assigned to the direction.

Consider a proposal for a common planning process. One manager may hear a consistent set of definitions. Another may hear central control over all local priorities. A third may assume that the existing process will continue with a new reporting format. Each can express support while expecting a different operating arrangement.

The leader should bring those interpretations into the discussion and resolve the material differences. This may require a clearer description of the future process, an explicit decision about authority, or a change to the proposal. Repeating the original message more forcefully would leave the underlying disagreement intact.

Treat objections as information to investigate

An objection may reveal a legitimate delivery commitment, an overlooked dependency, or a concern about how effort and credit will be distributed. It may also reflect a preference the organisation cannot accommodate. Listening does not mean accepting every objection. It means understanding the reason before deciding how to respond.

I would ask for a concrete example. When would the proposed approach become difficult? What would happen to the next team? Which current control would be weakened? Specific cases help separate a design weakness from a misunderstanding and make the trade-off easier to assess. They also invite participants to contribute knowledge rather than defend a position.

Leaders should pay attention to what is difficult to say publicly. A team may hesitate to admit that its records are incomplete or that it lacks capacity for the change. Smaller discussions and direct observation can provide a more accurate picture than a large status meeting. The purpose is to improve the plan, with discretion and respect for the people involved.

Close the loop with a decision

Listening loses credibility when people cannot see what happened to their contribution. After a discussion, the leader should explain which issue changed the design, which concern needs more evidence, and which trade-off has been decided. Where a request cannot be accommodated, a clear reason is more useful than an ambiguous promise to consider it.

The same discipline should continue after implementation begins. Employees can show where the actual work differs from the planned process. That feedback helps distinguish an adoption problem from a design problem. Both require action, but they need different responses and should not be combined under a general demand for greater compliance.

Effective listening improves the enterprise’s understanding of itself. It gives leaders access to the conditions that determine whether a strategy can be used, and it turns communication into a continuous part of designing and improving the work.