Might not get it all out but the essence of this post is about whether we need to be building technology based on context rather than capability. More and more there are great capabilities available but they fail to reach the desired adoption by the target user base. Why? I think it’s because they lack context for how/when/where/why the user needs the capabilities.

Agile user stories are effective because they provide some level of context… As a (audience), I want to (capability) so I can (goal). Both audience and goal gives us more context to understand how/when/where/why the capability will be leveraged.

A trend I’ve noticed about my successful work over the last few years is that the designs were directly influenced by understandinqg the context of the audience. Not just the job my product was hired to do, but the context in which that job is to be done.

Apps store success – many capabilities already optimized for a specific context (small screen, limited bandwidth, etc)

Blah blah blah