Suggest edit — disagreeing-productively

Title

Name

Note

---
visibility: public-edit
---

# disagree and commit: being forceful in idea exchange

this was one of the hardest lessons from working at a startup. i came in soft — deferring to anyone i thought was smarter than me, which was basically everyone. by the end, i understood that productive disagreement is a skill, not a character trait.

## the feedback loop

the feedback kept coming from multiple directions:

- a cofounder: "push back more. when people say things, push back more."
- another cofounder: "many times it feels that you are arguing to be right instead of for the benefit of pursuing the idea."
- my own reflection: "push back more. too soft with people i think are better than me."

these seem contradictory — push back more, but also stop arguing to win? the resolution is that there are two different failure modes:

1. **not pushing back at all** — accepting everything because the other person has more experience
2. **pushing back for ego** — arguing to prove you're smart rather than to improve the idea

i was doing both at different times, often in the same conversation.

## the filter coefficient

the best framing came from a cofounder's concept of a "filter coefficient":

- for people with a lot of experience, the coefficient should be *higher* (more skepticism), not lower
- they have a much higher chance of being tunneled in their own perspective
- definitely don't make it 0 for anyone — that means you're a pushover
- the test: "do you understand it well enough to explain it back to your sibling? if not, ask questions."

this was counterintuitive. i thought experienced people should be trusted more. but the filter coefficient idea says the opposite: the more someone knows, the more likely they are to have blind spots in their expertise. they need your naive questions more, not less.

## what good disagreement looks like

### think before speaking

"when saying things, think about them more. many times you say something and it's logically beat by someone. you could have gotten to that same conclusion yourself."

this stung because it was true. i was throwing out half-baked ideas and getting shot down, then feeling defeated. the fix wasn't to stop sharing ideas — it was to stress-test them internally first. know your own weaknesses and loopholes in thinking.

### disagree about the idea, not the person

i noticed inconsistencies everywhere at the startup. one person said the org cared about intern growth; another dismissed that as altruism. one said a former colleague was a mistake; another missed them. these contradictions were everywhere.

the skill wasn't calling people out on contradictions. it was using the contradictions to form better questions: "i've heard different perspectives on X. what's your take and why?"

### the "giving negative feedback is really good" principle

from writing up improvement notes for the org, i learned that you can be brutally honest if you frame it right. i literally wrote: "disclaimer — suggestions, not personal at all. for growth." and then gave pointed feedback to each founder about their blind spots.

the fact that they received it well taught me something: people at the top often have fewer people willing to be honest with them. your willingness to disagree is itself valuable.

### decrease the latency

"decrease the latency on the honesty. just say stuff more often." don't wait for the perfect moment or the right framing. the thing you're sitting on for days could have been said in a sentence yesterday.

## the org-level pattern

emotions matter a lot in how disagreements land. "org is run by humans; emotions matter a lot." you can be right about everything and still damage the relationship if the delivery is wrong.

but also: "gripe night" (a dedicated time for grievances) was tried and found to be risky. structured disagreement has its place, but it can backfire when grievances get personal.

the best pattern i found was walks. informal, low-stakes, one-on-one. the disagreement flows naturally when you're walking side by side instead of sitting across a table.

---

*see also: [[asking good questions|asking-good-questions]], [[pattern recognition|pattern-recognition]], [[social strategy|social-strategy]]*