The Room That Was Too Quiet

The Scene

The conference room was too quiet for a room that size.

I was being introduced as a consultant brought in to help with operational efficiency and growth. Ten, maybe twelve people. Most of them had been there for a decade. The silence was not polite — it was the particular silence of people waiting to find out whether their jobs were safe. Some were thinking: will being more efficient mean fewer roles? Some were thinking: how can you fix something this manual, this cumbersome? A few, I am certain, were thinking: she will not last here. We are too broken.

It was a small EdTech company serving K-12 schools across the US. Fewer than fifteen employees. Revenue under two million dollars. Every new client they brought on added cost rather than leverage, because the systems holding the business together were not systems at all. They were people. Specific people, carrying specific knowledge, with no documentation and no redundancy. One resignation away from institutional collapse.

I had spoken at length with the CEO before taking the role. I understood what he wanted to build. What I did not yet know — what I needed to discover for myself — was what the people inside the building were actually living.

The Weight

A month in, I had spoken with every member of staff. I had worked through every business system, every process document that existed. The picture that emerged was not the one the leadership team believed they were sitting inside.

What they believed was that their people were the problem. Unmotivated. Just-enough workers who had to be watched closely, or productivity would fall through the floor. They had promoted employees into VP-level positions over the previous twelve months — people who were talented, loyal, and genuinely committed, but who had not been given the skills or the support to lead. The CRM sat largely unused. Opportunities and pipeline were tracked in spreadsheets. Client satisfaction was slipping. Every day was firefighting.

The reality was something else entirely. The people were working inside a system that gave them no voice, no visibility, and no reason to bring their full energy. They arrived at eight and left at four. Not because they did not care. Because caring had never once changed anything.

There is a meaningful difference between a disengaged team and a team with nothing left to offer. Leadership was diagnosing the first. I was looking at the second. And the distinction matters enormously, because the interventions are completely different.

The Hinge

The conversation I needed to have first was with the CEO. Not the board. Not the leadership team. Him.

I sat down and told him it was worse than he thought. Not unkindly. But clearly. The words I used were not comfortable ones: toxic environment, single points of failure, right people in the wrong seats, a leadership culture built on fear rather than trust. He pushed back initially. That is a reasonable response when someone is telling you that the organization you built with years of your own effort is in a more fragile state than you realized. Then he went quiet. Then he asked me what I thought we should do.

That is the hinge. Not the assessment — the question that follows it. The moment a leader stops defending and starts listening is the moment real work becomes possible.

Next came the leadership team. I had spent weeks building relationships with each of them — through active listening, genuine support, and the kind of honest collaboration that earns trust before it asks for anything. So when I delivered the assessment of the current state, I watched them absorb it. I saw sadness. Disappointment. The specific weight of people who had worked hard and believed in what they were building, now hearing that it was not what they had thought it was.

And then I saw something else. A spark. The particular energy of people who realize they are being handed the chance to actually fix it.

One of the VPs turned to the CEO and said: we need to hire Michelle as our full-time COO. We need to build a culture we can be proud of — one that is a differentiator in the industry. A culture of genuine care.

That is the moment I think about most, looking back. Not because of what it meant for me. Because of what it revealed about them. They had been waiting for permission to want something better.

The Work

The real work looked nothing like a methodology. It looked like walking the office every morning before sitting down. Stopping to ask what the day looked like, what was in the way. Eating lunch with people and learning what was going on in their lives outside of work. Treating them like people, not productivity units.

We built continuous improvement teams — not a program, a practice. The people doing the work had direct input on what to fix and how. We documented processes. We completed system configurations that had been left half-built for years. We trained employees to champion the tools rather than work around them, and we rebuilt the visibility that the business desperately needed: client satisfaction data, pipeline metrics, the numbers that tell you whether you are growing or simply surviving.

We celebrated wins. We stopped calling things failures and started calling them lessons to course-correct on. The language changed before the systems did, and the language mattered.

I worked with the leadership team one to one. Not to critique them — to grow them. Strategic vision. People leadership. The daily discipline of celebrating your team’s impact rather than cataloging what still needs to be done. These are skills. They can be taught. They can be practiced. They are not character traits you either have or do not.

Technique beats force every time. I teach kickboxing, and the principle is identical in both settings. You cannot push a culture into health. You build the conditions — voice, accountability, genuine visibility — and you let it move toward them. That takes longer than a spreadsheet suggests. It is also the only approach that actually holds.

The Human

Who this mattered to most was the employees. Every one of them, regardless of role or title.

The shift that happened over those months was not the one I had been brought in to deliver. The CEO had hired me to improve operational efficiency. What actually changed was that people found their voices. They started showing up differently — not because of a program or a metric, but because the environment had changed enough that bringing their full energy felt worth the risk. Conversations happened in the building that had not happened before. People laughed. They went to yoga in the park on lunch breaks. They recognized each other publicly, specifically, for work that mattered.

The pressures that had felt like weight became challenges that felt like fuel. That is not a small thing. That is the difference between an organization that drains the people inside it and one that gives them something to move toward.

The Landing

Within twelve months, employee engagement was at an all-time high. Revenue was outpacing expenses for the first time, driven partly by the efficiency gains and partly by the fact that clients could feel the difference in how they were being served.

Then came the harder question: how do you maintain this through growth?

Organic growth is one challenge. Every new person added to a healthy team needs to be the right fit — not just for the role, but for the culture. One wrong hire in a team of twelve is a different disruption than one wrong hire in a team of two hundred. The culture is fragile in proportion to its size, and that fragility demands active stewardship.

Growth through acquisition is another challenge entirely. The culture you built does not automatically survive a merger. It has to be fought for, deliberately, by people who understand what they are protecting and why it matters. That is a different kind of work, and one that many organizations discover too late.

A culture of continuous improvement is not a project with a completion date. It is a daily choice made by everyone in the building, including — especially — leadership.

The Residue

I have since left that organization. Over six years. The relationships I built there — with the employees, with the leadership team, with the CEO who eventually asked the right question — are ones I carry with me.

Some of the people I worked with are still there. Still building. Still choosing the culture we made together, every day, even as the pressures of growth test it. I hear from them occasionally. That is not nothing. In fractional work, you enter a system, change what needs to change, and step back out. You are not supposed to leave a dependency. You are supposed to leave a capability.