When it comes time to meet face-to-face to discuss how to implement a new feature, we find it helpful to do things the old fashioned way: organize our UX flow with Post-it notes. Yes, you read that right and no, that’s not the name of a new productivity app. Although we typically use this before in-person meetings, there’s no reason you can’t use it afterward as well. This way, when the team finally meets together in person, everyone will be going into the meeting with a solid idea of what the main objectives are and which points still need the most work. While we don’t spend too much time on it, we use it to get a quick draft of the wire flow down and make notes of any points or questions we need to discuss. ![]() Google makes it easy for multiple team members to make changes in real time and combined with Slack and Zoom (more on those later), it’s really a breeze to start hacking out ideas as if everyone’s in the same room.īrainstorming and collaborating in Google DocsĪfter getting our basic ideas down, we shift to a tool called Miro, basically an online whiteboard and post-it notes. Typically, we start with a general idea of the feature we want to implement and create a simple flowchart that elaborates on its functionality. ![]() Unlike a traditional Word doc or PowerPoint slideshow, Google Docs and Slides are hosted online, and multiple users can edit the same doc in real-time, which makes it far easier to brainstorm and collaborate on new ideas. In a nutshell, Google Docs is Google’s version of Microsoft Office with one big bonus: at its core, it’s built around collaboration. Google Docs is probably pretty familiar to anyone reading this article. While neither of them are UX tools in their own right, they do tell us things like how a user is interacting with a new feature, which landing page designs are converting the best, and whether or not a new menu item is being seen, all of which help us determine what’s working and what’s not.Įvery UX idea we implement begins with two questions: What are our user’s goals and how can we make achieving them more streamlined? Once we’ve homed in on a part of our app that needs improvement or a new idea we want to implement, we begin with our first tool, Google Docs. We rely heavily on Heap and Google Analytics to provide the user data that informs our design decisions. We’ll follow the journey of a UX design from the ideation phase through to the wireframe, prototyping and design steps, before finally reaching the development stage. In this post, we’re going to give a bit of insight into our process, and more precisely, what tools we use to get the job done. Thankfully, we have a great UX team that’s developed a highly-effective and efficient workflow to tackle this never-ending challenge. As Donald Norman so eloquently said in his book, Living With Complexity: “ We must design for the way people behave, not for how we would wish them to behave.”Īnd let me tell you right now: That’s no easy task. This is a guest article by Jodi English, designer from AmpjarĪs a SaaS company, every day at work poses a problem: How do we reconcile our vision for our product’s user experience with how our users actually interact with it? As much as we’d like to fully indulge in creativity and explore our wildest ideas about what a modern user experience should be, we always need to weigh that with what the data shows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |