📎 Webclip
A New Approach to Feature Requests
Basecamp argues that feature requests should not be handled as a pile of tagged emails. For requests that might matter, support interviews customers to learn the situation behind the request and gather details the product team can use.
Reading notes#
- The team starts by asking where a request fits in Basecamp and then sends it down one of three paths: not doing it, maybe doing it later, or not knowing yet.
- Requests that will not be built are answered directly, so customers know whether to look for an integration, a workaround, or another product.
- Tagging requests alone produced raw data, but not enough context for the product team to act on it.
- For requests that might matter, support’s role is to collect information that helps the product team decide whether to build something.
- The example case is the request for a grid calendar in Basecamp 3.
- The support interview follows a Jobs-to-be-Done style, focusing on what happened before the email and what problem the customer was trying to solve.
- Annie needed to book a meeting room for a client session and drove to the office to check the wall calendar.
- The company had lost its secretary for cash flow reasons and replaced the old scheduling process with a painted wall calendar.
- Annie’s problem was not a full calendar app with integrations and recurring events.
- What mattered was seeing open space and how busy the day was.
- Other interviews showed the same pattern: customers wanted to see available space to plan work.
- After repeated interviews, the team wrote a pitch for a new feature, it was picked up for a cycle, and a team of three built it in about seven weeks.
- The process is ongoing, with support trying to schedule interviews the same day a feature request arrives.
