Skip to main content

Motivation Diagnosis

Reducing someone's behavior or position to a character flaw or suspect motivation rather than engaging with what they're actually saying.

  • "Engineer who was too lazy to write docs before now generates AI slop."
  • "They're just trying to protect their job."
  • "You only say that because you're invested in the ecosystem."
  • "This is just rationalization for not learning the right way."

Why It's Unproductive​

Psychoanalyzes intent instead of engaging with the actual practice or argument. Even if the motivation guess is accurate, it doesn't address whether the position has merit. People often do this when they disagree but don't want to make the effort to articulate why, so they attack character instead of engaging with substance.

The Better Move​

Talk about the practice, not the person. If you think something is a bad idea, say what's wrong with it and what you've seen go wrong. That's a stronger argument than guessing why someone holds the position they do.

Why It's Better​

Specific criticism of a practice is actually persuasive. Armchair psychology just makes people defensive, and even if your read on their motivation is right, it doesn't tell anyone whether the idea has merit.

Examples​

OP: "We started using Claude to generate API documentation and it's been a huge time-saver." Antipattern: "Engineer who was too lazy to write docs before now generates AI slop and continues not to write docs, news at 11." Better: "I'm skeptical. AI-generated docs often miss the nuance of why design decisions were made. Do you find you're doing substantial editing?"

OP: "I've been building side projects with LLM agents and I'm having a blast. Way more productive than I used to be." Antipattern: "This is just dopamine addiction. You're not being productive, you're pulling the slot machine lever over and over." Better: "Are the projects actually reaching a finished state, or do you find you spend more time prompting than shipping? Genuinely curious what the completion rate looks like."

OP: "I think we should move away from microservices and consolidate back to a monolith for our scale." Antipattern: "You only say that because you don't want to learn distributed systems." Better: "We tried that and the deploy pipeline got brutal around 50 contributors. What's your team size? That's the part where monoliths usually start to hurt."