Throughout my career leading SREs, DBAs, and full stack developers across SaaS, aerospace, defense, and retail, I have consistently promoted people who demonstrated a specific communication pattern.

Not the loudest voices in the room. Not the ones who shipped the most commits. The ones who said certain things, repeatedly, without being told to.

These seven phrases signal something deeper than technical competence. They signal ownership, strategic clarity, and the quiet confidence that separates executors from strategists.

Here they are.

1. “Here’s what I’d recommend and here’s the trade-off.”

Most people stop at the recommendation. They pitch the answer and wait.

The people I promote go one step further. They surface the trade-off before anyone asks. They tell me what we are giving up, what might break, or what scenario makes this the wrong call. Opportunity Costs.

This does two things. First, it builds trust. I know they have stress tested their own thinking instead of falling in love with their first idea. Second, it accelerates decisions. I do not have to waste time poking holes because they already did that work for me.

In IT strategy, every architectural decision is a trade-off between speed, cost, reliability, and maintainability. Leaders who cannot articulate those trade-offs are not leading. They are hoping with fingers crossed.

2. “I’ll own that.”

Three words.

Very few people say them unprompted.

When something goes sideways in a deployment, a migration, or a customer escalation, most people reach for context first. “The pipeline was misconfigured.” “The vendor changed the API.” “We did not have visibility into that layer.”

All of that may be true. But the people I promote lead with ownership. They say “I’ll own that” and then they explain what happened. Not the other way around.

Ownership is not about blame. It is about signaling that you are the person who will carry this across the finish line regardless of whose fault it was. That signal is rare, and it is instantly recognizable.

3. “What are we optimizing for here?”

This is the question that exposes whether someone is thinking tactically or strategically.

Tactical thinkers optimize for the task in front of them. Strategic thinkers ask what the task is supposed to accomplish in the first place. Are we optimizing for speed to market? For cost reduction? For reliability at scale? For team velocity?

If you do not know the answer, you are probably optimizing for the wrong thing. I have watched entire quarters get burned on infrastructure projects that were optimized for elegance when the business needed speed. Or vice versa.

The people I promote ask this question at the start of every initiative. They refuse to build in the dark.

4. “What are areas you think I could improve in?”

This one separates people with real confidence from people who are just performing it.

Asking for feedback, especially from people who report to you or sit above you, is uncomfortable. It opens a door you cannot close. But the people I promote ask this regularly and they ask it specifically. Not “any feedback for me?” but “what are areas you think I could improve in?”

The framing matters. “Areas I could improve in” assumes growth is ongoing. It assumes the feedback will be acted on. It invites honesty without making the other person feel like they are delivering a verdict.

In my experience, the people who ask this question improve faster than everyone else. They treat feedback as a raw material, not a performance review.

5. “Here’s what I learned from that.”

Post-mortems and retrospectives are standard practice in any functioning engineering org. But the people I promote do not wait for the scheduled meeting. They walk out of a failure, an incident, or even just a difficult migration and immediately synthesize what they learned.

More importantly, they share it. They write it down. They tell the team. They update the runbook. They do not hoard the lesson like personal currency.

This habit compounds. Over months and years, the person who reflexively distills and distributes lessons becomes the person everyone turns to when things are uncertain. They become the institutional memory not because of seniority, but because they built it.

6. “How does this help our customer?”

You can be deep in a Kubernetes migration, a database refactor, or a CI/CD pipeline overhaul and still lose sight of why you are doing it. The technical work is absorbing. It is easy to optimize for cleanliness instead of impact.

The people I promote drag the conversation back to the customer. Not in a performative “we love our users” way, but in a concrete, specific way.

“How does shaving 200ms off this endpoint help our customer?”

“If we delay this feature by two weeks for a cleaner abstraction, what does the customer lose?”

This question keeps teams honest. It exposes work that is technically interesting but strategically irrelevant. And it does something else: it signals to everyone in the room that this person thinks like an owner, not an employee.

7. “I need your feedback on this before I move forward.”

The people I promote do not disappear for three weeks and emerge with a finished product nobody asked for. They pull others in early.

This phrase signals two things at once. First, humility. They are acknowledging that their thinking is incomplete and that others will make it better. Second, velocity. They are not asking for permission. They are asking for input so they can move faster once they have it.

In tech leadership, the gap between “I have an idea” and “I shipped something” is where most projects die. The people who close that gap quickly, and with input from the right people, are the ones who get trusted with bigger things.

The Pattern Behind the Phrases

None of these phrases are complicated. You could teach them to a new manager in ten minutes. But the people I promote do not say them because they were trained to. They say them because they internalized a specific way of thinking about work.

That way of thinking has three layers:

Ownership. They act like the outcome depends on them, because it does. They do not wait for permission to take responsibility.

Clarity. They refuse to operate with ambiguous goals. They force the room to define success before they start building toward it.

Learning velocity. They treat every outcome, good or bad, as data. They extract the lesson, distribute it, and move on faster than everyone else.

These are not personality traits. They are habits. And habits can be built.

Putting It Into Practice

If you want to signal this kind of leadership maturity, start small. Pick one phrase. Use it in your next meeting. Not as a script, but as a genuine commitment to thinking differently about your work.

The people I have promoted over the years did not announce their leadership. They demonstrated it through the questions they asked and the ownership they took. Week after week. Meeting after meeting.

That consistency is the real signal.

Which of these phrases do you hear most often on your team? Which ones are missing?

Let me know on X at https://x.com/aarongxa