The Almost-Request: How Good Teams and Leaders Miss Each Other

Under every complaint is a need that isn't being met.

Unfortunately, too many of us hope that our needs will be met by voicing our complaints alone. 

We once had a manager in one of our Trauma-Informed Leadership workshops—we'll call him Cole—who spent three months trying to get his team to meet their deadlines. He raised the missed dates in meetings and pointed out the status updates had stopped coming. He told the team they struggled with follow-through, and frustrated, admitted out loud that he wished people cared more about the work. 

What Cole was making, over and over, is what we call an Almost-Request. An Almost-Request puts an idea out there without naming the need directly, or eliciting a commitment from anyone to meet the need itself. 

Almost-Requests sound like…

• Complaints: "Nobody ever sends updates around here."

• Observations:"I noticed nobody's sending updates anymore."

• Passive-Directives: “Updates need to happen weekly.”

• Hints and Wishes: “It would be nice if someone would send an update.”

• Generalizations:“This team really struggles with communication.”

• Suggestions:“It might be helpful if someone sent updates.”

They feel like speaking up, and they feel direct, since the thing is named directly, however they do not cross the threshold into determining how the need will be met, or by whom. 

Making a direct request is a vulnerable experience. Direct requests can be refused. There can be open pushback, opening the asker to feelings of powerlessness in front of others. It opens the asker up to potential criticism, just for making the ask. Without crossing into the threshold of directly asking someone for what they need, Almost-Requests protect the speaker from rejection, vulnerability, conflict, accountability, and power exposure.

Cole struggled to make direct requests and to secure commitment from others on the team to get those needs met. In our sessions, he practiced getting under his complaints, setting aside judgements (“It’s their job! They should know better!”), and identifying the need under the complaints. Once he was able to articulate precisely what was needed, he practiced delivering the request, without couching, hedging, or softening, and then took it back to his team to deliver.

“Every Friday, I need to report to senior management on the progress our team is making. It’s crucial that they understand that we’re making progress so that we can continue to receive sufficient funding. Without this funding, our initiative will cease to exist. I need a status report from every Team Lead by Thursday at noon so I can prepare. Team Leads–are you able to get me the report by Thursday at noon?”

The Team Leads looked at each other, and looked at him. Finally, one spoke up: “What report?”

Cole was shocked. Did they not know what a report was?

“Not like, a formal report… I just need you to give me an update. What your team has accomplished in the last week, and what’s on the docket for next week. I just need to be able to communicate this with my manager.”

They looked at each other, and back at him again. 

“Like, Hey Cole, this week, my team finalized the dates for the annual retreat, secured a venue, and reached out to vendors for abc. Next week we’re focusing on xyz. It doesn’t have to be that serious, I just need to know what we’re doing.”

What caught him off guard was their relief. The room exhaled. The vague disappointment they'd been living inside for months finally had a question they could answer. They had known he was unhappy–now they knew precisely what he wanted.

“That’s it? Two sentences in an email? Gladly. Thursday at noon is no problem.”

For months, Cole had caught flack from his supervisors for not being able to report up the chain knowledgeably about what his team was accomplishing, and he had been certain his team was the problem. They weren't following through. They didn't care enough. They should have known better. What he discovered, in the space of one direct request, was that they had no idea what he wanted. Further, they were downright relieved when they learned how easy it would be to deliver on the ask.

The Almost-Requests are devastatingly costly. Not only do they fail to get the need met, they routinely build confusion, resentment, and stories in the meantime. Every unanswered complaint becomes evidence: they don't care, they can't be trusted, the problem is them. Resentment and judgement accumulate in the gap between what we need and what we're willing to ask for, and we mistake that judgment as factual information. The story we build to explain the unmet need becomes more real than the need itself—we orient from connection to our team to protection from the people we are convinced are doing something negative on purpose.

Cole's team was never the problem. The problem was a need that never made it into a request. The gap between what we feel and what we're willing to ask for is where trust quietly erodes, where capable teams stall, and where good leaders convince themselves the fault lies in everyone but them. 

Learning to find the need beneath the complaint—and to make the request that meets it—is some of the most practical work we do inside our Trauma-Informed Leadership programs. 

If your team keeps circling the same frustrations without resolution, let's talk about getting underneath them.