Listen for patterns in feedback, not every opinion

Not every piece of feedback deserves action. Look for specific examples and meaningful patterns, then test a response without handing over your judgement.

Lead & Operate
Founder judgment

By the EWOR Team2 min read

A colleague says your decisions arrive too late. A mentor wants more deliberation. An investor wants speed. Combining those comments into “I need to be a better leader” produces little guidance. The useful question is whose observations bear on which decision, and whether a recurring pattern warrants a change.

Ask people who can see the work

Review feedback regularly, looking for patterns without trying to please everyone. Start with a behaviour you can examine rather than a broad judgment about who you are.

Choose a specific behaviour to examine and contributors who have relevant firsthand experience. A colleague involved in recent project handovers can describe what happened there; an occasional adviser may offer a useful perspective but have less evidence about those handovers. Prestige is not a substitute for proximity to the work.

Ask for a recent example, the consequence and what would have made the situation clearer. “Which decision left you unsure what to do next?” is more actionable than “Am I decisive?” Explain how you intend to use the feedback and respect any agreed confidentiality.

Look for a pattern, not a vote

Compare the situations behind the comments. Several people independently describing unclear ownership across different projects is more informative than several people repeating the same story. Recurrence is a reason to investigate, not automatic proof that a proposed remedy is right.

Keep observations separate from interpretations. “We left the meeting without a named owner” describes something you can examine. “You do not trust the team” is an interpretation that may or may not explain it. Ask what evidence connects the two.

A credible, consequential report may need prompt follow-up even if it occurs once. Repetition helps you spot routine patterns; seriousness can justify acting before a pattern emerges.

Test a specific response to the feedback

In a hypothetical example, multiple colleagues identify recent meetings where decisions lacked an owner. You might try ending relevant meetings with a short written decision, a named owner and an agreed next step. Then ask whether that specific ambiguity decreased. That tests a response to the observed ambiguity without accepting every interpretation of your leadership.

Record why you acted on some feedback and left other suggestions aside. Revisit the choice during your next reflection, especially if new examples contradict your interpretation.

Use other people’s observations to see effects you missed. You still have to weigh their advice against the evidence and your goals, explain the choice and revise it when new examples warrant it.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter