small_Fcsqb5pWQAAzPIK.jpeg

thumbnail_Fcsqb5pWQAAzPIK.jpeg

Adobe acquires Figma, cue the memes 🤪

large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

Still can’t get a UX job? Give up.

large_featuredImage

medium_featuredImage

small_featuredImage

thumbnail_featuredImage

Sticking to UI/UX trends is a losing strategy

Published on <a href="https://blog.prototypr.io/retrospectives-4a74f7512c0c?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> UX Boot Camp 
<h4>#30dayUXchallenge [Day 28]</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/800/1*H1nV8jRVkJcDc9cg5zFY6Q.png">
<h4>Nicola Rushton — Designing Team Culture</h4>
Every couple of months Nicola works with a new set of clients — new people, with new ways of working together. They created PostFacto — a tool for running remote retros. It is now used by around 2000 teams worldwide.
A show of hands shows most people are doing retros… but most have been in one that felt like a waste of time.
Nicola remembers her first retro, after a tough full-day scoping workshop. The clients were arguing amongst themselves, there was one person who clearly wanted to derail the project, a key person kept dropping out to take phone calls. After this day-long workshop from hell, someone said “wow…retro?”
They wrote up the usual went well, went wrong and do differently. The group was able to use this technique to figure out how to improve as a group, without blame or worry. It was a little weird to talk about your feelings at work… but it’s also nice to work with a team that can be open with each other.
The teams that communicate openly are the great teams.
<h3>Retrospective types</h3>
There are lots of variations on the retro. postfacto.io is an opinionated version, with “happy”, “wondering” and “sad” columns. The labels may vary but that’s their purpose.
Some retrospective may end up into games that teams need to play one per month and other even work like therapy — teams have the possibility to complain about their previous sprint issues.
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N6l9tw3g1OhZwcNxm6yRJQ.jpeg"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*54pHIlUzbZ4p08Fm73ek_Q.jpeg"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IBfVWqhx9T4HXpwxcy9-yA.jpeg">
The key in the end is to do this regularly, but ensure there are actions. Things actually need to change as a result of a retro.
It’s based on research digging into both good and bad retros — lots of 1:1 interviews, observation and dog fooding the product. This showed a common set of pitfalls:
<ol>
<li>The painful, awful retro. Often solved by having them more often (counter-intuitive, but works). Think of retros as scheduled maintenance for your team. Also set expectations, note the prime directive. Beware voting or skipping items — they had a ‘cheese’ item that looked like an easy-to-skip thing. But when they asked ‘who wrote this one?’, it ultimately showed their habitual retro snack of cheese was making a lactose intolerant team member feel a bit ignored.</li>
<li>People not really sharing the truth. It’s a serious problem when people don’t feel safe to share. things that can help: just invite the direct team; actively work to establish a feeling of safety (be vulnerable, or be the one willing to point out an elephant in the room).</li>
<li>The room is dominated by one or two voices. This needs a strong facilitator, who ensures everyone is heard. Watch for someone who has been talked over or interrupted, particularly if they have since shut down.</li>
<li>Same old problems over and over again. It helps to focus on the action items. Don’t repeatedly discuss a problem without trying solutions. If there are lots of options, do a time-boxed trial. Make sure the items are actually actionable, make sure they are owned by someone specific.</li>
</ol>
Last tips:
<ol>
<li>Do retros at least monthly and don’t skip them.</li>
<li>Make it a safe space.</li>
<li>Have a facilitator</li>
<li>Focus on action items (next steps)</li>
<li>Be kind</li>
</ol>
<h3>Design retrospectives?</h3>
We normally run ‘retrospective sessions’ in development teams where designers belong to, but we don’t tend to run design retrospectives between the design teams.
How about introducing some of those games ideas we happily use on development process to improve our social interactions between designers?
Let’s brainstorm together how design retrospective should like. A couple of ideas to start with:
<ol>
<li>Do retros at least monthly and don’t skip them.</li>
<li>Use a game to enhance people to tell honest opinions about some design processes used during the</li>
<li>Have a facilitator.</li>
<li>Focus on actions items (next steps for example: new workshops to learn, new initiatives, pair up with somebody to deal with issues, etc)</li>
<li>Be kind on feedback and areas to improve.</li>
</ol>
What do you think about that? Do you have a design retrospective? Can you imagine this instance as a happy one within your team?
<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F5eb5ba-2%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2F5eb5ba-2%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252F5eb5ba-2%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/8d5e2c740a04faf463af9accfa7e3c31/href">https://medium.com/media/8d5e2c740a04faf463af9accfa7e3c31/href</a></iframe><img alt="" src="https://cdn-images-1.medium.com/max/123/1*gRVYJu11nwFHTMt56Z93fA.png">Natalia Rey — UX Designer at RedGate, mom of 2 little creatures &amp; illustrator on her spare time<img alt="" src="https://cdn-images-1.medium.com/max/119/1*g1xXlc-Yf5xkdPNdA_gxEg.png">Gabi Braga — UX Designer at Envato Elements, freelancer at Toptal &amp; beer enthusiast in her spare time
This post is part of the #30dayUXchallenge: you can read more about why we started it <a href="https://medium.com/envato/why-were-embarking-on-a-30dayuxchallenge-e3d9f1bc1ac6">here</a>, and don’t forget to follow us on <a href="https://twitter.com/ux_bootcamp">Twitter</a> and <a href="https://www.instagram.com/ux_bootcamp">Instagram</a>!
<img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=4a74f7512c0c" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="https://blog.prototypr.io/retrospectives-4a74f7512c0c">Retrospectives</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Retrospectives

Retrospectives

#30dayUXchallenge [Day 28]

Nicola Rushton — Designing Team Culture

Top Stories