Research + validate code insights for core dev workflow features

[Joelkw]

Problem to solve

In line with our strategy update to focus on the core workflow, we need to validate the usefulness of potential core workflow contributions.

We need to do this research because we don't want to ship "best guess" contributions as that will only contribute to the existing noise in that workflow.

Measure of success

We have a strong conviction roadmap of ways and places insights features are useful to the core dev workflow.

Solution summary

We are actively doing customer research with IC devs.

Artifacts:

• Research plan
• Running research interview notes
• Productboard section for synthesis

What specific customers are we iterating on the problem and solution with?

• https://github.com/sourcegraph/accounts/issues/578
• https://github.com/sourcegraph/accounts/issues/3439
• https://github.com/sourcegraph/accounts/issues/542

[malomarrec]

Hey @Joelkw, this issue didn't have a team label. Given you created it, I assigned you and added your team label. Feel free to unassign yourself. If this is not the right label, can you make sure to add the right one?

[sourcegraph-bot-2]

Heads up @joelkw @felixfbecker @vovakulikov @unclejustin - the "team/code-insights" label was applied to this issue.