One aspect of this I've been thinking about for a long time (partially for intensely personal and complicated reasons!) is honing my criticism/complaint razor. I think I set up the idea pretty well in the last half of this comment.
The difficult thing about separating a critic (someone who helps you find a path through action space that deletes their complaint) from a complainer (someone who's the opposite of that) is that, while you have to protect your attention from complainers to a nontrivial degree, you may accidentally block a high quality adversary because what seems like a complaint is actually a criticism that's just really really hard to address, and you don't know the difference.
So on the one hand the existence of serial complainers (people who are hostile to solving problems) implies that problem solvers should be wary of crab buckets (and may be drawn to them out of humility or interest in soliciting criticism or desire to be actually right), on the other why should you expect to hone a heuristic for sorting them out quickly? It's deeply tricky.
Thanks for sharing, I like how concrete all of this is and think it's generally a really important practice.
One "hack" that came to mind that I think helped me feeling more relaxed about the prospect of even pretty harsh criticism: Think of some worst cases already in advance. Like when you do a project/plan your life, consider the hypotheses that e.g.
you should not do this in theory good project because you are the wrong person for it, e.g. due to you not being [insert relevant features/skills] enough (yet!)
the project you plan working on will actually make things worse for various potential reasons
the career you invested your energy into is far from the best you could be pursuing
and a catch-all "there are possibly some unknown crucial considerations I'm neglecting"
Internally I expect even harsh criticism to then kinda feel like "Yeah good point, but also haha, I already kinda considered that and you merely cause me to update!" xD
I like the word "leverage point", or just "opportunity". I wish to elicit suggestions about what kind of leverage points I could exploit to improve at what I care about. Or, the inverse framing, what are some bottlenecks wrt what I care about that I'm failing to notice? Am I wasting time overoptimising some non-critical path (this is tbh one of my biggest bottlenecks)?
That said, if somebody's got a suggestion on their heart, I'd happier if they sent me a howler compared to no feedback at all. I regularly (while trying to keep it from getting too annoying) elicit feedback from people who might have it, in case it's hard for them to bring it up.
AI Use Note: Main body text entirely human written. Claude (Opus 4.8) helped develop models of animal life histories in the appendix.
Cross-posted from Good Structures.
Executive Summary
* Animal advocates sometimes make claims like “there are X of this animal...
“How long have you been v*g*n?”
This is one of the most common icebreakers at animal protection events. It’s a baseline assumption, and it mostly holds true: if you’re out advocating for animals not to be tortured or abused, realistically these days you are v**n, or close. And it makes for good conversation. It seems fairly safe to assume when you meet strangers.
But this assumption is hurting the movement in a way which we don’t always notice: someone new comes into the sp...
Summary
Back in November 2023 I posted here to launch Spiro and raise our first $198k. Two and a half years later this is an update and a fundraiser for the next step.
The short version: we've now reached over-5,900 people with TB preventive medicine, including over 3,000 children under five years old. Our early results have held up well an...
Tl;dr/epistemic status: quick post mostly comprised of bullet points.
I have a pretty public-facing role, so I get a fair amount of feedback (both negative and positive) on my work from different people. A while back, I wrote a doc for myself on how I want to respond to this kind of negative feedback (and related stuff). Then I shared the doc with some folks I know and work with to get input on it,[1] then never shared it further. There’s been more related discussion recently, so I thought I’d share it now.[2] I haven’t really updated it except to add the introductory notes (before the first actual section), some links, and a picture.
I use the word “criticism” here for a pretty vague/broad class of things that includes things like “negative feedback” and “people sharing that they think I’m wrong in some important way.” (Other things are also arguably “criticism,” like people pointing out specific minor errors, but those are easier for me to handle, so I wasn’t really focusing on them when I wrote this.)
Please don't interpret this as a request to stop sharing feedback! Feedback has often helped me improve my work and grow. (I do think there are better and worse ways of sharing feedback, though — see more below.)
Notes on criticism
These were kind of used like lemmas for the original doc — claims to help arrive at my ~conclusions
What’s the point of (engaging with) criticism?
To improve what I’m working on now
To learn something I might be able to use in the future
[Something about supporting communal norms around engaging with good-faith criticism.]
Sometimes criticism isn’t really criticism and shouldn’t be (it could be reframed as a suggestion)
Criticism can be wrong
(Fear of) criticism can discourage action in bad ways
How I want to handle criticism
Steelman it before updating on it, or try to understand the other person’s point of view if I first want to respond to it.
Consider it rationally, and avoid over-updating on it. (Criticism can be wrong!)
Actually listen to it, and stare into the abyss if the criticism is potentially scary.
Interpret it in a productive way — what should I learn, how should I change my behavior (if at all) — and avoid immediately judging myself, worrying that it means that I’m terrible in some deep important way. (Related: "Flinching away from truth” is often about *protecting* the epistemology.)
Relatedly, avoid over-interpreting: avoid thinking that whoever is passing this on must think that I’m terrible in many other ways.
If it’s very aggressive, get some help dealing with it.[3]
Allow myself to engage with it in healthy ways, e.g. don’t go head-first into the criticism out of a misguided impulse towards ~epistemic bravado.
Sometimes I’m emotionally overwhelmed. It’s ok to listen to and process the criticism later. If someone is giving me feedback, I can ask them to write it down and send it a little later. If I have an email, I can snooze it until next week. A method that a friend proposed but that I’ve never tried is asking a friend to read the criticism and to contextualize it for me.[4] (I assume the process is something like “this is pretty chill, don’t worry about it,” or “hey, this is a criticism of your work on X. It’s pretty harsh. It sounds pretty reasonable, but even if it’s all true, it doesn’t mean you’re bad or anything like that.”)
Bonus: notes on how to share criticism in ways that make this process easier for the one being criticized
When possible, reframe things as suggestions or ideas rather than criticism.
Avoid judgemental language.
Criticize a product or a way of doing something, not the person.
Just be kind.
Explicitly flag the boundaries of the criticism — say, “I think this part of the project is performing poorly, but these other parts seem useful.” Express agreement or appreciation for something alongside the criticism.
Flag your uncertainty or how polished the criticism is, and whether you’re deferring to anyone or whether you might be biased in some way.
If you think the person might be getting lots of criticism, consider offering to share the criticism and offering to share it later (if it’s not immediately action-relevant).
Share it privately, unless you think it’s important for there to be common knowledge for some reason.
Remember that even if it doesn’t seem like the person has taken your criticism into account, they might be mulling on it and might e.g. update next time they notice something you pointed out (which they’re now on the lookout for).
More here (and in other places!): Supportive scepticism in practice. I'd be grateful for comments (or messages) that share other resources on this topic that people appreciate. (I might write more on this in the near future.)
One aspect of this I've been thinking about for a long time (partially for intensely personal and complicated reasons!) is honing my criticism/complaint razor. I think I set up the idea pretty well in the last half of this comment.
So on the one hand the existence of serial complainers (people who are hostile to solving problems) implies that problem solvers should be wary of crab buckets (and may be drawn to them out of humility or interest in soliciting criticism or desire to be actually right), on the other why should you expect to hone a heuristic for sorting them out quickly? It's deeply tricky.