Collaborating with design studio method
•Download as PPTX, PDF•
1 like•6,634 views
The presentation focuses on using the Design Studio method to facilitate collaborative, iterative and rapid design. I also wrote a blog post which covers this process https://medium.com/seek-user-experience/two-types-of-collaborative-design-sessions-46c6d7090b70 _______________________ Originally presented at an IIBA up-skilling day as a hands on workshop. August 2014 _______________________ If you are interested in having this presented at your workplace or Meetup, get in touch via Twitter @ThatBaldUXGuy
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
Collaborating with design studio method
- 1. Collaborative Design A practical introduction to the Design Studio method Vedran Arnautovic @ThatBaldUXGuy
- 2. What is ‘Design Studio’?
- 3. Illuminate, sketch, present, critique
- 4. Illuminate, sketch, present, critique
- 5. Illuminate, sketch, present, critique
- 6. Illuminate, sketch, present, critique
- 7. Illuminate, sketch, present, critique
- 8. Illuminate, sketch, present, critique Iterate
- 9. …but I’m a BA, not a designer
- 10. Who should be involved?
- 11. ‘It is hardly possible to overrate the value of placing human beings in contact with persons dissimilar to themselves, with modes of thought and action unlike those with which they are familiar.’ – John Stewart Mill (1806 - 73)
- 12. Illuminate
- 13. Persona Context Goals Emily • 33 years old • Married, two kids • Busy professional • Not very organised • Tech savvy • House robbed • Did not keep receipts • Issues with insurance company • Avoid situation in future • Catalogue assets • Minimise time spent cataloguing Constraints • smartphone or tablet app
- 14. For each belonging, capture • Receipt (if available) • item photo • Description, serial number, ID etc • Estimated Value • Other docs (e.g. valuation) Ability to • add/remove items • organise/group items • export/securely save list of items/details Requirements
- 15. Sketch
- 16. “I can’t draw”
- 18. 1 minute • Draw the following shapes Sketch exercise
- 19. 2 minutes • Draw a screen from your favourite app on your phone Sketch exercise
- 21. Present & Critique (15 minutes)
- 22. Iterate
- 23. start sketching feedback implement feedback refinement of selected ideas influence of others’ ideas
- 24. Challenges
- 25. Sketching is not difficult Getting over “I can’t sketch” can be
- 30. Chinese whispers
- 31. Thank you Vedran Arnautovic @ThatBaldUXGuy
Editor's Notes
- Today we will look at the Design Studio method, but we won’t just talk about it Through a set of interactive exercise, we will experience first hand how it works. Design studio is a way of working and designing that has origins in architecture and industrial design. These days, it is commonly applied to digital products and software development
- What A collaborative, interactive, fast paced design process for coming up with many possible solutions quickly, evaluating those solutions as a group and iterating on them, until the best solution is arrived at What its’ not A bunch of hipster designers sitting around in a warehouse with exposed brick walls and MacBooks, designing the new SnapChat app. It’s far more useful and practical than that. Part design Part buy-in and stakeholder management It helps you take everyone involved on a common journey of understanding a given problem through rapidly trying out different solutions and evaluating those solutions as a group
- Design studio is based on four principles Illumination Sketching Presentation Critique Iteration
- Illumination Who are we designing the solution for? What is their situation (scenarios, journeys etc) What are the business and user goals? What are our design principles?
- sketching Through rapid sketching activities, the team focuses on getting as many ideas (good and bad) down on paper as quickly as possible. This is not art, we are not producing masterpieces Focus is initially on quantity of ideas, then quality of ideas, never on quality of sketches
- present Each participant explains the rationale behind their ideas Ty and sell your ideas – what makes them good? What are you not happy about? Which aspects do you think are worthy of further exploration? This is where you present your sketches, your ideas It’s not just a matter of saying ‘here they are’ You need to defend them – you need to relate them to the persona you are designing for and the goals you are trying to meet You need to get good at presenting/defending your ideas, because the next step in the process is critique
- critique Good critique is hard to give, but it can also be hard to take. That is, if you don’t understand the purpose of it. The critique must not focus on personal opinions – it must focus on how well a proposed solution meets the stated problem for the target persona, in their given context Most importantly, critique should be a balance of positive and negative aspects of a design – without the positive part, the process falls apart because you don’t know what to take forward to the next iteration of the design
- iterate Next, we rinse and repeat as many times as required, or for as long as we can given our time constraints So, that’s the process in a nutshell…
- Hands up who thinks getting consensus from stakeholders is hard, or who has had a hard time with this? Getting consensus is a big part of design studio BA’s are often the facilitator in any project They are the ‘glue’ between different stakeholders Iteration managers – to get an iteration across the line, you can contribute to smoother sign off of requirements and designs BA’s are much more than requirements and user story monkeys By involving the relevant parties, you are facilitating towards easier sign-off designs and requirements It is very hard for someone who was involved in the design process to come back a month later and say that what has been implemented doesn’t meet your requirements
- Any member of the delivery team or the business Business stakeholders Business analysts Developers Testers Designers Different backgrounds, functional roles approach a problem from different angles and bring different viewpoints Don’t underestimate the power of buy-in! Product managers, developers
- John Stewart Mill was a British philosopher
- The illumination phase is where the team gains a shared understanding of the business context, customer, challenges, and market opportunities. What makes the customer tick? What are their pain points? Where are they, what are they doing, what are they trying to achieve? We will start by framing the problem, before we move onto designing
- The illumination phase is where the team gains a shared understanding the business context, customer, challenges, and market opportunities. We will start by framing the problem, before we move onto designing - ipad, wearable, on the wall (digital) Persona: Busy professional Generally a ‘busy’ person Doesn’t have much time for organising things around the house Context Emily has been robbed A number of valuables stolen from her house She hadn’t kept receipts or records of purchase for most of them Now has trouble with her claim with the insurance company Goals She wants to avoid this situation in the future But, she doesn’t want to spend much time cataloguing her existing belongings Also, this has to be an easy process, to make sure she sticks with it as she buys new stuff Design constraints iPhone app and/or iPad app
- Now for the fun part This is not art, or drawing. There is a difference between drawing and sketching Focus on the quantity of ideas initially, then quality of ideas. Quality of sketches is not important, as long as you can get your idea across The level of detail you should go into, depends on what you are trying to communicate – just enough detail
- This is normally where we hit the first obstacle
- YES YOU CAN Is there anyone in the room who thinks they can’t draw at this level?
- Now for the fun part This is not art, or drawing. There is a difference between drawing and sketching Focus on the quantity of ideas initially, then quality of ideas. Quality of sketches is not important, as long as you can get your idea across The level of detail you should go into, depends on what you are trying to communicate – just enough detail
- Remember what I said earlier, try and sell your ideas – what makes them good? What are you not happy about? Which aspects do you think are worthy of further exploration? Probably the most important aspect of design studio Can also be the hardest to master The idea is that we evaluate all ideas in a friendly and collaborative environment Focus on evaluating each sketch in terms of how well it addresses the stated problem, for the stated audience Identify aspects of the design which you think should be considered further, and those you think should be discarded ticks and crosses Group critique helps overcome individuals’ biases flash out details not considered in each sketch Avoid problem solving and suggestions Focus on how the design does or does not meet the problem statement/needs Use personas to keep focused and away from personal preferences
- Steal within teams and across teams – stealing is not only OK, it is encouraged Take into account the feedback you received, but just as importantly the good and bad aspects of other’s designs What would you like to incorporate in the next iteration of your design
- recap
- Avoid personal opinion, to avoid it being taken personally
- Facilitation includes setup keeping time keeping people focused