SOLUTIONS / YOUR NEXT PRODUCT DECISIONTurn product feedback
Turn product feedback
into a roadmap.
Listen closely. Choose deliberately.
Feature requests can point in different directions. Find the problem behind each suggestion, compare it with your product’s purpose, and explain what you will explore, build, or leave for later.
Can you send SMS reminders? Clients miss appointments.
Understand the missed appointmentCan I change the booking-page colors?
Preference or blocked task?THE FOUNDER’S QUESTION
What is getting in the user’s way?
A requested feature is a proposed solution. Start with the task.
Different feedback needs different next steps.
A bug, a confusing screen, a missing capability, and a visual preference do not ask the same question. Clarify the kind of problem before you decide how to respond.
Broken
Something that should work fails. Reproduce the issue and check who is affected.
“The confirmation never arrived.”
Confusing
The capability exists, but the next action is hard to find. Watch where the person gets stuck.
“Where do I change my hours?”
Missing
The current product cannot complete the task. Ask about the workaround and desired outcome.
“I need another person to manage bookings.”
Preference
A change may improve fit or presentation. Check whether it affects a necessary task.
“Could this match my brand?”
Three requests. Different decisions.
SessionPatch serves independent consultants booking one-to-one calls. That audience gives the founder a starting point. These sample decisions depend on the evidence available; they are not a universal feature ranking.
Team workspace
Could my team share one workspace?
Evidence and uncertainty
An agency needs to coordinate several calendars. That is outside the current solo-consultant workflow.
DecisionDefer
Next step
Record the need. Revisit if team scheduling becomes part of the product’s focus.
SMS reminders
Can you send SMS reminders? Clients miss appointments.
Evidence and uncertainty
Missed appointments matter to the intended audience. The cause is still unclear: timing, delivery, or the information in the reminder?
DecisionInvestigate
Next step
Ask about the most recent missed appointment and the current reminder workflow before choosing SMS.
Custom colors
Can I change the booking-page colors?
Evidence and uncertainty
The booking task still works. Check whether appearance affects client trust or is mainly a preference.
DecisionLower priority
Next step
Keep the request visible without promising a date.
Compare audience fit, impact, recurrence, and effort. A score cannot replace context.
Write down what would change your mind.
A confident decision can still be provisional. Record what you know, what you are assuming, and the next observation that would change the priority. Repeated requests from the same account are different from the same problem across independent customers.
Reminder decision brief
- Audience
- Independent consultants
- Task
- Get clients to the booked appointment
- Known
- A user reports missed appointments
- Unknown
- What caused the most recent miss?
- Next check
- Review the reminder and ask what the client saw
Evidence
before
effort.
Show the direction. Share the reason.
On Buildside, product feedback sits alongside your product’s roadmap. Keep requests separate from your decisions, update the status as work changes, and use a public update to explain the outcome.
Product feedback
Exploring
Reminder delivery
Understand missed appointments
Planned
Clearer reminder settings
Make the current options easier to find
Building
Email preview
Show the message before sending
Shipped
Appointment summary
Keep booking details together
Decision note
We’re keeping SessionPatch focused on solo consultants. Team workspaces are outside this release. We’re investigating missed appointments before deciding whether SMS is the right answer.
Acknowledge the need. Explain the scope. Leave room for new evidence.Take the decision out of your head.
Use the decision worksheet to compare the problem, audience, evidence, and effort. Then use the public-note template to explain what you decided, why, and what you will review next.
Includes a public decision-note template · editable text
When the feedback pulls in different directions.
Which feature requests should I prioritize?
Start with the intended audience and the task that is blocked. Compare impact, recurrence, confidence, and effort. Ask for more context when the problem is unclear.
What if early users want different things?
Check whether they serve the same audience and describe the same underlying need. Explain the product’s current focus before choosing a compromise.
How do I explain a request I will not build?
Acknowledge the problem, state the decision and reason, and avoid an unsupported delivery promise. Say what new evidence would make you reconsider.
Do votes decide the roadmap?
Votes show interest. They do not explain the task, urgency, or fit on their own. Use them alongside the conversation and your product’s direction.
A thoughtful no. A clearer next step.
Keep the conversation open, even when every request cannot become a feature.
Review your product feedback