It’s one of the hardest things to do… to actually listen to what someone is saying.

Recently, I interviewed Colin Nederkoorn from Customer.io in front of an audience of technical business owners.

With notecards full of questions, I had to resist the urge to simply go from question to question. Instead, I listened to Colin’s response and tried to make a conversation about it.

Asking a question and not listening to the response is an easy mistake to make.

In fact, I made that mistake at Zapier…

On every page of documentation, we asked for feedback via a form.

And, for longer than I’d like to admit, we didn’t look at it.

🤦‍♂️

My latest post, Ways to Get Docs Feedback From Developers, explores several ways your team can learn from your technical audience.

But it only works if you listen!

Our solution at Zapier was simple (and very Zapier): we created an automation to push every piece of feedback into a shared Slack channel.

And guess what? That feedback could give you great content ideas, too.

For help sorting through it, reach out to the EveryDeveloper team.