The Human Cost of "Just One More Thing"

The Day a Teammate Cried in a Meeting

I had a teammate who held more of the program in her head than anybody else on the team. Reliable. Senior. The person you went to when something was unclear.

In a meeting one afternoon she broke down crying. Not from a fight or a hard piece of feedback. From load. The math had finally failed. She had been carrying a stack of "just one more things" from multiple sponsors, multiple peers, and me, and the stack had gotten taller than her week. It showed up in a meeting because that was where she finally ran out of room.

I did two things in that moment. I stopped the meeting. Then I reset her workload in front of the people who had been adding to it, so the resets landed where they needed to land. The reason the second part mattered more than the first was that I had been one of the people adding. The reset was as much for me as it was for the rest of the room.

The lesson was not that I had a fragile teammate. The lesson was that I had been keeping my own running total wrong, and she had been keeping it correctly, and I had been mistaking her composure for capacity.

The Team That Went From Thirteen to Three

A different program. Same shape of problem at a different scale. The team I was leading shrank from thirteen people to three over the course of the work. Some left for other roles inside the company. Some left the company. Some were reassigned during a reorg. The work did not shrink with the team.

I had to keep delivery commitments while the people doing the work disappeared. The honest version of that experience is that I added "just one more thing" to the remaining people every week, sometimes every day, and most weeks they did it. The reason they kept saying yes was not that the asks were reasonable. The reason was that they cared about the work and they cared about each other.

I lost two of them while the program was still running. Not because they were unhappy with me personally. Because the period had cost them more than they could keep paying. The work kept needing to be done. The team kept getting smaller under it. The shrinking did not happen at the end. The shrinking happened in the middle, in the same months I was asking for one more thing. That is what the running total looks like when it fails in real time.

The "Besides Everything Else" Question

There is a phrase teams use that I have learned to listen for. "Do you want me to do this besides everything else I do?"

The phrase sounds like resistance. It is rarely resistance. It is the team telling you the running total has gotten too high. They are inviting you to think about what comes off the list when you add.

The leadership move is not to power through the question. The leadership move is to answer it. I usually flip it back to the function the request came from. Security. Legal. Compliance. Sales. Each of those functions has heard the same phrase from teams in the past. None of them accepted the phrase as a reason to drop the work. They got the work added by tying it to brand, to risk, to revenue, until "besides everything else" became part of how the team worked.

The same logic applies to whatever you are adding. Either tie it to something the team already cares about, so it stops being separate, or accept the answer and take something off. Pretending the choice is not there does not make the choice go away. It just decides who carries it.

What the Running Total Actually Looks Like

The running total is invisible to the leader and visible to the team. The leader and the team are not looking at the same list. That is where the problem starts.

A leader sees a single ask. The team sees the new ask plus everything else on the list, plus the meetings, plus the on-call rotation, plus the personal life that did not stop existing because work got busy. When the leader gets a "yes" from the team, the leader is hearing yes to the new ask. The team is saying yes to a stack the leader cannot see.

The way to make the total visible is to ask. The question is not "can you do this." The question is "if you take this, what comes off." The first question gets a polite yes. The second question gets the truth. Most teams will tell you what comes off if you ask. Almost no teams will volunteer it if you do not.

What to Do When You Have to Add Anyway

There are weeks where you have to add. Surprise risk. Customer escalation. Compliance deadline. The work shows up and the team has to absorb it. You will not always have the option to take something off in time.

Here is what I do in those weeks.

Here is what that last one looks like in practice. I have a teammate I work with now who tends to absorb more than her share. When I can tell she is stressed and carrying too much, I sit down with her and I ask one question. "What are you going to give me?" Sometimes she tells me she is too busy. I repeat the question. "What are you going to give me?" I keep saying it until she starts handing me tasks. The move works because the trust was there before the move. She knows I am asking to help, not to test her. She also has the leadership experience to know that handing work off is the right call when somebody asks. She now does it on her own, before the load gets too high, without needing me to start the conversation. The whole move is one sentence, asked into a relationship where the question can land.

A team is finite. The running total is real, even when only the team can see it. When you add, subtract something else, on purpose, and say it out loud. When you cannot subtract, name the cost. When the math fails, repair it. The work you can do as a leader is to keep the total honest. That alone is enough to keep most teams together through hard weeks.