By Paul Stefanski — 03 Mar 2026

The methodology trap (and how to escape it)

Agile? Waterfall? Hybrid? None of them fit your messy reality perfectly. And that's okay.

Let me guess:

You've been asked (probably more than once): "So, are you Agile or Waterfall?"

And you've probably said something like, "We're Agile... mostly. With some Waterfall elements. It's hybrid. Kind of."

Then comes the awkward silence where the other person either nods politely or launches into why their methodology is superior.

Here's what nobody wants to admit:

None of the methodologies fit perfectly.

Not Agile. Not Waterfall. Not SAFe. Not Scrum. Not Kanban.

Why? Because methodologies are designed for ideal scenarios. And your project? It's beautifully, frustratingly, uniquely messy.

So you have a choice:

You can keep trying to force your square-peg project into a round-hole methodology.

Or you can become a bespoke tailor.

The Principle: Adaptive Thinking

Adaptive Thinking means customizing your approach to fit the unique context of each project rather than rigidly following a single methodology.

It's about being flexible, not flaky. Intentional, not inconsistent.

Think about it:

Would you run a 3-month website redesign the same way you'd run a 2-year enterprise software implementation?

Would you manage a team of 5 co-located developers the same way you'd manage a distributed team of 50 across 6 time zones?

Would you approach a project with clear requirements the same way you'd approach one where stakeholders "will know it when they see it"?

Of course not.

Context matters. And leaders who adapt to context deliver better results than those who follow a playbook.

The Methodologist Trap

I see this all the time:

A PM gets certified in Agile (or PMP, or Scrum, or whatever). They learn the framework. They internalize the rules. And then they become... rigid.

They quote the methodology like scripture:

"That's not Agile"
"We can't do that in Waterfall"
"The framework says we need a daily standup"

And meanwhile, the project is struggling because the methodology isn't serving the work.

Here's the truth: Methodologies are tools, not identities.

You're not an "Agile PM" or a "Waterfall PM."

You're a project leader who uses whatever approach serves the project best.

Sometimes that's Agile sprints. Sometimes it's a detailed Gantt chart. Sometimes it's a hybrid nobody's invented yet.

And that's not failure. That's leadership.

Tailoring, Not Compromise

Let me be clear: Adaptive Thinking isn't about doing whatever you feel like or abandoning structure.

It's about intentional customization.

Ask yourself:

What does this project need to succeed?
What does this team need to thrive?
What do these stakeholders need to stay confident?
What constraints am I working within (time, budget, resources, culture)?

Your answers should drive your approach.

Maybe you need:

Agile sprints for development + Waterfall gates for compliance
Daily standups for the core team + weekly syncs for extended stakeholders
Flexible scope in some areas + locked requirements in others

That's not "hybrid" because you couldn't pick a side.

That's bespoke because you designed it to fit.

Change Isn't the Enemy

Here's the other part of Adaptive Thinking: embracing change as opportunity, not disruption.

Methodologists hate change. It breaks their process. It messes up their plan. It requires... adaptation.

But leaders? Leaders expect change.

They know:

Stakeholder priorities will shift
New information will emerge
Market conditions will evolve
Teams will grow and change

And instead of resisting that reality, they build flexibility into how they work.

They create space for adaptation without chaos.

The AI Advantage

This is where GenAI becomes incredibly powerful:

AI can help you rapidly customize frameworks and processes to fit your specific context without starting from scratch every time.

Need a retrospective format for a remote team with trust issues? AI can design it.

Need a decision framework that balances speed with stakeholder input? AI can build it.

Need to adapt your sprint structure for a team juggling maintenance work and new features? AI can map it out.

You bring the context. AI helps you tailor the approach.

And instead of spending hours Googling "hybrid Agile-Waterfall templates," you spend 10 minutes crafting a custom process that actually fits your reality.

This Week's Prompt

Use this prompt to design a custom approach for your current project:

Copy/paste this into ChatGPT or Claude:

WHO: Act as an expert project methodology designer with experience across Agile, Waterfall, Lean, and hybrid approaches

WHY: because my current project doesn't fit neatly into any standard methodology, and I need a tailored approach that serves my specific context

WHAT: based on the project details below, design a customized project framework that addresses my unique constraints and needs. Include:
1. Recommended project phases or iterations
2. Key ceremonies or checkpoints
3. Decision-making approach
4. Flexibility points where adaptation is expected

HOW: outline a clear framework with 4-6 key elements, explain WHY each element fits my context (not just what to do), and identify where I should stay structured vs. where I should remain flexible

[Paste your project context: team size/structure, timeline, stakeholder landscape, requirements clarity, constraints, risks, etc.]

What you'll get: A custom methodology designed for your reality: not someone else's ideal scenario.

This Week's Challenge

Look at how you're currently running your project and ask yourself:

"Am I doing this because it serves the project, or because it's 'the way we do things'?"

Find ONE process, meeting, or artifact that doesn't fit your context and adapt it.

Maybe it's:

Shortening standups because your team works asynchronously
Adding a visual board because stakeholders need to "see" progress
Dropping a ceremony that's become a checkbox exercise
Creating a custom review format that actually generates useful feedback

You're not abandoning structure. You're not "going rogue."

You're leading with Adaptive Thinking.

You're tailoring your approach to serve the work.

And when you do that—when you stop being a methodologist and start being a bespoke tailor—your projects run smoother, your teams perform better, and your stakeholders trust you more.

Because you're not following a script.

You're leading with intention.

Get Intentional,

Paul

P.S. The best project leaders I know can't be put in a box. They're certified in multiple methodologies, but they don't worship any of them. They adapt. If you're still trying to "pick a side," give yourself permission to stop. Your job isn't to be Agile or Waterfall. Your job is to deliver value. Use whatever helps you do that.