Content Inventory - In an effort to understand the kind of content we are designing for a detailed content inventory was created to map, content type, relevance and priority.
Collecting Requirements - Spending time onsite at one of the stores, I found this unused lock in a locker to be one of many examples of the culture of trust that Container Store has built.
Collecting Requirements - Onsite performing contextual interviews and following specific roles allows for some of the casual assumptions to be dismissed. This is not what the team had in mind for a place to interact with the software we designed.
Collecting Requirements - There is a cool widescreen display of a windows 7 PC. That was valuable information for our solution.
Collecting Requirements - This is the way the stores communicate. I like to call it a clip board taxonomy.
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Collecting Requirements
Card Sort - With a content inventory we discovered the kinds of content that was being created. What we needed to clarify was how the people consume the content classified it. An open card sort was our solution.
Card Sort - Sideways card sort.
Card Sort
Measuring Results - One of the many views created to analyze the results of the card sort.
Personas
Personas
Personas
Personas
Personas
Personas
Wireframes
Wireframes
Measuring Results
Measuring Results
Measuring Results
Measuring Results
Measuring Results
Wireframe Round 02
Context - This was a way to visually tie together the personas, wireframes and roles. In this way it was much more clear as to the context we are designing for.
Developers & Context
Final Design
IPad
Thank You!
gLike