ADDIE is a linear model in a networked world.

Sure, it provides some structure, but so did the waterfall model for software development (requirements -> design -> implementation -> verification -> maintenance). Object oriented programming replaced the waterfall model in the 1980s (who develops software using waterfall today?). Since then approaches such as extreme programming and UML have emerged and supplanted OOP.

Why? because they fit better in a world where change is the new 'normal'. ADDIE may have worked for very stable industrial-type environments and in the military when change was rare and slow, but it doesn't where the imperatives are innovation, responsiveness, and speed to competence.

ADDIE is one reason why learning/training has had difficulty being seen as a strategic business component in organisations - ADDIE makes the whole process of developing learning solutions for business problems too slow and projects simply can't deliver to demanding timelines.

Apart from the above, I've always had a big problem with the 'E' being at the end of the process. Surely you need to decide the evaluation model to be used for any learning event/process before you start the design. Otherwise how do you scope and define the design? And surely the 'DDI' processes need to be iterative - design->develop->test->refine the design->redevelop->test->refine the design etc. etc.

So maybe it should have never been called ADDIE in the first place, but EDDIDDIDDIDDIDDIDDIDDI......