When pattern recognition goes wrong…

Appearances can be deceiving.

Pattern recognition is one of the most valuable skills a Chief of Staff can develop. With experience comes an ability to spot recurring dynamics, recognise familiar behaviours and identify the root causes behind problems that initially appear unrelated. It's one of the ways experienced Chiefs create disproportionate value. They can often see where a situation is heading before anyone else does.

The trouble is that pattern recognition has a habit of turning into pattern assumption.

At first glance, that sounds like a fairly trivial distinction. In practice, it can be perilous. Recognising a pattern should generate a hypothesis. Assuming a pattern leads you to believe you've already found the answer. Once that happens, your curiosity starts to disappear, and with it, one of the most important ingredients in a trusting relationship with your Principal.

Experience can create certainty

Experience rewards speed. If you've seen the same organisational dynamic play out five or six times before, it's perfectly natural to assume you're looking at it again.

Your Principal wants to restructure a team. You suspect the real issue is a lack of strategic clarity. They ask for another board deck. You think the underlying problem is indecision. They become frustrated with a stakeholder, and you're fairly sure you've seen this particular relationship dynamic before.

Sometimes you'll be right.

The problem isn't recognising something familiar. In fact, that's exactly what experience should help you do. The problem begins when that recognition quietly becomes certainty before you've fully understood the situation in front of you.

Once you've decided you know what's really going on, you start listening differently. Instead of trying to understand your Principal's perspective, you're looking for evidence that supports the explanation you've already formed. Questions become less exploratory. Contradictory details become easier to overlook. Without meaning to, you've moved from investigation to confirmation.

Trust is built through actively listening

There's another consequence that's less obvious.

Trust isn't simply built on giving consistently good advice. It also depends on whether people feel understood. Those two things are related, but they aren't the same.

Most of us have experienced conversations where someone immediately tells us what our problem actually is. Sometimes they're correct. It rarely feels that way in the moment. Instead, it often feels like they've skipped past what we were trying to say in favour of demonstrating that they've already worked it out.

It's surprisingly easy to create the same experience for your Principal.

As soon as you assume you know better than they do what they need, the conversation subtly shifts. Your focus moves away from understanding their perspective and towards validating your own interpretation. Even if you eventually reach the right conclusion, your Principal may leave the conversation feeling that they weren't really listened to.

Over time, those moments accumulate. Trust doesn't usually disappear because of one spectacular mistake. More often, it fades because someone no longer feels heard.

What your principal wants must be taken seriously

Chiefs of Staff spend much of their time looking beyond symptoms. That's a useful instinct, but it can encourage us to dismiss what our Principal says they want because we're more interested in what we think they need.

The difficulty is that wants contain information.

What someone wants tells you what currently feels important, frustrating or meaningful to them. It tells you where their attention is and, often, why they're seeking your help in the first place. If you move too quickly to your own diagnosis, you lose the opportunity to understand what sits behind that request.

More importantly, you risk communicating something you probably never intended.

That the thing your Principal cares about isn't actually worth engaging with.

Very few people respond well to that. Principals are no different.

Ironically, taking someone's stated wants seriously is often the quickest route to understanding their deeper needs. Once people feel they've been listened to properly, they're usually far more willing to explore alternative perspectives. Curiosity builds trust, and trust creates the conditions for better conversations.

Keep your patterns, just lose the certainty

None of this means ignoring your instincts. Experience is valuable precisely because it helps you generate better hypotheses than someone seeing a situation for the first time.

The challenge is remembering that a hypothesis is still something to test.

When you notice a familiar pattern, treat it as the beginning of your thinking rather than the end of it. Ask another question. Look for the details that don't quite fit. Stay open to the possibility that this situation resembles something you've seen before without necessarily being the same thing.

Your judgement becomes more valuable as your experience grows. The temptation is to become increasingly certain of it. The better habit is to become increasingly curious.

Pattern recognition is one of the defining strengths of an effective Chief of Staff. Just don't let it become a substitute for listening.

Ready to set off on your journey towards excelling as a Chief of Staff? I’d love to support you. If you’d like to explore how we could work together, book a call here or sign up to the Chiefly newsletter below.

Previous
Previous

Chiefs of Staff aren’t an excuse for poor leadership

Next
Next

Silence is golden