Contextual and Automatic Bug Reporting

Automating bug reporting to drive growth.

Author

Bastien Vélitchkine
November 10, 2023 • Temps de lecture : 4 minutes

This post is a reedition. “LinkedIn to Notion” (aka “LtN”), then “recruitivity” is no longer maintained (even though the extension still exists).

We may have found what the most underrated growth lever for recruitivity.

Many would discard it, as unworthy of their time and un-impactful.

But we didn't, and I can't wait to assess the ROI.

In this thread, you’ll enjoy (dare I say):

  1. Workflow overview: from the extension to the Notion database.

  2. The rationale: churn reduction is under-appreciated.

  3. Growth mindset: don’t try to be flamboyant.

1. Workflow overview

In recruitivity

I think we’ve all learned to ignore these buttons.

Still, solving bugs is essential for user retention (therefore, growth).

So we came up with a solution that I hope will drastically improve the bug reporting in recruitivity: context.

The form link shows up in the extension when we know something wrong happened.

In Tally

When users click to report a bug, they end up on a tally.so form.

Tally's perfect bc:

  1. It's free

  2. Forms look great with little effort

  3. They have webhooks to connect with 3rd-party apps

In n8n

On form submission, the data is sent to n8n thanks to a webhook.

For those whose don't know n8n yet:

  1. It’s like Zapier but better.

  2. Fair-code (almost like open-source): you can self-host and automate at microscopic costs

It's pivotal for small teams to decrease time-consuming operations.

In Notion

n8n puts the form data in a Notion database.

Why?

  1. We love Notion lol

  2. The whole project is managed there

  3. The bug ends up in a board to be dealt with at lightning speed.

2. Rationale

Churn

Focusing on churn is unsexy: somehow, we get more excited by new signups.

But, churn reduction still has one of the most sensible impacts on revenue growth.

And, ultimately, the less bugs, the less shame opening the gates of acquisition.

Disclaimer

How do I know that this bug reporting feature will reduce churn? One might object that I talk about stuff I’ve never experienced.

It’s only half true: I’ve experienced the impediments of churn (50% of users uninstalled the app). But yeah, it’s more a hunch than a science-backed fact—I’ll admit.

A-tier reporting

We strive for "A-tier bug reporting" by:

  • Asking questions specific to user actions in our product

  • Relying as little as possible on open-ended questions

In short: better questions ⇒ better answers.

(this has really been transformational in my life btw)

Growth mindset: avoid stupidity

Thinking of growth, we often wonder about "hacks". We're trying to be flamboyant.

A better strategy (even if it’s unexciting) would be to avoid stupidity and fix obvious issues and leaks. It's true for many other things in life too.

I'll let you sleep on that.

Reply

or to participate.