How to choose the right UCD collaboration style.pptx
•Download as PPTX, PDF•
2 likes•213 views
User-centred design is a team sport involving lots of different players, from designers and researchers to engineers and product managers. Collaboration is critical, but all too often the wrong style of collaboration is utilised. In this presentation from UCD Gathering 2022 you will find out how to determine and use the most effective collaboration style for a particular task, regardless of whether you're working without someone remotely, or face-to-face.
Recommended
Recommended
More Related Content
Similar to How to choose the right UCD collaboration style.pptx
Similar to How to choose the right UCD collaboration style.pptx (20)
More from Neil Turner
More from Neil Turner (20)
Recently uploaded
Recently uploaded (20)
How to choose the right UCD collaboration style.pptx
- 1. HOW TO CHOOSE THE RIGHT UCD COLLABORATION STYLE NEIL TURNER Photo by Antonio Janeski on Unsplash
- 22. COLLABORATION STYLES • Instruct • Pair • Coach • Delegate
- 23. WHO? WHAT? • What is the task? • Is the task understood? • Have they done the task before? • How do they feel about doing the task?
- 26. INSTRUCT WHO • Keen beginner • Little to no experience of task • Enthusiastic & motivated HOW • Clarify understanding of task • Provide clear direction • Regular check-in
- 28. PAIR WHO • Demotivated learner • Some experience of task • Confused & overwhelmed HOW • Listen and support • Work together to problem solve • Build confidence • Pair where possible
- 30. COACH WHO • Capable, but not yet self- reliant • Good experience of task • Concerns, might be lacking confidence HOW • Listen and question • Understand concerns • Coach to build self-reliance • Give space between check- ins
- 32. DELEGATE WHO • Confident & self-reliant • Extensive experience of task • Enthusiastic HOW • Support autonomy • Set expectations • Encourage visibility • Don’t get in the way!
- 33. HIGH LOW HIGH COMPETENCE & EXPERIENCE INSTRUCT DELEGATE PAIR COACH CONFIDENCE & COMMITMENT
- 36. COLLABORATING WITH SIMON WHO • Front-end developer • Some UI design experience • More comfortable coding than critiquing WHAT • Updating the UI with a new design system • Resolving any usability issues LOW COMPETENCE & EXPERIENCE CONFIDENCE & COMMITMENT HIGH HIGH INSTRUCT DELEGATE PAIR COACH
- 38. COLLABORATING WITH THE DEV TEAM WHO • Little UX design, or research experience • Keen to learn more about user- centred-design WHAT • Carrying out user interviews to better understand users • Identifying key user insights LOW COMPETENCE & EXPERIENCE CONFIDENCE & COMMITMENT HIGH HIGH INSTRUCT DELEGATE PAIR COACH
- 40. COLLABORATING WITH MIGUEL WHO • Very experienced UX designer • Keen to utilise his experience WHAT • Defining the best UCD approach • Exploring design ideas LOW COMPETENCE & EXPERIENCE CONFIDENCE & COMMITMENT HIGH HIGH INSTRUCT DELEGATE PAIR COACH
- 42. GROUP EXERCISE • Discuss the 4 collaboration scenarios in the PDF (link via chat, suggested answers at back) • Which style(s) would you use and why? • (If time) Discuss your current / previous projects • What collaboration challenges did you face? • Which style might have worked well?
- 44. RECAP • Match collaboration style to person(s) and task • Key questions • What is the task? • Is the task understood? • Have they done the task before? • How do they feel about doing the task?
- 45. HIGH LOW HIGH COMPETENCE & EXPERIENCE INSTRUCT DELEGATE PAIR COACH CONFIDENCE & COMMITMENT
- 46. COLLABORATION STYLES INSTRUCT • Keen beginner with little task experience • Clarify task & provide clear direction PAIR • Demotivated learner with some task experience • Pair to listen, support and problem solve together
- 47. COLLABORATION STYLES COACH • Experienced, but concerns & lacking confidence • Listen, question and coach to support self-reliance DELEGATE • Confident with extensive experience of task • Support autonomy & don’t get in the way
- 48. FURTHER RESOURCES ARTICLES • Situational leadership – A summary (Paul Hersey & Ken Blanchard) • Guide to Situational leadership (Research in Practice) VIDEOS • Situational Leadership Model Explained (10 mins) • Situational leadership talk by Hal Mayer (60 mins) BOOKS • Leadership and the One Minute Manager (Ken Blanchard)
Editor's Notes
- Thank you for joining me If you have questions then please post them as we go along and I’ll try to answer them at the end But first, I should introduce myself
- I’m Neil Turner Lead designer at Redgate software in Cambridge, UK Designing and developing software for database development and management
- Also been told that I have an uncanny likeness to Phil Spencer, the UK’s favourite estate agent and co-star of Location, Location, Location Sadly not much demand for a Phil Spencer look-a-like So, let’s talk about collaboration This talk is titled ‘How to choose the right UCD collaboration style’, so let’s talk about user centred design
- User-centred design is a very broad term There are lots of different user centred design processes
- We have the classic double diamond
- The newer triple diamond
- We have Lean UX with emphasis on rapid learning and iterating
- With have processes that are a mix of design thinking, lean UX and Agile What do all these processes have in common? Aside from being user-centred
- One thing all these approaches have in common is that they require lots of collaboration There are lots of different stakeholders involved There are designers, engineers, business stakeholders, project managers, product managers. The list goes on… User-centred design is very much a team sport
- When I started out as a UX designer, I imagined that every project would be like this Everyone would implicitly get along and before long be best of friends
- Of course reality is often very different Rather than a chummy episode of Friends, most projects were more like the Office Collaboration could be very hit and miss, and teamwork was certainly not always dreamwork I experienced this myself early on in my UX career
- I want to take you back 16 years to 2006
- Time was wondering if Barack Obama could be the next president of the America
- Italy won the 2006 World Cup in Germany With Zidane getting memorably sent off for a head butt, and Wayne Rooney for kicking out at Ronaldo
- And I was a fresh faced UX designer, with fewer wrinkles and more hair than I have now
- I had recently started as a UX designer at Johnlewis.com I was part of the UX team, which worked very closely with the web design team
- This meant that I was often creating wireframes like this for the web designers to work from These were the days before cross-functional Agile teams When wireframes were traditionally created by a UX designer for a web designer to turn into a pixel perfect design to be implemented
- I was having some difficulties working with the web design team I put this down to a case of ‘UI designers don’t understand UX designers’ And ‘UX designers don’t understand UI designers’
- There was one UI designer in particular who I was struggling to work with We got along ok, but really struggled to work together on projects I came to realise there was a very good reason for this You see I was using the wrong collaboration style with this particular designer
- By defining very prescriptive wireframes I was taking a very instructive approach
- By delivering very prescriptive wireframes I was taking a very instructive collaboration style I was treating the UI designer as if she didn’t know much about UX design, when in fact she knew an awful lot
- Rather than a very instructive style I should have been taking a more pairing, or even coaching approach
- This is something that I learnt as a UX designer You have to flex your collaboration approach depending on who you’re working with Once I started doing this, I had a lot more collaboration success As a designer there are 4 key collaboration styles Based on the situational leadership model These are instruct, pair, coach and delegate I’ll take about these styles shortly, but first how do you determine which style to use?
- But it not only comes down to who you are collaborating with but also what you are doing You might have someone who has a lot of domain experience, but not necessarily for a particular task It’s therefore vital to ask some key questions Questions which will help inform the best collaboration style to use
- These questions will give you an indication of the competence someone has with a task Along with their level of confidence and commitment This will help inform the best collaboration style to utilise
- You should instruct when someone has little competence but lots of confidence and commitment This is the sort of approach a driving instructor might take
- You should pair when someone has relatively little competence and might have lost confidence and commitment For example, they’ve realised they’re realised how much they still have to learn This is the sort of approach that development teams often take for pair programming
- You should coach when someone has good competence but might have lost confidence and commitment For example, they’re struggling to see the purpose of the task, or how they can apply what they already know This is the sort of approach that a sports coach will take with their team
- You should delegate when someone is highly competent, confident and committed You don’t want to tell someone how knows what they are doing how to do they’re job, you should let them get on with it This is the sort of approach that you might take when bringing in an outside expert
- The task competence, along with the level of confidence and commitment will help determine the best collaboration style to use
- Meet Simon
- Meet the development team Collaboration style isn’t just for individuals, can be utilised for groups and teams as well
- Meet Miguel - An experienced UX designer
- Now it’s your turn You’ll break out into small groups to share and discuss the best collaboration style to use for different scenarios Have 20 mins to work from the example scenarios, and then to discuss your own examples in a group Will set-up Zoom break out rooms for the exercise
- Let’s recap what I’ve covered today
- Either delegate or coach as good task competence and you are confident in your abilities Coach might be a better approach if there is a lack of clarity around the task
- Will upload the slides to my blog – UX for the masses And also provide a link via twitter – where I can be found @neilturnerux Let’s look at what questions have been posted
- I should also mention that we really value collaboration at Redgate software We’re currently hiring for product designers to join the design team Come and chat with me if you want to find out more