● Customer Success · Play 03 · v1.1
The Feedback Cycle
When a customer tells you something about the software, the service or the support, make it actionable and answer with options: a short-term option now, a long-term solution with an honest status, and a recommendation. The manual, and the log that closes the loop.
Why it matters
A customer who tells you what is wrong is still a customer; the one who stops telling you is leaving. Feedback Cycles uncover business problems that our solutions are not addressing. Customer Success makes each piece of feedback actionable and answers it with options: a short-term option the customer can use now, a long-term solution with an honest status (shipped, planned, or not planned), and a recommendation. It holds the cycle open until the customer agrees, and until anything promised for later has shipped and been told back. On the Operating Model’s grid it is tactical and reactive. On the Customer Journey it is moment 22, touching milestone 08.
What’s inside
Defined. What a Feedback Cycle is and is not, where it sits on the grid and on the journey, and the one sentence it comes down to.
When to run one. Four ways in: a survey answers, a request, “not what we expected,” something said in passing. When to run a different play instead.
Open: the Structured Call. Prepare, set the stage, past and present, future and recap, and why silence is consent.
Run: evaluate, analyze, synthesize. The root issue, the impact in the customer’s terms, and the answer in two halves with a recommendation.
The answer: shipped, planned, not planned. How to say each one, and telling them no as the most success-oriented response.
The clock: 1-3-7, and agreement. The same day, three days, seven days. The exit is the customer’s agreement in writing, and a planned item stays open until it is told back.
Surveys: detractor, passive, promoter. A script for each band of the zero-to-ten question.
Who does what, the round trip to Product, and is it working. Success responsible; Support and Product accountable; Services consulted. The play at the dedicated, shared and digital tiers. A monthly triage with Product and a quarterly “you asked, we listened.” Four measures and the checklist.
How to use it
Read the manual once. When feedback arrives, acknowledge it the same day and give it a row on the log. Hold a structured call, consolidate the problem, and deliver the options within three business days. Record the customer’s agreement and its date. Walk the Themes tab with Product every month, tell back what shipped every quarter, and read the four measures on the Book tab.
Provenance
Run as the Feedback Loop in 2017 and 2018 as Senior Director of Customer Success at a hospitality-software company in the Vista Equity portfolio. Success guided product feedback to Product’s roadmap, and survey responses flagged detractors and neutrals for follow-up automatically. It was named the Feedback Cycle on the customer journey of a managed file transfer and network management software company in 2018, and written into the partnership framework of a financial services software company in 2020. Rebuilt here as a Juan.co play: the four ways in, the Structured Call, and the short-term option and long-term solution. The detractor and passive scripts, the shipped, planned and not-planned answers, and the monthly round trip to Product are written out.