Becoming the Person Who Decides What Gets Built
The most common career advice in this shift, with the instructions attached. The conversation isn't gated by title — it's under-resourced, and one specific move changes outcomes immediately.
"Move toward deciding what to build" is the most common piece of career advice in this shift and the least often accompanied by instructions. The decision-making happens in specific conversations, and getting into them is a set of concrete moves rather than a promotion you wait for.
Why it's not gated the way people assume
The assumption is that scope decisions belong to product managers or senior leadership, and you get there through a title change.
In practice these conversations are usually under-resourced. The people making them want information they don't have: what will this cost, what breaks, what's the cheap version, what did we learn last time we tried something like this. Engineers hold most of that and mostly don't offer it.
→ The gate isn't permission. It's that contributing usefully requires knowing things most people in the room don't bother to find out.
The moves
1. Ask to be in the room, once. Most planning and prioritization meetings will accommodate an engineer who asks. This is a small ask that people over-estimate.
2. Bring the cost and risk information. Your differentiating contribution is knowing what things actually cost to build and maintain, what's fragile, and what a proposal implies that isn't in the proposal. Show up with that and you're contributing rather than observing.
3. Offer the cheaper version. ✅ The single highest-value move. Someone proposes something expensive; you describe the eighty-percent version at a fraction of the cost. This is a decision contribution, it's specifically an engineer's contribution, and it changes outcomes immediately.
4. Say what it will cost to keep. Most proposals are evaluated on build cost. Being the person who reliably names the maintenance cost — the ongoing support, the configuration surface, the thing you'll carry for five years — changes how decisions get made and is consistently undersupplied.
5. Follow up on outcomes. After something ships, find out whether it did what was intended. Most organizations don't check. Doing it makes you the person with actual evidence about what works, which is the strongest position in any prioritization argument.
6. Write the one-pager. When you think something should be built, write it up: the problem, who has it, the options, the costs, the recommendation. This is what a decision-maker consumes, and producing it is how you become one.
⚠️ The mistakes
Advocating only for technical work. If you're only in the room to argue for refactoring and infrastructure, you're a stakeholder, not a decision-maker. Contributing on product questions is what changes the role.
Arguing in engineering terms. "This is technical debt" loses. "This is why the last three estimates slipped, and here's what it costs to fix" wins, because it's stated in something the listener already cares about.
Waiting to be senior enough. The contribution is judged on its content. A junior engineer who reliably provides the cheap alternative and the maintenance cost is in the decision faster than a senior one who doesn't.
Confusing having opinions with contributing. Opinions are abundant. Evidence about cost, risk, and outcomes is not.
💡 What actually makes someone good at it
The people who are genuinely good at deciding what to build share three things, none of which is seniority:
They know what things cost, in build and maintenance, from having done it.
They know the domain — what users actually do, what the business needs, where the money comes from.
They follow up. They know how previous decisions turned out because they checked, which means their judgment is calibrated against reality rather than accumulated confidence.
That third one is the differentiator and the rarest. Most people make many decisions and learn from few, because nobody makes them look.
The takeaway
The decision conversation is under-resourced, not gated. Get in the room, bring cost and risk information nobody else has, offer the cheaper version, name the maintenance cost, write the one-pager, and — the part almost nobody does — follow up on how it turned out. That last habit is what turns making decisions into being good at them, and it's available to anyone regardless of title.