UX Meets Agile: Design Studio Methodology
Design Studio is a quite simple and efficient way to run UX meetings. Yesterday we tried it for the first time. There are several variations of Design Studio, we made it simple for the first run and set the following rules:
- Define problem.
- Sketch 5 ideas individually. No more than 5 minutes per idea.
- Present and categorize ideas to the team.
- Discuss positive and negative sides of the ideas.
- Select interesting ideas and create 2 versions for each final final solutions.
We ran Design Studio for the first time to design Email Integration plugin UI. This plugin allows to setup emails integration and define some rules like “bind email to project and create request”. This way TargetProcess retrieves emails and does some interesting things.
Alex, UX designer, is asking some questions.
Sketches categorized by ideas: 1 vertical line = 1 category.
Sticky notes show votes for each idea. 3 ideas have been selected as top ideas.
2 most repeated ideas: define email rules via drop downs and via drag and drop
The wall overview
Setup email rules via drop downs
Setup email rules via drag and drop
In general, the meeting went fine. It took about 2 hours to generate, discuss and select ideas. 8 people participated in the meeting, and it seems too many. I think it is much better to have 4-5 people, no more. Also the ideas convergence phase should be improved. Too many people generate too much buzz, so it is harder to make decisions. Anyway, we are going to try Design Studio again and adjust it to our needs.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)