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

From Design System to ‘NFT Design System’: Creating TinyFaces

Neurodiversity and Inclusion: Choosing Kinder Design

medium_652ccf22c8853584bde5553986a4eed0.png

small_652ccf22c8853584bde5553986a4eed0.png

thumbnail_652ccf22c8853584bde5553986a4eed0.png

Web5 is here. Goodbye Web3? TBD.

<p><a href="https://uxplanet.org/9-problems-that-ux-teams-face-and-how-to-solve-them-f8a6b3bb2768?source=rss----819cc2aaeee0---4">UX Planet &mdash; Medium</a> | Alana Brajdic <img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tJY_bSPFPQRW4LTtBeSEaQ.jpeg"></p>
<h3>1. You don’t know what each person in your team is working on.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/500/1*PrPwLqI0nEnzlW2aDvLo1Q.gif"></p>
<h4>Have Daily Stand Ups</h4>
<p>Also known as a ‘daily scrum’ or a ‘daily huddle’. In these, the team meets every day at the same time, <strong>for a quick status update</strong>. Use this time to ask for help, to collaborate, mention blockers, or any other general messages.</p>
<h4>Create a UX Sprint Board</h4>
<p>Create a physical (or digital) UX sprint board, tailored to your team.<strong> You can refer to it and update the progress of projects during stand up each day. </strong>Categories could include, research, usability testing, design, deliver.</p>
<h4>Team Design Critiques</h4>
<p>Make these regular to ensure everyone is up to date and able to give meaningful feedback. It’s a great way to see an overview of each person’s work.</p>
<h4>Project Design Documentation</h4>
<p>For complex projects, design documentation is a life saver. <strong>It acts as a go-to place to view the evolution of a project. These documents are available for everyone to read through.</strong> Making it very easy for future handovers and communication with stakeholders.</p>
<p>In this, you’d note research, testing results, prototypes, design decisions, risks, reasonings etc. Use a project management tool for this, such as Confluence. If you have less resources, a google document would also work.</p>
<h3><strong>2. You work remotely or don’t sit together in the office.</strong></h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/480/1*SE2wvU_CGQjW-ZxaB7i02w.gif"></p>
<h4>Create a digital chat and peer view room.</h4>
<p>Keep the chat room for banter and the peer review for design feedback. This is a way to get instant feedback on a design without setting up a formal design critique. It allows people away from the office to add and receive feedback as well.</p>
<h4>Organise team outings.</h4>
<p>This can be as simple as a self organised team lunch. <strong>Relationship building is the key to a strong functioning team.</strong></p>
<h4>Create a digital window between offices.</h4>
<p>Let’s say you have two offices that people work from. With a microphone, webcam and TV screen, you can create a ‘window’ to join the two together in real time. This allows you to communicate casually with someone, face to face as if you were both there.</p>
<h4>Create a very organised shared drive in the cloud.</h4>
<p>Files need to be accessible for all teammates. These include assets, master files and current work. Create a standardised file naming convention and folder practises to maintain the organisation. If not, it can it very become overwhelming.</p>
<h4>Set time aside for a UX academy day.</h4>
<p>UX academy is a time allocated to sharing knowledge, communicating and learning as a team. You can learn more about what to do in an academy day here.</p>
<p><a href="https://blog.prototypr.io/how-dedicating-a-weekly-ux-day-will-strengthen-your-design-team-c6dd39195af4">Things You Can Do to Strengthen Your Design Team.</a></p>
<h3>3. There’s a lack of ownership over work.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/500/1*i51k3XqZf5xVEWsWdCmkeA.gif"></p>
<h4>Create a team culture of unconditional support from leads and teammates.</h4>
<p>Support and a good team culture is like having a safety net under you. It gives a person courage to take ownership and accountability of work. It’s about making people comfortable to take on challenges and speak up when they don’t know how to do something.</p>
<p><a href="https://blog.prototypr.io/what-the-hell-is-team-culture-and-why-is-it-so-important-d923141854e5">What the Hell Is ‘Team Culture’ and Why Is It so Important?</a></p>
<h4>Give someone more responsibility by creating a UX owner model.</h4>
<p>A ‘UX owner’ model means that one designer has ownership over a whole project. They’ll be the go-to source of all knowledge and documentation. <br />When we’re handed immense trust from our leaders, we take our position more seriously.</p>
<h3>4. Teammates have different methods of working.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/500/1*pxX49Jp8pc-gS7TrKJlVLg.gif"></p>
<h4>Align on ways of working by discussing and testing them as a team.</h4>
<p>Everyone has a unique way of working, which is a great thing. But if it starts to cause friction in the whole team’s workflow, then it’s an issue. For example, when someone isn’t using the shared file system in the correct way, or they’re not using it at all. This impacts the whole team.</p>
<p>It’s important to iron out the standard methods you want to do as a team. Talk about new programs you want to trial, go over what’s working well in other teams. What’s not working well? Trial, test and align.</p>
<h4>Create a standardised ‘instruction’ manual/guide.</h4>
<p>This could be for file naming conventions. How to package assets, where to put designs or how to create a new icon. It’s a great thing to collate for future staff onboarding as well.</p>
<h3>5. The Experience for Apps is Different to the Website.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/480/1*FrHjr0NK4SLjhdEBG2xbEA.gif"></p>
<h4><strong>Take on a UX owner model and design the feature across every platform.</strong></h4>
<p>Imagine two designers working on the same solution. One is designing for web and the other for apps. These designers would need to be in constant communication to ensure they’re aligned. This isn’t sustainable. <strong>A ‘UX owner’ model, means that one designer has ownership over a solution that spans across every platform.</strong> They’ll design with all platforms in mind, ensuring a harmonious experience.</p>
<h4>Don’t hand over designs until you’ve had team critiques.</h4>
<p>Sometimes we can become blind to our own work. <strong>Others will be able to raise considerations and inconsistencies you may have missed.</strong> Along with impacts on other areas of the app. Always share your designs with your teammates.</p>
<h3>6. There are different visual languages.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/480/1*HVM9FlBv1IFG5MdcXbS1sw.gif"></p>
<h4>Create basic design guidelines</h4>
<p>This is a standardised set of guides to design by. It outlines button styles, colour pallets, tone of voice, font sizes, font types, contrast levels etc. Trust me, you’ll end up memorising those HEX codes.</p>
<h4>Create a component library</h4>
<p>A component or pattern library is a collection of user interface design elements. Team members can use these as building blocks when designing, allowing for quicker and more consistent work. Store these in a shared file for all team members to use.</p>
<h4>Have dedicated teams to maintain the visual language.</h4>
<p>This is best for large scale companies. For example, at Spotify, they have the GLUE team (<em>a Global Language for a Unified Experience). </em>GLUE actively documents and maintains Spotify’s design styles. Along with guiding teams when creating new UI elements.</p>
<h3>7. You haven’t officially documented or shared your UX process.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/500/1*hgkjpNMkN9ZMi7nVAdQkgw.gif"></p>
<h4>Create your design process as a team</h4>
<p>You don’t need to reinvent the wheel. The <a href="http://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond">double diamond</a> process is a great starting point. Tailor it to your team and build these assets together. This ensures that everyone has ownership, and the knowledge to act on it.</p>
<h4>Give visibility to these assets to educate and communicate with others.</h4>
<p>You can now use these defined assets to explain to people where you’re up to in the process. This is useful when scope creep is occurring, or stakeholders want to make changes. Refer to it to explain the ramifications, where it might set you back in the process, or why you can’t turn back now.</p>
<h3>8. There’s misconceptions in other departments around what UX does.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/320/1*0PZ6DWcGk5WyQgiyVx_8fQ.gif"></p>
<h4>Align on your message and definition of UX.</h4>
<p>Designers need to be able to articulate the definition and value of user experience as a united team. The more consist the message, the more effective it will be. Document your design process, principles and the definition of UX as a together as a team. Also, don’t forget to align on your lexicons. For example, it’s <strong>usability</strong> testing, not <strong>user</strong> testing. We aren’t testing the users!</p>
<h4>Invest time into educating people about UX</h4>
<p>This could be in a formal stakeholder session or casually in a kitchen conversation. Speak the language of the person you’re informing. To a business stakeholder, explain UX in the context of business goals and value to the company.</p>
<h4>Create a stronger relationship with other departments.</h4>
<p>Invite them to your user findings sessions, ask them to give your team a talk on what they do. Create visibility around what you’re team does. Build trust, offer to listen and help with their problems.</p>
<h3>9. You want to make a change but don’t know where to start.</h3>
<p><img alt="" src="https://cdn-images-1.medium.com/max/400/1*SMN6XCqS9H7hsofc1zDZZQ.gif"></p>
<h4><strong>Hold a team retrospective.</strong></h4>
<p>To put it simply, this is a team based session in which you reflect on what is working well and what isn’t. In this case, the most effective retro is a motivational one. Ask the question “where do you want the UX team to be in 6 months time?”. Create actionable items and walk away from that room feeling excited for the journey ahead.</p>
<blockquote><p>Making change takes time and effort. But the most important to remember is that this needs to be a whole team effort. Everyone needs to be behind it, supporting each other and working towards a common goal.</p></blockquote>
<h3>Any of these sound familiar?</h3>
<p>All teams experience different problems. These are usually influenced by the scale and maturity of the team. So, let’s spark a discussion. How are you solving these problems in your organisation? Are there other problems you’re confronting? Let’s learn from each other.</p>
<p><em>Feel free to reach out to me on </em><a href="https://twitter.com/alanabrajdic"><em>Twitter</em></a><em>, and </em><a href="https://medium.com/@alanabrajdic"><em>follow me</em></a><em> on Medium for more design articles coming soon. In the meantime, why not check out these?</em></p>
<ul>
<li><a href="https://blog.prototypr.io/10-reasons-why-all-designers-should-start-writing-more-f34646a6e06b">10 Reasons Why All Designers Should Start Writing More</a></li>
<li><a href="https://blog.prototypr.io/22-things-new-ux-designers-should-know-before-entering-the-workplace-8eb324615cb9">22 Things New UX Designers Should know Before Entering the Workplace</a></li>
</ul>
<p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;url=https%3A%2F%2Fupscri.be%2Fb3e808%2F&#038;image=https%3A%2F%2Fe.enpose.co%2F%3Fkey%3DdRXnS9Gplk%26w%3D700%26h%3D425%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%252F%253Fenpose&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=f8a6b3bb2768" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou"></p>
<hr>
<p><a href="https://uxplanet.org/9-problems-that-ux-teams-face-and-how-to-solve-them-f8a6b3bb2768">9 Problems That UX Teams Face and How to Solve Them</a> was originally published in <a href="https://uxplanet.org">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>


9 Problems That UX Teams Face and How to Solve Them

9 Problems That UX Teams Face and How to Solve Them

1. You don’t know what each person in your team is working on.

Top Stories