Unlocking Leverage: How Systems Thinking Catapults Analytics Careers

In partnership with

This sponsor’s tip could make your next analysis land better. Have a quick look - your visit also keeps this newsletter free.

PS: Clicking costs nothing; it buys me time to write the next deep dive. Thanks!

Find out why 1M+ professionals read Superhuman AI daily.

In 2 years you will be working for AI

Or an AI will be working for you

Here's how you can future-proof yourself:

1. Join the Superhuman AI newsletter – read by 1M+ people at top companies

2. Master AI tools, tutorials, and news in just 3 minutes a day

3. Become 10X more productive using AI

Join 1,000,000+ pros at companies like Google, Meta, and Amazon that are using AI to get ahead.

Sign up and start learning AI

Leaders think in systems.

Read that again.

If you want to be a tech leader or a people leader, this is one skill that can change everything.

Systems thinking is how you stop reacting to requests and start designing outcomes. It teaches you to see the structure underneath the chaos, then make a small, smart change that shifts behaviour at scale.

Just like a leader does.

Donella Meadows’ Thinking in Systems is a very clearly laid out path to build that skill, fast.

A system is a set of things connected in ways that produce their own pattern of behaviour over time. If you keep getting the same disappointing result, the system is built to deliver it.

That is not an insult to your effort, it is a cue to look at structure, not events.

Give me 7 minutes, and in this jam-packed issue we will:

• Stop chaos: a 3-line intake rule that names an owner and a decision date, so work cannot stall

• Make impact visible: two follow-up prompts at 1 and 4 weeks that turn reports into decisions

• Win back time: a 20-minute flow audit to find one leverage point, cut cycle time, and reduce rework

Lets go.

Pull one leverage point: Change how the system behaves = Earn more influence.

Meadows shows that small, precise changes to information flows, rules, goals or paradigms can shift outcomes at scale.

In an AI world, the person who designs the system, not the person who pushes the buttons, becomes irreplaceable.

But to do it we need to think logically and step by step (You work with Data - this is likely your area of strength!)

Best way to understand this is to break it down with an example that looks at your workflow.

See your whole lane (and why great work dies)

Grab your last 10 requests. Count how many got stuck. How many made you feel like you were running in circles?

Now do this 60-second exercise:

Draw: Intake → Prioritise → Build → Decision → Feedback

Write real names under each box. Who does what? Who actually decides?

Circle the pain: No clear owner. Waited 6 days. Last-minute changes. No decision deadline.

Here's what you'll discover: Your analysis was solid. The system was broken. And unlike your stakeholders' ever-changing priorities, you can actually fix this.

Get your time back (by fixing the flow)

Yesterday, how many requests came in? How many did you finish? What's left in your backlog?

If requests keep piling up, make one rule change today:

✓ No ticket accepted without a named decision-maker and decision date

✓ Ship bite-sized pieces (one KPI, one page) with 15-minute reviews, not 60-slide decks

Talk it through with your manager, get their buy-in to let you try to help fix something that will make them look better.

Watch what happens: Fewer panic requests at 4:47 PM. Fewer "can you just change this one thing" messages. More time for work that actually moves needles instead of just dashboards.

Make your impact stick (so people remember your wins)

Ever send a report and wonder if it changed anything? Here's how to know - and prove it.

For every big delivery, calendar two follow-ups:

• 1 week later: "What changed because of this?"

• 4 weeks later: "What decisions got made? What didn't - and why?"

If nothing moved, capture what was missing (clear target audience? decision criteria? timeline?) and bake it into your next intake form.

The result? You become the analyst whose work doesn't just get opened - it gets acted on.

Add that to your system

Use leverage (tiny moves, big reputation)

Want to be seen as strategic, not just tactical? Pull these levers:

Information flow: Loop the decision-maker and sponsor on the summary email so the right eyes see it.. When the right eyes see your work, action follows.

Boundaries: "No Friday 4 PM data pulls." Respect your own time first - others will follow.

Language: Stop calling it "the report." Start calling it "the decision brief." Words shape how people treat your work.

Goals: Change "deliver dashboard" to "enable pricing decision by September 20th." Clarity kills confusion.

Protect your wins (from the traps that kill momentum)

The problem is not reporting, it is dithering. Fix it up front.

Make every request come with a pre-commitment to act.

At intake, require four fields

• Decision question: “What choice will this inform?”

• Decision owner: one name, not a team.

• Decision date: a real calendar date.

• Pre-commit lines: “If we learn X, we will do Y. If we learn A, we will do B.”

Book the decision time when you accept the ticket

• Put a 15-minute decision slot on the owner’s calendar for the delivery week. No slot, no work.

Ship a one-page Decision Brief

• Options, trade-offs, your recommendation, blast radius, next action. Keep the pre-commit lines visible at the top.

Close the loop

• 1-week check: “Did we take the action we pre-committed to?”

• 4-week check: “What changed after we acted?”

Tiny scripts

• Intake: “To start this, I need the decision owner, the date, and two pre-commit lines. That way the work turns into action, not a read.”

• Delivery: “We agreed that if churn rises after the price change, we roll back the tiering. We saw that rise. Shall I action the rollback now or set a date?”

Why it works

• It turns analysis into a contract for behaviour change, not a document.

• It kills scope creep and avoids “let’s think about it” drift.

• It builds your reputation as the person who creates decisions, not decks.

When someone bypasses your intake rules, track the cleanup hours. Share the number quietly. Facts change behaviour faster than lectures.

SO many examples. All little levers that can change the flow of the work, the quality of the outcome, the impact to the stakeholders..

What this looks like when it clicks

Monday morning. Your inbox has 12 emails, not 47.

Your 15-minute review becomes a 5-minute "yes, let's do this" conversation.

A Slack message pops up: "Sarah, can you look at the retention data? We're making the Q4 call Thursday."

Your manager forwards your brief to the C-suite. You get pulled into strategy discussions before decisions get made, not after.

Same tools. Same skills. Different reputation.

When thinking about all the small parts of the system you operate in you will see lots of little levers to pull. Just implement one at a time, monitor, adjust, embed then move on to the next.

Your 20-minute starter experiment

Here is a 20-minute starter that sits squarely in Meadows’ toolkit of small, local experiments:

1. Draw three boxes: Backlog (a stock), Inflow, Outflow (flows).

2. Count last week’s requests in, requests out, and today’s backlog.

3. Ask which single rule or information gap makes backlog grow. Common culprits: vague briefs, no decision-maker named, no SLA for data fixes.

4. Change one rule for seven days: stricter intake form, a daily 10-minute triage, or one decision-maker per request.

5. Report before and after rates to your sponsor next week.

You just pulled a leverage point and proved the system can change.

This isn't about becoming a systems expert or reading management books.

It's about becoming the analyst whose work moves the needle - the person leadership waits to hear from before they decide.

The tools are the same. The skills are the same. But when you fix the system around your work, everything can change.

Thats what I mapped onto your analytics workflow from the heart of Meadow’s book Thinking in Systems

Which lever will you pull first?

Why care if you are an average data professional?

Because structure beats effort.

One targeted change to a rule, an information flow, or a goal can cut cycle time, reduce rework, and raise adoption.

AI can generate charts. It cannot reframe goals, align incentives, or engineer trust.

That is your domain.

Give this a try just once, and you'll notice the change.

Make it a monthly habit, and soon enough, folks will be curious about how you're making such strides with the same resources.

That's the magic of Thinking in Systems: spotting patterns, identifying leverage points, running small tests, refining feedback, and making adjustments. It's not just abstract theory; it's a hands-on approach to transforming solid analysis into tangible business improvements that people can really sense.

And that's precisely the kind of impact that can lead to a promotion

Best,

Tom.