Situations · Workplace
When your boss will not take your advice, find out what they are accountable for and what they fear, then rewrite the proposal into something they can defend upward.
When a boss rejects a proposal, it is usually not because the proposal is wrong. It is because it does not answer the question they actually care about: how they will explain it upward, and who carries it if it fails.
The order of judgement is: what they are accountable for this quarter, how much extra risk your proposal puts on them, and whose opinions they actually listen to.
Managing up is not saying it louder. It is rewriting the proposal into a version that can be tried small, reversed, credited to them if it works and carried by you if it fails, and walking them through it privately before any formal setting.
Also searching for: boss does not listen to my ideas · how to manage up · how to get your manager to accept a proposal · manager keeps rejecting my suggestions
A boss who hears an unprepared proposal in front of others defends by reflex. Most good proposals die at this step, not on their content.
The bigger the proposal, the more risk it puts on them. If you do not name it, they fill in the worst version themselves.
No usually means not now or not in this shape, not never. Without asking which one it is, you give up.
Citing an outside expert or another executive to prove you are right turns a proposal into a question of allegiance, which makes it harder to accept.
Find what they have promised upward this quarter and which metric they most fear breaking. If your proposal touches that line, explain first how the line is protected.
Count the budget they must approve, the people they must move, and the people they must explain it to. That is the real price of their yes.
Every boss has a few trusted sources. Knowing who they are decides whether your idea should pass through them first or go straight to the boss. The outcome differs a lot.
The Art of War, chapter 1, Laying Plans
When the calculation of advantage is heeded, then create momentum.
Sun Tzu says to lay out the gains and losses so they can be heard, and only then build momentum. Managing up follows the same order: work out the boss's stakes first, shape the proposal so it can be heard, and momentum follows. Building momentum before the calculation mostly builds opposition.
Shrink the proposal to a pilot that needs no budget approval, get a result in two to four weeks, and return with the result to discuss scale. Let them approve a low-risk test, not a direction.
Listen to the doubts privately without arguing and write them down. Make the next version answer those exact points, and let them see in the formal setting that their view is already inside the plan.
Stop pushing the same proposal. Let the idea be discussed among the sources they trust, and write your plan into a short document on file. When the problem finally surfaces, your plan is the ready answer.
Tell the strategist the proposal, how the boss responded, what the boss is accountable for this quarter, and what you guess they are worried about.
The strategist puts the boss's stakes and your proposal on one table, showing which part touches their line and which part can become a small test.
You leave with an action card: three opening sentences for the next private conversation, and a signal that tells you when to pause.
This page covers the order of judgement. Your own situation, opponent, and resources are worked through with the strategist in the app.
Get the app and run your situationNot accommodate, reroute. Pushing head-on against a wrong boss usually ends with you out, not with them changed. Turn the proposal into a cheap test and let the facts persuade them. That is faster than you persuading them.
Sound it out privately in person first, then write. A written proposal without groundwork reads as putting it on record, and the boss gets defensive. Once you roughly agree, the written version becomes the tool they use to explain it upward.
It depends on the reason for the no. If it was resources, wait for the next budget cycle. If it was doubt about the direction, wait until you have new evidence. If there was no reason given, stop and observe for a quarter.
Accept it the first time; that is part of the price of adoption. What you want is the idea implemented and the next ideas heard. Being erased repeatedly is the problem worth handling, and that is the credit-taken page.
Workplace · When another department will not cooperate, look at what they are measured on and what your request costs them, then decide whether to change the exchange, escalate, or go around.
Workplace · When someone takes credit for your work, separate one-off from pattern and peer from manager, then decide whether to add a record, have a direct conversation, or change how you work.
Workplace · When you and a colleague are up for the same role, find out who decides, what they measure, and what the role requires, then decide where to put your effort.
Workplace · When a new boss is parachuted in, find out what they were sent to do, whom they listen to, and what they must deliver in ninety days, then become the person they need.
This page covers management judgement only and is not HR or legal advice. Do not use Sun Tzu's language to justify manipulating, pressuring, or harming colleagues or managers. Instructions that break rules or the law belong in your company's formal channels.