loading words...

Apr 30, 2019 16:09:02

Using Canny Internally

by @hum | 543 words | 🐣 | 215💌

Sarah Hum

Current day streak: 0🐣
Total posts: 215💌
Total words: 107318 (429 pages 📄)

If your team has more than 50 people, it's likely that silos of information and knowledge are forming. Marketing and sales aren't in touch with product or vice versa. Even within the product org, product teams don't know what's going on outside their own domains.

When it comes to giving feedback, people feel left out and unheard. Feedback is exchanged in one-on-one conversations in the hall or in Slack. Usually, there's no conclusion or action plan. However, listening to your teammates is just as important as listening to your customers. 

Many teams on Canny use it internally. We did a case study with Bench Accounting that revealed how Canny was able to build a culture around product feedback.

People don't think of Canny as a software tool, they think of it as their voice. It's their primary channel to get eyes on a problem. It's baked into the culture in a way that gives people a voice they didn't have before. That's the biggest impact Canny's had.
– Joshua Berkowitz, Head of Product at Bench

Check out the full Bench case study.

Let's talk about how you can set Canny up for internal feedback. We'll also go over pitching Canny to your teammates.

Set up

Setting Canny up for internal use is easy. Our goal here is to make sure external customers can't see or access the internal board.

All you need to do is adjust your board settings to "Private". Under "Specific emails by domain", you can whitelist your email domains. For us, that would be @canny.io. That way, only people with @canny.io emails can access our board.

Once you have your board(s) set up, you just need to share your Canny link with the team. If they sign in with the email address you've added to the whitelist, they'll be able to see the boards.

Announcing Canny

The main challenge here is to get your teammates onboard with using Canny. It's hard to change people's habits and workflows. The best thing you can do is communicate the benefits of using Canny.

Stop losing track of feedback

Say you have feedback for an area in your team's product. First, you need to find the right person to talk to. Then, you catch them in person or message them on Slack. You're depending on them to internalize the feedback and do something about it. More often than not, they go about their day and your feedback is lost.

This cycle leads to you not giving feedback anymore.

With Canny, all feedback is fair game. Your idea gets written down and preserved for others to see. You add your idea to the Canny board and other teammates can vote on it if they agree. Anyone can chime in to give additional context or thoughts.

All feedback in one place really helps the product team

Build transparency into product decisions

Everyone wants to contribute to the product they work on. As your product org grows, it becomes opaque. People not working in product don't understand why certain decisions are being made.

Canny helps bring everyone into the fold. Everyone can see the status of an idea from ideation to launch.

Increasing transparency helps your whole team feel like a cohesive system instead of individual limbs. 

From Sarah Hum's collection:

contact: email - twitter / Terms / Privacy