Edit Team

One Modal To Rule Them All...

(UI / UX / USER ACCEPTANCE TESTING / AMBASSADOR OF GOODWILL)

The entire purpose of the StandOut dashboard is to give managers the ability to observe their teams' behavior within the platform. So having the ability to create new teams and edit existing ones as SCRUM teams are formed and dissolved is an incredibly important, frequently used feature of the site.

The Opportunity

As you can see in the original image, these processes were hidden behind an abstract icon. Click data collected through Google Analytics indicated it was one of the least interacted buttons on the page. Customer Service tickets for "How do I create a new team?" were consistently within the Top 5 user issues month after month. Moreover, I observed users fail tasks assigned to them in user tests when they were asked to create a new team or edit an existing one. They were left frustrated and required help. 

The Approach

I'm not going to dress it up I had some anxiety around this JIRA ticket, it was a pretty unique situation as the UX lead on this particular ticket was transitioning out of the company in the middle of the sprint and I would be "heading this one up" without completed wires or additional design resources. To further complicate matters the story felt incomplete as it only addressed issues the users were having creating new teams and editing existing ones. Key functions like 'Change Team Photo' and 'Disband Team' were completely unaccounted for.

The wires really helped me identify the things that were not mentioned in the story. Namely that we were only solving half the puzzle. Allowing the user to easily do everything in one place, would eliminate unnecessary clicks and provide a much more thoughtful user experience.

At this point frustration had set in amongst the product mangers, designers and engineers alike as the end of the sprint was closing in fast. I felt going back to the to drawing board was the only viable solution, but this time around I got the engineers involved in every decision that was being made. Engineers were looking at sketches, wires, mocks... everything. So far so good, but I faced a lot of resistance (from my own department) as not everyone was comfortable with that level of collaboration. The mindset for some had always been I design and you build. I was confident that I could begin to change those attitudes, all while delivering a great set of features.

The Solution

The finished product was a bit buggy and the first iteration did not include the 'Change Team Photo' functionality within the modal. But the user finally had a place to do everything, the slick animations and overall polish added to these assets made this a really fun ticket. Upon implementation, click rates increased, Customer Service tickets decreased (for the first time in years) and user test participants were able to complete their tasks successfully. Win - win - win!!  However, the crown achievement here was the level of collaboration that was ushered in with this ticket as it was an important milestone for a young team.