Ninety Days Is Enough to Prove It

There is a pattern in how organizations approach culture work, and it goes something like this: someone at the senior level acknowledges that there's a problem. Maybe the engagement scores have dipped. Maybe there's been a high-profile departure. Maybe the CEO has a gut feeling that something isn't right. A conversation starts. Options are explored. And eventually, a decision is made to bring in outside support.

What follows is usually a twelve-month engagement with a consulting firm or a series of coaching sessions that stretch across the better part of a year. Timelines are loose. Milestones are subjective. And somewhere around month eight, the board or the CEO starts quietly wondering: is this actually working? Has anything changed? Because it doesn't feel like it.

I think ninety days is enough to prove it.

 The problem with long timelines

Long consulting engagements persist because they serve the consultant, not the client. A twelve-month contract provides revenue certainty for the provider and a comfortable sense of action for the organization. We're working on it. We've hired someone. The project is underway. These are satisfying things to say in a board meeting. They feel responsible.

But long timelines also provide cover. When the results are expected to take a year, there is no urgency at month three. There is no accountability at month six. The work exists in a permanent state of "in progress," and the moment someone asks whether it's making a difference, the answer is always: we need more time.

I've watched this play out across industries and countries. The work is earnest. The consultants are credentialed. The PowerPoint decks are impressive. And the organization, twelve months later, is functionally the same. Because the work was never designed to produce measurable change in a timeframe that demands accountability. It was designed to produce activity.

 What ninety days forces

When you commit to showing measurable impact within ninety days, everything about the work changes.

The scope gets sharper. You cannot boil the ocean in three months, so you have to choose. Where is the dysfunction most visible? Which team, which leader, which dynamic is creating the most drag on the organization right now? Ninety days forces precision, and precision is the enemy of vague culture work that tries to change everything and changes nothing.

The measurement gets real. You have to define what "better" looks like before you start, not after. That means baseline data. Specific metrics around whether people speak up, whether feedback flows upward, whether leaders are creating the conditions for honesty. Numbers that you can revisit at day ninety and compare to where you started, so that the conversation about progress is grounded in evidence rather than anecdote.

And the accountability gets tight. When the timeline is ninety days, there is no hiding behind "we need more time." Either the needle moved or it didn't. Either people report that something has shifted or they don't. The results are visible, and they're visible quickly enough that the board, the CEO, and the organization can make an informed decision about whether the work is worth continuing.

 What you can accomplish in ninety days

I know the objection. Culture change takes years. You can't fix deep-rooted dynamics in three months. And that's true, if your definition of "fix" means permanent transformation. But permanent transformation doesn't start with a twelve-month plan. It starts with a proof point. A demonstration that this kind of work produces tangible results in a timeframe that matters.

In ninety days, you can measure a baseline of how honestly people communicate across a team or a leadership group. You can surface the specific patterns that are preventing honest conversation - the unwritten rules, the risk calculations, the behavioral habits that keep people quiet. You can build and begin practicing new agreements about how the team works. And you can measure again, at day ninety, to see whether the experience of being on that team has actually changed.

These are not soft outcomes. They are measurable, reportable, and board-ready. When a CEO can go to the board and say, "Three months ago, thirty-two percent of this team felt they could speak honestly about problems. Today, that number is fifty-eight percent. Here's the data, here's what we did, and here's the plan for the next phase" - that is a fundamentally different conversation than "we've been working with a consultant for a year and we think things are improving."

 the commitment this requires 

Ninety days is enough to prove the work, but only if the work is done with genuine rigor. That means the CEO is involved, not as a sponsor who checks in quarterly, but as an active participant who models the vulnerability and accountability being asked of everyone else. It means the measurement is honest, not designed to produce a favourable result. It means the organization is willing to hear what the data says, even if the data points to uncomfortable truths about specific leaders or specific behaviors.

This is the part that most organizations struggle with. Not the timeline. The exposure. Ninety days doesn't give you anywhere to hide. It doesn't give you the luxury of hoping things will get better on their own. It demands that you look at the data, name what you see, and decide what you're going to do about it.

 Proof, not promises

I work this way because I believe that organizations deserve evidence, not promises. If the work I do doesn't produce measurable change within ninety days, you should stop paying for it. If it does produce measurable change, you have a proof point that justifies deeper investment - not on faith, but on results.

The question for any CEO considering this kind of work is simple: would you rather have a twelve-month plan that promises change, or a ninety-day commitment that proves it?