View of eLearning Development Approaches - Ease vs. Power

Based on some discussions around What is Rapid eLearning? and Shift in eLearning from Pure Courseware towards Reference Hybrids, I've realized that one of the mental models I use can be roughly summarized by the following picture:

where Ease is roughly how easy (cost, time) is it to develop using that approach and Power is the ability of the tool to provide robust, complex learning solutions.

Many learning applications do not require more powerful tools, thus, the Reference Hybrids that I discussed previously is a blend of low-cost solutions with point solutions when higher power is needed.

I welcome feedback on this mental model.

Also since this is a picture and about half of the people who visit my web site come through search, I thought I'd include the text here so it can be found: Custom Coding, Flash, DHTML
Rapid eLearning, PowerPoint + Audio + Interactions, Form-based Authoring (LCMS), Interactive PowerPoint, Simple HTML, Dreamweaver, CMS (Content Management System),
RoboInfo, Simple PowerPoint, Wiki, Podcasts, Blog, Email, Authoring Tools, Lectora, Captivate.