Words matter: Sharing Vocabulary to Strengthen Teams
•
0 likes•38 views
Design is complicated, but sometimes not as complicated as it feels when you are speaking about design with your cross-functional colleagues. In this workshop we will navigate key moments before, during, and after a project when wires tend to get crossed and expectations are poorly set due to miscommunication. We will discuss why it is important to kick off projects with a shared vocabulary that everyone on the team understands, and how not being intentional and concrete about the words we use can cause friction amongst your team, and increase the additional risk to the success of your project. Looking across the stages of design, we will start to layer on this vocabulary to help our teams make decisions, set expectations, and articulate how we arrived at our final designs.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Words matter: Sharing Vocabulary to Strengthen Teams
Similar to Words matter: Sharing Vocabulary to Strengthen Teams (20)
Recently uploaded
Recently uploaded (20)
Words matter: Sharing Vocabulary to Strengthen Teams
- 3. DESIGN CODE
- 8. Avg person has meetings per day 3 for managers
- 9. Assuming an average of 45 min meeting and 125 words spoken per minute.
- 20. ExternalInternal
- 22. Internal Internal (ex. Technical lingo) External (ex. RACI Inform, steering committee)
- 24. Language InternalExternal Design Systems Branding Copywriting Technical Decision Administrative Status PRODUCT Marketing
- 25. Organizations which design systems are constrained to produce designs which are - Conway, 1967.
- 30. We need to do more discovery. Why are we starting over?
- 31. What words have created the most misunderstanding and confusion amongst you, your stakeholder, and/or your cross functional teammates. 3 minutes Individually jot down a few ideas 5 minutes Find a partner and discuss your ideas 7 minutes In a small group discuss the topic 1 minute per group What are three key takeaways?
- 32. How might we categorize these?
- 34. What is impact?
- 35. Impact is not a thing, silly!
- 39. ● Certainty ● Impact ● Effort ● Complicated ● Intuitive ● Usability problem ● Urgency ● Discovery ● Done ● MVP ● Design Process ● Ready ● Prototype ● Research ● Problems ● Innovation
- 40. low high ● Certainty ● Impact ● Effort ● Risk ● Feasibility ● ….
- 41. How are you on your hypothesis? What is confusing? low high Solution One
- 44. low high Solution One Solution Three Solution Two Easier to get consensus, since there is little value in arguing how much more difficult one solution is over the other.
- 47. Create a product to help students study Adaptive Quiz Application In-ebook highlights and notetaking
- 48. Create a product to help students study Adaptive Quiz Application In-ebook highlights and notetaking
- 49. Create a product to help students study Adaptive Quiz Application In-ebook highlights and notetaking Who’s effort? Impact on what?
- 50. Effort = Dev Impact = $$
- 51. Create a product to help students study Adaptive Quiz Application In-ebook highlights and notetaking Impact on Student Outcomes ContentDevEffort
- 52. 1. Code an assessment application 2. Write several hundred questions that will be used by the assessment application
- 54. I am thinking that the development effort is low because... This is going to require a huge content lift.
- 55. Product EngineerContent Designer We may have a library for this. This sound complicated to code.
- 56. Product Engineer was not invited, or wasn’t allowed to attend Content Designer This sound complicated to code.
- 57. $21887 per/month Content Content Content Dev $30109 per/month Dev Dev Dev Content 27% (not including scrum master, qa, ...) $25,000+ difference per quarter
- 59. How might you plot your the words? Impact on Delays Frequency
- 62. ● Discovery ● Done ● MVP ● Design Process ● ...
- 64. I need to see the entire flow before I size this
- 66. Have we agreed on to expect ? Ready for Forecasting Ready for Epic Grooming Ready for Story Grooming Ready for Implementation Ready for Beta
- 71. ● Prototype ● Research ● Problems ● Innovation ● ...
- 73. Young UX designer is given a list of 8 initiative to work on, and they want to make a great impression! What do they do?
- 74. Semester Starts Sept 14th Checklist Thinking Toss it over the wall Optimism Despair
- 75. There is only one way of solving this problem I have no idea how to solve this problem
- 77. Semester Starts Sept 14th Controlled Risk Taking High Risk Low RiskMid Risk
- 79. low high ● Is everyone approaching the term from the same lens? ● Does the group have a mental model of what low and high look like? ● Can we get more specific to create shared meaning?
- 80. ● Does everyone understand what is expected of them in each status? ● What signals are we looking for to know that we have completed this status? ● Could the same term be used for multiple milestones? (ex. Ready...ready for what?)
- 81. ● Could people identify one type from another? ● Does a change in category correlate with an increase of effort? How much?
- 86. standardizing the , while keeping team
- 87. How do you plan on addressing the language at your workplace? 3 minutes Individually jot down a few ideas 3 minutes Find a partner and discuss your ideas 5 minutes In a small group discuss the topic 1 minute per group What are three key takeaways?