Get your team documenting

Since I started to get the UX team to document everything from sketches on paper, meetings with devs, and final designs on a confluence page, we have seen a massive reduction in meetings to refine and communicate ideas. This workflow was quickly adopted by the team and also enhanced their thoughts as they can look back on where they started and get back to the main goal, which is the business case of the problem. We also found that by having this page, the technical handover became much easier for the teams who pick up development requirements later on, and sometimes the designers even forget what they do. Still, by having this page, the confluence pages solved the problem_

Issue
Sharing of ideas
Solution
Documenting on confluence
Measurement
Reduction of meetings and loss of communication
Level to implement
Easy

Move to Figma

The UX field is going through a major shift right now. Many designers made a move from photoshop to Sketch in the last ten years, but now a new technology is emerging by the name of Figma. This tool will bring efficiency and collaboration to a new level. When we decided to make a move, we knew we had a lot of work ahead of us to bring our design systems over, but since introducing this tool, our team has reduced the time and effort it takes to build workable prototypes and has reduced costs by 80%. I think everyone in management was glad I proposed to make this move_

Issue
Costs of previous tools & collaboration
Solution
Introduce Figma tool
Measurement
Reduction of costs of designs
Level to implement
Very hard

Understand the cost of a sprint

Understanding the costs of your department and others is crucial for any UX manager to negotiate ideas through the pipeline. My designers have many ideas that they can bring to an application, but it means nothing unless I have some costs behind me to negotiate with the business. If an idea costs a certain amount and brings no return, then no one will listen. When stakeholders love to bring ideas that have no value, the best way is to evaluate the costs that occurred to design, develop and test and then see if they are interested in pursuing it further once the costs are outlined to them_

Issue
Cost of ideas
Solution
Establish the cost of a sprint
Measurement
Reduction of unwanted meetings
Level to implement
Easy

Agree on naming conventions

Get your team to agree on naming conventions because this is important to the team's communication across the company. Once you have that decided, make sure you communicate these names as much as possible so that other departments are also aligned when talking about the same subject. Even though this detail is tiny, it brings so many problems when people are using different terms t fit them and cause many issues, as I have seen before. Ensure that the name is not taken by someone else and is also on what you have labeled your subject about. I have often seen teams using words for entirely unrelated topics, and even though they communicate this naming convention, people are still confused when it is not subject-related_

Issue
Issue on subject communication
Solution
Establish correct names of subject matter
Measurement
Reduction of confusion
Level to implement
Very easy