G Ragu Review

Updated September 2026: in 2020 I wrote about my manager promising leadership a deliverable within two days, over a weekend, without asking whether I was available, then pushing me for a draft before any real information arrived. I have rewritten it as a guide to handling a deadline someone else promised for you.

Leadership had criticised my manager for collecting irrelevant information and wasting a week. He promised to share everything they wanted within two days, which fell on a weekend, without checking whether I was free. I had no choice but to work the weekend while he chased the account owners. Before any information came back, he pressed me for a draft, and at one point I had to raise my voice and ask him to stop until there was something to work with. By the end of the day the account team sent inputs that were vague and did not fit the context. With the time left, I shared a first version with leadership for review.

Why do managers commit their team's time without asking?

Usually under pressure. After criticism, a quick promise feels like a way to recover. It is rarely personal, but the cost falls on the person doing the work.

What should you do when it has already happened?

• Ask what exactly was promised, and to whom.
• List the inputs you need and who must provide them.
• Agree a realistic first version, such as a draft with gaps clearly marked.
• Set check-in times instead of constant chasing.

How do you push back without an argument?

Name the dependency calmly: "I can build the structure now, but the numbers depend on the account team. I will fill them in as soon as they arrive." That makes the blocker visible without blaming anyone. Raising your voice may feel justified, but it rarely helps next time.

What do you do with vague inputs?

Use what fits and flag the rest. Mark unclear figures in the draft and list the questions for the account team. Leadership would rather see an honest draft with gaps than a polished one built on guesses.

How do you prevent it next time?

Talk to your manager after the deadline, not during it. Ask to be consulted before commitments that need weekend work, and agree how much notice you need. Framing it as avoiding a rushed result usually lands better than a complaint.

Keep reading

• Caught Between Your Manager and the Client Team
• Said Yes Too Fast at Work? How to Weigh a Request
• Assigned to a New Team Overnight: First Steps

Updated September 2026: in 2020 I wrote about returning from a long vacation to an opportunity where my manager's suggestions kept being rejected by the onsite team, there was no offshore support, and the two sides argued over small things. I have rewritten it as a guide to working between a manager and a client-facing team who do not get along.

After my long vacation, my manager put me on an opportunity with the team I found hardest to work with. He shared inputs that did not match the client's requirements. I worked hard to collect the slides he asked for, and the onsite team rejected them all because they conflicted with what the client wanted. The onsite team then shared new direction, with one condition I found hard to accept: no offshore support at all. My manager tended to complicate simple things and suggest ideas the onsite team would throw out, and both sides had strong egos and argued over small points.

Why do you end up in the middle?

Because you do the work both sides review. Your manager directs you, the client-facing team judges the output, and when they disagree your effort is what gets thrown away.

How do you avoid wasted work?

• Confirm requirements with the client-facing team before building, in writing.
• Show your manager the confirmed brief, so their suggestions start from it.
• Build a small draft first, two or three slides, and get both sides to agree the direction.
• Keep a change log of who asked for what, and when.

What if there is no offshore support?

Adjust the scope. Tell both sides what you can deliver alone by the deadline and ask them to agree priorities. It is better to cut sections early than to deliver everything poorly.

Should you take sides?

No. Stay with the client's requirements. When your manager's idea does not fit them, say so privately and suggest how to adapt it. When the onsite team dismisses something useful, ask what the client would need to see for it to work.

When should you raise it higher?

If arguments start delaying the deliverable, ask for a short call with a senior sponsor to agree the direction once. Frame it around the deadline, not the personalities.

Keep reading

• After a Good Kickoff: Keeping Project Scope in Check
• Building Proposal Slides That Reviewers Choose
• Said Yes Too Fast at Work? How to Weigh a Request