The warning arrived before the complaint
A support team flags a problem before a release. The release happens anyway. Customers call about exactly the issue the team raised. After enough repetitions, employees stop bringing it up. The company may interpret the quieter meeting as agreement, even though it has actually lost an early warning system.
Erika Till describes this pattern in her ChatGTM conversation with Michael Beck and Chad Horn. Her experience spans the customer-facing work of restaurant technology, including onboarding, implementation, support and customer success. She founded Riselight Co. to help organizations address the gaps between the people doing that work and the leaders making decisions about it.
Her argument gives employee experience a very practical place in the growth discussion. The people answering questions, resolving exceptions and explaining delays know where the promise is breaking down. When their observations cannot travel back into decisions, the same issue can become both a retention problem and a reason good employees disengage.
Find out what keeps pulling the founder back in
Till starts with diagnosis. Why are customers leaving? Why does the founder keep getting pulled into conversations that supposedly have an established process? Why is the team scrambling? These questions lead to two connected areas: the operating foundation and the way people communicate.
The foundation includes documented workflows, clear responsibilities and training. A process stored entirely in one person's memory may work while that person is available. It becomes fragile as volume grows, people take time off or another team needs to act. Introducing another tool does little if nobody understands how to use it or who owns the next step.
Before commissioning a broad culture initiative, trace one recurring escalation. Write down what the customer expected, what each team knew, where the handoff happened and who could resolve the issue. That small investigation can reveal a missing decision, an unclear responsibility or a promise made without the information needed to keep it. Those are concrete things a team can change.
Let sales and delivery compare their realities
Till sees recurring friction between sales and the teams responsible for onboarding and retention. Sales works under expectations, timelines and incentives. Delivery teams inherit commitments and must make them work for a real customer. If neither side understands the other's pressures, an ordinary handoff can become a running argument about who caused the problem.
She recommends getting those teams into conversation about what happens after the sale. Which questions should be answered earlier? What does implementation need to know? Where does an exception require an explicit decision? The goal is enough shared context to change the process, rather than another meeting that simply gives everyone time to defend their department.
Executive promises deserve the same scrutiny. Till describes the strain created when a feature is promised before the internal team considers it ready. Her recommendation is to involve the people responsible for delivery and explain the business reason behind the request. For a leader applying that advice, the conversation also needs an honest account of capacity, testing and tradeoffs. Understanding the reason cannot manufacture time that does not exist.
Close the loop after you ask
Listening loses credibility when nothing observable follows it. Till distinguishes between employees accepting a decision they disagree with and employees repeatedly seeing their evidence ignored. The latter teaches people that speaking up costs effort without affecting the outcome.
She recommends summarizing what the organization heard, protecting individuals' identities where appropriate, and explaining how leadership will respond. That response can include a decision to take a different direction. What matters is that people can see their input was understood and can follow the reasoning behind the next step.
A useful follow-up has an owner and a date. Explain which concern will be addressed, what needs more investigation and when the team will hear back. If a suggestion will not be pursued, explain why. Asking people to be candid creates an obligation to return to the conversation; another survey does not discharge it.
Make honesty easier to deliver
Till is realistic about who should conduct these conversations. When trust is badly damaged, putting employees in a room with the executive they fear may produce polite answers instead of useful information. A trusted intermediary can create a better route for feedback, especially if leadership acknowledges why that distance is needed.
For everyday conversations, she favors attentive listening and questions that invite explanation. Asking someone to help you understand a decision gives the discussion a different opening from immediately arguing with it. Put away the distractions, ask a follow-up and leave enough room for the answer.
The business value is straightforward. A team that can explain what is going wrong gives a growing company more chances to fix it while the customer relationship is still recoverable. The next useful piece of discovery may come from the person who has already handled the same support call five times.
