Commitment, consistency, ownership

Our biggest meeting room. A newly formed team - six developers, three QAs, and our engineering manager. We had just been handed a huge task in a domain none of us knew, and the integration with one of our providers would end up dragging on for six, seven, eight months. It was a nightmare, and we were not doing okay.

And in that room, again and again, our engineering manager repeated the same thing:

"There are three things I want you to remember and follow daily. If I wake you up at night, I want you to be able to tell me - commitment, consistency, ownership."

The first few times, it sounds like a poster on the wall. Somewhere around month four of an integration that refuses to end, it starts to sound like a plan.

What the words turned into

Commitment - you sign up for the outcome, not for the attempt. On a task that long, there are plenty of moments where nobody would blame you for letting quality slide or the scope quietly shrink. Commitment is what stops that.

Consistency - showing up in month seven the way you showed up in week one. No heroics, no bursts followed by silence. Over eight months, boring and steady beats brilliant and occasional every single time.

Ownership - everyone became an owner of something. Not "assigned to" - an owner. When something breaks in the part you own, you do not wait to be asked. You already know, and you are already on it.

The part where it worked on me

I joined that team as a senior developer. I left the role as a team lead.

The promotion did not come from a stroke of brilliance. It came from being consistent and from owning the things I wrote - which is to say, the three words were not just something my manager said to the room. They turned out to be, very literally, the promotion criteria.

Repeating it forward

As a team lead the pillars changed shape. Now they show up in one-on-ones, in feedback sessions, in annual salary reviews - because the job stopped being only about the code I ship and became about the people I take care of. It is a different kind of ownership, and honestly the most rewarding one so far.

And I catch myself doing exactly what my manager did - repeating the same three words to my own team, until they can say them half asleep.

I think that is what culture actually is. Not the slide with the values on it - the thing a manager repeats until the team starts saying it back.

The recipe

Commitment, consistency, ownership. It is not an original recipe, and that is the point - it is a recipe that works for anyone in R&D, at any level.

And if you wake me up at night, I can still say it.