--- title: "Working With a Difficult Boss Without Losing Yourself" author: "Harry" published: 2026-10-31T04:50:11.251Z updated: 2026-10-31T05:08:24.255Z category: "Career & Teams" tags: [] canonical: "https://fxblog.dev/posts/how-to-deal-with-a-difficult-boss-developer" --- # Working With a Difficult Boss Without Losing Yourself ## 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. > **TL;DR** When a boss or client cuts your estimate, arguing the number loses twice: you lose the argument, then you miss a date you never agreed to. How to deal with a difficult boss: work out which kind of difficult you face, find the pressure behind the demand, and answer with options that trade scope for time. Shouting and humiliation are different: write them down and report them. > > **Do this:** Next time a demand lands, ask what date it is for, then reply with two or three options, each with a date and its assumptions. 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:** 1. **Working With a Difficult Boss Without Losing Yourself** (you are here) 2. **Feedback Both Ways: Asking For It and Giving It**: feedback you can use. 3. **Say No Without Making Enemies, and Keep Your Energy**: trade, don't refuse. 4. **Keep Learning: Bringing New Tools (and AI) Into Real Work**: a fair pilot. 5. **Talk to the Business: Working With PMs and Non-Engineers**: impact first. 6. **Ask for the Raise: Showing Your Value Without Bragging**: evidence and a number. ## 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. > **Note** > > **Pip:** But the sandbox, the tests... > **Admiral:** Three. > **Kit:** Give us until tomorrow. We'll bring options. 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. | Kind | What it looks like | What helps | | -------------- | --------------------------------- | -------------------------------------- | | Under pressure | Short, demanding, moves dates | Find the pressure; bring options | | Unclear | "That's not what I meant" | Write the ask back before starting | | Micromanaging | Checks every step | Update before they ask | | Absent | Decisions stall | "Unless you object by Friday, I'll..." | | Abusive | Shouts, humiliates, discriminates | Not a style: document and report | ![A difficult boss, sorted: under pressure, unclear, micromanaging or absent each get their own response; abusive behaviour goes to documentation and HR, not to coping](https://fxblog.dev/media/01a1904a-c2c0-77b3-b749-c3e0c0c9e53d/1600) _Which kind of difficult, and what helps_ The Admiral was the first kind. That's good news. Pressure is something you can work with. > **Warning** > > Shouting, humiliation, threats and discrimination are not a difficult style to manage. Write down what happened, when, and who saw it, and take it to your lead or HR. If nobody acts, leaving is a reasonable answer. ## 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. ```text Thanks for explaining the 1 December sale. Three options: A) Full self-service refunds in the app: 8 days. Ready 14 Nov. B) Staff-only refunds, support clicks "refund" in admin: 4 days. Ready 7 Nov. C) B now, then A after the sale. Assumes the payment sandbox is available by Monday. We recommend C. Which would you like? ``` 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: 1. Name the kind of difficult before you answer. 2. Ask what the demand is for: which date, which promise, which number they're measured on. 3. Reply with two or three options, each with a date and its assumptions, and say which you recommend. 4. Recap the decision in writing the same day. 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 ```text Read the post "Working With a Difficult Boss Without Losing Yourself". 1. I'll describe my boss's behaviour. Help me work out which kind of difficult it is. 2. I'll paste a demand I received. Draft three options with dates and assumptions. 3. Write a friendly same-day recap of the agreement for me to send. ``` > **Success** > > You can tell what kind of difficult you face and answer pressure with options instead of arguments. Next: **Feedback Both Ways: Asking For It and Giving It**. ## 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.