loading words...

Jun 03, 2019 17:46:36

Canny Best Practices: User Research & Design

by @hum | 837 words | 🐣 | 215πŸ’Œ

Sarah Hum

Current day streak: 0🐣
Total posts: 215πŸ’Œ
Total words: 107318 (429 pages πŸ“„)

This series is on Canny best practices for your role. In this post, we highlight a few ways that Canny can be used for UX research and design.

Also check out best practices for other roles:

Canny for Product Management
Canny for Customer Success

As people working in UX, our job is to create the best user experience for our customers. This involves putting in the work ahead of time to understand what that means. There are many ways that your team can do research to reveal insightsβ€”both before and after the design process.

Conducting user interviews, creating surveys, and running beta tests are just a few popular methods. With those, you can find answers to many questions:

How will this feature make their lives easier?
How do they want the feature to work?
Is the UI intuitive?

With Canny, you have another group of people who are willing to share their opinions. Everyone in Canny has expressed interest by leaving votes on requests. These are people who have experienced the problem they think will be solved by a particular request. Having this information at your fingertips is very handy for preliminary research through to the final prototype. Here's how you can best put data in Canny to use.


Before prioritization

Prioritizing the roadmap is largely the responsibility of the product manager. However, insight from the UX team can help make prioritization a lot easier.

Once your team has had Canny running for a while, you'll have a clear list of requests ranked by popularity. This is your opportunity to look into select requests that need more clarity or refinement.

Each Canny post will have a list of voters who are also interested in the request. Someone leaving a simple vote in Canny is high signal that they will have more to say. These are people your can reach out to for additional thoughts.

You can easily leave a comment on the Canny post itself with your questions. As admins in Canny, your comment will be sent out to all voters for maximum engagement. This is very low-effort while being highly targeted.

Alternatively, since all feedback is tied to an actual person, you can reach out privately. Hopping on a call is a great option to dig deep into the problem they're looking to solve.

Tip: If you talk to customers outside Canny, use internal comments to add your learnings to the post afterwards. It's helpful for product management to have everything in context to the original post.


During execution

Great, your team has made some decisions and there's a roadmap of projects to be completed. This time is where you can get into the nitty gritty of the feature itself. 

Oftentimes, you'll have several options of designs for the feature. How do you decide which one to build? With Canny, you can easily post a few options and allow your customers to chime in with feedback. We recommend including the mocks as they communicate the product a lot better. If you don't have mocks, make your questions really specific.

While the final decision is always up to your team, your customers may provide insights that you haven't thought about. Your customers will also feel great about being involved in the process. 

If your team wants to run a beta test for the feature, people who voted on the post in Canny are prime targets. They will be highly engaged and excited to see your team building a feature that will solve their problem. Just leave a comment letting them know that the feature is ready to test and that you're looking for beta testers.

Doing this work before official release helps make sure that your release will be a success.


After release

Just because your team has released the feature, doesn't mean the feedback stops! It's crucial that your team prioritizes the right features because they do require maintenance afterwards. This could be in the form of improvements as well as bugs.

At Canny, we err towards shipping MVFs (minimum viable features). What elements are a must-have in order for the feature to deliver its intended value? We figured this out before we started building.

Now that we real customers using our MVF, we can see if we should add more to the feature. Customers can create new Canny posts with new ideas on how to make the feature even better.

TIP: If your team decides to run a beta test, you can optionally create a separate Canny board for it. Make it private so only your beta testers have access. It's a great way to continue iterating on a feature before officially releasing it.


Cover all your bases

As the UX team, paying attention to feedback before a feature is prioritized, during execution, and after launch is extremely helpful. With feedback, you can ensure that you're considering everyone's point of view. The more aligned you are with your customers' expectations, the more successful your feature launches will be. Canny can help in each of those stages.

From Sarah Hum's collection:

contact: email - twitter / Terms / Privacy