In my advisory work, I’ve seen this pattern emerge repeatedly.

• The loops are well defined.

• Cadences are running.

• Dashboards are live.

• The work is getting done.

But something slows everything down.

• Every handoff triggers a Slack thread.

• Every experiment stalls while waiting for alignment.

• Every decision travels upward before it moves outward.

It’s not a motivation problem. It’s not a tooling problem. It’s a system that does not yet trust itself to move.

That erosion isn’t always obvious. In fact, it often hides inside otherwise functional teams.

This essay offers a different lens.

Trust is not a feeling. It’s a system design choice.

It shapes how motion compounds or slows down.

You can measure, score, and improve it the same way you would a product funnel or onboarding flow.

Inside this piece, you’ll get:

• A diagnostic to help identify where trust is slowing your loops

• A …

Read more

In many launches, PMMs are asked to lead but start without full context. They’re handed documents, maybe sit in on a few PM meetings, and are expected to make sense of it all. What often follows is a sequence of deliverables: blog post, press pitch, email, one-pager. All intended to position the feature externally. But without a clear model of what adoption looks like after launch, it turns into a checklist, not a system.

The result often looks like this:

Spike on launch
Flatline by week two
No sustained usage. No movement in retention.

Code shipped. Announcements made. But nothing stuck.

Familiar? Read on.

Read more

What actually keeps velocity high?
Clarity. Not in the vague, inspirational sense. Real, operational clarity. The kind that helps a team make consistent decisions, cut through noise, and stay aligned when plans go sideways.

When clarity is working, people move fast and independently. They know what great looks like and what matters now. They don’t need constant check-ins because they’re operating from the same map.

Read more

Most teams start with the same building blocks. But only a few turn those inputs into momentum. What separates them isn’t tech. It’s how they move.

Everyone has access to the a similar stack now: same AI models, templates, the power of automation, same 24 hours.

So why do some teams feel like rocket ships (Lovable, Gamma)…And others feel like they’re dragging a piano uphill? (won’t name names)

Here’s my take: The edge isn’t your tools or the recent star hire. It’s your system.

In 2025, what’s actually scarce isn’t technology, it’s how you organize humans around it.

I saw a team last week with a world-class tech stack stall for two weeks on a decision because no one felt safe just saying "go." And another team, with a very similar tech stack, shipped a product launch and three product tests in the same window.

The 3 variables that create asymmetric speed

⚡ Speed

• Most teams optimize for consensus (no bu…

Read more

People are the engine.
Fuel is the culture leaders create to power them.
Systems unlock scale.

GrowthFuel is a playbook for people-first growth teams in the AI era.

If you’re building in high-speed environments: startups, scaleups, ambitious teams, then, you already know:

The biggest bottleneck isn’t execution.
It’s Trust. Alignment. Energy.
That’s the fuel.

This newsletter helps you design for that.
Every post is a drop of fuel: insight, clarity, momentum.
It’s for your people and your system.

🎯 Who This Is For

• Growth leaders scaling teams without losing trust or energy

• Founders & execs aligning vision, team design, and systems thinking

• Operators designing cultures that ship, and last

If you’ve ever said “we’re moving fast, but something feels off”, then you’re in the right place.

🧠 What You’ll Find Here

📝 Field Notes
Fast, raw reflections from inside growth leadership. Published on LinkedIn, archived here.

Think: strategy in motion, not in theory.
→ Start with: Lifecycle Leverage Starts With Inputs You Can Trust

🧭 Culture Catalysts
Stories, systems, and interventions that build trust, energy, and alignment inside fast-moving teams.

These are the fuels behind the engine—trust, clarity, belonging, purpose.
→ Start with: Energy Debt: The Leadership Cost You’re Not Tracking

⚙️ Decision Physics
How high-output teams actually make decisions. Clarity loops, permission debt, and system design.

Beyond diagrams. Deeply practical.
→ Start with: Language as Leverage

⚒️ Growth tools
Practical tools I wish I had years ago, built from lived experience and hard-earned insight.

Includes the Hypothesis Engine & a sample size calculator, and prioritization to help you produce better hypothesis, and better results.
→ Tools page coming soon.

📈 Tactical Playbooks (coming soon)
Field-tested frameworks, templates, and mini-systems for solving specific growth and team challenges.

Designed for velocity without chaos: playbooks on activation, lifecycle, retention loops, onboarding flows, team ops, and more.

🧯 Failure Fuel (coming soon)
Lessons from breakdowns— mine, yours, and the industry’s.

When the fuel runs dry, we learn.

🌟 Remarkable Leaders (coming soon)
Bold, human-centered leadership moves that changed the game.

Because great systems start with courageous decisions.

Subscribe now

🔥 The GrowthFuel Model

People are the engine.
Fuel is the culture leaders create to power them.
Systems unlock scale.

I use “fuel” as a shorthand for the conditions leaders create inside the engine.
The key fuels I write about:

• Trust – the foundation for autonomy and speed

• Clarity – the antidote to drift and indecision

• Purpose – the meaning behind the motion

• Belonging – the emotional glue for loyalty and energy

• Autonomy – the path to flow and initiative

• Creative Friction – the spark for innovation and breakthrough thinking

You won’t find productivity articles or growth hacks here.
Just high-trust systems, people-first design, and the decision infrastructure behind real momentum.

📚 Where to Start

Here are a few posts readers come back to again and again:

• 🔥 Fast Teams Move on Trust, Not Permission
   Speed isn’t a mindset. It’s a system output.

• 🧠 Your Org Might Be Shipping. But Is It Learning, Fast?
   Activity ≠ progress. Here's how to tell the difference.

• 📡 Lifecycle Leverage Starts With Inputs You Can Trust
   When your growth systems lie, your decisions collapse.

• 🔨 Tools Are the New Content
   Why the future of thought leadership is productized.

🧾 My Promise to You

No fluff.
No empty hustle stories.
Just clear thinking, lived experience, and tools you can use.

Each post is handcrafted to deliver insight, emotional clarity, and systemic leverage.
You’ll walk away with something that changes how you lead, sometimes subtly, sometimes profoundly.

❓FAQ

How often do you post?
I post 1–2x per week, depending on flow. I focus on quality over routine.

What’s your background?
I’ve led growth and marketing at Shopify and Dropbox. I advise startups, build tools, and study systems design for a living. GrowthFuel is my lab.

Where else can I follow along?
LinkedIn is where Field Notes drop first.
This newsletter is where they get sharpened, layered, and archived.

🙋 Why I Started This

Because too many great people burn out in broken systems.

I built GrowthFuel to answer a simple question:

What if we scaled trust, not just tactics?

This is the playbook I wish I had 10 years ago.
Now I’m building it in public for the next generation of leaders who care about people and performance.

📥 Subscribe

Join hundreds of growth-minded leaders designing better engines and systems.
Fuel your team. Sharpen your strategy.
Lead with intent.

Subscribe now

🧠 This post is Part 2 of a 3-part series on how high-performing teams make faster, sharper decisions without chaos.

• Part 1: On Making Better Decisions Together
  Introduces a systems-first approach to decision-making.

• Part 2: Fast Teams Move on Trust, Not Permission (this post)
  How trust drives execution speed and removes second-guessing.

• Part 3 (next week): The Clarity Stack
  How great teams scale alignment without meetings or micromanagement.

It was the start of the COVID pandemic. The world was getting flipped upside down.

Like every other company, at Shopify, we were rethinking everything, growth roadmaps included.

Our filter became brutally simple:
If it helps the merchant right in this moment, it’s a go.

I didn’t wait for the formal ask. I saw what was coming.

I called an emergency brainstorm with my team, shelved our lifecycle roadmap, and pulled our leadership team into a live session to come up with a new one.

Nobody paused. Nobody asked, "Are we allowed to do this?"

We didn’t need permission. We had the mission, and trust.

📍 By 9 a.m., I made the call.
📍 By 10 a.m., we were moving.
📍 By end of day, we had a new roadmap.

This new roadmap was grounded in what merchants needed most given the lockdowns, some of it backed by qual research, some of it just informed hunches.

The next day, our senior leadership team held a town hall.
They formally asked all teams for the same thing.

We were a day ahead, already shipping from the new roadmap.

That early clarity drove impact fast. And that impact created momentum, the kind that compounds into bigger wins.

Speed Doesn’t Come from Hustle Alone.
It Comes from Trust.

People think fast teams run on adrenaline. On non-stop energy. On late nights.

In my experience, and the data backs this up, fast teams run on something else entirely: trust.

Fast teams aren’t reckless.

1/ They’re aligned.
2/ They’re trusted.
3/ They’re clear on the mission and empowered to move.

When trust is built into the operating system, speed becomes the default.

The Velocity Loop:

Trust → Autonomy → Speed → Momentum → Trust

Here’s what I’ve consistently seen separate top 1% teams from the rest:

It’s not tools, headcount, or rituals. It’s a self-reinforcing loop where trust begets speed, and speed compounds.

And it shows up everywhere: in how decisions get made, how risks get framed, and how teams move, even when no one’s watching.

• Trust creates autonomy.

• Autonomy unlocks speed.

• Speed builds momentum.

• Momentum reinforces trust.

This isn’t philosophy. It’s physics. I call it decision physics.

Teams don’t slow down because they lack skill or a better sprint template.
They slow down because they don’t trust each other enough to act.

And in 2025, trust is in freefall.

Since January, 332 tech companies have laid off over 77,000 people, that’s 501 per day (source). Layer that on top of hundreds of thousands more in the past two years.

What’s left behind isn’t just leaner orgs, it’s teams running on fear.

The result: permission paralysis.

Even top-performing ICs are hesitating. Not because they lack skill, but because the environment no longer feels safe to act.

Subscribe now

What Low-Trust Looks Like

Trust erosion is rarely loud. It shows up quietly, in friction and hesitation.

It sounds like:

• “We should schedule a sync.”

• “Can someone else review before we ship?”

• “Let’s get more buy-in first.”

These aren’t bad habits. They’re adaptive responses.

They signal fear of blame, murky ownership, or baggage from past escalations.

This happens when people stop believing the system has their back.

It’s not just about reorgs. It’s about tone.
About the slack message that never got a reply.
The postmortem that felt like finger-pointing.

Trust doesn’t mean being nice. It means removing second-guessing.

And removing second-guessing means:

• People know what “good” looks like.

• They know who owns a decision.

• They know they won’t be punished for reasonable action taken in good faith.

• They trust that escalation isn’t a trap, it’s a safety net.

Why this Matters

In low-trust teams, people hesitate not because they lack talent, but because the cost of getting it wrong feels higher than the reward of moving fast.

Removing second-guessing unlocks:

1/ Faster decisions: No waiting for green lights.

2/ Less emotional drag: No exhausting mental loops about whether you’ll be blamed.

3/ Higher engagement: People feel like owners, not just executors.

How High-Trust Teams Move Fast
(While Building More Trust)

High-trust doesn’t mean hands-off. It means clarity built into the process.

The fastest teams I’ve led didn’t rush. They decided better, faster because the conditions were already built for action.

What that looked like:

• Clear decision ownership: One person accountable. (DRI model.)

• Reversion rights: Act now, escalate if needed.

• One-way vs. two-way door framing: Not every choice needs a consensus.

• Lightweight decision logs: Not for control — for transparency.

• Language that enables action: Phrases like “Assume it’s a go unless flagged” or “Ship it, we’ll course-correct if needed” signal permission, not pause.

  You can read more on language and how to leverage it in your team in this post.

And behind all of it?
A concept we used often at Shopify: the trust battery. One of my favourite concepts.

Every teammate walks in with theirs partially charged. Each moment of clarity, ownership, and follow-through recharges it. Each ambiguity, micromanagement, or letdown drains it.

Fast teams don’t just preserve trust, they keep building it.
With every decision made cleanly and every moment of autonomy earned, the battery recharges, creating a compounding loop of trust → action → momentum → more trust.

When autonomy is the default, trust becomes operational.

Make Trust a System, Not a Slogan

We often hear leaders say, “we trust our teams.” But trust isn’t something you declare. It’s something you design for, and reinforce every day through systems, rituals, and defaults.

In high-performing environments, trust isn’t left to chance or charisma. It’s intentionally baked into how the organization runs.

Let’s break it down:

Rituals: Async updates that assume competence, not control

In high-trust teams, updates are for awareness, not oversight.

• There’s no pressure to justify every move or wrap decisions in disclaimers.

• Leaders read updates and respond with curiosity or help, not micromanagement.

Example: A daily Slack thread where team members post what they shipped, no approvals needed, just transparency by design.

Artifacts: SOPs that clarify ownership, not who to blame

• Clear documentation signals: We trust you to own this — and here’s how you know it’s yours.

• Instead of postmortems that feel punitive, teams have living documents that support better future decisions.

Example: A playbook that names the DRI (Directly Responsible Individual) for each decision type — with clear escalation paths if needed.

Language: Framing that shows belief in people, not fear of failure

• High-trust teams use language that encourages agency, not approval-seeking.

• Phrases like “Let’s try it” or “It’s your call” reinforce belief in team members’ judgment.

Example: Instead of “Are you sure this is okay?”, leaders say, “What do you need to move forward confidently?”

Why This Matters

Without systems, “trust” is just a slogan that buckles under pressure. When conflict hits or stakes get high, teams default to their operational reality, not their cultural posters.

But when trust is structured into the work:

1/ People move faster.

2/ Teams collaborate with less friction.

3/ Mistakes become learnings, not liabilities.

For remote leaders especially, this is non-negotiable.

Recent surveys show 85% of execs struggle to trust remote productivity. But surveillance won’t solve that. Clear systems and trust will.

Don’t Wait for Permission

Fast teams don’t wait.

Most teams miss deadlines because they’re stuck waiting: for approvals, for consensus, for someone more senior to say “yes.”

High-velocity teams don’t wait because they don’t have to. Their systems are designed so that waiting isn’t necessary.

They move fast because they know what good looks like

• High-trust teams have shared standards, success criteria, and decision principles.

• There’s clarity on what “done” means and what “good enough to ship” looks like.

• No one’s guessing whether their work is aligned, they’ve internalized it.

They move fast because the system lets them

• Structure matters. If your team needs a 5-step sign-off for every change, no amount of trust will create speed.

• The right guardrails, not gatekeepers, enable action.

• Fast teams operate within frameworks that support forward movement, not constant approval-seeking.

They move fast because they are trusted, and they trust themselves

• External trust is powerful. Internal confidence is the unlock.

• When people feel trusted, they start trusting themselves, which leads to better judgment, faster learning, and more boldness.

• It's not bravado; it’s earned autonomy.

The Real Impact

Teams who don’t wait:

1/ Move faster.

2/ Iterate more often.

3/ Spot and respond to reality sooner.

Permission cultures slow you down. Clarity and trust speed you up.

Design for trust, and speed becomes the operating norm and high impact.

Thanks for reading, and I hope it was valuable to you.

Now here’s why that matters.

Read more

But that wasn’t the failure. The failure came in the retro.

Everyone had a theory.
But no one said what we were all actually thinking.

The conversation bent around the truth.
We softened our takes, redirected to safer variables, and buffered real insight with polite analysis.

It stayed just beneath the surface, not because we didn’t care, but because it didn’t feel safe to name it.

That’s where learning breaks.

Because you can still ship.
You can run retros.
You can even call yourself a learning org.
And still be stuck.

Over time, you start mistaking throughput for clarity.
Decisions get made, but no one remembers why.
People attend meetings, but with less and less to say.
Mistakes repeat themselves, with slightly different packaging.

The most dangerous part?

The system still looks like it’s working.

I’ve seen this pattern in large companies and small ones.
At Shopify. At Dropbox. In scrappy teams. In elite ones.

They’re thoughtful. They move fast. They care deeply.

What’s missing isn’t capability. Or intelligence.

It’s something quieter, and harder to spot.

A system that makes it risky to say what’s obvious.

A lack of psychological safety with enough strength to support the truth.

Let’s define it.

Psychological safety isn’t a cultural vibe or team-building byproduct. It’s a shared belief held by every team member that it’s safe to speak up, admit a mistake, ask a question, or offer a challenge without fear of embarrassment, rejection, or retribution.

It’s not comfort. It’s not consensus. It’s knowing that saying what you see, even if it's inconvenient, and it won’t quietly cost you later.

Amy Edmondson, who pioneered the concept, defined it as “a climate in which people are comfortable being themselves.” But in execution, it’s far more operational. It’s about how the system responds when the truth enters the room.

The 4 Stages of Psychological Safety, as outlined by Dr. Timothy R. Clark, was a foundational read for me. It cemented what I had intuitively felt for years, that learning velocity, creative risk-taking, and high trust cultures all depend on a system of permission, not just encouragement. His framework gave structure to those instincts, and backed them with the kind of research that leaders can use to operationalize trust, not just talk about it.

Clark’s model moves through four progressive conditions:

1. Inclusion Safety – feeling accepted and connected

2. Learner Safety – feeling safe to ask questions and grow

3. Contributor Safety – feeling trusted to make a difference

4. Challenger Safety – feeling free to challenge the status quo

Fast-learning teams aren’t just high output. They’ve designed systems where these four layers are present and protected.

This article on the 4 stages of psychological safety from Spill, I thought does a great job breaking the concept down

So why does it drive learning velocity?

Because learning isn’t an intellectual activity. It’s a behavioural one.

As summarized in The Science of Learning report by Deans for Impact,

“The measure of learning is behavior change, not just knowledge acquisition.”

Think about it. You can only course-correct if people feel safe enough to say, “We’re off-course.” You can only adapt fast if someone feels safe enough to ask, “Why are we doing this again?”

And you can only generate leverage from failure if the first reaction isn’t blame, but curiosity.

Here’s the causal chain:

Safety → Disclosure → Shared Insight → Ownership → Adaptation → Velocity

Break the chain at the start, if someone holds back, and the rest never happens.

Unlike tooling, this loop doesn’t scale with automation.

It scales with trust.

Subscribe now

Tools vs. Safety: What really makes teams faster?

Most teams try to fix learning gaps with tools.

You’ve seen it. A new retro template. An “insights” channel in Slack. Quarterly feedback forms. Engagement surveys. Maybe even a pulse poll or two.

None of these things are inherently bad. But when they’re used in place of trust, they don’t solve the real problem, they just digitize the dysfunction. Because when people don’t feel safe, they don’t say what they really see. They say what sounds reasonable. They manage tone. They pick the safe answer. And the system congratulates itself for participation while the signal never moves.

A team with basic tools but high trust will outperform a team with perfect tooling and low safety. Not occasionally, consistently.

What does it actually look like when a team has it?

At Shopify, we eventually shifted to running async postmortems after every experiment sprint (at least in my teams). But we didn’t just collect answers, we designed the ritual to protect the insight itself.

• Everyone wrote private reflections before seeing each other’s comments

• No one spoke first, comments came first, anonymously

• Feedback was reviewed by a neutral facilitator, not a stakeholder (we often asked our friends in UX)

• Every insight needed a named follow-up, not just a “noted”
  

The result?
Truth surfaced. Decisions changed. People felt seen.
And the feedback loop wasn’t just faster, it was trusted.

That’s psychological safety in motion.
It didn’t come from culture decks.

It came from structural decisions that protected truth from power.

So what do you do with that?

It doesn’t start with a new retro format or another feedback tool. It starts by recognizing that trust isn’t a vibe or a leadership style, it’s a system condition. When people know they can surface what feels uncomfortable without social penalty, they stop holding back and start offering the kind of signal that actually moves the team forward. You don’t need dramatic moments. You need a system that quietly rewards truth and makes learning a shared responsibility, not a personal risk.

That shift changes everything. Instead of interpreting hesitation as disengagement, you begin to see it as a clue. Instead of assuming alignment from silence, you start looking for what hasn’t been said. When that kind of awareness becomes normal, when trust is structurally supported, not just hoped for, insight shows up earlier, and teams respond faster. And that’s when learning stops being a retrospective idea and starts becoming a competitive advantage.

Here’s what that looks like in practice:

1/ Own the silence before you try to fix it.

If you sense people are holding back, name it. Don’t spin it.

“I’ve noticed we don’t always name what’s not working. That’s on me. I want to change that.”

You don’t need vulnerability from your team. You need to model it first.

2/ Shift retros from review to reckoning.

Stop asking what happened.
Start asking what changed about how we think, what we missed, and what we’ll do next time.

“What did we assume and never validate?”
“What felt off, but we didn’t dig into?”
“What are we going to do differently because of this?”

Don’t just document insight. Assign it.

3/ Give insight a name, not just a ticket.

Every clear signal in a retro or review needs someone responsible for making sure it turns into a shift.

Too often, we treat feedback as input. But input without ownership is just noise.

Learning needs an owner, or it leaks.

4/ Make it easier to speak up than to stay quiet.

You don’t need psychological safety theory. You need systems that reward clarity and truth seeking more than consensus.

Start by listening for discomfort. And when someone challenges the status quo, back them up in real time.

If your team sees that honesty gets curiosity, not consequences, you’ll get more of it.

5/ Use structure to protect the truth from politics.

Don’t rely on courage. Use rituals.

Try GitLab’s async demos. Use Amazon’s six-pagers. Rotate who leads the retro. Create systems where the truth doesn’t need to fight for airtime.

A good system makes candor the default, not a personal risk.

6/ Look at who isn’t speaking.

If the same few voices dominate every conversation, your learning loop is incomplete.
Often, the people with the most useful insight have the most reasons to stay quiet.
New team members. ICs. People who’ve spoken up in the past and saw nothing change.

Ask yourself: “What does this system do to their voice?”

Because if it doesn’t amplify it, you’re not really learning. You’re just reinforcing what’s already comfortable.

When trust becomes part of the operating system, everything compounds.

When trust becomes part of the operating system, the energy of the team shifts. People stop managing impressions and start surfacing patterns. Feedback loops don’t just close, they create forward motion. The effort once spent navigating personalities or protecting status gets redirected into making the work stronger, faster, and clearer.

This isn’t about psychological safety as a leadership buzzword. It’s about engineering a system where learning can move faster than fear, where signal isn’t diluted by caution, and speed doesn’t come at the cost of silence. When that system is in place, teams don’t just execute. They adapt. And that’s the real advantage.

Want to know how your team is actually doing?

Try the Trust Loop Scanner: a free, GPT-powered audit tool I designed to create a tangible asset to help you.

Simple paste your last meeting transcript (please get permission and tell everyone about the exercise before hand), and get a breakdown of:

• Your team’s Learning Culture Score

• Missed insight patterns

• Psychological safety breakdowns

• And custom, role-specific actions to help your team learn faster

Built for leaders who want learning velocity, not just retros.

👉 Run your first audit

Further Fuel:

Recent articles I wrote on leadership that you may have missed.

• On Making Better Decisions, Together
  Why most growth teams don’t need more data, they need clearer upstream calls.

• Energy Debt: The Leadership Cost You’re Probably Ignoring
  Burnout isn’t about bandwidth. It’s about unacknowledged drag in your org.

• Language as Leverage: How Better Words Build Better Orgs
  A system breakdown in most teams starts with bad syntax.
  

  ---

  Thanks for reading GrowthFuel! This post is public so feel free to share it.

  Share

Too many systems are built around what’s easy to track, not what’s meaningful. Too many articles skip straight to branching logic without questioning the foundation. Too many dashboards give the illusion of insight.

This note is a response to that pattern. It's for anchoring personalization efforts in signals that actually move the needle because they’re observable, repeatable, and meaningful.

This piece is focused solely on signal validation. Operationalization, tooling orchestration, and data governance each deserve their own treatment and will be covered separately.

At Shopify, when we first built the lifecycle programs in 2018, we had no shortage of signals: product usage, support pings,…

Read more

This post is part of my “Field Notes” series: real-time observations, sharp POVs, and reflections from the edge of execution. It’s raw, honest thinking in motion, less polished, more proximal. Notes from the journey, not just the destination.

Read more

🧠 This post is Part 1 of a 3-part series on how high-performing teams make faster, sharper decisions without chaos.

• Part 1: On Making Better Decisions Together (this post)
  Introduces a systems-first approach to decision-making.

• Part 2: Fast Teams Move on Trust, Not Permission
  How trust drives execution speed and removes second-guessing.

• Part 3 (next week): The Clarity Stack
  How great teams scale alignment without meetings or micromanagement.

Your team made hundreds of decisions last quarter. The question isn’t how many you remember. It’s how many created momentum you didn’t have to revisit.

We obsess over optimizing funnels and timelines. But some of the most impactful shifts start upstream, in the moments when we choose what to pursue, how we rally, and whether we stick to our calls. Decision-making shapes everything. Oddly, it gets skipped over.

This isn’t about adding red tape. It’s about having enough structure to move with intent, not just speed. Let’s map it out.

A Working Model for Decision Flow

Here’s a simple model I use. It’s not perfect, but it’s useful for spotting where decisions gain momentum or lose steam.

Decision Funnel:       Inputs → Framing → Tradeoffs → Choice

This is the core of decision-making. Not execution, not reflection. Just the moment of shaping and selecting. When done well, it sets up everything that follows.

Let’s break it down.

1. Inputs

What it is: The signal before the decision. What you’re noticing, hearing, or feeling that suggests a choice needs to be made.

Example: Users are dropping off a new feature faster than expected.

How we use it: Start by asking, “What’s actually happening here?” Surface the data, instincts, and edge cases. Decision quality begins with signal clarity.

2. Framing

What it is: Defining the question you’re really trying to answer.

Example: Is this a UX issue or are people simply not discovering the feature?

How we use it: Slow down here. It’s cheaper to reframe than to rebuild. And this is where second-order thinking comes in. Don’t just ask, “What should we do?” Ask, “What might this create beyond the immediate goal?” Good framing sees the ripple effects, not just the splash.

3. Tradeoffs

What it is: Naming what you’re giving up in order to move forward.

Example: Do we fix the drop-off now or stay focused on the current roadmap?

How we use it: Make the cost visible. Time, trust, optionality, team energy.
These are all currencies. Tradeoffs get easier when the team agrees on what matters most.

4. Choice

What it is: Making the call clearly, out loud, and in writing.

Example: We’re fixing the UX. Team A owns the work. Launch target is next sprint.

How we use it: Say the decision, not just the discussion. If no one can point to “the call,” it didn’t happen.

That’s the Decision Funnel. But smart teams don’t stop there.

They feed decisions into a loop, one that builds follow-through, trust, and long-term rapid learning.

Decision Loop:   Choice → Ownership → Execution → Learning → Inputs

This loop turns good decisions into great systems. It keeps the organization from chasing its own tail. And it’s where teams can fall apart, not for lack of effort, but for lack of visibility.

1. Choice

What it is: The final call. A decision made clearly, documented, and time-stamped.

Example: We’re prioritizing the self-serve onboarding flow this cycle.

How we use it: Capture the call. Don’t let decisions live in Slack threads or someone’s memory. Make it visible, repeatable, referenceable.

2. Ownership

What it is: Explicit accountability. Who is responsible for driving the decision forward?

Example: Growth PM owns the rollout. Design and data are supporting leads.

How we use it: Tag ownership wherever the decision lives: project docs, meeting notes, or roadmaps. Remove ambiguity early.

3. Execution

What it is: The work. The system that tracks whether what was decided is actually happening.

Example: Tasks are scoped, assigned, and progress is shared weekly.

How we use it: Use your existing sprint rituals but link them back to the original decision. It grounds action in context.

4. Learning

What it is: The post-decision review. Did it work? What emerged that we didn’t expect? What didn’t work and why?

Example: Signup conversion improved, but trial-to-paid stayed flat. Why?

How we use it: Run after-action reviews. Even 10 minutes of reflection can pull forward months of insight.

5. Inputs

What it is: Feeding what you’ve learned back into the next cycle of decisions.

Example: Insights from the onboarding test shape how we frame the next monetization discussion.

How we use it: This is the return path. Strong teams don’t just document outcomes. They reuse the learnings.

Some might look at this and see echoes of the OODA loop. It’s a fair reference but the purpose here is different.

OODA: Observe, Orient, Decide, Act: is built for rapid response in fast-changing environments. It’s optimized for agility, especially when the cost of delay is high.

But many of the hardest decisions in growth and leadership aren’t about speed. They’re about depth. About framing the right question, making tradeoffs visible, and building trust through clarity.

This model isn’t about reacting faster. It’s about reducing relitigation, aligning across functions, and learning as a team. Where OODA optimizes for tempo, this system optimizes for momentum you don’t have to undo later.

Where Decision Flow Breaks

Most decision pain isn’t caused by a single bad call. It comes from small misfires compounding in systems that aren’t designed to surface or resolve them.

Here’s what breakdown looks like in the Decision Funnel:

• Debates that repeat with slightly different phrasing, because framing was fuzzy.

• Decisions that feel implied but never get confirmed, so no one knows who’s moving.

• Deadlines without clarity on who owns the call, or what tradeoffs were made.

• Questions asked out of sequence, like jumping to solutions before naming the actual problem.

And here’s where things often fall apart in the Decision Loop:

• No visible owner, so follow-through gets distributed across silence.

• Execution begins but loses momentum because no one checks back in.

• Learning never happens, because there’s no trigger to revisit what was decided or why.

• Consequences show up—but because the decision path wasn’t logged, no one sees the connection.

These aren’t edge cases. They’re common operating conditions in most orgs.

The cost isn’t just delay. It’s cognitive churn, unclear priorities, and erosion of team trust. According to McKinsey, ineffective decision-making costs Fortune 500 companies more than 530,000 days of lost productivity per year. That’s over $250 million in wasted capacity, before you count the cost of rework or missed insight.

If your team is moving fast but not learning, you’re not compounding. You’re circling.

A better system doesn’t just help you decide well. It helps you follow through and learn faster than you forget.

Systems that Scale: How Great Teams Do It

Amazon uses PR/FAQs to clarify proposals before committing. Stripe tracks decisions with naming conventions and written documentation. Notion uses memos to create shared reference points that don’t fade after the meeting ends.

These tools aren’t about control. They’re about creating decision systems where choices are framed well, followed through clearly, and revisited with intention.

What sets high-functioning teams apart isn’t just the quality of their initial decisions. It’s their ability to track ownership, surface outcomes, and refine their thinking over time. That’s what the Decision Loop is for.

Here are six low-lift practices that support both halves of the system:

1. Decision logs

What it is: A running log of context, reasoning, and expected outcomes for major decisions.
Use case: Log the “why now” and revisit it 30 days later.
System impact: Builds memory. Feeds the learning loop.

2. Framing Trees

What it is: A tool to map out the actual question before jumping to answers.
Use case: Use when a problem feels “solved” too fast.
System impact: Forces better framing. Avoids solving the wrong problem well.

3. Pre-Clarity Sessions

What it is: A short, structured convo before kickoff: “What are we trying to learn?”
Use case: Before launches, OKRs, or bets.
System impact: Clarifies intent. Surfaces assumptions early.

5. Weekly Review Rituals

What it is: A standing 10-minute practice: “What decisions did we make this week? Are we tracking them?”
Use case: Team standups or Friday wrap-ups.
System impact: Keeps decisions visible. Supports accountability.

6. Retros for Decisions

What it is: A lightweight post-mortem for decisions: “Did it work? What surprised us?”
Use case: At project close, or 30 days after a call.
System impact: Feeds insight back into Inputs. Closes the loop.

These aren’t just habits. They’re leverage points. The orgs that scale cleanly don’t make more decisions—they make fewer decisions twice.

Start Here: Building Your Decision System

If you’re short on time, begin with these three moves: one for the Funnel, one for the Loop, and one that strengthens both.

1. Weekly Decision Review (Loop)

End each week by asking, “What decisions did we actually make?” Write them down.This builds memory and visibility. It turns vague consensus into clear ownership.

2. Track Decision Latency (Funnel)

Measure the time between identifying an issue and making a call. You’re not optimizing for speed alone but long latency often signals unclear framing or fear of tradeoffs.

3. Shared Glossary of Tradeoffs (Both)

Define terms like “bet,” “non-negotiable,” “sacrifice,” and “MVP.” A shared language reduces ambiguity in framing and prevents misalignment during execution. I wrote a post on Language as Leverage you should check out.

Each small fix compounds. Not just in speed, but in clarity, energy, and trust.
Because when decisions are made clearly and tracked visibly, teams move faster, and they don’t waste energy circling back.

What would change if your org tracked decisions as rigorously as growth metrics?

Leave a comment

You don’t need to add overhead. Just intention. A simple system will give your team more focus, more feedback, and fewer repeat meetings.

Because speed doesn’t only come from urgency. It comes from clarity too.

Further Fuel

1. A Leader’s Framework for Decision Making – HBR
A breakdown of the Cynefin model and how to match decision style to complexity.

2. How to Beat Decision Fatigue - Wake-Up Call
A grounded, human-centered take on improving decision quality, especially useful for emotionally complex calls.

3. Decision Intelligence: Integrating AI into Decision-Making - AI Collective
Battle-tested ways to structure high-stakes decisions in fast-moving orgs.

Subscribe now

This post is part of my “Culture Catalysts” series: an inside look at how systems, rituals, and language shape high-trust, high-clarity teams.
It's about the invisible levers that drive momentum: not perks or vibes, but the architecture of how people align, communicate, and compound.

Speed rarely stalls because people aren’t working hard.

More often, it slows down in quieter ways, like when “impact” means something different to every team or when “strategy” floats without a shared definition, or when that acronym that everyone uses means something just a bit different to your key stakeholders.

Burnout often has less to do with pace than with the kind of friction that builds when teams are using the same words but meaning different things.

In this post, I unpack how language quietly governs trust, speed, and execution, and why most teams don’t realize it until things break.

As Google’s Project Aristotle showed, teams rarely fail because they lack talent. They fail because they lack shared understanding. When meaning slips, execution slows. When language decays, culture follows.

In the last two posts, we explored what happens when leaders scale without tending to team energy. But beneath energy debt is something deeper: communication decay. Not cadence. Not tooling. Language.

The missing lever most teams ignore: shared vocabulary

Notion, GitLab, and Stripe all treat language as infrastructure. Because they’ve learned the hard way: execution relies on shared syntax.

One word with three meanings becomes three weeks of rework. “Impact,” “shipped,” “strategic” “insert your acronym here”. These aren’t definitions. They’re decision accelerators. Or friction multipliers.

When leaders don’t design language intentionally, it designs itself through shortcuts, power gradients, and unspoken assumptions.

We over invest in tools and rituals (docs, Slack, async stand-ups) but skip the substrate: the words those rituals are built on.

And the cracks show up in subtle ways:

• A junior teammate says, “I’m not sure what ‘own the outcome’ actually means.”

• A director hears “be more strategic” as a veiled critique.

• A product team defines “MVP” as the leanest testable thing; GTM hears “nearly launch-ready.”

These are simple examples, but you get my meaning. I hope.

Misalignment doesn’t announce itself. It compounds in the background like tech debt, but semantic.

Codifying language is leadership work

Great leaders don’t just communicate. They codify.

Language is a performance tool. Treat it as such. Language drives clarity, precision, and safety, if wielded well. And it compounds trust when modelled consistently.

At Stripe, high-leverage documents are reviewed with the same rigor as code because writing is thinking. At GitLab, the 2,000-page public handbook acts as a shared neural net. At Notion, onboarding starts with an internal language tour.

None of this is about being pedantic. It’s about speed through clarity.

Simon Sinek calls it “making meaning visible.”. Adam Grant reminds us that “clarity isn’t just kind—it’s efficient.”

This isn’t soft. It’s systems work.

And like any system, it needs regular auditing.

The Clarity Surfaces Audit:
5 places where language breaks under pressure

Here’s how to spot where semantic drift is quietly derailing your org:

1. 1:1s

• Are word choices building safety or defensiveness?

• Are phrases like “just a quick chat” spiking anxiety?

• Are we solving too fast instead of asking “What do you need?”

2. Stand-ups

• Are updates reflecting priorities or performance theater?

• Is “blocked” a safe word or a risky one?

• Do teams use consistent terms for scope and velocity?

3. Team Meetings

• Do people say “Can we define that?” before debating?

• Are trade-offs named out loud or assumed?

• Does language signal inclusion or hierarchy?

4. All-Hands / Town Halls

• Are strategy words like “focus,” “ownership,” and “impact” defined or floating?

• Is the Q&A real dialogue or signaling?

• Are values encoded in stories or buried in slides?

5. Written Docs

• Are acronyms and terms drifting without re-grounding?

• Is writing calibrated for context level and audience?

• Are definitions portable across product, GTM, and ops?

Where confusion compounds, a language fault line is often underneath.

Leave a comment

A moment where language broke

A moment where language broke

Here’s how an entire roadmap can quietly derail from one well-meaning directive: “De-risk the launch for the SMB segment.”

A senior leader used this phrase during an offsite. Everyone nodded, then dove into planning. But no one paused to align on what risk actually meant—or whose risk they were solving for.

Product cut scope to reduce technical debt.
Legal pulled timelines forward to double-check compliance.
Marketing slashed the campaign to lower external exposure.

By launch week, the product was stable but momentum had vanished. The market didn’t notice. Internally, teams blamed each other for being “too cautious.”

The language wasn’t wrong. It was interpreted in isolation. Each team optimized for a different version of risk. No one clarified the frame. So alignment quietly fractured.

Cognitive scientists call this “assumed alignment”. It’s when everyone thinks they agree because no one asks what the words actually mean. Sticky Honey Bear, anyone?

What high-trust teams do differently

The best teams I’ve been on and led, treat language like infrastructure. They don’t just optimize rituals. They fortify meaning.

They:

• Maintain glossaries for words like “done,” “impact,” “shipped”

• Normalize asking: “What does that mean to you?”

• Dedicate retro time to: “Where did meaning slip?”

• Use metaphors and models across functions to sync mental frames

• Teach not just what terms mean but why they exist

At Shopify, our CEO Tobi Lütke banned acronyms. Not just for clarity but for access. Acronyms often gate keep context. Removing them levelled understanding, flattened power gradients, and sped up decision-making.

At Amazon and Dropbox every meeting starts with a memo, and a silent read. No slides. No assumptions. Just shared context.

At Stripe, narrative writing isn’t a tool, it’s the culture. Docs are reviewed for clarity like code. Because writing is clarity.

This isn’t about words. It’s about speed, trust, and alignment.

Small actions that shift the system

Language systems aren’t built in one meeting. They’re tuned over time.

Here’s where to start:

• In your next 1:1, ask: “Has any term we use been confusing lately?”

• In your next team meeting, clarify 3 frequently used words.

• In your next doc, write a 2-line glossary up top.

• Model “What does that mean to you?” in high-stakes rooms.

• Start a shared vocabulary doc. Revisit it monthly.

Language is how we scale trust

Language is how we scale trust.
If energy is the battery, and execution is the motor, then language is the circuitry.
It connects every function, every feedback loop, every decision layer.

Clarity isn’t just kind. It’s how you move at speed without breaking culture.
The highest-leverage shift a leader can make isn’t to communicate more, it’s to teach teams how to build meaning together.

Because speed doesn’t come from moving fast. It comes from meaning that moves.

And if you’re a growth leader, you’ve probably have backlogs of ideas and roadmaps searching for the next lever in acquisition, activation, retention. But we rarely look inward at the words we use every day to ship, align, and decide.

Language isn’t overhead. It’s a hidden lever for speed, trust, and alignment, if you choose to wield it.

Bonus:

Want to audit how language is working or failing inside your org?
I’m building a practical toolkit to help leaders score clarity across 10 key surfaces. It’s designed to be fast to run, useful to act on, and easy to share internally.

I’m testing it now as a GPT + resource bundle.

If you want early access and can give direct feedback, DM me or post a message in the comments. You’ll help shape something designed to become a go-to ritual for high-trust, high-clarity teams.

—

PS: This post closes a 3-part series:

1. Energy Debt

2. Burnout & Team Scaling

3. Language as Leverage

If this series helped you see your team differently, send it to someone scaling through fog. Or forward it to your CEO. Because language work is leadership work.

This post is part of my “Culture Catalysts” series: an inside look at how systems, rituals, and language shape high-trust, high-clarity teams.
It's about the invisible levers that drive momentum: not perks or vibes, but the architecture of how people align, communicate, and compound.

The burnout crisis isn’t new. But the scale is.

77% of professionals say they’ve felt burned out in their current job (Deloitte survey). More than half say it’s happened more than once.

That’s not a wellness issue. That’s a design flaw. And the impact doesn’t stop at work.

83% say burnout affects their personal relationships too. It’s not just costing teams output, it’s bleeding into people’s lives.

Most teams aren’t breaking down because people don’t care. They’re breaking down because people have been caring too much, for too long, without relief.

This isn’t about weak people or skipped PTO. It’s what happens when we build systems that reward urgency, ignore capacity, and normalize silence.

Burnout doesn’t come from individuals. It comes from design.

If you want to scale, you need to treat energy as a performance asset, one that deserves the same rigour as your roadmap or your product strategy.

Burnout gets framed like a wellness issue. Take a walk. Use your Calm subscription. Log off a little earlier next Friday. But the truth is, burnout isn’t about mindfulness gaps. It’s about systemic leadership debt. It’s the way we’ve been building teams, setting pace, and rewarding performance.

So, it seems we have a system problem, and in 2025, it’s showing up everywhere.

That’s not surprising when you look at the conditions:

• Reorgs are constant. Team structures shift every quarter. Roadmaps get reset. The ceiling keeps moving. When was the last time your team got re-org’d, this year?

• AI is adding pressure, not relief. Teams are expected to adopt new tools while keeping up their old velocity.

• Workloads are up. Headcount is down. The teams left after layoffs are carrying the load, often without acknowledgment or recovery.

Meanwhile, burned-out teams are becoming cynical teams. Passion becomes protection. Engagement drops. Creativity flattens. Leaders mistake this for “quiet quitting,” when in fact it’s a rational response to an unsustainable pace.

And here’s the thing, the data seems to show that burned-out teams don’t go quiet because they’ve stopped caring. They go quiet because they’ve been caring too much, for too long, without relief.

87% of professionals say they love their job—yet 64% say they’re frequently stressed. Passion doesn’t protect you from burnout. It just makes you more likely to ignore the warning signs until it’s too late. (Deloitte Survey)

“Image Source: Deloitte Burnout Survey, 2024”

Burnout isn’t about individual resilience. It’s about systemic overload.

“She’s just tired.”
It sounds harmless but it reduces a chronic, system-wide issue to someone needing a nap. Burnout isn’t temporary. It’s not about rest. It’s a red flag that the system itself is running too hot, for too long.

“He’s not managing his energy.”
This one puts the onus entirely on the individual.
It assumes the problem is personal discipline, not structural overload.
But you can’t time-block your way out of a broken system.

“They need to speak up if they’re drowning.”
This frames silence as a choice, ignoring that most teams don’t feel safe calling out burnout. By the time someone says “I’m not okay,” they’ve probably been under water for months.

“Maybe they’re just not cut out for this pace.”
Now we’ve reframed burnout as weakness. Instead of asking whether the pace is sustainable, we question whether the person is. It’s a fast track to normalized attrition.

“They should use their PTO if they’re feeling off.”
Time off helps, but it’s not a fix.
You can’t vacation your way out of a system that burns you out the moment you log back in. Worse, many people don’t feel safe or supported enough to take the time they’ve earned.

But the numbers, and lived experience tell a different story.

Burnout correlates more with how a team is led than who’s on it.

As Gallup puts it, “70% of the variance in team engagement is determined solely by the manager.” That makes leadership one of the most critical levers in preventing burnout, not because leaders intend harm, but because the systems we design are quietly defaulting to depletion.

Urgency has become the culture. Everything is a sprint. Recovery is optional, if it’s discussed at all. We wouldn’t run our servers at 99% CPU all day and expect reliability. But we run our teams hot at that level, all the time.

This isn’t just an HR issue. It’s a performance liability.

Burnout doesn’t just drain people. It breaks the system.

Productivity tanks.
Even when hours increase, output doesn’t. Burned-out teams stay late and grind through the motions, but the quality drops. Not because they’ve checked out, but because they’re running on empty.

Decision quality erodes.
When teams are exhausted, clarity disappears. Instead of weighing trade-offs or thinking long-term, decisions become reactive. People start choosing what’s easiest, not what’s best.

Innovation stalls.
Creativity doesn’t happen under pressure. It needs breathing room. Burnout crowds out the space to think, to explore, to experiment. Teams stop taking risks and start playing it safe.

Attrition rises.
Almost half of burned-out employees are thinking about leaving. But the real damage starts earlier, when people disengage. They stop raising ideas, stop challenging the status quo, and eventually stop caring.

The longer you delay addressing it, the more compounding damage you absorb: customer churn, knowledge loss, brittle morale.

The emotional cost is high. But the operational cost might be higher.

What’s driving this? Look at the system design.

Burnout shows up in people, but it originates in systems. And those systems are built, explicitly or implicitly, by leadership.

Here are a few examples from the field:

No slack in the roadmap.
Teams are at full capacity by default. Any disruption (a reorg, a teammate off sick, a new top-down priority) pushes the system past the breaking point.

Recovery is not designed in.
Big launch? Great. But what happens the week after? If the answer is “another big launch,” you’re compounding debt.

Feedback loops are too slow.
By the time you see someone withdraw or disengage, burnout has already done its damage.

Psychological safety is low.
If people feel like flagging burnout will be seen as weakness or complaining, they’ll stay silent, and quit quietly later.

Workload is invisible.
There’s no shared language for capacity, so burnout hides in plain sight. Without regular check-ins or honest signals, leaders assume things are fine—until they’re not. What looks like underperformance is often just unseen overload.

The signs are subtle, but the stakes are massive.

Most teams won’t tell you outright that they’re burned out. But the signals are there, if you’re paying attention.

Execution becomes more reactive than proactive.
Instead of planning ahead, teams shift into survival mode. Work becomes about getting through the day, not building toward the future. Strategy takes a backseat to urgency.

High performers stop contributing outside their job scope.
The people who used to volunteer, ideate, or coach others start pulling back. Not because they’ve stopped caring, but because they’re conserving what little energy they have left.

Team norms start to erode.
Meetings get quieter. Async threads go unanswered. Follow-through gets fuzzy. What used to feel like a high-trust, high-functioning team starts to fray around the edges.

Morale boosters land flat.
The wins still get shared, the shout-outs still happen, but the team barely reacts. It’s not that they don’t appreciate the effort. It’s that they’re too depleted to feel it.

By the time someone says, “I’m out,” the real damage happened quarters ago.

This is fixable. But not with perks.

You can’t perk your way out of burnout.

Lunch stipends, Calm apps, even mental health days, these are helpful gestures, but they don’t fix the underlying system design. A system that creates burnout will always outpace a program that tries to treat it.

What does fix it?

You need an Energy Operating System.

A system-level design that going beyond “supporting wellness”, a system that protects energy like a core performance asset.

Here are its 5 core levers:

🔁 Pacing Cycles

Design recovery with the same intention you bring to delivery.

Sprints are normal. Pressure is part of the job. But without intentional recovery, you keep teams in peak mode too long. And peak mode turns into survival mode.

Every major push should be followed by a decompression window. This could mean lighter cycles, reflection time, or even just fewer meetings. The goal is to reset the system, not collapse at the finish line.

Add recovery blocks to your roadmap the same way you add deadlines. Make them visible. Make them non-negotiable.

This is not about going slow. It’s about sustaining consistent impact..

📊 Load Visibility

If you only measure output, you miss the strain underneath it.

Most teams have no shared language for load. So burnout creeps in quietly. People hesitate to speak up. Leaders assume silence means capacity.

Build regular check-ins for capacity. Use a 1-to-5 scale in standups. Add a “how are we tracking energy?” moment to team meetings. Don’t just ask about tasks or results. Ask about tension.

What you surface early, you can solve early.

🧠 Cognitive Slack

Protect time to think, not just time to do.

Burnout accelerates in back-to-back, reactive environments. When teams are always responding, no one is creating. No one is solving upstream.

Schedule deep work blocks like meetings. Cut out performative updates. Reduce context-switching. Let people breathe between asks.

Slack in the system is not wasted time. It’s where clarity, focus, and creativity happen.

💬 Energy Dialogue

Make energy a real conversation, not a silent struggle.

People will talk about their output. They’ll even talk about stress. But most won’t talk about energy unless you create the space.

Normalize questions like:
“What’s draining us right now?”
“What’s giving us energy?”
“Where are we stretched too thin?”

Bring these into 1:1s, team retros, planning meetings. Treat energy like velocity. Name it, track it, and treat it as shared responsibility.

🌱 Systemic Recognition

Acknowledge not just what gets done, but how it gets done.

In high-stress environments, people often go unrecognized until they burn out or quit. Traditional praise focuses on output. But what about sustainability? What about care?

Start recognizing the quieter forms of leadership. The teammate who held the team together during a chaotic launch. The one who flagged an unrealistic timeline early. The one who made space for rest without needing permission.

When you celebrate sustainability, you signal that it's not just allowed, it’s expected.

These aren’t perks. They’re design principles.

The most resilient teams don’t rely on individual grit. They operate inside systems that preserve the conditions for creativity, engagement, and care.

The takeaway

You can’t scale on a burned-out team.

Not sustainably. Not creatively. Not without turnover.

And here’s the hard part: you might be accidentally building that system right now.

If you’re in a leadership role, this isn’t a guilt trip. It’s a prompt. It's a call to action.

Audit your Energy Operating System.
Look at your pacing. Make the load visible. Create slack. Start the right conversations.

Because this isn’t about making work easy. It’s about making energy sustainable.

And in 2025, that’s a performance advantage.

🔁 Let’s open-source the fix

1/ Where in your current system is burnout being accidentally built in?

2/ What’s one norm or policy you’re upholding that might be rewarding unsustainable behavior?

3/ If your team worked like this for another 6 months, what would break first?

Drop a comment. Share this post with someone leading through burnout. Let’s compare systems, and build better ones together.

🔗 Further Fuel

• Deloitte Burnout Survey

• Gallup: Employee engagement and how to improve it

• From Burnout to Balance: AI-Enhanced Work Models

This post is part of my “Culture Catalysts” series: an inside look at how systems, rituals, and language shape high-trust, high-clarity teams.
It's about the invisible levers that drive momentum: not perks or vibes, but the architecture of how people align, communicate, and compound.

Read more