Working With a Difficult Boss Without Losing Yourself
Arguing a cut estimate loses twice: the argument, then the date. Name the kind of difficult boss you have, find the pressure behind the demand, answer with options that trade scope for time, and recap in writing. Abuse is different: report it.
Key takeaways
- Difficult bosses come in kinds: under pressure, unclear, micromanaging, absent, and abusive. Each needs a different response.
- Most difficult behaviour comes from pressure you cannot see; ask what your boss is measured on before you argue.
- An estimate is a range with assumptions. Offer options that trade scope against time instead of defending one number.
- Recap every agreement in writing the same day, so a changed mind is visible instead of a surprise.
- Shouting, humiliation and discrimination are not a style to manage. Write down what happened and take it to your lead or HR.
Contents
FAQ
What should I do when my boss changes my estimate?
Do not argue the number. Ask what date or outcome they need, then offer two or three options that trade scope against time, each with its assumptions, and let them choose. Recap the choice in writing.
When is a difficult boss a reason to leave?
When the behaviour is abusive (shouting, humiliating, discriminating) and nobody acts after you report it, or when it is harming your health. Difficult is something to manage; abuse is something to escape.
Sources
Only you and the owner see your answer and rating. Send private feedback
Enjoyed it? Support fx-blog with a coffee.
Related posts
Build the Ship You Want to Sail On: Culture and Giving Back
If a team's good habits live only in its lead, it works only while the lead is in the room. Repeat a few habits weekly: specific thanks, a calm reply to bad news, sponsoring people for real chances, and handing on what you learned.
Manage the Team: Goals, Trust and Delivery
Eleven goals nobody remembers, and a red result found in week 12, cost a lead the team's focus and the boss's trust. Set a few measurable results with one owner each, send a five-line update weekly, and report red early with a plan.
One-to-Ones That Matter, and Handling Conflict
Skip one-to-ones and you hear about trouble when someone stops coming to standup. Hold them weekly with their agenda first; when two people clash, talk to each privately, then together, and end on a shared rule, not a winner.
Comments
Oldest firstNo comments yet. Start the conversation.
Calm Sea ended with Pip passing probation, and a storm warning: the Red Fox's biggest client had a new director. Everyone calls him the Admiral. Thursday, 10:00, first meeting. He has Pip's estimate for the refund feature in front of him.
"Eight days?" He crosses it out. "Three."
Dev Voyage: Open Ocean, in six parts:
The number was never the argument
The Admiral is the client's director, not Pip's manager. On an outsourcing team that hardly matters: he sets dates and approves the work.
Outside, Kit said the line that saved Pip's week: "Don't argue the number. Bring options."
In Managing Your Boss, John Gabarro and John Kotter argue that your boss has goals and pressures of their own, and the relationship works when you understand them. So Kit asked the Admiral's team one question: what does he need, by when, and why?
The answer: the client had promised its board that customers could request refunds before the holiday sale on 1 December. He didn't care about eight or three. He cared about that date.
Which kind of difficult?
"Difficult boss" covers people who need opposite responses, so name the kind before you react.
The Admiral was the first kind. That's good news. Pressure is something you can work with.
Answer with options
An estimate is a range with assumptions, and early on the range is wide. Construx's cone of uncertainty puts early estimates as far as four times too high or too low. One number hides that. Options show it.
Basecamp's Shape Up adds the other half: fix the time you're willing to spend, the appetite, and let the scope flex. Pip wrote three options that evening. On an outsourcing team, dates are a promise from the whole ship, so Kit read them first and sent them.
He replied within ten minutes: "C. Good." He got a date he could trust, and the crew got a scope they could build.
Then one more message the same day, recapping what was agreed and what it depends on. People under pressure forget meetings. A written recap makes a changed mind visible.
Try it
Next time a demand lands:
The refund feature shipped on time. But after the next demo, Pip overheard the Admiral tell Ollie, the product manager, that her updates were "hard to follow". Nobody told her what that meant, and she doesn't know how to ask without it turning into a fight. Part 2, Feedback Both Ways: Asking For It and Giving It, is how she finds out.
Read this with your AI