Putting the user first

Understanding the user and what they’re trying to accomplish is at the core of our development process here at BitBakery.

Our clients trust us to provide complete tech teams to build their MVP – minimum viable product. When we tackle these projects, we put the user at the center of our process. This ensures we’ve got the right problems identified before we start designing. 

Whether you call it human-centred design or design thinking, it’s a straightforward way of doing discovery that we use on every project. 

In my intro post, I shared with you that I’m starting my journey to learn as much about user experience design as I can. My role as a Software QA Engineer gives me a chance to work with our head of design and our developers. I get to see the entire design and development process unfold – and help shape some of the decisions we make.

Here’s a few of my takeaways so far – 

Know who you’re designing for

One of the first steps in the discovery phase is creating personas. These are representations of users – and can include their education, family background, likes/dislikes and more. Personas are meant to represent groups of users. A great design will target the right users, most of the time, not the entire world. 

Research here is crucial. We want to get the most accurate and reliable representation of the users that will use the product. We take a look at the product market to get a better profile of what ideal users could be. 

We work with our clients in creating the personas. Together, we iterate potential personas until we have a good set to work with. This helps us optimize for the right users by using their insights into their business and industry.

Keep your user stories simple

Creating personas is the foundation. With well-developed personas, we can move on to researching and identifying the right problems. To do this, we start with larger problems called epics and then start to break those down using our personas.
When writing epics, it is important to keep them simple while still describing the core of the users’ needs. “You’re not describing a solution you are describing the need of the user”, said Attila Schmidt, our Director of User Experience and Interface. Here’s a look at the hierarchy we use when writing out epics:

Epics should be high-level so we can group similar tasks together to start identifying problems. These epics are then broken down into user stories. User stories focus more in-depth about why a user may have a certain need:

User stories must also be simple enough to allow for developer creativity. If you give too much detail, you are limiting the possible solutions. “We, as designers, may have an idea of how we would like to see a feature, but we would be taking away the possibility of getting a much better method thought out by developers,” Schmidt said. 

Our developers then take these stories and create sub-tasks. They describe specific features that will become the puzzle pieces of the product. This is typically where our developers come up with innovative and optimized solutions!

Never stop learning

The discovery process is more than just identifying the problems – and it doesn’t end when development begins. The process helps drive open and consistent communication between our clients and our team of developers, designers, and QA teams. At BitBakery we make it a priority to keep everyone up to date throughout the duration of the project.

I recently attended a talk about how design teams can leverage other teams to change design culture by Matt Rae. What stood out to me the most is having the entire team involved during the design iteration process. This is key, everyone involved in the tech team can give valuable feedback. Such feedback will not only serve well for the current project but for subsequent ones as well. 

Talks like these really stand out to me. They always push us to improve our tech team environment. Together, with our clients, we can always try to optimize our product development. 

If this sparked as much interest to you as it did for me, I suggest attending community talks. There are amazing UX community initiatives here in the Waterloo Region. Here are some of my regulars: 

UXWaterloo – by Communitech P2P 

UX Book Club

Terminal Talks

Shopify Tech Talks

So, say hello if you see me at one of these. Until next time! 

Keep updated on my journey here at BitBakery.

The end of “you’re not using it right. . . ” and other lessons in UX and design from Fluxible 2019

Have you ever had that experience where you’re looking at buying a new car (or any major purchase really) and you start to see that car everywhere you go? 

Over the weekend, Attila Schmidt, our Director of User Experience, and I attended Fluxible 2019 here in Waterloo. Over the two days of the conference, we couldn’t help but to see the impact user experience has on our daily lives. 

Alex and Attila at Fluxible 2019
Alex and Attila at Fluxible 2019.

Fluxible is celebrating eight years of bringing user experience professionals together to look at the present and future of user interaction design. Fluxible isn’t just a conference – it’s a week long series of brown bag lunch meetups and site tours around Waterloo Region that leads up to two days of speakers from around the world at the Centre for International Governance Innovation (CIGI) building in Waterloo. 

Fluxible attendees inside the beautiful CIGI campus in Uptown Waterloo.
Fluxible attendees inside the beautiful CIGI campus in Uptown Waterloo.

Fluxible is a unique conference. It’s a user experience conference organized and run by user experience practitioners – including conference founders Mark Connolly and Robert Barlow-Busch. While the conference is a paid ticket, they offer free daily brown bag lunch meetups and evening activities during the week to bring more people into the conversations. 

Here’s our top three takeaways from our time at Fluxible 2019 – 

Stop saying “you’re not using it right”. You designed it wrong.

Setting the stage for one of our favourite talks, Fluxible organizers gave the conference’s first content warning before a talk. Based in London, Ontario, emergency physician Tarek Loubani works with the Glia Project who design high-quality, low-cost, open source medical hardware that can be manufactured anywhere.

Loubani talked about the harrowing work he and others do as volunteer emergency physicians in Gaza. Tools we take for granted, such as stethoscopes and tourniquets, are the difference between life and death in areas like Gaza. The Glia Project has produced a $3 version of the world’s best selling $300 stethoscope that can be 3D printed that works just as well (and in some cases better) than the $300 model.

Loubani’s talk focused on design problems with the tourniquet. One of the problems was the packaging. Based on price, a bag was chosen that opened at the bottom instead of at the top by the cardboard product tag. This confused physicians in the field whose cognitive memory of consumer packaging has you always try to open at the top. This added a five-second delay to the time it took to open the package – critical time when trying to treat a patient. We see unintended problems like this often when startups design MVPs using the Lean Startup method.

There was also feedback from the field that tourniquets were breaking – but the response was that they were not being used right. Loubani experience three out of four tourniquets breaking during his last time working in Gaza and was able to get the tourniquets re-designed. The original design had them working at four turns and breaking at five – but in the field under gunfire, physicians and volunteer EMTs were not counting. The re-engineered tourniquets can now support five times the force that is needed to work correctly.

Everything that is going to be invented will need design.

Fifteen years ago, no one specialized in designing interfaces for a five inch piece of glass that your touched with your finger. Ten years ago, interaction designers hadn’t begun to get into the intricacies of designing voice interactions for a cylinder that sits next to your couch. 

Zendesk’s Principal Designer Bill DeRouchey opened his talk with a look at how much technology can change during our careers. For those at their mid-career (~45 year-olds), technologies like the world wide web, mobile phones, and cloud computing hadn’t been invented when they began their careers. Over the last 20 years, these technologies have become commonplace – and user experience design has played a major role in how we use them every day. 

He then went through a laundry list of technologies emerging today; synthetic reality, deep fakes, autonomous vehicles, drones, 3D printing, nanotechnology, and material science to name a few. These are all technologies that will need to be designed – and the user experience professionals at their early-career (~25 year-olds) will be the ones who shape these interactions. 

Bill DeRouchey gave examples of what topics you could use for future tech topic book club.
Bill DeRouchey gave examples of what topics you could use for future tech topic book club.

DeRouchey’s advice: learn one new topic every month. His suggestion is to omit July and December for holidays and focus on ten topics a year. We’re going to start a “tech topic book club” and meet once a month to discuss our own deep dives into a new topic.

There’s no “right question”.

If you’ve ever done a user research session, you’ve most likely spent more time than you’d like to admit coming up with the perfect questions. Meena Kothandaraman, a senior strategist at Boston-based twig+fish, challenged attendees to stop doing that – and instead focus on how we can get people to open up and share all the interesting nuggets, experiences, and insights that are what we really need.

Kothandaraman shared a few great ways that we can provide participants with platforms to help them articulate their thoughts – and create a fun and engaging space for them to do it.

“It’s your job as a researcher to get people comfortable to start talking,” said Kothandaraman, “the right question is ‘share your answer’”.

Meena Kothandaraman presents on stage at Fluxible.
Meena Kothandaraman presents on stage at Fluxible.

One way is by giving the user an empathy map and letting them take the time to complete it. Instead of starting with what you are interested in, let them start from whatever point they feel is important to them. An empathy map can also become a great shared artifact for both you and the user to continue to write on during the interview.

Later in the day, Carolyn MacGregor took the stage to share her favourite research tool – “the fly on the wall”. MacGregor is the Associate Chair Undergraduate Studies, Systems Design Engineering at the University of Waterloo and identifies herself as an introvert. For her, “the fly on the wall” is her way of observing users to get their full, honest experience. Like Kothandaraman, MacGregor wants to give the user the freedom to express their feedback without judgement. 

Being a fly on the wall with Carolyn MacGregor
Being a fly on the wall with Carolyn MacGregor

Fluxible is not a conference where you come out with new tools to apply in daily practice. Instead, the speakers at Fluxible ask you to look at the emerging patterns in user experience design – and what those changes mean to the ethos of user experience.

We’d love to hear what your takeaways from Fluxible were – let us know in the comments.