Self-reflection questions for developers: ask what, not why

MeetYu — Tue, 10 Nov 2026 14:00:00 +0000

Self-reflection questions work a lot like incident reviews: the wording decides whether you learn something or just feel bad.

Plenty of developers do a weekly review that is really a string of why questions. Why did Thursday disappear into Slack? Why did I say yes to that extra review? Why does the side project never move? It feels like serious analysis. It rarely produces anything you can act on on Monday.

Good engineering teams solved this problem for production incidents a long time ago.

Blameless postmortems don't ask "why did you do that?"

Postmortem culture is built on one idea: look at what happened and what made it possible, not at who is to blame. The Google SRE book describes blameless postmortems as reviews of contributing causes without finger-pointing, because people who feel judged hide information, and hidden information causes the next incident.

The questions in a good postmortem are mostly what questions:

What happened, in order?
What signals did we miss?
What would have made the right action easier?
What is the one change we'll make?

Notice what's missing: "Why did you deploy on a Friday?" That question invites a story, a defence or a confession. None of them fixes the pipeline.

The same holds for your own head

Organizational psychologist Tasha Eurich and her team studied how self-awareness works. One finding: highly self-aware people ask what far more often than why when they look at themselves (Harvard Business Review, 2018).

The logic matches the postmortem. Why sends you looking for a cause you often can't see, so your brain supplies a plausible one. "Why am I like this?" has no useful answer. "What set me off today?" does.

A personal postmortem in three swaps

Instead of	Ask
Why am I like this?	What set me off today?
Why can't I focus?	What would make the next hour easier?
Why did I say yes again?	What did that yes cost me?

Each what question points at something observable, and each one ends in a next step. That's the point of a postmortem: not understanding for its own sake, but one concrete change.

A five-line weekly template

Written like a tiny incident report:

1. What happened this week that I want to remember?
2. What drained me, and what gave me energy?
3. What pattern do I see across the last two weeks?
4. What would have made the hard part easier?
5. What is one small change for next week?

Two things make it work:

Write it down. Patterns are hard to see from the inside, and memory edits the story. A written log is your monitoring dashboard.
Look across weeks, not just one. One bad Thursday is noise. Three bad Thursdays is a signal worth acting on.

Where an AI coach fits

The second point is where tooling helps. We build MeetYu, an AI life coach & journal app for iOS and Android. You write short entries, and the coach remembers them, so it can ask the what questions across weeks: "What's different about the days that went well?" It's the same idea as a postmortem that can read every previous incident report.

You don't need an app to try the swap, though. Next time you catch yourself asking why about your own week, rewrite it as a what, and check whether it ends in something you can change on Monday.