Conversation
The Methodology page says we gather evidence through continuous interviews, often with sales, but nothing described how to run them. The new page covers the weekly cadence, the two formats (the end of a sales call, or a dedicated call), which calls sales should flag, the interview itself, and what happens after it. Following Torres, engineers interview alongside product, and we rotate who joins. To keep sales calls about the customer, only one person from product or engineering joins a sales call, and at most two join a dedicated call.
✅ Deploy Preview for flowfuse-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
Preview affected pages: |
dimitrieh
commented
Sep 29, 2026
Co-authored-by: Dimitrie Hoekstra <hi@dimitr.ie>
Fix the hypotheses typo and give the "interview together" sentence a subject. The dedicated call now allows up to three of us in both places it is described, and the team learns from the recording now that the snapshot step is gone. Add two reasons from the one-pager: interviews keep our picture of customers current, and one story can show that several feature requests share one need.
…views A one-row summary under the intro gives cadence, length, what we collect and the two formats at a glance. A table under "Two ways an interview happens" compares the formats side by side (length, who is there, how it starts, sales' part, our part), so the per-format sections drop their duplicated length and attendee lines.
dimitrieh
commented
Sep 29, 2026
Per review, the rep and whoever joins from product or engineering plan ahead of the call how to run it and when to hand over, rather than the rep only leaving time at the end.
Keep the defined weekly slot but leave how it gets filled to the team, instead of prescribing self-booking, recruiting channels and a booking link. The mix of people to talk to becomes something to aim for over time.
Contributor
Author
|
@ZJvandeWeg @allthedoll @MichaelBDavis please give a brief review here as this describes the why, how, what on continuous interviewing, ensuring we learn from customers and inform our product and eng decisions. |
dimitrieh
commented
Sep 30, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a Continuous Discovery Interviews page to the product handbook, linked from Methodology and the product index. Methodology says we gather evidence through continuous interviews, often with sales, but nothing described how to run them. Engineers interview alongside product, and to keep sales calls about the customer, one person from product or engineering joins a sales call and at most two join a dedicated call.
Related Issue(s)
None.
Checklist