"Stop building for us and start building for our staff." That was the feedback. It came from the managing partner of a large disability firm about six months after we launched Chronicle. At the time, we focused on dashboards for executives. We wanted to show owners how many cases they had and where bottlenecks were happening. But this partner told me the real problem wasn't visibility. It was the sheer volume of mail. His staff spent hours every day sorting through letters from the Social Security Administration. They were drowning in paper. He told me if I could fix the mail problem, the dashboards wouldn't matter. So we pivoted. We built a virtual mailroom feature that automatically sorts and processes ERE notices. We shifted our focus from executive reporting to operational efficiency for the intake staff. That single conversation changed our entire roadmap. We stopped trying to impress the bosses and started trying to save the paralegals time. It worked. Now, firms use us because their staff demands it, not just because the owners want data. It taught me to solve the headache, not just report on it.
The most valuable feedback I ever received didn't come in a survey or a review — it came at the end of a long night, while we were breaking down the bar. It was a private event, everything went smoothly, guests were happy, drinks were flowing. I honestly thought we had nailed it. As the host was walking me out, she stopped, looked at me, and said: "Your bartenders were amazing... really amazing... but... but what really mattered is that I never had to think about the bar once." That line stuck with me. She went on to explain that with other services she'd used before, she was constantly checking on things — lines getting too long, bartenders disappearing, guests asking questions, small fires popping up. That night, she said, she actually enjoyed her own event. She felt present. Relaxed. Like a guest in her own party. That was a turning point for me. Up until then, we focused heavily on drinks, speed, setup, and pricing. All important things. But her feedback made something click: people aren't hiring bartenders just for cocktails — they're hiring peace of mind. From that moment on, we changed how we built our service. We stopped staffing events with "available" bartenders and only used experienced, senior people who could read a room and solve problems without being asked. We adjusted training to focus more on anticipation, communication, and ownership — not just recipes. We improved our prep systems so nothing felt reactive on-site. And we started selling our service differently, talking less about what's included and more about how the client will feel during their event. That one comment shaped everything. Even today, when we onboard new team members, I repeat that sentence: "The client shouldn't have to think about the bar." If they walk away feeling calm, taken care of, and able to enjoy their own event — then we did our job right.
The best feedback we ever got was contradictory. A customer told us they loved the experience and then never used it again. That silence hit harder than any survey score. We stopped treating feedback as what people say and started watching what they do. When engagement dropped right after onboarding, it wasn't confusion. It was friction we'd missed. So we stripped out the extra steps, made the next actions obvious, and rebuilt the product around real behavior instead of polite approval. Since then, we've learned the same rule applies everywhere. Words are reassurance. Actions are data. The most valuable feedback usually hides in that quiet gap between enthusiasm and usage.
The best feedback I've received was a client saying they felt busy, but not profitable. That forced us to stop reporting on activity and start reporting on outcomes. It completely changed how we run our company. At the time, we were sending long reports full of tasks, charts, and marketing jargon. Impressive? Maybe. Useful? Not really. That feedback pushed us to rebuild our service around ROI first tracked leads, signed cases, and revenue impact and cut everything else. It also shaped our month-to-month contracts and transparency-first approach. If we're not producing results, clients shouldn't feel trapped. Period. Ironically, once we stopped trying to "look smart" and focused on being accountable, retention skyrocketed and referrals followed.
Executive Coach (PCC) + Board Director (IBDC.D) | Award-Winning International Author at Capistran Leadership
Answered a month ago
The most valuable feedback I ever received wasn't a compliment—it was a moment of precise truth. A long-standing client once said to me, "You don't just help me think. You help me say the thing I'm avoiding—and then act on it." They paused and added, "That's not coaching as most people experience it. That's what makes this indispensable." At the time, I thought I was simply doing my job well. But that feedback clarified something important: the real value wasn't the insight alone—it was the combination of discernment, timing, and the courage to name what others wouldn't. That comment reshaped how I structured my services. I stopped positioning my work around generic outcomes like development or growth. Instead, I designed my offerings around moments that matter most—inflection points where leaders need clarity, not consensus. I tightened the process. I set clearer expectations. I named the standard explicitly: this is a space for truth, responsibility, and forward motion. It also changed how I screened clients. Not everyone wants that level of candor, and that's okay. But those who do experience results faster and with greater confidence. That single piece of feedback reminded me that the strongest products aren't built by adding more. They're built by honoring what's already working and having the discipline to lead with it.
The best feedback I ever got was from a client who said my onboarding was "overwhelming" and she did not feel clear about where we were going. She liked the information I gave her—questionnaires, welcome PDFs, and our full agenda. But after our first meeting, she did not know how any of it would help her business step by step. That comment really made me think. Coaching should be about helping people take real action, not just talk. If someone feels lost at the start, it will be hard for the two of us to get good results together later on. I listened to that feedback and changed my onboarding process to be clear and quick. Now, instead of a long form, I send out a short quiz with three questions. This quiz helps find out what matters most to the client in less than five minutes. The answers then create a personal "Kick-Start Guide." This guide gives a 30-day plan, shows important steps, and lists all the tools the client will use, like worksheets, videos, and tracking tools. In our first session, we read through this guide together. We also come up with a way to measure how things are going and set up short meeting times for the first two weeks. Because the onboarding is made easy and all about clear goals, clients feel good about making progress from the start. This has led to higher satisfaction in my coaching practice, and more people keep working with me.
For me, the most valuable piece of feedback I've ever received from a client wasn't about pricing or negotiation, it was about communication. Early on in building Jack Ma Real Estate Group, a seller told me, very honestly, that while they trusted my expertise, the moments of uncertainty during the process were the most stressful part for them. They didn't want just updates when something happened; they wanted to understand why things were happening and what to expect next. In my opinion, that feedback completely reframed how I viewed my role as a real estate professional. I realized clients aren't just hiring me to open doors or write contracts, they're trusting me to guide them through one of the biggest financial and emotional decisions of their lives. Even when everything is going smoothly, silence can feel like a risk to a client. As a result, I made communication a core part of our service model. I built clearer timelines, set expectations upfront, and made proactive updates the norm, even if there was "nothing new" to report. I also started breaking down complex steps, like inspections or appraisal issues, in plain language so clients felt informed rather than overwhelmed. That feedback also led me to leverage better systems for follow-ups, reminders, and post-transaction check-ins, which strengthened long-term relationships. What surprised me most was how this shift impacted the business overall. Clients became more confident decision-makers, transactions felt smoother, and referrals increased because people felt genuinely taken care of. That feedback reinforced an important lesson: expertise matters, but trust is built through clarity and consistency. Shaping our service around that insight helped elevate not just the client experience but also the reputation of my brand as a whole.
One of the most valuable pieces of feedback I received was from a senior client who said: "My English isn't the problem. It's what happens to my thinking when I have to speak." That single sentence changed everything. Up until then, many English programmes, including parts of my own, focused heavily on vocabulary, grammar, and correctness. Useful, yes. But incomplete. Her feedback made it clear that the real issue was cognitive pressure. Speaking under time constraints. Being observed. Needing to sound credible while processing ideas in a second language. As a result, I reshaped my offering in three key ways. First, I shifted from language improvement to performance coaching in English. We now train how to think, structure, and prioritise ideas before focusing on phrasing. Second, I built in pressure simulations. Live presentations, interruptions, challenging questions, and decision making in real time, because confidence only grows when the nervous system is trained, not just the language. Third, I reframed success. Not sounding perfect, but sounding clear, authoritative, and human. That feedback helped me move away from teaching English as a subject and towards using English as a leadership tool. And it is the reason my clients do not just speak better English. They show up differently when it matters most.
Among the most significant comments we received was from a customer who expressed, "The website is fantastic, but I am not sure what is going on or what work you are doing behind the scenes after the launch." It was a straightforward reply, and it caused us a little discomfort, but at the same time, it was a realization that even though we carried out a lot of productive activities (like SEO tweaks, speed changes, A/B tests), their gain was not visible to us and our clients. So, we came up with a clearer service model consisting of "care plans" that are tiered, accompanied by monthly check-ins and short, visual reports showing what changed and how it affected our clients. Clients felt empowered, were more willing to continue with the retainer agreement and even our internal processes became more concentrated due to this.
The most valuable feedback we ever received came right at the beginning of the pandemic from a U.S.-based client we'd been working with through our software outsourcing business. They told us something simple but powerful: they wanted to hire two developers from our team full-time because of how well they'd worked together, but they assumed hiring European engineers directly wasn't realistic for them. At the time, that comment wasn't a complaint, it was an honest constraint from their side. That feedback became a turning point. It highlighted a gap between what clients wanted and what the market made difficult. We realized the real value wasn't just in delivering projects, but in enabling long-term, direct relationships between companies and engineers across borders. That insight pushed us to pivot from a pure outsourcing model to a tech staffing company, which is what Uptalen is today. We redesigned our service around compliant international hiring, long-term team integration, and continuity for both clients and engineers. The result was better retention, stronger partnerships, and a model that scaled much better during and after the pandemic. The lesson was clear: the best product ideas don't come from brainstorming sessions, they come from listening closely when customers explain their constraints.
In 2014, two of our largest customers came to me within a week of each other with essentially the same question. They both had purchased what, at the time, was our largest product: an "all you can eat" (unlimited) job posting package for $12,500 per year. Coincidentally, they both asked if we could deliver four times as many early career candidates to them if they paid us four times as much money. Given that they were already getting to advertise as many jobs as they wanted, we couldn't offer them more job posting ads. Instead, we needed to somehow deliver more candidates to them from the job postings they were already running. We could drive more volume, but that would mean diverting candidates from other customers or spending more money to source more candidates, with some or even all of those going to these two employers. We ruled out diverting customers from one customer to another. Was there a way to source more candidates, but in a way that would increase our profitability? We realized that we could create a win-win-win for the employer, candidate, and College Recruiter job search site if we charged the employers on a performance- instead of duration-basis. We'd charge every time one of "our" candidates clicked to the employer's site or applied. One employer preferred to pay for the click, the other for the application. They both signed for $60,000 instead of $12,500 per year. We delivered more candidates, the employers hired more people, and we made more money.
Sometimes, the most valuable feedback comes totally unexpected. This is what happened to me, at Tall Trees Talent, recently: we'd just wrapped up what I thought was a textbook-perfect search. We'd filled the role quickly, the candidate looked great on paper, and the hiring manager was happy with the technical fit. I didn't expect any negativity, but then, the client mentioned that I might have oversold the role. At first, I was a little taken aback. But I soon understood what they meant: we'd brought in too many candidates whose expectations didn't match the reality of the work. In energy, especially on the tech and engineering side, a lot of roles involve legacy systems, regulatory complexity, and slow-moving infrastructure. The work is meaningful, but it isn't always glamorous, and we hadn't reflected that enough in our postings. That feedback has really stuck with me. Sugarcoating a role is never my aim. So, I am taking more time now to highlight not only the upside of any role, but also, the constraints and challenges therein. It should make our placements stick longer, reduce early-stage attrition, and help us build teams that are actually excited about the work they're walking into, not just the idea of it.
Feedback from a customer gave Spendbase a new perspective - we would not just be seen as a cost optimisation tool, but rather provide people with confidence in making financial decisions. A customer told us: "I don't want another dashboard; I want to have fewer things to worry about." We were very surprised to hear this comment. This has shifted the way we think of our product and our role in it. We no longer just think about surfacing data for our customers or savings opportunities. Instead, we have focused more on automation and clarity. We started to prioritise features that identify risks, recommend next steps and take away manual work (SaaS renewals, discounts, etc.). And this is what we now are using to develop our product. Customer feedback has influenced the way we work with customers. We have started to see ourselves as partners for our customers; instead of just being a "reporting body" for the customers, we relieved them of the necessity to constantly deal with often-so-overwhelming details. That feedback reinforced a simple principle we follow today: the best products don't just provide information - they take work off your plate. When we work with that mindset, both the product and the customer experience improve.
One of the most valuable pieces of feedback we received early on was from a founder who said, "I don't want another HR tool or advisor. I want this to just stop being a problem." That was clarifying. We had been thinking about features and workflows, but what they were really asking for was relief from coordination, follow-ups, and the mental load of wondering whether something had slipped. That feedback pushed us to design DianaHR less like a traditional HR product and more like an operating layer. Instead of optimizing for dashboards or documentation, we optimized for ownership and outcomes: someone is responsible, it gets done, and the founder doesn't have to chase it. It shaped everything from how we scope work to how we communicate, because the value wasn't in "more HR," it was in making HR quietly reliable in the background.
I had a client tell me I needed to get my s4!t together before I took on another project. The wild thing was, I was making a ton of exceptions for this client, doing fully custom work and altered my pricing to assist with their budget constraints. I wasn't embarrassed by the work product I put out - but I did need to evaluate that client's alignment with my business. While it was painful at the time, it stopped me from taking on clients in the future that didn't have clear expectations on what I would and would not provide in what timeline for what money.
While working with a large enterprise customer evaluating our product for scale and reliability, we ran into a scenario that challenged some of our existing assumptions. The product was performing well for most enterprise workloads, but this customer had a unique pattern, scaling resources while simultaneously reading large volumes of data, which exposed limitations in our current architecture. Through collaborative brainstorming, we recognized that this wasn't just a one-off edge case. Customer workloads were evolving, and our architecture needed to evolve with them. The resulting architectural changes not only unblocked this customer but also strengthened the platform for future large-scale enterprise deployments.
I was the CUO for an insurtech company selling insurance policies to gig economy workers. We would regularly invite customers to come and meet team members and share their experience of the product - what worked well, what didn't work well and so on. One customer, an uber driver, shared that the telematics part of the policy was good, but there was not much transparency around the premium discount that we gave. They gave the example that the app said they would get a discount of 10% on the renewal premium, but when the renewal was offered, the premium actually went up due to price rises and changes in his risk. We asked what the customer would do differently. The feedback given was to allow customer to take the reward as a cashback on a monthly basis or whenever they wanted to. We implemented these changes.
I remember a customer once said to me, "I picked you because your trees felt like they were grown with love, not just a mass produced and box shipped plant." This has always stuck with me. It was a reminder that a consumer isn't just purchasing a plant, they are entrusting us with a portion of their property or their home. Ever since, I've tried to be even more intentional in my packaging and to give every order that personal touch I value so much, like handwritten planting instructions or ensuring the roots have been wrapped to the proper amount. It's that kind of feedback that alters the way I train my employees and reach out to consumers—it's about making them feel like an individual.
One comment from a parent has completely altered our views of education. The parent stated, "Your platform is fantastic, however my child is still feeling they are being rushed through classes they enjoy and being stuck in classes that frustrate them." This was a really simple and plain response, but it deeply resonated with us. We knew then that we weren't just creating a curriculum; we were creating an entire learning experience that would take into account and celebrate the individual pace and passion of each student for their learning. Based on that feedback, we decided that we had to completely airbrush our approach. Instead of creating a definitive, strict, "one size fits all" learning path for students, we wanted to utilize adaptive, student-centered learning pathways. We stopped measuring student success based on the time spent at a desk and/or working on assignments, but began to develop a system for assessing student growth based on their confidence and curiosity as primary characteristics of growth. The result of this change was huge. Students who had been completely disengaged have started to become excited about learning again. Parents reported less crying over homework and more discussions around the family table about what their kids wanted to study next. Additionally, from the perspective of our organization, that feedback changed our product mentality from "providing content" to "building pathways with our students." That feedback reminded us that tech in education isn't just about automation, it's also about amplification. It should amplify each student's voice, not silence it.
The most important feedback I have received from a customer was surprisingly direct, stating "I don't want more capabilities, I want fewer choices". At this time, we were very proud of our product's capabilities to be flexible and powerful; however, this statement made it clear that we were creating unintentional friction for customers and the customer did not have capability issues, but cognitive overload issues instead. This feedback changed the way that we develop products. It led us to streamline our workflows, create more intelligent defaults, and eliminate unnecessary choices in the interface. Because of this feedback, customers experienced quicker onboarding, greater usage of the product, and increased customer satisfaction. This experience showed me that a great product is not defined by the capabilities that it provides, but by how simply and easily it provides customers the ability to perform the things that are most important to them.