Predictive vs Adaptive

Here's a question that separates people who've read about agile from people who understand it: Is agile always better? The honest answer is no. And being able to say no — and exactly when — is about to make you rarer than most practitioners.

By the end of this video, you'll have a three-question decision lens for judging whether a piece of work wants a predictive approach, an adaptive one, or a deliberate mix — and you'll leave with eight agile myths permanently busted.

Let's define both approaches without a villain. Predictive — often called waterfall — plans the whole endeavor up front and then executes: strongest when the work is well understood, the requirements are stable, and late change is expensive. Adaptive — the agile family — plans in short cycles and adjusts from feedback: strongest when the work is novel, requirements will evolve, and feedback is available fast. Neither is morally superior. They are tools with different grips.

When you meet any piece of work, ask three questions.

Question one: how knowable are the requirements, honestly? Building the fourth identical warehouse: highly knowable. Launching a product nobody's seen before: you're guessing, and the guesses are the risk.

Question two: how costly is late change? Pouring concrete, filing with a regulator, printing ten thousand brochures — change after the fact is brutal, so decide carefully up front. Editing a webpage, adjusting a service, reordering a plan on a wall — change is cheap, so let learning drive.

Question three: how fast can we get real feedback? If real users, real patients, real customers can react to something small within days, adaptive working compounds that advantage. If genuine feedback only arrives at the very end — a bridge either stands or it doesn't — you must front-load the thinking instead.

Knowable, expensive-to-change, slow-feedback work leans predictive. Unknowable, cheap-to-change, fast-feedback work leans adaptive. Most real work is a mix — which brings us to the word that frightens purists.

Hybrid. A hospital renovation fixes the building phases predictively — approvals, structure, safety — while the ward teams adapt their workflows iteratively inside it. A wedding locks the venue and the date like concrete, and adapts the guest list and program like software. That's not indecision, and it's not failure to "go full agile." It's the entire skill: fit the approach to the work, not the work to the fashion. Remember the GPS from Lesson 2? A GPS is a hybrid in your pocket — a firm destination and route, held loosely, re-planned the moment reality speaks.

Now — you've earned this. Eight things people confidently say about agile, each wrong, each flipped in one line.

Agile means no planning? Agile plans more often, in smaller pieces. No documentation? Just enough, kept current — the working thing wins tiebreaks. Only for software? The ideas outgrew software long ago. Agile is Scrum? Scrum is one framework in a bigger family — Module 2 makes this crisp. A silver bullet? You just learned a three-question lens that sometimes answers "predictive." No deadlines? Agile is full of deadlines — short ones, on purpose. Undisciplined? Sustainable pace, self-review on schedule, quality held under speed. Discipline, pointed inward. Fast and sloppy? Agile targets sooner and smarter, never careless — quality is one of its principles.

You might think, after all this myth-busting, that the danger is other people's ignorance. That's understandable. Actually, the most expensive myth is usually one of our own: "adaptive is always the enlightened choice." You now know better. Choosing predictive for the regulatory filing is not a failure of imagination — it's the lens working.

Three things to keep. One: three questions — how knowable are requirements, how costly is late change, how fast is real feedback. Two: predictive, adaptive, and hybrid are all legitimate; hybrid is a skill, not a compromise. Three: eight myths, busted — and the ninth myth to watch is "agile always."

You can now judge the work. Time to meet the people — the roles, the rhythms, and the two most misunderstood job titles in modern work. Module 2.