Please Fix Everything. Budget Pending.

Please Fix Everything. Budget Pending.

The pitch was clear. They had a mess. They knew it was a mess. They needed someone with enough experience and judgment to come in and sort it out, and they understood that kind of work would require real authority and real support.

Then you start.

The support is taking a little longer than expected. The additional people are still being discussed. The budget will be clearer next quarter. Everyone remains very committed, though. They want you to know that.

A few months later, nobody mentions the promised support unless you bring it up.

Meanwhile, the thing you were hired to fix turns out to be older, larger, and considerably worse than anyone described during the interview. The authority shown on the org chart bears little resemblance to what you are actually allowed to decide. Every request for resources gets some version of let’s revisit that next quarter, as if quarters are a natural resource and the company is waiting for another one to grow.

Eventually, the job you accepted and the job you are doing stop being the same job.

That is when the question arrives: Was I hired to solve this, or to be the person standing next to it when it failed?

First, support means something

Companies love the word support because it can mean almost anything. It can mean budget and headcount. It can also mean someone nodding warmly while explaining why you will receive neither.

Being set up to succeed is not a feeling. It is a set of conditions you can check.

1. A mandate everyone can describe the same way. You should be able to state the job in one sentence, and your boss should give roughly the same sentence if asked separately. If those answers do not match, everything underneath them will move whenever it becomes inconvenient.

2. Budget and people attached to the mandate now. Not after the next planning cycle. Not once you have demonstrated progress with the team you do not yet have. If the work requires ten people and you have four, enthusiasm does not close the gap.

3. Decision rights that match the accountability. If you can be blamed for the outcome, you need enough authority to shape it. Owning a result while every meaningful decision belongs to someone else is not leadership. It is being assigned the consequences.

4. Access to the person who actually decides. A skip-level meeting once a quarter is not access. You need a real line to whoever can approve the resources, settle the argument, or decide that the work continues when priorities shift.

5. An honest account of what is broken. This includes the embarrassing parts, the political parts, and the problems everyone has quietly agreed not to mention. If you are learning about major failures from your own team several months after starting, you were not given the job. You were given the public version of it.

6. Someone above you whose own success depends on yours. This is the condition people check least and the one that may matter most. If nobody with power loses anything when your work fails, your resources will always be the easiest ones to trade away.

7. A written definition of success with a date attached. Not improve the function or build a world-class team. What will be different, by when, and how will everyone know?

Count how many of those conditions you actually have. Not how many were implied. Not how many are still being worked through. How many exist today?

Count the conditions. That number will tell you more than another month of reading the room.

So, were you set up to fail?

Maybe.

That is the honest answer, and I know it is not satisfying.

Sometimes a company deliberately puts someone into an impossible role because it needs a name between the problem and the people who created it. That happens.

Sometimes the company genuinely wants the problem solved and is simply too chaotic to fund the solution. Sometimes the person who hired you meant every word and then lost a budget fight two levels above you in a meeting you will never know occurred. Sometimes your boss is kind, sincere, and not particularly good at being a boss.

Those situations have very different intentions. From inside your calendar, they look almost identical.

The same meetings get postponed. The same positions remain unfilled. The same decisions require six approvals. The same goals stay in your performance plan even after the resources disappear. Whether somebody planned the conditions or merely failed to prevent them, you still wake up inside the same job.

I have worked in more than one version of this, and I still cannot say with certainty which one I was in each time. Years later, someone told me that a situation I had understood as malice was mostly ordinary incompetence. I believed her. It changed how I felt about that period of my life without changing a single thing that happened during it.

Different intentions can produce identical working conditions. From inside the job, you may never know which one you got.

The motive does not change the job

Letting go of the question is not an exercise in emotional maturity. It is a practical decision.

The answer does not change your position.

Unsupported is unsupported. A role you cannot succeed in because someone arranged it that way and a role you cannot succeed in because nobody bothered to arrange anything are still the same role. Your days are the same. The missing people are the same. The decisions you cannot make are the same.

The outcome may be the same too.

And this is the part that actually stings: unless you create a record, the history will eventually read the same way.

The problems that existed before you arrived become problems that continued under your leadership. The headcount that never appeared becomes your inability to build the team. The mandate that changed three times becomes a lack of focus. The authority you were never given will not appear anywhere beside the results you were expected to produce with it.

The organization’s version will be shorter than the truth, and the short version usually wins.

So stop spending all your energy trying to determine the motive. Pay attention to the conditions, because you can observe them. Pay attention to the record, because you can still affect it.

Unsupported is unsupported. The days are the same, the outcome may be the same, and the record will not explain the difference for you.

Why the hardest job goes to the person least able to refuse it

This does not happen evenly.

The severely underfunded turnaround often gets presented as an opportunity to someone who has been made to wait longer than their peers for that level of opportunity. After hearing no enough times, a yes can be disorienting. You are so busy proving that you deserve the job that you forget to ask whether the job deserves you.

You are grateful, and grateful people do not ask nearly enough questions.

You do not push hard on budget because you do not want to seem difficult before you have even started. You accept vague promises about headcount because the title is real and the problem is interesting and surely nobody would hire you to do work they had no intention of funding.

Surely.

If you are coming from outside the organization, you also lack the protection an insider would have. The insider has years of relationships, history, and people willing to explain what really happened. You have an impressive title, an orientation deck, and a calendar full of introductions.

None of this requires a conspiracy. It is what happens when the hardest job goes to the person with the most to prove and the least room to refuse it.

The hardest job often goes to the person with the most to prove and the least protection if it fails.

Before you sign

Ask the seven questions out loud.

Do not present them as demands. Ask them plainly and listen to how specific the answers are. An organization that has seriously planned the work will usually answer quickly. An organization that has not will become warm and vague.

Warmth in response to a specific budget question is an answer.

Ask what has already been approved. There is an enormous difference between we have six open positions and we intend to request six positions in the next planning cycle. One is a resource. The other is a hope wearing a spreadsheet.

Ask why the last person left. Then, if possible, speak to them. People will tell you a remarkable amount in twenty minutes once they are no longer responsible for protecting the organization’s version of events.

Ask what has changed besides the person taking the job. Did the budget change? Did the reporting structure change? Did the people who repeatedly blocked the work lose the ability to block it? Did leadership make any decision that would cause this attempt to end differently?

If the answer is that nothing changed except the name in the role, you are not being sent in to fix the system. You are being added to it.

If you are already in it

You may have accepted the job while suspecting some of this. Plenty of people do. Months of searching will beat principle. A paycheck matters. An imperfect offer can still be the only offer available, and I am not going to pretend that math does not exist.

But once you are inside, stop relying on the organization to preserve the starting conditions accurately.

Write down what you inherited. Do it during the first few weeks if possible and later if it is not. Keep it factual: staffing, systems, outstanding risks, missing decisions, existing commitments, and what was already failing when you arrived. Send the assessment to your boss with a date attached.

This should not read like a defense document written by someone expecting to be fired. It should read like a competent leader establishing the baseline. Six months later, that distinction may be the only reason anyone remembers when the problems actually began.

Get the mandate in writing, even if you are late. Send one clear paragraph: this is what I understand the goal to be, this is what success looks like, and these are the resources or decisions required to get there.

If the reply is vague, you have learned something. If nobody replies, you have learned more.

Find one win that can survive the larger story. The entire turnaround may not be salvageable, but something inside it usually is. One team, one system, one process, one measurable change that can be explained to a stranger in two sentences without requiring the entire tragic backstory.

That is the difference between leaving an impossible job with nothing you can cleanly claim and leaving with one real thing nobody can take away from you.

Set your exit condition while you are still clearheaded. Choose the event and the date. If the promised positions are not approved by a certain point, you start looking. If the mandate changes again without resources, you start looking. If the decision rights still do not match the accountability, you start looking.

Do not wait until that date to decide what the date means. By then you will be exhausted and absolutely convinced you are two weeks from turning the corner.

That feeling has purchased more unpaid loyalty than any company benefit ever invented.

Keep one person outside the organization who knew your work before this job. Talk regularly enough that they understand what you inherited and what you are actually accomplishing. If the ending becomes ugly, you need someone whose opinion of your ability was not formed inside an impossible situation.

Sometimes the most valuable thing another person can do is remember who you were before the job started teaching you not to trust yourself.

What none of this guarantees

I would like to tell you that doing all of this protects you. It does not.

It improves your odds. It protects parts of the record. It may help you recognize the situation earlier and leave before it takes more than you intended to give.

Sometimes you do everything right and the work still fails. It still lands on your history. You still spend the next few years trying to explain a complicated situation in an interview while the person who denied the budget explains nothing to anyone.

What I can tell you is that Was I set up to fail? is the wrong question to spend years trying to answer.

I spent too long trying to solve for intent because I thought it would tell me whether I was allowed to be angry. It never told me what to do next. The missing headcount did. The disappearing authority did. The promises that kept moving into another quarter did.

The useful question was always whether the conditions for success existed. That was something I could have answered much earlier if I had known what to count.

Now you know what to count.

The resources may remain pending forever.

Your accountability will not.