How to Address Client Feedback Effectively

I've seen too many enterprise software companies get caught with customers in the 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗧𝗿𝗮𝗽: • Promise too much = lose focus • Listen too little = lose trust I was super lucky to have two incredibly product-minded co-founders in Ted and Joshua. Of the many things I learned from them, one that has really stuck with me is that while customers understand their pain points better than anyone, they're not best positioned to solve that pain - they're too close to it and just don't have as many data points across variants of that pain, resulting in a failure of imagination as to the optimal solution. Customer feedback is absolute gold, but that doesn't mean every nugget should get directly translated into the product roadmap. The topic came up during the AMA after our Logicbroker All Hands last week - here's what I shared with my team:  1. 𝗟𝗶𝘀𝘁𝗲𝗻 𝗮𝗰𝘁𝗶𝘃𝗲𝗹𝘆 - Make sure the customer is heard and build a 3D model of their pain in your head by probing into the granular details of what they're dealing with 2. 𝗦𝗲𝘁 𝗲𝘅𝗽𝗲𝗰𝘁𝗮𝘁𝗶𝗼𝗻𝘀 𝗲𝗮𝗿𝗹𝘆 - Thank them for the feedback and communicate how this will inform related product research as we work towards an optimal solution 3. 𝗘𝘅𝗶𝘀𝘁𝗶𝗻𝗴 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝗲𝗱𝘂𝗰𝗮𝘁𝗶𝗼𝗻 - Have we already solved this pain point, but in a counterintuitive way? Educate the customer on how other clients are successfully handling this today. Encourage them to try it out and share back additional feedback to round out our understanding 4. 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝘁𝗵𝗲 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 - Advocate for clients by employing methodologies like RICE (Reach x Impact x Confidence / Effort) to map feedback to prospective projects in a structured way that will automatically reprioritize initiatives as incremental data points are collected over time  5. 𝗙𝗼𝗹𝗹𝗼𝘄 𝘂𝗽 𝗰𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝘁𝗹𝘆 - In subsequent client QBRs, share new learnings around initiatives their feedback has matured. Be transparent about where they fall in the company's priorities and update on new related releases that may partially address their original pain point  Valuing customer feedback and protecting the product roadmap are not mutually exclusive. These two goals are inherently intertwined and mutually reinforcing. Building every client request will degrade the product, but ignoring client feedback will also degrade the product - it's a fine balance. Customers don't need a 'yes' - they need to be able to trust that you're listening and leading with purpose.

Had a tough conversation last week. A long-time Pavilion member told me I'd broken his trust.  When you run a community, there are going to be lots of people that love what you do and lots of people that… don’t.  Here’s what I’ve learned about having difficult customer conversations. FIRST, SOME CLARIFICATION He was right. On the substance of the feedback, he was right.  He was also angry. And… sort of nasty. He'd been with us since the early days. Contributed ideas. Showed up. Built relationships. Mentored some of the younger folks who were up and coming.  Then we got bigger. Changed things. Made promises we didn't keep. He felt forgotten. At the same time there was an edge to his comments that felt almost masochistic. So what do you do when someone is sharing useful feedback but doing it in such a way they’re sort of acting like an asshole. Step 1: Don’t debate Not my natural instinct.  I can get quite defensive and want to defend myself. Often, your angry customers are sharing something that is explicitly not true. And they’re unfair. And… It doesn’t matter Because we're not here to score points. We’re here to listen. Step 2: Find the signal Once you know that you’re not in a pissing contest and you can stabilize your fight or flight instinct, you can get to work. What’s being said that’s true? What’s being said that’s useful? You don’t lose anything by simply working hard to find the pieces of feedback that are relevant and accurate. Step 3: Be grateful The hardest feedback to hear is the feedback that's true. Trust takes years to build. Seconds to break. And forever to repair. But here's what I've learned about trust and feedback: The people who care enough to tell you when you've failed them are gold. Most people just leave. They ghost. They talk behind your back. They smile and nod and disappear. The ones who sit across from you and say "You broke my trust"? They are giving you a gift. They're saying: "I still care enough to be angry." They're saying: "I want this to work." They're saying: "Fix this." Every leader breaks trust sometimes. We make decisions that hurt people. We prioritize wrong. We forget our promises. The question isn't whether you'll break trust. The question is what you do when someone tells you. Do you defend? Do you deflect? Do you justify? Or do you shut up and listen? Trust isn't built in the big moments. It's built in the response to failure. In the willingness to hear hard truths. In the commitment to do better. Not just say better. Do better. I’ve made my share of mistakes over the years and the single biggest thing I’m working on is the ability to listen without defensiveness. And to get to work incorporating that feedback on the journey to improvement. Every single day.

Ever walked into a surprise 9-alarm fire with a customer? The kind where you thought you were walking into a normal check-in… and suddenly you realize:  • They’re extremely upset  • They have multiple product issues stacked up  • They’re already halfway out the door It happens for a lot of reasons:  • You’re new to the account and inheriting someone else’s mess  • Portfolios shift and you discover things are way worse than you thought  • Or, even if you’ve stayed on top of it, product issues snowball into a much bigger crisis The question is: What do you do when you’re blindsided by a firestorm like this? The only play I’ve seen work isn’t damage control. It’s resetting the relationship. Here’s how: 𝟭. 𝗚𝗲𝘁 𝗶𝘁 𝗮𝗹𝗹 𝗼𝘂𝘁 𝗼𝗻 𝘁𝗵𝗲 𝘁𝗮𝗯𝗹𝗲. Open a shared doc or slide, write every issue down in front of them. Don’t flinch if it’s 20 items, keep asking “Anything else?” until they’re empty. 𝟮. 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗲 𝘄𝗵𝗮𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 𝗺𝗼𝘀𝘁. Not every issue is critical. Ask which ones actually block their ability to achieve business value. Focus on the 2–3 that will make the biggest impact right now. 𝟯. 𝗦𝗮𝘆 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂’𝗹𝗹 𝗱𝗼. 𝗧𝗵𝗲𝗻 𝗱𝗼 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝘀𝗮𝘆. Outline the next steps, owners, and timing. Follow up the same day to prove the shift has already begun. Always state when your next follow up will be and then meet that due date. Even if your update is that the team is still working on the issue. 𝟰. 𝗦𝗵𝗼𝘄 𝗱𝗶𝘀𝘁𝗶𝗻𝗰𝘁 𝗰𝗵𝗮𝗻𝗴𝗲. The customer must feel a clear difference between the old way of working with you and the new way forward. Consistent delivery builds back trust. When you do this, a customer who came in saying “everything is broken” often walks out realizing there are really just 2–3 solvable issues. And solving those gives you the chance not just to save them for one renewal cycle, but to truly reset the relationship for the long term. Have you ever had to walk into a customer fire like this? What’s worked best for you to turn things around? #customersuccess