Backstaff, the full simulation.
A Texan planning tool vendor for maintenance teams, whose client feedback piles up without anyone reading all of it. The case followed on this page, a request for an offline mode, repeatedly raised by technicians working in basements without network coverage.
A Texan planning tool vendor for maintenance teams, whose client feedback piles up without anyone reading all of it.
Every piece of client feedback is linked to the relevant feature.
- Based in Austin, Backstaff develops a tool that schedules the work of maintenance teams in factories and warehouses across the United States. Technicians receive their jobs on their phone, and managers track progress from a dashboard. The company has forty people.
- Client feedback arrives from everywhere, from support tickets to sales notes, via app store reviews and satisfaction survey responses. No one reads all of it.
- The product lead builds her roadmap around requests from the biggest clients, whose voices are heard most, while other clients' requests get lost.
- An agent reads every piece of feedback as soon as it arrives and files it under the feature it concerns, separating bugs from enhancement requests. It links each piece of feedback to the client’s account and keeps the client’s exact sentence alongside its categorisation.
- Every Monday, the product lead receives a per-feature summary, with client quotes and the week’s new feedback. She can trace each line back to the original feedback.
What remains with the product team
The product lead alone decides the roadmap and priorities. The agent works internally and replies to no client.
- Feedback classified within the week
- Feedback escalated through to a product decision
- Time between a bug report and ticket creation
- Clients informed of an enhancement they had asked for
Bug reports with reproduction steps
Every bug reported by a client becomes a complete ticket, detailing the app version, phone model, reproduction steps, and client screenshots.
Developers set the priority for each ticket.
Closing the loop with clients
When a requested feature is released, the agent prepares a message for each client who asked for it, including a link to the release notes.
The account manager reviews the message and sends it themselves.
User interviews
For each upcoming feature, the agent invites clients who mentioned it and organises the interviews. It then produces a summary, supported by direct quotes.
Designers lead each interview, and nothing is recorded without client consent.
Account reviews
Before each renewal, the agent prepares an account review covering tool usage and client feedback over the past year.
The account manager leads the review and decides on any commercial discounts.
a request for an offline mode, repeatedly raised by technicians working in basements without network coverage
A recurring request, before and after.
- The feedback
- A technician writes in an app store review that the app does not work in the basement.
- The agent reads the review the same day and files it under offline mode as a feature request.
- First workstream
- Other feedback
- The same request sits in tickets, sales notes and surveys, without anyone making the connection.
- The agent connects all these pieces of feedback to the same feature and keeps each customer's exact phrasing.
- First workstream
- The weight of the request
- The product lead only hears from the two largest customers, who are asking for something else.
- The Monday summary shows the accounts raising the request, along with their quotes.
- First workstream
- The decision
- The decision is made on intuition, in a meeting.
- The product lead decides on evidence, tracing each line back to the original feedback.
- First workstream
- Bugs
- Bugs reported by customers reach developers without the steps to reproduce them.
- Each bug becomes a complete ticket, ready to reproduce.
- Workstream 2
- The release
- Customers who had requested offline mode find out by chance.
- Each customer receives a message from their account manager, with a link to the release notes.
- Workstream 3
- Collect
- It receives feedback from tickets, sales notes, reviews and satisfaction surveys.
- Read
- It reads each piece of feedback in full and preserves the customer's exact wording.
- File
- It files each piece of feedback under the relevant feature, according to the product map maintained by the team.
- The product lead keeps the feature map up to date.
- Distinguish
- It separates bugs from feature requests.
- Link
- It links each piece of feedback to the customer account and their tenure.
- Summarise
- Every Monday, it prepares a summary by feature, with quotes and new feedback.
- The product lead decides on priorities.
- Trace
- Each line in the summary links back to the original feedback.
- Flag urgent items
- Feedback describing a blocking outage is immediately forwarded to support.
- Support takes over with the customer.
- Ticketing tool
- Requests received by support.
- Read only
- CRM
- Customer accounts and sales notes.
- Read only
- App stores
- Reviews published on the mobile app.
- Read only
- Satisfaction surveys
- Open-ended responses from customers.
- Read only
- Feedback table
- The database where each piece of feedback is filed and linked.
- Read and write
- Product lead
- Decides on the roadmap and keeps the feature map up to date.
- Account managers
- Maintain the relationship with each account and send messages to customers.
- Support
- Takes over urgent feedback and responds to customers.
- Developers
- Prioritise bugs and fix them.
- FDE
- Leads the engagement and writes the agent rules with the team. Accountable for each agent.
- Reading agent
- Reads and files each piece of feedback.
- Summary agent
- Prepares the Monday summary.
- Ticket agent
- Turns bugs into tickets ready to reproduce.
- Review agent
- Checks a sample of classifications each week and flags errors to the FDE.
- Feedback is misclassified.
- The customer's exact phrasing remains next to the classification, and a sample is verified each week.
- Large accounts overshadow others.
- The summary shows each request alongside all accounts raising it, including smaller ones.
- The agent decides on behalf of the product team.
- It sets no priorities. The product lead decides the roadmap alone.
- A customer receives an automated reply.
- The agent operates internally and never responds to customers.
- Customer data leaks.
- The agent reads feedback without the ability to export it. Every access is logged, and data remains where contracts specify.
- We measure the baseline over the last quarter, such as feedback received, feedback read, items leading to a decision, and the time between a reported bug and its ticket. The product lead drafts the feature map with us.
- The agent files feedback from the past quarter, and the product lead checks a sample.
- Feedback flows in continuously, and the first Monday summary is delivered.
- We compare against the baseline and select the next workstream with leadership.
- Feedback classified within the week
- Share of feedback filed under a feature within seven days of receipt.
- Feedback traced to a product decision
- Share of roadmap decisions that link back to customer feedback.
- Time between reported bug and ticket
- Gap between customer feedback and the creation of a complete ticket.
- Customers informed of a requested feature
- Share of customers notified within the week following the release of a feature they requested.