Join us now at Integrity Leaders: Community membership and learning, for new leaders, learner-managers, or first-time founders seeking clarity on their leadership style, and who have a healthy love of sci-fi (more info at the bottom!)

Listen to this week’s podcast episode, Ep.220: Business Operations Systems, AI & Coaching; How to Use Systems Thinking the Right Way, with Scott Abbott, click here to hear it now.

Everybody talks about having balance, but balance is a myth. It's static, rigid, and impossible to maintain in the real world. Instead of balance, what we should be pursuing is harmony because harmony is about integration, rhythm, and flow. Harmony tunes life and leadership into something sustainable, meaningful, and powerful.

Scott Abbott: Founder & CEO, Business & Executive Coach, Investor & Board Member, Best-selling Author

Systems That Serve People

This week on Leading with Integrity, I’m joined by Founder, CEO and best-selling author Scott Abbott for a wide-ranging and grounded conversation about systems.

Not systems as abstract ‘black boxes’ or frameworks for their own sake, but business operating systems, AI, coaching, and what it really means to think systemically without losing sight of the people inside the system.

Because if there’s a tension running through modern leadership right now, it’s this: how do we embrace structure, automation, and intelligent tools without losing sight of the people at the heart of businesses… without becoming rigid, impersonal, or over-engineered?

Scott’s answer to this problem is refreshingly pragmatic…

Why Systems Thinking Is So Often Misunderstood

“Systems thinking” is one of those phrases that sounds impressive but quickly becomes vague. In our conversation, Scott draws an important distinction: a system isn’t just documentation, software, or a playbook. It’s the interconnected set of processes, behaviours, decision rights, and feedback loops that determine how work actually gets done.

Many leaders believe they have systems because they have tools, or flow diagrams (even if hand drawn..!), ‘SOPs’, etc. But tools and bits of paper do not a system make. A CRM isn’t a sales system. A project board isn’t an operations system. An AI tool isn’t a strategy.

Without clarity of purpose, ownership and outcomes, tools create noise rather than leverage; they can muddy the waters, make things more complicated and, worse, create a false sense of security (or in this case a false sense of planning and efficiency).

Scott emphasises that good systems reduce friction, they make decision-making clearer, shorten feedback loops, allow people to spend less time firefighting and more time executing. Bad systems do the opposite: They create bureaucracy, slow things down, and distance leaders from reality.

The Business Operating System as a Leadership Tool

A recurring theme in our discussion is the idea of a Business Operating System as the infrastructure for sustainable growth. As companies/organisations grow, complexity increases, which means communication stretches, assumptions multiply and very soon Founders can no longer rely on proximity or instinct to make good decisions.

At that point, leadership needs to shift from reactive management to structured clarity, Scott talks about this as a need for:

  • Clear priorities

  • Defined roles and responsibilities

  • Consistent meeting rhythms

  • Transparent metrics

  • Accountability mechanisms that are visible and fair

When these are in place, execution becomes less personality-dependent, the organisation no longer relies on heroic effort of its high performers, it runs with rhythm. And therefore becomes less vulnerable to when those high performers inevitably burn out, leave, or both.

And perhaps most importantly, leaders gain space to think strategically rather than constantly plugging gaps, fighting fires, spinning plates… other cliches also available.

AI as a System Amplifier, Not a Substitute

It’s kind of impossible to talk about systems in 2026 without touching on AI. But what struck me most in this episode was the balanced tone Scott takes when talking about our new digital assistants; he doesn’t treat AI as a silver bullet, nor does he dismiss it as hype.

Instead, he frames AI as an amplifier, one that magnifies the strengths and weaknesses of your existing systems. If your processes are unclear, your data inconsistent, and your objectives fuzzy; AI will scale confusion faster. But, if your systems are well-defined, your data clean, and your priorities sharp, AI becomes a powerful multiplier.

This is an important leadership lesson: Technology doesn’t compensate for unclear thinking, it accelerates whatever already exists. (Much like that old adage about alcohol and your personality..? Maybe I’m reaching there…).

The real question for leaders isn’t “How do we use AI?” but “What problem are we solving, and how does AI fit into a coherent system?”

Coaching Inside the System

Given Scott’s background as an executive coach and my own focus on people-first leadership, we also explore the human side of systems. There’s a common fear that systemisation reduces autonomy or creativity, removes the human and the impact that we can and should still have. That once you document processes and introduce structure, you suffocate initiative.

But in practice, the opposite is often true; and I’ve experienced that in my own career: often a good process doesn’t put people’s thinking on rails, but rather removes the unnecessary waste of thinking power being spent on the repetitive, foundational task and processes. Again, there’s a parallel there to the best way to employ AI.

When expectations are clear and decision rights defined, people feel safer to innovate within their lane, because ambiguity drains energy where clarity releases it.

And so, in this context, coaching becomes about alignment instead of motivation. Scott highlights the role of coaching in helping leaders step out of the weeds, delegate more effectively, move from ‘operator’ to ‘architect’ and hold themselves accountable to the system they design.

Systems Thinking, the Right Way

So what does “systems thinking done right” actually look like? From our discussion, several principles stand out… Firstly, start with outcomes, not tools. What result are you trying to produce? Revenue growth? Operational efficiency? Client retention? Without clarity on outcomes, system design is guesswork.

Second, design for simplicity. Complexity often masquerades as sophistication when, in reality, the most effective systems tend to be the clearest and most repeatable.

Third, make ownership explicit. Every key process must have a named owner, unclear responsibility with multiple ‘owners’ leads to neglected systems.

Fourth, build feedback loops. Metrics matter for learning, not reporting, so if a system isn’t producing the desired result: adjust it.

And finally, remember that systems serve people, not the other way around. When leaders forget this, systems become rigid structures that constrain judgment rather than support it.

Shifting from Founder-Driven to System-Driven

For founders and growth-stage leaders, this episode carries particular relevance. In the early stages of a business, energy, ‘cool idea’-ness and proximity can compensate for the absence of structure. Founders know everything, decisions are quick, communication is informal.

But scale changes the equation, Scott speaks candidly about the moment when growth demands discipline. When the leader must transition from being the primary driver of output to the designer of the environment in which output happens.

That shift can be uncomfortable, it requires letting go of control while introducing structure. It requires trust in the system rather than constant intervention. And it requires humility, recognising that sustainable performance is rarely built on personality alone.

Avoiding System Fatigue

Of course, there’s a risk at the other extreme: system overload. Some organisations chase frameworks endlessly, they adopt multiple methodologies, layer upon layer of tools, and confuse teams with constant restructuring.

Scott’s perspective here is measured and a callback to earlier on: systems should clarify, not overwhelm. If a process isn’t adding value, remove it. If a meeting rhythm isn’t producing decisions, redesign it. If a metric isn’t driving action, question why it exists.

Systems thinking is about refining, not adding.

Practical Reflections for Leaders

If you’re considering your own leadership and operations this week, you might reflect on a few questions:

  • Do we have a clear operating rhythm, or are we reacting week to week?

  • Are roles and accountabilities explicit, or assumed?

  • Are we introducing AI thoughtfully within defined processes, or experimenting without direction?

  • As a leader, am I building systems or bypassing them?

The answers to these questions often reveal where friction lives in your team or organisation and that friction, left unaddressed, compounds.

Final Thoughts: Structure as an Expression of Integrity

There’s a strong connection between systems thinking and integrity. Integrity in leadership isn’t only about character, it’s also about consistency. About creating an environment where expectations are clear, standards are maintained and decisions are grounded in principle rather than impulse.

Well-designed systems reflect that consistency, they communicate what matters, they reinforce priorities, they reduce ambiguity. And when paired with thoughtful use of AI and a coaching mindset, they can enable organisations to grow without losing their centre, their purpose or their values.

Scott’s message is that without systems, execution depends too heavily on individuals. With systems, performance becomes repeatable.

If you’re leading a team, scaling a business, or simply feeling the strain of complexity, this episode offers a practical lens: design your system intentionally, use technology wisely and remember that structure (when done well) empowers rather than restricts.

As always, I’d love to hear your reflections and experiences if anything in this newsletter or the podcast this week has rung a bell for you! And tell me, where could clearer systems reduce friction in your organisation?

-

Or, if you’re a video person not an audio one, then you can watch on YouTube too: https://youtu.be/XxHL7mMZ8fc

Join me again next week when I’ll be chatting with Jenny Green about balancing work, life and the education system as a parent, avoiding creepy bosses, good vs bad leadership, and more!

As always, thanks for reading, listening, and supporting; there’s no show without you!

Until next time: Be a Leader Not a Boss,

- David

In case you don’t know me that well, I’m David Hatch and I’m here to help new managers and first-time founders with their leadership skills, so they can become leaders not bosses, lead with integrity, and build happier, higher performing teams, more effective organisations, and, ultimately: successful teams.

Turn away from the dark side of management! If you’re a new manager or first-time leader and you’re feeling lonely, stuck, overwhelmed, or simply ready for your next chapter in leadership, the Integrity Leaders Community offers conversations, courses, resources and support to help you grow one step at a time. If you have a healthy love of sci-fi and want to learn more about leadership, then this is the community for you! Solopreneurs also welcome. 😉

Embrace the Light Side of Leadership today, at: Integrity Leaders: Community membership and learning, for new leaders or first-time founders.

Keep Reading