A tweet by Lewis Howes has stayed with me for years:
“The mind is so powerful that when you ask for what you want, the world starts aligning to show you more of that thing. You must take the actions and decision to follow through on your desires instead of falling into past habits or sabotaging yourself. You must be consistent in your pursuit of positive qualities otherwise it’s easy to slip back into a place of suffering.”
I’ve seen this play out in engineering leadership more directly than any self-help book predicted. The leaders who get what they want are not the ones who negotiate hardest. They’re the ones who know exactly what they want and ask for it clearly — without hedging, without softening, without pre-apologizing.
Here’s what I’ve learned about the power of a precise ask.
The Vague Ask Problem
Most engineering leaders under-ask. Not because they’re timid, but because they’ve learned that softening the ask reduces the chance of rejection. “We could use some more headcount.” “It would be nice to have more budget for tooling.” “Maybe we should think about improving our testing practices.”
These are not asks. They are wishes. And wishes, unlike asks, produce nothing.
The problem with vague asks is that they give the recipient nothing to respond to. An executive hears “we could use more headcount” and has no frame for evaluating it. More than what? For what purpose? By when? In exchange for what? The ask is so soft that the only safe response is “we’ll look into it” — which means nothing will happen.
The leader walks away feeling unheard. But the problem wasn’t the listener. It was the ask.
What works better: Before you make any ask, write it down in one sentence. “I need two additional senior engineers in Q3 to deliver the platform migration on schedule.” If you can’t write it in one sentence, you haven’t thought through what you actually want. The discipline of the single sentence forces clarity. And clarity is what makes an ask answerable.
Clarity as a Leadership Tool
Precision in asking serves two purposes. First, it increases the probability of getting what you want — because the other party knows exactly what they’re agreeing to. Second, it builds trust — because leaders who ask clearly are perceived as knowing what they’re doing.
Consider two requests in a leadership meeting:
“We should invest more in developer experience.”
Versus:
“We need to reduce CI build times from 22 minutes to under 5 minutes. This will require $15K in new build infrastructure and one engineer allocated for six weeks. Here’s the expected impact on team velocity.”
The first request generates discussion. The second generates a decision. The first is safe but ineffective. The second is risky but actionable. The difference is not in the tools or the budget — it’s in the clarity of the ask.
What works better: Include three elements in every ask: the specific outcome, the specific resource required, and the specific timeline. “I need X by Y to achieve Z.” If any of the three is missing, the ask is incomplete. Complete asks get decisions. Incomplete asks get meetings.
Asking for Resources
The most common asks in engineering leadership are for resources — headcount, budget, time, tooling. And the most common mistake is leading with the resource instead of the outcome.
“I need two more engineers” invites the question “why?” But “our on-call rotations have teams paged twice a week, and we’re burning out our senior engineers. I need two engineers to build a self-healing infrastructure layer that reduces page volume by 80% within six months” answers the question before it’s asked.
The resource is the answer. The outcome is the ask.
What works better: Frame every resource request around a measurable outcome. The executive’s job is to allocate resources to outcomes. If you bring them an outcome with a price tag attached, their decision is straightforward. If you bring them a price tag with no outcome, their decision is impossible. Make their job easy.
Asking for Outcomes
Just as important as asking for resources is asking for outcomes from your team. Many leaders state expectations so vaguely that no one knows whether they’ve been met. “I want us to be more proactive about quality” is an aspiration, not a goal. “I want the change failure rate below 5% by the end of the quarter” is an ask.
The precision matters because it removes ambiguity about success. When the ask is clear, the team knows what to aim for and when they’ve hit it. When it’s vague, everyone pretends to agree and goes back to their previous priorities.
What works better: State outcomes as measurable conditions. Not “improve reliability” but “achieve 99.95% uptime for the customer-facing API.” Not “ship faster” but “reduce cycle time from feature request to deployment from 14 days to 5.” The measurement is what makes the outcome real. Without it, the ask is a wish.
The Consistency Requirement
Asking clearly once is not enough. Lewis Howes said it: consistency is required. The same ask needs to be repeated, refined, and reinforced until it becomes part of the organization’s operating rhythm.
The reason is that organizations have inertia. A single clear ask gets absorbed into the noise of competing priorities. It takes repeated, consistent articulation for the ask to actually change behavior.
I’ve seen leaders make a brilliant, clear ask in a strategy meeting — and then never mention it again. Six months later, nothing has changed. They assume the ask was heard. It was. But it was also forgotten. Consistency is what converts an ask from a statement into a priority.
What works better: Repeat your most important asks in every relevant forum until they stop needing to be repeated. The first time, people hear it. The second time, they consider it. The third time, they start acting on it. If you’re tired of saying it, you’re probably saying it enough.
The Gratitude Component
The original tweet mentioned gratitude. This is not softness — it’s practicality. Leaders who ask clearly and then acknowledge progress when it happens create a positive reinforcement loop. Teams that feel seen are more likely to align with the next ask. Executives who feel appreciated for saying yes are more likely to say yes again.
Gratitude is not about being nice. It’s about closing the loop. An ask that produces a result and is acknowledged builds trust for the next ask. An ask that produces a result and is met with silence trains the other party that their effort went unnoticed.
What works better: When someone delivers on an ask, acknowledge it specifically and publicly. “Last quarter I asked for a 40% reduction in CI build time. The team delivered it in 10 weeks. That’s why we’re able to ship faster today.” The acknowledgment makes the next ask easier because people remember that the last one led to something real.
What I’ve Learned
Five things that have shaped how I think about making asks:
Vague asks are not safer — they’re riskier. A vague ask can’t be rejected, but it can’t be accepted either. It produces nothing. A precise ask might get a no, but a no is useful information. You can negotiate from a no. You cannot negotiate from “we’ll look into it.”
The ask reveals the leader. When I hear a leader make a vague ask, I know they haven’t thought through what they want. When I hear a precise ask — this outcome, these resources, this timeline — I know I’m dealing with someone who has done the work.
You can always ask for more than you think you can. Most leaders undershoot because they pre-compromise. They decide what’s realistic before they ask. Let the other party decide what’s realistic. Your job is to ask for what you actually need, not what you think you can get.
The ask is not the negotiation — it’s the starting point. A precise ask is not a demand. It’s a proposal. The other party may counter. That’s fine. But a precise ask gives them something to counter. A vague ask gives them nothing. Precision enables negotiation. Vagueness prevents it.
Gratitude is not optional — it’s the system that sustains the cycle. People who deliver on your asks need to know it mattered. Acknowledge it. The next ask will land in a different context because the last one was honored and recognized.
Ask for exactly what you want. Not because the universe will align — but because clarity is the only thing that gives the people around you a chance to help you get there. Be bold. Be precise. Be consistent. And when progress comes, acknowledge it.