OK, it's official. I am now siding against use cases, scenarios, and the other typical design methodologies, as instantiated in this post about learning resource repositories. Why? Because they freeze your perspective on design and development into a view of what is rather than what could be or ought to be. The use cases here, for example, limit the author's view to learning resources created by tutors or publishers, to uses consisting of 'put' and 'get', and to thinks like intellectual property rights being at the forefront of design principles. When we look like an assertion like "The benefits to users depend on how they already share their teaching content with their peers" we can see immediately not only how constraining it is, but also how false it is. As I commented somewhere recently: imagine how email would have turned out had it been designed with existing constraints in mind.
Today: 6 Total: 88 [Direct link] [Share]
