Using Feedback Loops to Improve Processes

The Paradox of Growth: The Bigger You Get, the Less You Know I came across something that stuck with me: When companies scale, they gain users — but lose understanding. Not because they stop caring, but because their customer feedback starts living everywhere — support tickets, sales calls, forums, surveys, social media, and app store reviews. That thought really made me pause. I’ve seen this firsthand. When a company is small, every piece of feedback feels personal — every bug report or review has a face behind it. But as you grow, those voices scatter across platforms and departments. Support sees the frustration, sales hears the hesitation, leadership sees the numbers — and somehow, everyone’s looking at the same customers, but no one’s hearing them anymore. That, in my opinion, is the quiet cost of growth. This is the problem Enterpret is solving — by helping teams stay in tune with their customers even as they scale. Here’s how it works: → It collects real-time customer feedback from 55+ channels — support tickets, sales calls, social media (X, Reddit, Instagram, Facebook), app store reviews, community forums, surveys, Slack, and more. → It analyzes all that feedback using AI and tells you exactly what to fix or build next. → It maps everything through a customer knowledge graph that connects feedback, complaints, and requests by channel, user, and payment data. → It even provides a chat interface where you can directly ask questions, and AI agents that flag bugs or issues automatically. That’s why teams like Notion, Perplexity, Canva, Chipotle, and The Farmer’s Dog use it — to make sure customer voices never get lost in the noise. In my view, the real lesson here isn’t about using more tools — it’s about staying close to the people you build for. Here’s how I’d approach it: ✅ Centralize every piece of feedback — even if it’s messy. ✅ Look for patterns instead of isolated complaints. ✅ Use AI systems like Enterpret to uncover the “why” behind what customers say. Because in the end, growth shouldn’t make you deaf. It should make you listen better — just faster. How does your team make sure you’re hearing what customers really mean, not just what they say? #CustomerFeedback #AIProducts #ProductStrategy #VoiceOfCustomer #Enterpret #Leadership

How I Track 10+ Projects at Once as a Program Manager at Amazon It’s a question I get a lot: How do you stay on top of everything without letting something slip? Different teams. Different timelines. Different deliverables. And a lot of noise. Here’s how I keep it all moving…and still make it home for dinner: 1/ I use one central tracking system for everything ↳ One doc, one view. ↳ If it’s not in the tracker, it doesn’t exist. ↳ I update it daily and keep it brutally simple. 2/ I start every week with a 15-minute self check-in ↳ What’s behind? What’s on track? What’s at risk? ↳ If I don’t do this Monday morning, the week runs me instead of the other way around. 3/ I color-code by priority and risk ↳ Green means I don’t need to touch it. ↳ Yellow means it needs a check-in. ↳ Red means I need to escalate or unblock. 4/ I follow up with context, not just reminders ↳ “Just checking in” turns into “We need this by Friday to keep X on track.” ↳ People respond to clarity, not pressure. 5/ I keep a running weekly update for leadership ↳ 3 bullets: what moved, what’s stuck, and what I need help with. ↳ It keeps everyone informed without another meeting. Managing 10+ projects isn’t about multitasking. It’s about systems, focus, and momentum. You don’t need to know everything. You just need to know where to look…and what to move next. How do you track your priorities without getting overwhelmed?

Stuck in an endless loop of client changes? Lost track of what revision this constitutes? Yeah. Been there. Done that. The secret? It's not about saying no. It's about saying yes to the right things upfront. Every project that goes sideways starts the same way: Vague agreements. Fuzzy boundaries. Good intentions. Six weeks later you're bleeding money and everyone's frustrated. Here's my framework after 30 years of running two 8-figure businesses: The SOW is your salvation. Not some boilerplate template. A real document that covers: • Exact deliverables (not "design work" but "3 homepage concepts, 2 rounds of revisions") • Hours of operation ("We respond M-F, 9-5 PST. Weekend requests get Monday responses") • Revision rounds spelled out ("Round 1 includes up to 5 changes. Round 2 includes 3.") • Feedback cycles defined ("48-hour turnaround for client feedback or the project may be delayed or additional fees may be incurred") But here's what most people miss— Don't work on client notes immediately. Client sends 37 pieces of feedback at 11pm Friday? Producer sends conflicting notes from the CEO? Marketing wants one thing, sales wants another? Stop. Collect everything first. Resolve the conflicts. Get on the phone and discuss it with your client to get alignment. Separate the "have to haves" from the "nice to haves". Then present unified changes. "Based on all feedback received, here are the 8 changes we'll implement. This constitutes revision round 2 of 3." Watch how fast the random requests stop. No extra work that goes unappreciated. No more feelings of being taken advantage of. Communicate before the crisis, prevents the crisis from happening. "Just so you know, we're entering round 2. You have one more included. After that, it's $X per additional round." No surprises. No awkward money conversations. No resentment. Scope creep isn't a them problem. It's a you problem. And that's good news, because that means you are in control. They're not trying to take advantage. They just don't know where the boundaries are because you never drew them. Draw the lines early. Communicate them clearly. Everyone wins. What's your most painful scope creep story? What boundary would've prevented it? Small Business Builders #projectmanagement #clientmanagement #businessgrowth

HR doesn’t need more dashboards. It needs better listening. Most people teams measure what’s easy…like engagement scores or turnover. But the best teams? They build feedback loops that help them predict problems, not just react to them. This post gives you 11 of the most useful, often-overlooked loops you can implement across the employee lifecycle: 🟢 Week 2 new hire check-ins (capture early impressions) 🟠 Post-interview surveys (from both sides) 🔵 Onboarding reviews (day 90 is your goldmine) 🟡 Skip-level 1:1s (cross-level truth-telling) 🟣 Quarterly team health check-ins (lightweight, manager-led) …and 7 more. 📌 Save this if: • You’re building a modern HR function • You want fewer “We should’ve seen this coming” moments • You believe listening is strategy Which feedback loop is missing in your company?

Accountability is one of the most important—and often overlooked—skills in leadership. It’s not about micromanaging or policing your team. It’s about setting people up for success. How? 🤷♀️ Through the three C's of clear expectations, challenging conversations and consistent follow-through. While we all want to believe people will naturally follow through on what they commit to, that doesn’t always happen. And when it doesn’t, too many leaders let it slide. But brushing these moments under the carpet doesn’t help anyone, all it does is erode accountability over time. So, what DO you do?? 1️⃣ Be crystal clear about expectations. Ambiguity is the enemy of accountability. If people don’t know exactly what’s expected of them, how can they deliver? Take the time to clarify actions and responsibilities WITH them, not for them. 2️⃣ Document commitments in 1:1 check-ins. Writing the actions down is REALLY important. It ensures nothing gets lost and sets a reference point for everyone involved. 3️⃣ Explain the 'why.' People are much more likely to follow through if they understand why their actions matter. How does their work contribute to the bigger picture? What’s at stake if it’s not done effectively and efficiently? 4️⃣ Anticipate and address barriers. Ask if there are any obstacles standing in the way of getting the job done. When you help remove these barriers, you’re building trust and giving people every chance to succeed. 5️⃣ Follow up at the agreed time. Don’t leave it to chance—check in when you said you would. Ideally, your team members will update you before you even have to ask. But if they don’t, don’t skip the scheduled follow-up. 6️⃣ Acknowledge effort or address gaps. If the action was completed, recognize the effort. If it wasn’t, outline the expectations for the role and provide specific feedback on what needs to improve. Be transparent about the implications of not meeting role requirements over time, ensuring the person understands both the consequences and the support available to help them succeed. (A lot of people need help to develop the skills to have this conversation!!) 7️⃣ Plan the next steps. Whether the task was completed or not, always end by agreeing on the next steps and setting clear timelines. If you need a lean/leadership coach to work on these areas and help increase accountability right across your organization, then get in touch! It's one of my specialties... 😉 _____________________________________________________ I'm Catherine- a Lean Business and Leadership Coach. I take a practical hands-on approach to helping teams and individuals achieve better results with less stress. Follow me for insights on lean, leadership and more.

At Radical Candor, I often hear the question, "How do I know if my feedback is landing?" The answer is simple but not always easy: Radical Candor is measured not at your mouth, but at the listener’s ear. It’s not about what you said, it’s about how the other person heard it and whether it led to meaningful dialogue and growth. Before you start giving feedback, remember the Radical Candor order of operations: get feedback before you give it. The best way to understand how another person thinks is to ask them directly and reward their candor. Next, give praise that is specific and sincere. This helps remind you what you appreciate about your colleagues, so when you do offer criticism, you can do it in the spirit of being helpful to someone you care about. When giving feedback, start in a neutral place. Don't begin at the outer edge of Challenge Directly, as this might come across as Obnoxious Aggression. Just make sure you're above the line on Care Personally and clear about what you're saying. Pay attention to how the other person responds - are they receptive, defensive, sad, or angry? Their reaction will guide your next steps. If someone becomes sad or angry, this is your cue to move up on the Care Personally dimension. Don't back off your challenge - that leads to Ruinous Empathy. Instead, acknowledge the emotion you're noticing: 'It seems like I've upset you.' Remember that emotions are natural and inevitable at work. Sometimes just giving voice to them helps both people cope better. If someone isn't hearing your feedback or brushing it off, you'll need to move further out on Challenge Directly. This can feel uncomfortable, but remember - clear is kind. You might say, 'I want to make sure I'm being as clear as possible' or 'I don't feel like I'm being clear.' Use 'I' statements and come prepared with specific examples. Most importantly, don't get discouraged if feedback conversations sometimes go sideways. We tend to remember the one time feedback went wrong and forget the nine times it helped someone improve and strengthened our relationship. Focus on optimizing for those nine successes rather than avoiding the one potential difficult conversation. Creating a culture of feedback takes time and practice. Each conversation is an opportunity to get better at both giving and receiving feedback. When you get it right, feedback becomes a powerful tool for building stronger relationships and achieving better results together. What’s one small adjustment you’ve made to give or receive better feedback? I’d love to hear your thoughts!

The key to progress on hard, complex projects comes down to latency and bandwidth — the interfaces through which teams communicate. 1 / Latency is the delay. How long it takes for information to travel, decisions to be made, or problems to surface. High latency slows everything down — people wait, guess, or lose momentum. Strong leaders reduce latency by creating environments where: Feedback moves quickly. Problems are flagged early and acted on decisively. Communication loops are short, direct, and clear. 2 / Bandwidth is the capacity. How much information can flow between people. Low bandwidth leads to confusion, blind spots, and misalignment. Strong leaders increase bandwidth by ensuring: Teams share the right context at the right time. Communication is open, transparent, and efficient. People trust each other enough to exchange ideas freely. When latency is low and bandwidth is high, progress accelerates. Teams collaborate seamlessly. Small signals get noticed before they become big problems. Decision-making improves. Great leaders don’t just manage — they optimize the interfaces of communication within the team. They create systems where ideas flow, feedback happens in real time, and no one is stuck waiting for clarity. Because in the end, the speed and quality of progress aren’t just about individual talent — they’re about how well the team interacts. Thoughts??? If you’re building hard things and want signal over hype, subscribe to Per Aspera. 👉🏻 Join here: https://lnkd.in/gacTgUkh

Every company says they listen to customers. But most just hear them. There's a difference. After spending years building feedback loops, here's what I've learned: Feedback isn't about collecting data. It's about creating change. Most companies fail at feedback because: - They send random surveys - They collect scattered feedback - They store insights in silos - They never close the loop The result? Frustrated customers. Missed opportunities. Lost revenue. Here's how to build real feedback loops: 1. Gather feedback intelligently - NPS isn't enough - CSAT tells half the story - One channel never works Instead: - Run targeted post-interaction surveys - Conduct deep-dive customer interviews - Analyze product usage patterns - Monitor support conversations - Build customer advisory boards - Track social mentions 2. Create a single source of truth - Consolidate feedback from everywhere - Tag and categorize insights - Track trends over time - Make it accessible to everyone 3. Turn feedback into action - Prioritize based on impact - Align with business goals - Create clear ownership - Set implementation timelines But here's the most important part: Close the loop. When customers give feedback: - Acknowledge it immediately - Update them on progress - Show them implemented changes - Demonstrate their impact The biggest mistakes I see: Feedback Overload: - Collecting too much data - No clear action plan - Analysis paralysis Biased Collection: - Listening to the loudest voices - Ignoring silent majority - Over-indexing on complaints Slow Response: - Taking months to act - No progress updates - Lost customer trust Remember: Good feedback loops aren't about tools. They're about trust. Every piece of feedback is a customer saying: "I care enough to help you improve." Don't waste that trust. The best companies don't just collect feedback. They turn it into visible change. They show customers their voice matters. They build trust through action. Start small: 1. Pick one feedback channel 2. Create a clear process 3. Act quickly on insights 4. Show results 5. Scale what works Your customers are talking. Are you really listening? More importantly, are you acting? What's your approach to customer feedback? How do you close the loop? ------------------ ▶️ Want to see more content like this and also connect with other CS & SaaS enthusiasts? You should join Tidbits. We do short round-ups a few times a week to help you learn what it takes to be a top-notch customer success professional. Join 1999+ community members! 💥 [link in the comments section]

Innovation is the lifeblood of progress, but it doesn’t happen by chance. It’s cultivated in environments where team members feel safe to share ideas and challenge the status quo. Creating a culture of innovation means nurturing an environment where bold ideas can flourish. It’s about openness, diverse perspectives, and the freedom to experiment. When people feel empowered to speak up, creativity thrives, and true innovation follows. So, how do you create such a culture? 1️⃣ Embed a Growth Mindset: Encourage continuous learning and development across all levels of the organization. Provide resources for professional growth and celebrate learning milestones, fostering an environment where knowledge and skills are constantly evolving. 2️⃣ Facilitate Cross-Functional Collaboration: Break down silos and encourage teams from different departments to work together. Cross-functional projects can bring fresh perspectives and spur innovative solutions that wouldn’t emerge in isolation. 3️⃣ Implement Structured Feedback Mechanisms: Establish regular feedback processes focused on constructive criticism and actionable insights. Ensure psychological safety so team members feel secure, viewing feedback as an opportunity for growth rather than critique. 4️⃣ Encourage Calculated Risks: Promote a culture where calculated risks are welcomed. Empower your team to explore new ideas and approaches without fear of failure. Recognize and reward innovative efforts, even when they don’t result in immediate success. By embedding these principles into your organizational culture, you can pave the way for continuous growth and success. Let’s create spaces where innovation is not just an aspiration but a tangible reality. #Leadership #Innovation #FutureOfWork

At the top of the "are doomed to repeat it" category is the notion of "spec-driven development" (SDD). Though some claim that SDD is all about very tiny specs that encompass only a tiny amount of work, the vast majority of comments I see on the topic are hyping old-school waterfall big-up-front design as if that's a new, innovative idea. It's pushed by the most irresponsible of the vibe-coding crowd, who imagine that, if only the prompt were more detailed, they'd get better results. They won't. We stopped working from big up-front specs decades ago for a reason—the approach fails in every context but the most boring ones: either the same program written over and over again, or something that effectively implements a mathematical formula of some sort. In that last case, a spec-driven approach will probably yield a UX so bad that it makes the formula implementation irrelevant. People don't know what they need until they get something into their hands and try to use it. Any way of working that doesn't acknowledge that truth will fail. I suppose, if the only thing you've ever experienced is chaos, SDD seems like an improvement, but believe me, it's not. In my experience, incremental feedback-driven approaches always yield better outcomes. Collaboratively develop a strategic goal. Collect enough information to start. Start. Get feedback as you work. Adjust. Works like a charm.