Every year around April 1st, we like to have a little fun.
But as with most good humor, there’s usually a grain of truth underneath it.
After working with thousands of teams and leaders over the years, one thing has become very clear: agile rarely succeeds or fails because of a framework. It succeeds or fails because of leadership behavior under pressure.
When deadlines tighten….
When scope grows….
When velocity dips….
When stakeholders ask uncomfortable questions…
Patterns emerge.
Some leaders protect the outcome.
Some protect the date.
Some protect the process.
Some protect momentum.
None of these are “good” or “bad.” They’re instincts. And under enough pressure, we all fall back on instinct.
So this year’s April Fools exercise is a simple (and only slightly unscientific) question:
Which leadership archetype shows up most often?
Answer it about yourself.
Or answer it about someone you work with.
Just choose the responses that feel uncomfortably familiar.
The results are 100% accurate. Approximately.
Okay, Now Seriously
It’s easy to laugh at archetypes.
It’s harder to recognize that under pressure, most of us drift toward one.
Agile frameworks don’t fail because teams forget a ceremony. They struggle when leadership instincts unintentionally override the conditions that make empiricism work: transparency, adaptation, and trust.
The good news? Leadership patterns aren’t fixed traits. They’re habits. And habits can change.
If this exercise felt a little too accurate, that’s not a problem. It’s an opportunity.
Because small shifts in how leaders respond — to scope, to deadlines, to uncertainty — can have an outsized impact on how teams perform.
That’s the part that isn’t a joke.
If you’re curious what those shifts look like in practice, we’ve spent the last two decades helping leaders explore exactly that.
Last update:
April 1st, 2026