Early in building this company I thought a maybe was a generous answer. Someone would bring me a proposal, I was not sure, and rather than shut it down I would say "let me think about it" or "let's revisit next week." I believed I was keeping options open and protecting the team from a hasty call. What I was actually doing was freezing five people in place while I enjoyed the comfort of not committing. It took me longer than I would like to admit to see that a maybe is rarely a kindness. To the person waiting on it, it is paralysis with a polite face.
The core mistake is a failure of perspective. From the leader's chair, a maybe feels low cost. You have not closed any doors, you can still change your mind, and you have spent nothing. From the team's chair, the same maybe is expensive in a way the leader almost never sees. Work that depends on the decision stops. People hedge their bets, doing half of two plans instead of all of one. Nobody wants to invest fully in a direction that might evaporate, so everything proceeds at half speed and nothing ships clean.
A maybe is a decision to do nothing, charged to someone else
Here is the reframe that changed how I lead. A maybe is not the absence of a decision. It is a decision to keep everyone waiting, and you have charged the cost of that decision to your team rather than carrying it yourself. When I say "let me think about it," I have decided that the engineer cannot start, the designer cannot finalize, and the deal cannot move. I just have not labeled it as a decision, so I get to feel like I avoided the responsibility while still imposing the consequences.
Run the math on it. Say a maybe holds up four people for a week while they wait. That is a person-month of fully loaded capacity spent on hedging and idling, and it produced nothing. I would never approve a project that cost a person-month and shipped nothing, yet I used to authorize exactly that several times a week without noticing, simply by declining to decide. Decisiveness is not about being fast or reckless. It is about refusing to make your indecision someone else's problem.
Why a clear no is a gift
People assume that a no is the harsh answer and a maybe is the gentle one. It is the reverse. A clear no is one of the kindest things a leader can offer, because it returns time and certainty to everyone involved. When I tell someone no, cleanly and with a reason, they get to stop. They redeploy their energy. They take the idea elsewhere, improve it, or move on without resentment. A no closes the loop. A maybe leaves it open and bleeding.
The version of no that builds trust is specific. Not "I don't think so," which is just a slow maybe, but "No, we are not doing this, because it pulls focus from the launch and the upside does not justify that this quarter." Now the person knows the real constraint. They might come back next quarter, or with a version that respects the constraint, and that is a productive conversation rather than a stalled one. I have had people thank me for a no, genuinely, because it freed them. Nobody has ever thanked me for a maybe.
The few cases where waiting is the right call
I want to be precise, because decisiveness gets misused as an excuse for snap judgments, and that is its own failure. There are real situations where the honest answer is "not yet," and the discipline is to make that a genuine decision rather than a dodge. The test is simple. If you are waiting because more information is arriving on a known date and that information will change the answer, waiting is legitimate. Name the date. "We will decide on Thursday once the usage numbers land." That is not a maybe. That is a decision with a deadline attached.
The poison is the open-ended maybe with no trigger and no owner, the one that drifts because deciding is uncomfortable. If you cannot say what you are waiting for or when the wait ends, you are not gathering information. You are avoiding a choice, and the team can tell the difference even when you cannot.
How we keep decisions from rotting
The practical fix is to make open decisions visible so they cannot quietly rot. We track meaningful decisions the way we track work, with an owner and a date by which an answer is due. When something has been sitting in maybe for too long, it surfaces, and someone has to either decide it or set a real deadline for deciding it. We run this inside Atlas alongside the projects the decisions block, so a stalled call is never invisible. The point is not the tool. The point is that an undecided thing should never be allowed to hide.
I also try to model the behavior at the top, because decisiveness flows downhill or it does not flow at all. If I sit on calls, every manager learns that sitting is acceptable, and the whole company slows to the speed of its most hesitant leader. When I decide quickly and clearly, even when I am only 80 percent sure, people learn that a direction is safer than a fog. You can correct a wrong decision once you see it move. You cannot correct a maybe, because it never moves at all.
The discipline underneath good management
The hardest lesson I have learned as a CEO is that protecting my own comfort is not leadership. A maybe protects me. It lets me defer the discomfort of choosing and the risk of being wrong. But leadership is precisely the willingness to absorb that discomfort so the team does not have to. The job is to take the ambiguity onto myself and hand back clarity, even when the clarity is a no the person did not want to hear.
So my rule now is plain. Give people a yes, give them a no, or give them a date. Never give them an open maybe and call it kindness. The next time you feel the urge to keep your options open, ask who is actually paying for that option to stay open. It is almost never you. Decide, and let your team get back to work.