A staff engineer holds almost no formal authority: no budget, no hiring power, no veto on the roadmap. People who take the role discover their work drops off the leadership agenda when nobody writes down the outcome. Managing up is the set of habits that keeps impact visible without turning into self-promotion. Will Larson, in Staff Engineer (O'Reilly, 2021), spends a large part of the book on working without formal authority and treats the relationship with the direct manager as the highest-leverage point of the role.
Two-line update every two weeks
What changed and what needs a decision. A short email every two weeks to your manager and the CTO, always in the same format: state of the fronts you drive, then the pending decision. Andy Grove, in High Output Management (Vintage Books, 1985), calls amplifying your own work the habit of handing over information in a form ready to pass on. Tanya Reilly, in The Staff Engineer's Path (O'Reilly, 2022), recommends booking the check-in before your manager picks the format.
Risk written before it becomes a fire
Three fields: what can break, likelihood, what you are asking for. Record it the day the risk shows up, with a date. Once written, it becomes history of your reading of the context even if nothing happens; when it does happen, the conversation moves from blame to response and your manager finds your name in front of the decision.
An ask for a decision with a deadline
Two options, the cost of each, your recommendation and a cut-off date. A real deadline: a sprint, a board meeting, a contract. An open question with no date sits still and returns to your messages two weeks later, with the cost already collected. Package the decision and your manager only confirms.
When no answer arrives
Escalate the channel and keep the tone. After a week, send the same decision to your manager and the business stakeholder together, opening with the cost of waiting: a stalled sprint, a contract, a risk in production. Escalating with a number is management routine; escalating with a complaint turns into noise nobody reads.
Bring asks to the quarterly conversation
Feedback, training budget and project access come with evidence. Build the list from what happened: project you drove, decision you documented, person you developed. Grove treats management as an activity measured by data in High Output Management (Vintage Books, 1985), and your ask follows the same logic. People who wait to be noticed usually wait one cycle too long.
