Internal tools
Requests from colleagues still deserve a decision.
Helpful BoB is built for B2B SaaS teams answering customer requests. The same approach fits requests for internal tools: collect what colleagues asked for, group the ones describing the same problem, and weigh it up before someone builds it.
Easy to build is not the same as worth building, and every internal tool needs someone who fixes it later.
- 01
Collect the requests
Add what a colleague asked for, in their words, with the team they are in. Connect a Slack channel if that is where requests arrive.
- 02
See the repeated problem
Similar requests group into one theme, so two teams do not get two tools for the same problem.
- 03
Weigh it before building
Read the reasons for and against, then decide what to build, what to leave and who owns it afterwards.
Example
A dashboard request from the warehouse team.
Read how it works, or use the free feature request template.
- Customer request
- “A live dashboard on the warehouse screen showing today's outstanding orders.” Raised by a warehouse supervisor.
- What the feedback shows
- Three requests describe the same problem: the team refreshes a spreadsheet through the day and disagrees about which copy is current.
- What the team could do
- Consider a read-only view that refreshes on a schedule, name who fixes it when a refresh fails, and check which figure counts as outstanding before building.
Start with one internal request.
Add it with the team it came from and see what else it connects to.