Introducing Agile Discovery™
Most failed transformations don’t fail during development. They fail before a single line of code is written, because nobody took the time to discover the process first.
Over two decades of business process automation, I’ve watched organisations choose a delivery methodology, argue passionately about Waterfall versus Agile, and still end up with software that doesn’t reflect how their people actually work. The methodology wasn’t the problem. The missing step was.
That missing step is why I developed Agile Discovery, and why I wrote my new book, Discover Your Process First: The Missing Step in Every Failed Transformation.
The two methodologies we all know
Waterfall
Waterfall is linear and sequential. Each phase must be completed before the next begins. Requirements are gathered and documented in full at the start, the scope is fixed, and the customer typically appears twice: at the beginning to set out requirements and at the end to validate the finished product. Testing happens late, after implementation, and the whole product is delivered in one go. It works well when requirements are clear, stable and well defined, and timelines are predictable. But when it goes wrong, it goes wrong late. Risks are hard to spot early and changes are difficult and costly once a phase is complete, so problems surface as expensive rework at the worst possible moment.
Agile
Agile was the answer to that rigidity. Work is broken into short sprints, requirements emerge and are refined continuously, and change is welcomed at any stage. Customers collaborate and give feedback throughout, testing is built into every iteration and a workable product is delivered incrementally. It’s the natural choice for complex, uncertain or fast-moving projects, and it catches issues far earlier than Waterfall.
Yet Agile has a blind spot of its own. Its discoveries are made in software. Every misunderstood handoff, every conflicting approval rule, every step nobody mentioned is found by building something, showing it to users and building it again. That is faster than Waterfall’s late surprises, but it is still discovery by development, and development is the most expensive place to learn how your process really works.
Introducing Agile Discovery™
Agile Discovery™ is the Intelligent Actions methodology in which a collaborative team creates a graphical specification of a workflow process that is actively modelled during specification capture, verifying that it behaves as expected and identifying unintended conflicts.
In plain terms, it takes everything that makes Agile effective (emergent requirements, continuous collaboration, early testing, openness to change) and moves it upstream into the specification itself.
Instead of iterating on code, the team iterates on a living, visual model of the process. Everyone in the room can see it, understand it and challenge it. As the specification is captured, it is actively verified: does this path actually complete? Does this approval conflict with that one? What happens when two people act on the same request? Those questions are answered while the process is still a diagram, not after it has become a system.
How the three compare
On approach, Waterfall is linear, Agile is iterative and Agile Discovery is collaborative graphical process discovery.
On requirements, Waterfall fixes them upfront. Agile and Agile Discovery both treat them as emergent and refine them continuously, with Agile doing so throughout the project and Agile Discovery doing so throughout specification capture.
On change, Waterfall offers little flexibility. Agile welcomes change at any stage. Agile Discovery welcomes change during specification capture too, and can do so with confidence because every change is verified against the model straight away.
On customer involvement, Waterfall limits it to the start and the end. Agile keeps customers involved throughout, and Agile Discovery does the same during specification capture, because active verification gives stakeholders something concrete to react to.
On testing, Waterfall leaves it until late. Agile tests incrementally throughout development, while Agile Discovery tests incrementally throughout specification, so issues are found and resolved before development begins.
On delivery, Agile Discovery keeps what works in Agile: frequent, incremental delivery of a workable product after each iteration. On risk, the difference is the heart of the matter. Waterfall struggles to identify risk early. Agile addresses it quickly through fast feedback cycles. Agile Discovery goes a step further and enforces a detailed specification ahead of development, made possible by fast feedback from verification during specification capture. You get Agile’s responsiveness and the confidence of a well-defined specification, without Waterfall’s rigidity.
Where Agile Discovery fits
Agile Discovery applies to any project that can be represented graphically, where multiple users provide their primary input through webforms into a structured workflow process. That describes a huge share of the systems businesses depend on every day: approvals, onboarding, recruitment, requests, case management and much more. If your transformation involves people handing work to other people, Agile Discovery was built for you.
Discover your process first
In Discover Your Process First, I explain why digital transformation so often fails, how Waterfall and Agile each fall short at the crucial early stage, and how Agile Discovery and Active Process Discovery™ close that gap. The book walks through the whole workflow journey with real case studies, practical worksheets and the tools you need to put process discovery at the centre of your next project.
The book is now available to support through a presale campaign with Manuscripts. If you’ve ever been part of a transformation that looked right on paper and went wrong in practice, I’d love your support, and I’d love to hear your story in the comments.
Back the campaign and reserve your copy.
And if you know someone involved in business change, process improvement, automation or digital transformation — please pass this on.
Discover your process first. Everything else follows.
A D Blagden © 2026 intelligentactions.co.uk
#DigitalTransformation #ProcessDiscovery #Agile #BusinessAutomation #Workflow #SoftwareDevelopment #AgileDiscovery