Shena brings best of frontend programming and backend architecture together, to ensure that the on-screen user experience is in absolute synch with backend architecture, for immaculate customer experience and business goals.
If journey maps are new to your team, a great way to introduce them is to spend an hour or two during a kickoff or brainstorm session working in small groups, with each group roughing out the path of a different user. If they’re already part of your UX process, you might just need to start working from a wider range of personas and scenarios.
Our UX practice is comprised of four disciplines: design, front-end development, research, and content strategy. Since we’ve defined these are the UX perspectives we value most on our product teams, we’ve made sure they’re well represented on our systems team. When we defined the team that would work on Polaris back in January 2017, it was important to have representatives from each of these disciplines as contributors and as stakeholders.
Without retros it would be hard to take learnings from what hasn’t gone so well and to figure out ways to work better together next time around. As the saying goes, the definition of insanity is doing the same thing over and over again, but expecting different results. That’s where retros come in.
While it is useful to interview your existing and potential new customers to find out which jobs-to-be-done are important to them, it’s also worth noting the differences that will be key among these groups: if you design from a clean slate, trying to solve the jobs-to-be-done in a way which suits the brand new users, you will likely severely alter the workflows of your dedicated, existing customers (and thus negatively impact their productivity, as they have to relearn the product).
Often, a feature or UX will fail. If it was defined by a User Story, then discovering why it failed will be difficult, because implementation was coupled with motivations and outcomes. Because of the coupling, how can anyone know what was wrong? Was the implementation wrong, or were the assumptions about motivations wrong?
Use an input selector if there are over 5 options. Incorporate contextual search within the drop-down if there are over 25 options.
If you want to connect with Shena via LinkedIn, please drop her a message for why.
Shena loves products and ContentHug was one such experience. She may invest her learning in something else, some day.