It is completely unthinkable that someone would hire a Data Engineer who had no skills in Python, Java, or SQL. How could they possibly fulfil the demands of the role without foundational capabilities? We view these as concrete skills requiring instruction, practice, and continuous development, and rightfully so.

Across the previous five posts in this series, we explored Peter Hawkins' 5 Disciplines of team effectiveness individually: Commissioning, Clarifying, Co-creating, Connecting, and Core Learning.

In practice however, leadership teams rarely have the luxury of addressing these disciplines one at a time, life just doesn’t work that way. Most organisations operate under constant commercial pressure, shifting priorities, and continuous workload demands. Whenever a new frameworks is taught as an isolated module, leaders often struggle to apply them to the chaos of daily delivery. Intellectually the stimulate, but making the transition from theory to reality is a challenge.

How often does a scheduled retrospective get pushed back in your diary, again and again, until it simply disappears because too much time has passed? Or when the session actually happens, how often does it feel like going through the motions?

How often do you, as a leadership team, regularly reflect on how you work together in the moment while the work is happening, rather than treating reflection as a separate, isolated calendar entry?

Over the past decade, the widespread adoption of Agile methods brought the retrospective into everyday corporate routines. While this shift productionised the idea of looking back, it frequently hollowed out its substance. In practice, retrospectives often become mechanical exercises. Teams gather to fill digital whiteboards, list minor process tweaks, and move swiftly on to the next backlog.

Christopher Nolan's Odysseus has brought ancient Greek mythology back into the spotlight, making it worth remembering how the Trojan War actually started: an uninvited guest throwing a golden apple into a wedding feast.

In large institutions, leadership teams frequently repeat King Peleus' mistake. They engage comfortable allies and senior sponsors (thank Zeus), while leaving awkward or inconvenient voices across compliance, risk, or audit off the guest list. Months down the line, that neglected stakeholder appears with an apple of discord that halts delivery.

In many organisations, when cross-functional collaboration falters, senior management defaults to social bonding. Offsites are organised, team-building exercises are scheduled, and the general assumption is that if leaders simply spent more time together, joint working would improve.

Discover why executive team charters are frequently filed away and how leadership teams can build active alignment that lasts.

Discover why senior teams suffer from strategic drift and how establishing an explicit mandate prevents costly external interventions.

Why a comfortable executive team might be a failing one. Discover why true psychological safety means moving past camaraderie and into real strategic value.

Discover the ultimate reward of shifting from reactive safety to creative leadership using Bob and Bill's framework. Learn how to achieve progress that holds.

In the final part of our series, discover how leaders use intellectual distance to insulate themselves from risk, and how to shift to authentic leadership.

Discover how hierarchical pressure and the fear of negative feedback drive senior leader burnout. Learn how to shift from safe compliance to true relational leadership.

Are you driving your team's performance, or are you just gripping the steering wheel too tightly?

Most senior executives reached the top because of their relentless drive for quality. In leadership theory, this is called The Will. You tolerate pressure, you focus on delivery, and you expect high performance from yourself and others.

Your greatest leadership liability is almost certainly just an overuse of your greatest asset.

When a senior leader is described as overly controlling, overly detached, or too agreeable, we aren't looking at a lack of talent. We are looking at a brilliant person who is leaning too hard on the very tools that got them to the senior table in the first place. They are running a high-powered machine on a restricted Safe Mode setting.

Leadership is a broadcast, not a private conversation.

Your internal "Safe Mode"—that subconscious need to be right, to be liked, or to be in control—does not stay under the bonnet. It creates the weather for everyone around you. If you are playing not to lose, your team will eventually stop trying to win.

80% of leaders are stuck in a Reactive mindset. Discover why shifting to Creative leadership is the key to both personal growth and bottom-line performance.

We often fail because we try to solve Adaptive Challenges with Technical Solutions. We try to fix a lack of trust with a new feedback model, or a lack of collaboration by redrawing the org chart. These are technical band-aids on adaptive wounds.

“Do you have any tips or tricks?”

It is one of the most common questions I get from leaders. But in a complex organisation, more information is rarely the answer. You don't need a new "tip." You need more capacity.

Even the most popular tips, like blocking out "thinking time" in your diary, fail if your internal operating system still values "being busy" over "being clear."

In my latest post, I discuss why we need to move past horizontal skills and focus on upgrading our internal capacity to lead. At Bywater, we focus on the thinking that leads to progress that holds.