Inquiry Based Design

From GSLISWiki

IBD does not fit into other design categories, because it describes an alternative design cycle from that which is typically conceptualized. The typical design cycle is:

1. Brainstorm, conceptualize, design.
2. Build system.
3. Test it, release it.

The IBD cycle is:

1. Build a simple, sufficient, rough system
2. Test it out by giving it to users
3. Design a new system based on what the users need, want, have difficulty with, etc.
4. Build it, then go back to step 2.

It is a constantly evolving design cycle, rather than an attempt to design for the user, once and for all. It requires considerable user patience, as the first few systems tend to be buggy. However, it essentially describes how software actually is developed: in versioning cycles.

IBD is Chip Bruce's brainchild, it is what the iLabs project of the Inquiry Group is all about.