builders vs naysayers: ten dimensions

after publishing my current philosophy, i had some delightful conversations and specific feedback on “boosting builders, not nagging naysayers” line.

"are you on the path to sycophancy?"
"what does it mean to be a builder or a naysayer?"
"is it static or changeable?"
"are people builders in some areas but not in others?"

loved the conversations. here’s a more detailed look into ten dimensions of builders vs. naysayers.

want to use the tool by itself? open it on its own page →

the sycophancy trap

if naysayer only means “critical,” the inverse is “agreeable.” this leads to sycophancy trap.

this is the failure mode i’m most worried about. squashing any thought that isn’t “yes i agree with you.”

i want people to tell me i’m full of shit, they disagree because X, Y, or Z, and here’s what i missed.

why? that’s where we learn, create shared context, and figure out how to move forward. we engage.

skin in the game

both builders and naysayers can be critical. what separates them is whether their criticism comes with the willingness to own the alternative.

adam grant sharpens this on his podcast in the creative power of misfits: disgruntled creatives are people who have a better way and can’t find an avenue. so agency has two halves:

• would they own it? (the person)
• do they have a path? (the org)

a naysayer in one org is a builder in another.

what this is NOT

phrases like “boosting builders, not nagging naysayers” can mean anything to anyone. the meaning is bastardized & people apply it in whatever way is convenient at the time. vibe thinking. ugh.

this does not mean:

• not “ignore critical feedback”
• not “label dissenters as problem children”
• not “stop pressure-testing strategy”
• not “boost the people who agree with you”
• not “sort your team into builders and naysayers”

what this IS: framework for understanding where to spend the limited time and energy i’ve got in the places where it’ll have an impact. builders, not naysayers.

behaviors, not labels

people aren’t builders or naysayers. people show builder or naysayer behaviors on different dimensions.

someone can be a builder on one dimension (quitting: able to kill projects with discipline) and a naysayer on another (feedback: sees it as attack). each dimension can be developed independently. each dimension can shift over time.

two implications:

• don’t label people. label behaviors and dimensions. “they’re a naysayer” is wrong. “on the question of process, they’re currently in a naysayer pattern” is useful. the first calcifies a point in time. the second invites movement.
• investment is per-dimension, not per-person. you meet someone where they’re already a builder. you grow them along the dimensions where they’re stuck. the frame becomes a developmental map, not a sorting hat.

this is not a filtering mechanism for good vs bad. it’s for noticing where movement is possible. on yourself, your team, your collaborators. a static point-in-time snapshot for now, and this can change.

and even with this said, there will be people who misuse it. :shrug: maybe point them to this section and tell them to fuck off, idk. good luck with that.

the map

jump to any dimension:

1. updating priors
2. quitting
3. impact vs busyness
4. feedback + candor
5. own your own learning
6. operating frame
7. engaging with new
8. reasoning
9. self-awareness + reflection
10. pain

1. updating priors

continuous improvement. “this no longer serves me, i’ll update going forward.”

• naysayer: can’t update priors. uses past as proof, not data. weaponizes hindsight (“i told you so”). defends status quo by treating the system’s past prior as proof against the present (“we tried that in 2022”).
• builder: updates without ceremony. treats own past positions as drafts. hindsight = data for next time. status quo is a hypothesis like any other, open to revision when conditions change.
• the shift: ego separation from position. “who was right” → “what changes now.” the past you doesn’t owe loyalty to current you.

2. quitting

ability to kill or quit a project when it no longer makes sense.

• naysayer (type 1): refuses to quit anything. sunk cost runs the show. “i’m not a quitter” as virtue.
• naysayer (type 2): quits the people, defends the dead thesis. inverse failure. looks like decisiveness, is actually thesis-loyalty in disguise.
• builder: quits early when signal is clear. stopping is clarity, not betrayal. identity is not the project.
• the shift: separate identity from project. replace “am i a quitter” with “what does the next dollar of my attention deserve.” build quit conditions before you’re emotionally invested.

annie duke in quit: quitting on a thesis isn’t betrayal. it’s clarity about what deserves the next dollar of attention.

society mythologizes never quitting. no good!

3. impact vs busyness

deep understanding of the why and what matters to stakeholders / business. not enamored with busy work just for sake of working busily.

• naysayer: optimizes for being seen working. ships features for features sake, no connection to thesis on why this is worth doing. uses activity in promotion rationale. “i got this cert. i did this program. i led this working group.” doesn’t follow with what it unlocked or what impact came from this achievement.
• builder: optimizes for what changed for someone. will sit still when sitting still is right. when asked to do busy-for-busy-sake work, doesn’t move forward and explicitly names it. has framework for what would make it impactful, and offers the path, not just the no.
• the shift: “i was busy” → “what changed because of me.” and “i’ll just do it” → “i can’t do this in good conscience because [reason]. to make it matter, it would need to [path]. want to do that instead?”

the builder isn’t the person who refuses. the builder is the person who refuses with the better question already drafted.

4. feedback + candor

how you treat critical information flowing in both directions. includes initiating the discomfort of the hard conversation. and engaging with difference. perspectives unlike yours are a form of input you can receive as data or as attack.

• naysayer (withhold): sees the issue, says nothing in the room, vents in DMs after.
• naysayer (criticize for sake): sees criticism as the end goal, not as a path forward.
• naysayer (receives as attack): any feedback collapses into ego defense. trains everyone to stop telling them anything.
• builder: gives critical feedback because they care. receives feedback as data. initiates hard conversations. extracts signal from poorly-delivered feedback. engages with perspectives unlike their own as input, not threat.
• the shift: “i don’t want to make it weird” → “the weirdness now is cheaper than the rot later.” on receiving: “why are they coming at me” → “what’s the data here, separate from how it was delivered.”

5. own your own learning

owns the gap between where you are and where you need to be. owns the not-knowing. owns outcomes including parts that weren’t your decision.

• naysayer: outsources learning. “nobody trained me. there’s no documentation.” hides not-knowing. bluffs in meetings, spends more energy concealing the gap than closing it. abdicates outcomes. “that was X’s call.”
• builder: doesn’t wait to be taught. owns their own learning. fitfo. owns the not-knowing explicitly. “i don’t know this yet, here’s how i’m going to find out, back by friday.” owns outcomes including the parts that weren’t their decision.
• the shift: “why didn’t anyone tell me” → “what’s my path to knowing this by [date].” and “that wasn’t my decision” → “i had a chance to flag it and i didn’t, here’s what i’d do next time.”

ownership and blame are different. you can own the outcome without it being your fault.

6. operating frame

operates from a framework that’s yours. use process when it helps. route around it when it doesn’t. comfortable when the map runs out. ambiguity is the test condition for the why-muscle.

• naysayer: latches onto capital-P Process. follows the checklist blindly. vibe thinking. substitutes the artifact for the outcome. demands the map. won’t move until ambiguity is removed by someone above them.
• builder: can articulate why this thing matters, why this approach, why now. uses process when it serves the why. routes around it when it doesn’t, and explains why. drives toward clarity instead of demanding the map first.
• the shift: “that’s not how we do it” → “why do we do it that way, and does the why still hold here?” and “i need more clarity before i can start” → “here’s what i can start on now, here’s what i’ll come back with by when.”

cross-link: this dimension pairs with dimension 3. process compliance without the why IS busyness. process as activity-as-proof. and pairs with dimension 5. ownership of not-knowing + internal why-muscle = FITFO. figure-it-the-fuck-out.

7. engaging with new

what you do when something unfamiliar shows up. a new idea, a new approach, a new domain. lean in or lean back.

• naysayer (challenges nothing): defends the status quo reflexively. “we tried that in 2022.” dismisses the new by pattern-matching it to something old.
• naysayer (refuses action): bias to objection. analysis as deflection. endless meetings, more research needed, can’t proceed without [moving target].
• naysayer (failure-spotting only): generates 14 reasons it won’t work, no associated path forward, no suggested experiment. the sophistication is the disguise. it reads as rigor, it functions as veto.
• builder: challenges status quo including their own. bias to trying. runs the small experiment. spots failure modes paired with a path forward to build to learn. “this might fail on X. if we fix X, does the rest hold? want to spike it?”
• the shift: “this won’t work because [X, Y, Z]” → “this might work if we solved [X, Y, Z]. smallest version we can try this week?” failure-spotting reframed as a gift to the design, not an end in itself.

this is the most easily-confused-with-builder naysayer pattern. devil’s advocate, stress-testing, playing it safe. all sound like rigor. the diagnostic is paired with a path forward to build to learn. without a path, it’s veto cosplaying rigor.

8. reasoning

make your thinking visible. build in public, not in performance sense, in show-your-work sense. externalize the logic so it can be examined at the thinking layer, not the person layer.

• naysayer: positions arrive without legible steps. “trust me.” / “i just have a bad feeling about this.” nothing to audit later. past decisions become folklore. when challenged, treats it as personal attack. the logic and the person are fused.
• builder: writes it down. says it out loud. distinguishes what i observed from what i inferred from what i’m recommending. each layer separable. welcomes pushback because the layers are visible. past reasoning becomes the audit trail.
• the shift: “i think X” → “here’s what i’m seeing, here’s how i’m reading it, here’s what i’d do, where am i wrong.”

this dimension keeps the main focus on the main focus. when thinking is implicit, conversations devolve into “are you attacking me.” when thinking is explicit, conversations stay on “is this reasoning sound.”

connects to no vibe thinking. vibe thinking is the implicit version. reasoning is what’s left when vibe thinking has been ejected.

9. self-awareness + reflection

notice your own patterns. behavior happens by you, not to you.

• naysayer: pattern-blind to self. “i just react that way.” / “that’s just how i am.” same shape recurs across years and they don’t see it. when the pattern is named for them, defends it as personality rather than examining it.
• builder: notices their own recurring shapes. “i do this thing where i go quiet when i feel cornered. i’m doing it right now.” treats own behavior as observable data, same as anyone else’s. asks the second question. “why did that land like that for me. what’s actually going on.”
• the shift: “i’m just being honest / that’s just how i am” → “i notice i do this. what’s the pattern? where does it come from? what does it cost me? what would i want to do differently?”

“that’s just how i am” is a sentence that prevents change. the same trait, named as a pattern instead of an identity, becomes movable.

this dimension is the unlock for every other dimension. you can’t update what you can’t see. you can’t notice when your reasoning skipped a step if you can’t catch yourself doing it. it’s also what makes the self-rating tool below actually work. rating yourself honestly is, secretly, exercising this dimension.

movement here is uniquely hard because the deficit is invisible from inside. the reliable entry points: feedback you’ve heard from multiple sources independently, patterns in your outcomes you can’t keep blaming on others, and trusted relationships that can name a pattern without making you defend it.

10. pain

can you name what hurt you, why it’s still active, and what you’re going to do with it. address it or consciously park it. not let fester.

this is the dimension most likely to be misread. someone who names their pain often sounds naysayer-ish on the surface (wary, pattern-matching, citing history) when they’re actually a builder talking.

• naysayer: can’t name it. the pain is the lens. every new initiative refracts through the unprocessed event. they don’t know that’s what’s happening, which is why “just be more open” doesn’t work. “hurt people hurt people”. pain emerges as criticism, withdrawal, sabotage, cynicism, but the originating wound is invisible to them.
• builder: “i got burned on the X project. the specific thing was [Y]. it made me wary of [Z pattern]. that’s why i’m pushing back on what looks like a repeat.” pain becomes information about what they’re protecting. separation between person and pain. decides what to do with it: address (work through it, repair what’s repairable, change conditions, get help), or consciously park (acknowledge it, set it down for now, don’t pretend it’s gone).
• the shift: three sub-moves. notice. the reaction is disproportionate to the trigger. name. what’s the underlying event, what was the actual harm. decide. address or consciously park. not let fester.

the relief of naming (disappointment, baggage, the thing you’ve been carrying) is itself the shift. naming creates the doorway to forward motion. unnamed pain is a closed door you’re pushing against without realizing it’s there.

diagnostic question: can they tell you, in their own words, what they got hurt by and why it shaped how they engage now?

• yes → builder talking, even when the surface sounds wary. the pain is data they’re working with.
• no → pain is doing their thinking. different intervention is required, or it isn’t yours to do.

the metacognition stack

dimensions 8, 9, and 10 work as a stack:

• 8 reasoning = logic about the world.
• 9 self-awareness = logic about yourself.
• 10 pain = logic about what hurt you and why it still drives you.

each enables the next. pain without reasoning = vibes-naysayer. pain without self-awareness = pain doing the thinking. reasoning + self-awareness applied to pain = address it. skipping that = fester.

rate yourself

i’m using ten dimensions to reason about builders vs naysayers and identify where change is possible.

a few notes before you rate:

• this tool is meant for personal self-reflection and growth. share it with your mentors, your team, etc. get them to engage with it.
• expect to be builder-shaped on some dimensions and naysayer-shaped on others. each person has a different recipe.
• low scores aren’t bad news. they’re where growth happens.
• prefer the tool on its own page? open it.

the named-pain diagnostic in practice

we all bring our histories and interactions and experiences to current-day. the shitty bosses, the great teammates, the successes and failures.

someone on your team is being difficult. they’re skeptical of every initiative. they push back hard, sometimes with substance, sometimes with what reads as cynicism. is this a naysayer to reflexively rejecting without thinking, or a builder protecting against a real pattern they’ve seen before?

ask them. not as a confrontation. as curiosity. “what’s the experience that’s shaping your response?”

if they can name it (“i’ve watched this exact thing fail twice, here’s what specifically broke, and here’s a few options on how to move forward”) you have a builder. their pushback is information. their wariness is a feature. the named pain is showing you what they’re protecting and the context that shapes moving forward.

if they can’t (“i don’t know, i just don’t trust it, failed twice before”), you have unnamed pain doing the thinking. their pushback isn’t about this initiative. it’s about something deeper, and we gotta unpack this. what’s underneath the surface here?

two leader failure modes around pain

writing off too fast

labeling someone a naysayer when they’re actually a frustrated builder whose pain is just barely surfaced. the fix is the named-pain diagnostic. create the space to engage, push the onus onto them to name it, and be present on the path forward.

over-saving

pouring leverage into someone whose pain is unnamed, hoping warmth will unlock it. it usually doesn’t. the missing piece isn’t your warmth, it’s their own ability to see the pattern and engage. you drain yourself, your builders watch you do it, and the message they get is: acting hurt is a way to get more attention.

builders quietly disengage. then you wonder why your high performers are leaving while you’re still pouring time and energy into the person whose situation never seems to improve.

most leaders default to one of these two failure modes without realizing it. notice which one you lean toward.

then zoom out: this is wider than just individuals. sometimes the org broke faith with someone. a promotion that didn’t come. a project killed mid-flight. layoffs with shady reasoning. yet another reorg “yaro”… no trust.

in these cases, we have to move a level higher to the conditions and structure of the org. the org is the root cause. sometimes rotten to the core.

how to use this today

three audiences, three applications.

for yourself. open the rate-yourself tool. pick the dimension you scored lowest on. don’t try to move all of them. pick one. work it for the next week. notice the moments it shows up. catch yourself in the pattern. try the shift.

with your team or with a peer. take it into a 1:1. “check out these builder vs naysayer dimensions. which one resonates? let’s dig into it together over the next few days/weeks.” the reciprocity matters.

at org level. use it for condition design, not sycophancy. ask: what conditions in our environment punish builder behavior on each dimension? where do we reward naysayer behavior? busyness over impact (dimension 3)? avoid feedback in name of niceness (dimension 4)? worship capital P Process (dimension 6)? name these. change them. create builder conditions.

use it on yourself first

before you apply this map to anyone else, run this on yourself. where are you builder-shaped, and where are you naysayer-shaped? what about org-wide structure?

pick three behaviors you wish were more common in your sphere of influence (your team, your peer group, your org). for each, ask: what conditions in the current environment punish this behavior or fail to reward it?

if you can’t name the conditions, you’re still trying to fix individuals, not designing structure.

open threads

this is where my thinking is today. areas to further explore.

• builder sub-archetypes worth naming. the translator who builds bridges between groups. the catalyst moves stuck systems forward with lower activation energy and high leverage. these probably deserve their own treatment.
• a naysayer pattern not yet captured: the exhausted former builder. used to have agency. got burned. now criticism is grief in disguise. needs its own diagnostic.
• what does a 1:1 with a disgruntled creative builder actually sound like vs a naysayer performance critic? the named-pain diagnostic is one approach. what are others? what’s this look like over time? success?
• concrete shifts per dimension. what does growth on, say, dimension 5 (own your own learning) actually look like over time? example checkpoints per dimension. avoids “i’ll just work on them all since more is better.” that turns the framework from concept into operational tool in targeted ways.

if you take the framework into your own practice and find more of these (patterns it doesn’t capture, places it breaks down, dimensions that need to split or merge), i’d love hear it. this thing gets better through use, not through more theorizing.

rate yourself. pick one dimension. engage with it. let’s see what happens.