Dev Velocity Lab
← Back to blog
engineer-growth

Five Productivity Books, One Idea That Stuck: Own the Loss

After reading five productivity books in five weeks, the only idea that changed my work was simple: when something goes wrong, the first question is what I'll do next, not who or what to blame.

Watch on YouTube
ShareX / TwitterLinkedIn

I read five best-selling productivity books in five weeks. Most of what they said blurred together. One idea didn't: take responsibility for everything, especially the bad parts.

The idea that stuck

It sounds like common sense. Of course you should own your results. But knowing it and doing it are different things. Owning it means going back, tracking the decisions you actually made, and seeing how they affected you.

For me, that covers a lot. Pushing a lot of code changes is on me. Asking questions, or not asking them, is on me. Building the connections I need at work is on me. Staying up late and then making excuses for missing my schedule is on me too.

When I looked honestly at my bad weeks, the pattern was the same. I didn't communicate well, I didn't balance my time, and I didn't follow through. Then I felt down, and the stuff I cared about stopped moving. Blaming someone else was the easy way out, and it cost me the most.

Stop asking "why did this happen to me"

The shift that helped most was in how I respond to a bad outcome. The old reflex was: why did this happen, who messed up, what was outside my control. The new one is: this is terrible, what can I learn, and what do I do next?

That shift is small, but it changes everything after it. If a bad hour is just a bad hour, it stays an hour. If I let it turn into "my whole day is ruined," it drags into the rest of the week.

So I go back to the routines. I have two anchor points a day, morning and evening. When something goes sideways, I ask: what's the next thing I can do that matches my habits? Not a perfect recovery, just the next right action.

Track two things

You can't own what you can't see, so I track two signals:

  1. Actions. Did I do the habit? Did I write down my goals? Did I name one area to improve today or this week? This is visible. Use a notebook, a spreadsheet, or an app. It's either done or it isn't.

  2. Energy. How do I feel day to day, even hour to hour? Am I overwhelmed and hectic, or are things running in order? Am I making new connections at work, learning something technical, moving toward my goals?

The first tells me whether I'm putting in the work. The second tells me whether the work is sustainable. Together they give me feedback I can act on, instead of guessing.

Iterate on the habit, not on yourself

Setting a habit is easy. Finding out whether it fits your life is the hard part. Wake up when the alarm goes off, for example. If you miss it three days in a row, that's data about your sleep, your evenings, or your schedule. It isn't proof you're lazy.

Treat each habit as an experiment. Run it, check the actions and the energy, adjust, and run it again. Over a few weeks, you'll learn much more about how you work than any book can tell you.

What this looks like if you're new to a role

If you've landed in a new role or stack you didn't pick, the pressure to catch up is real. Ownership helps in a specific way: it turns "I'm behind and it's hopeless" into a list of things you can do this week. Ask the question you were embarrassed to ask. Log the thing you didn't understand. Name one concept to learn tomorrow. Then check how you feel at the end of the day.

Takeaways

  • When something goes wrong, skip the blame and ask what you'll do next.
  • Keep a bad hour from turning into a bad week by returning to your morning and evening routines.
  • Track two things: whether you did the action, and how you felt doing it.
  • Treat every habit as an experiment. Adjust based on what the data says.

Ownership isn't a personality trait you either have or don't. It's a loop you run every day. That's the part I'm going to keep practicing.