Executive Judgment in Unfamiliar Systems

The fine line between solving problems and misreading the context

In the first weeks of a new senior role, things can feel awkward and unnatural.

Our decision-making feels clunky. We’re missing knowledge of the customs and processes that enable us to move at speed. At the same time, we see early signs that things could be clearer, faster, and more effective. Our instinct is to act to demonstrate capability, reinforce the hiring decision and gain confidence.

The problem is, we don’t know what we’re missing. We don't know what the organisation is optimising for, which inefficiencies are deliberate trade-offs and which are consequences of previous decisions, why previous attempts to change things have broken down or how decisions get made when the pressure is real.

It’s tempting to rely on our track record, reference past successes and draw parallels when making recommendations. Track record might be why we were hired, but once inside a new organisation, that history carries very little weight. “Show me what you can do here” is much more prevalent than “tell me what you’ve done elsewhere”.

What's being assessed is whether we can exercise sound judgment in a context we don't yet understand. That is what determines how much autonomy we're given. People are forming a view on whether our judgment holds under the conditions we're actually operating in.

That assessment happens in moments that carry more consequence than we might think.

We're in a leadership meeting, and a decision is moving toward closure. The logic is incomplete, and the gaps are visible. We also know that stepping in, especially this early, will shift the conversation. We're not just adding a perspective; we're changing who “owns” the room. So we choose how to intervene carefully, aware that how we do it will be noticed by everyone.

We're asked to review a plan that doesn't meet the standard we're used to. We could call it out immediately. Instead, we sit with what's there long enough to understand what the team believes good looks like, and why. Not because we’re prepared to accept it, but because we need to understand it.

We hear frustration about a process that is clearly inefficient, and there's a clear expectation that we'll fix it. Often, the process is compensating for something else: capability gaps, risk sensitivity, or a previous failure that left the team feeling shy about taking a different direction. Changing it too quickly risks removing the symptom without understanding the cause.

Patience to understand can be tough for those of us with a burning bias for problem-solving.

Move too early, and we risk solving the wrong problem, or solving it in a way the organisation can't absorb. The work gets done and then undone, or worse, quietly worked around. Move too slowly and something else happens: we are seen as someone who can operate within the system, but not someone who can shift it.

The work at this stage is to show that we understand what we're intervening in and that when we do act, we do so with enough understanding and precision that people are willing to follow.

At this stage, our colleagues and team members start to look at our behaviour patterns.

Do we assume the problem is obvious, or do we spend time on what sits behind it? Do we move quickly to improve, or do we first establish that we can operate within what already exists? Do we challenge in a way that sharpens the conversation, or in a way that pulls it toward us?

None of this is formally assessed; it quietly accumulates in the background.

Over time, these form a view of whether we can be trusted. Once that confidence starts to build, the system responds differently. Our questions carry more weight. The same intervention that would have been resisted early is now considered on its merits. It shows up in how quickly people align when we speak, and how we require less context before acting.

Having said all that, the idea of "earning the right" to change things can point us in the wrong direction. It implies a linear sequence of understand first, act later. In practice, both are happening simultaneously. We are forming a view on the system while the system is forming a view on us, and every action, intervention, and moment of decision and restraint contributes to that picture.

The goal isn't to wait or to prove value as quickly as possible. It's to establish that our judgment holds in our new context so that our decisions will be supported and executed as intended.