I would bring up an issue with the project. Something real — requirements that did not exist yet, a date nobody had checked, work that could not start until someone above me made a decision. And my manager would say: “Sounds like we need a happy hour.”
That was the answer. Not a plan. Not a decision. Not even a disagreement. Drinks.
This is Part 3 of a series about my eleven years as a Disney cast member. Part 1, The Storage Closet, is the accommodations bill. Part 2, No Conference Rooms, is the absurdity bill. This one is about accountability, and the claim is not that I worked for one bad manager. The claim is that the organization was built so accountability could only flow in one direction. Leadership hoarded the decision-making power and distributed the responsibility. Down.
The Happy Hour Method
Understand what the phrase actually did. A problem raised in a meeting demands something — an owner, a decision, a change. A problem carried to the bar demands nothing. The issue was never argued with. It was dissolved. The unspoken instruction was to drink it off and not bring it up again.
It trained us. Raising a problem got you a social event; it never got you a solution. So the team learned what any team learns under that arrangement: live with it. Avoidance was not my manager’s personal quirk. It was the culture he was building, and culture flows downhill faster than any mandate.
I will be honest about what that cost, because it belongs on the record. The only sanctioned way to cope was the bar, and the method worked on me. I found myself drinking too much just to get through the weeks. I was not alone — others on the team came to lean on alcohol the same way, for the same reason. When the official solution to every problem is a drink, people learn the lesson.
The Lead Who Carried the Blame
For part of my time there, I was a lead software engineer. On paper, that is a position of authority. In practice, I had none. I could not slow the project down and I could not change course — my manager told me directly that we could not do either. What the title came with instead was the blame. When something did not make it to production on time, whatever the actual cause, it landed on me.
The rules engine was the clearest case. I told them, many times, that we needed to slow down because the business team did not know what they needed yet. That was not a knock on our business partners — as I wrote in Part 2, not yet knowing what you do not know is how real projects begin. But leadership had already told people, without checking with anyone who would build it, that the rules engine would be in production soon. So the dates were set by the promise instead of the work, and we were forced to chase them. This was the same manager who needed to see movement on the rules engine. I was never listened to. I was talked down to.
So I stepped down. Voluntarily, from lead to senior, with a sizeable pay cut. The title carried no power and all of the blame, and I paid my own money to put it down.
Here is what the organization did next: nothing. They did not backfill the lead position. They did not cut any scope from the project. The team was expected to pick up the slack, and I was expected to keep doing everything I had been doing. They were happy to give me a paycheck and keep demanding the same of me.
Paid in Full Regardless
Below the manager, the same vacuum. We had constant problems with vendors not doing their jobs. Nothing happened to them — no correction, no escalation, no consequence. They simply remained until their contracts expired. The expiration date did the job that management would not.
We hired a business analyst who was supposed to own requirements — the one thing this team needed more than anything, as the rules engine kept proving. Nobody defined the role, nobody coached it, nobody corrected it, and it shrank into glorified note-taking that software could have done better and cheaper. Her camera would flick on by accident in meetings and she would be sitting in the front seat of her car. Regularly. Nothing ever happened, and she made her money through the contract regardless. That is less a story about her than about the vacuum around her. In an organization with working feedback loops, someone notices, someone coaches, someone corrects. Nobody did any of those things. Nobody was watching anybody.
The Money Speech
Then the same manager complained to the team that we were running out of money.
Consider what the money had gone to. Contracts that coasted to their expiration dates. A requirements role that produced notes. And hires we did not need — because this manager insisted on adding team members, on the theory that a developer is a developer, interchangeable units you can swap in and out at any point. That is not how it works anywhere, and it is especially not how it works on a twenty-year-old legacy system with deep tech debt and very little documentation. The knowledge lived in people’s heads. A new developer was a long, expensive ramp, not a plug-in part.
It was the same belief that made my empty lead position feel free. If developers are interchangeable, you never need to replace one — the rest can simply absorb the work. One belief, two costs: paying for people we did not need while declining to replace the one we did.
And the bill for all of it was presented to us, as a grievance, by the man who had signed it. We were running out of money. We needed to understand that.
The Pattern
None of this was new information by then. I had been written up for an involuntary autistic meltdown while nobody answered for the accommodation request closed out during my medical leave. Specs changed retroactively and the team absorbed it without a word. Deadlines bore down and leadership went home early. We were promised first dibs on seating at KP2 and were moved again within months.
The last time I raised a problem in that job, I already knew what the answer would be.
The drinks arrived. The problem did not come up again.
