The Room Where the Story Was Told

This is a leadership fable, a composite of multiple experiences I have observed across organizations over many years, most recently during the past year’s transitions as people moved into new roles. The characters, the company, and the specific events are fictional. The pattern is real, and I have watched it play out more times than I would like.

Part One: The Operator

David Okafor arrived at Sterling Media Group on a Tuesday in January. It was raining. He stood outside the building for a moment with his umbrella folded under his arm, looking up at the glass facade, and felt a feeling he would later struggle to name. Not confidence exactly, but something close to it. A sense of alignment. He had chosen this company carefully, and they had chosen him, and the work ahead was work he knew how to do.

He was the new Chief Product and Technology Officer. The CEO, Margaret Yoon, had recruited him personally. Over two dinners and a three-hour conversation at her office, she had described what she wanted: a leader who could modernize Sterling’s technology stack, build a real product organization, and deliver the platforms the company needed to compete in a market that was shifting faster than their legacy systems could handle.

“I need someone who can just run it,” Margaret had told him over the second dinner, leaning forward with the focused intensity that made people want to work for her. “I do not want to have to manage the technology function. I want to hand it to someone and know it is handled.”

David had nodded. That was exactly what he did. He ran things. He inherited messes and turned them into functioning organizations. He hired well, built systems, shipped products, and kept the machinery working. At his previous company he had taken a demoralized engineering team of sixty and, over two years, turned it into one of the highest-performing technology groups in the industry. He did not do this through charisma or politics. He did it through craft. Good architecture. Clear priorities. Honest communication with his team. Relentless focus on the work.

His first ninety days at Sterling confirmed everything Margaret had told him. The technology organization was a mess. Three competing code bases for the same product. An infrastructure team that had not upgraded the core platform in four years. A product management function that consisted of two people writing requirements documents that nobody read. An engineering culture built around heroics: late nights, weekend deploys, and individuals who held critical knowledge in their heads because nothing was documented.

David went to work. He did what he always did. He listened first. He spent three weeks in back-to-back meetings with engineers, product managers, designers, and business stakeholders. He sat in on standups. He reviewed the architecture. He read every planning document from the past two years. He ate lunch in the cafeteria instead of the executive dining room because that was where the engineers ate, and engineers told you the truth when they were eating sandwiches and not sitting in a conference room with their boss’s boss.

By the end of the first quarter, he had a plan. By the end of the second quarter, he was executing it. He reorganized the engineering teams around product lines instead of technology layers. He hired a strong VP of Engineering and a Head of Product Management. He killed two of the three redundant code bases and built a migration plan for the third. He implemented a release process that replaced the chaotic weekend deploys with predictable, automated deployments every two weeks.

The results came. They came in the way results usually come for good operators: quietly, steadily, and without drama. Uptime went from 97.2% to 99.8%. The release cycle went from quarterly (theoretically) to biweekly (actually). The engineering team’s attrition rate dropped from 28% to 9%. Three products shipped on time. Customer-reported bugs fell by half.

David tracked these numbers. He put them in his monthly report to Margaret. He mentioned them in his Thursday one-on-one. He felt good about the progress. He assumed Margaret felt good about it too.

He was half right.

Part Two: The Monday Meeting

Every Monday morning at 9:00, Margaret Yoon held a meeting in the seventh-floor conference room, the one with the long walnut table and the view of the river. The meeting had no formal name. People called it “the Monday meeting” or “Margaret’s staff meeting,” but it was not really a staff meeting. Not everyone on the executive team was invited.

The regular attendees were: Margaret. James Hadley, the Chief Revenue Officer. Priya Nair, the CFO. And Tom Breck, the COO.

David was not in the Monday meeting. Neither was Rachel Torres, the Chief People Officer. Neither was the General Counsel.

David knew the meeting existed. He had seen it on Margaret’s calendar. In his second week, he had asked Margaret’s chief of staff, a quietly efficient woman named Helen, whether he should attend.

Helen had paused in a way that told him the question was not as simple as it seemed.

“It is really a business review,” she said. “Revenue, operations, finance. Margaret likes to keep it small.”

David accepted this. It made a kind of organizational sense. Revenue, operations, and finance were the commercial engine. Technology and product were enablers. The business set the direction; technology built the road. He did not see himself as excluded. He saw himself as appropriately focused on execution rather than sitting in meetings where the discussion would not directly involve his work.

This was his first mistake, and he did not know it for eleven months.

The Monday meeting followed the same rhythm every week. James went first. He always went first. He had the kind of presence that naturally took up space in a room, tall, broad-shouldered, with a voice that carried without being loud. He dressed in clothes that communicated ease and authority simultaneously. He had been at Sterling for seven years, two years longer than anyone else on the executive team except Tom Breck.

James came to every Monday meeting prepared. Not with slides, not usually. He came with a narrative. He had an instinct for storytelling that was as natural to him as breathing. He understood that in a room of busy executives, the person who tells the clearest, most coherent story about what is happening in their world is the person whose version of reality becomes the shared reality.

On a Monday in March, four months into David’s tenure, James began the meeting the way he often did.

“Revenue is tracking six percent above plan for Q1. I want to be honest about why and where the risks are.”

Margaret leaned back in her chair. Priya opened her notebook. Tom poured himself water.

“The outperformance is almost entirely driven by the enterprise segment. The mid-market team closed three deals this quarter that we expected to push to Q2. Good execution by the sales team. But there is a risk I want to flag.”

He paused. James was good at pauses.

“The new customer portal that product and technology are building is late. We were told it would be in beta by the end of February. It is not in beta. I do not have a new date. My enterprise clients are asking about it because we showed them the roadmap in the fall, and they are expecting it. If it slips past the end of Q2, I am going to have some difficult conversations.”

Margaret frowned. “How late is it?”

“I am not sure. I have asked David’s team for an updated timeline and I have not gotten a clear answer. I do not think they have one.”

Tom Breck, the COO, made a small note on his pad. “Is this a pattern or a one-off?”

“I would not call it a pattern yet. But there was a similar situation in January with the reporting dashboard. It was supposed to ship in December. It shipped in late January. The features that shipped were not what we originally scoped. I do not want to make too much of it. David is still new. But I think Margaret should be aware.”

Margaret nodded. “I will bring it up with David on Thursday.”

This is how it worked. Every Monday, James provided Margaret with a frame for understanding the world. The frame was not false. The customer portal was behind schedule. David’s team had not provided a clear updated timeline. These were facts. But facts do not come with their own interpretation. James selected the facts, arranged them, and delivered them in a sequence that told a specific story: revenue was performing well because of the sales team’s work, and the risks to revenue came from outside the revenue organization.

The customer portal was late because James’s team had changed the requirements three times after the project started. The first change added a single sign-on integration that had not been in the original scope. The second added a reporting feature that required a new data pipeline. The third changed the user interface to match a design that one of James’s enterprise clients had specifically requested. Each change was small enough to seem reasonable. Together, they added two months to the project.

David knew this. His VP of Engineering had documented every scope change with dates and the name of the person who requested it. David had even mentioned the scope changes to Margaret in one of his Thursday one-on-ones. But he mentioned them the way an engineer mentions a technical constraint: as context, not as narrative. He said something like, “The portal is behind because the requirements expanded. We are managing it.” He did not say, “The portal is behind because James’s team changed the scope three times, and each change added weeks to the timeline.” He did not say this because it felt like blaming a peer, and David did not blame peers. He solved problems.

Margaret heard David’s version on Thursday. She had heard James’s version on Monday. By Thursday, the frame was already set. When David said the requirements had expanded, Margaret heard an excuse. When David said they were managing it, Margaret wondered why it needed managing in the first place.

Part Three: The Narrative Takes Shape

Months passed. The pattern deepened.

Every Monday, James told the story of Sterling’s commercial progress. He was generous in his framing. He praised the marketing team when a campaign generated leads. He credited Priya’s finance team when a pricing change drove margin improvement. He mentioned Tom’s operational improvements when they reduced fulfillment costs. He built allies systematically by giving them credit in the room where credit mattered.

He rarely mentioned David or the technology team, except as a source of risk or delay.

James did not do this with malice. That is the part people misunderstand about organizational narrative. They imagine a villain, a schemer who sits in a dark room plotting to undermine a colleague. James was not a villain. He was a skilled operator who understood how organizations actually work. He understood that the people in the room shape the story, and the people outside the room become characters in someone else’s story. > The people in the room shape the story, and the people outside the room become characters in someone else’s story.

He understood that executives who wait for their results to speak lack a basic understanding of how decisions get made at the top of companies.

In May, there was a product launch. David’s team had built a new analytics platform that replaced a legacy system Sterling had been running for eight years. The new platform was faster, more reliable, and gave Sterling’s business users capabilities they had never had. David’s engineering team had delivered it on time and under budget. It was, by any objective measure, a significant achievement.

James mentioned the launch in the Monday meeting. “The new analytics platform went live last week. I have not heard complaints, which I take as a good sign. The real test will be whether it helps the sales team close deals faster. I am cautiously optimistic.”

That was it. A significant technology achievement, reduced to a sentence and a half, framed not as an accomplishment but as a tool whose value would be determined by whether it helped James’s team.

Margaret never heard about the analytics platform launch from David. His Thursday one-on-one that week was cancelled because Margaret had a board-related conflict. It was rescheduled for the following week. By then, the launch was old news. David mentioned it briefly. Margaret said, “Right, James mentioned that. Sounds like it went well.”

David felt a flicker of something. Not quite irritation, but a sense that the accomplishment had been absorbed without being recognized. He let it go. He had more work to do.

In July, a production outage took down Sterling’s main website for forty-seven minutes on a Wednesday afternoon. David’s team identified the root cause within twelve minutes: a database failover that did not execute properly because of a configuration error in the cloud infrastructure. They had the site back up in forty-seven minutes, conducted a thorough post-mortem, and implemented three changes to prevent the same failure from recurring.

James mentioned the outage in the Monday meeting. He did not mention the twelve-minute diagnosis or the forty-seven-minute recovery or the post-mortem. He said: “We lost forty-seven minutes of uptime last Wednesday. I have been getting questions from clients. I told them it would not happen again, but I would appreciate some assurance from the technology side that we have a plan to prevent this.”

Tom Breck added: “Do we know the root cause?”

“I believe it was a database issue,” James said. “I did not get the details.”

Margaret made a note. “I will ask David.”

On Thursday, Margaret asked David about the outage. David walked her through the post-mortem in detail. He explained the root cause, the response time, and the preventive measures. Margaret listened and nodded. She seemed satisfied.

But the damage was already done. In Margaret’s mental model, the outage had been registered on Monday as a technology failure that was worrying clients. David’s post-mortem on Thursday was received as a response to a problem, not as evidence of a team that handled a crisis exceptionally well. The frame mattered more than the facts.

Part Four: The Erosion

In September, David noticed something. His Thursday one-on-ones with Margaret, which had been thirty minutes at their most consistent, were now frequently twenty minutes or less. Margaret seemed distracted during them. She asked fewer questions. She checked her phone more often.

David attributed this to the pressure of board preparation. Sterling’s board met quarterly, and September was a heavy month. He did not consider the possibility that Margaret’s engagement level with him reflected a shifting assessment of his importance.

He also noticed that Tom Breck, the COO, had started attending more meetings with the product team. Tom would show up to product reviews and ask detailed questions about timelines, staffing, and priorities. David found this mildly irritating but assumed it was Tom’s natural operational instinct. Tom was a detail-oriented person who liked to know how things worked.

What David did not know was that Margaret had asked Tom to “keep an eye on” the technology organization. She had not told David this. She had framed it to Tom as making sure the operational side had visibility into technology timelines, since the Monday meeting kept surfacing concerns about technology delivery.

In October, David lost his best VP of Engineering. Not to a competitor. To frustration. The VP, a woman named Sonia Alvarez, came to David’s office on a Friday afternoon, closed the door, and said she was leaving.

David was stunned. “What happened?”

“Nothing happened. That is the problem.” Sonia sat down and chose her words with the precision of someone who had rehearsed this conversation. “I love the team. I love the work. But I have been here a year and I still feel like the technology organization is treated as a cost center that sometimes causes problems. Nobody at the executive level talks about what we have accomplished. I was at the all-hands last month. Margaret spent ten minutes on revenue growth and thirty seconds on the platform migration. Thirty seconds, David. That migration was six months of work by forty engineers.”

David sat with this. He wanted to argue, but he could not, because Sonia was right. The all-hands had been exactly as she described. Margaret had breezed past the technology accomplishments because, in her mental model, technology accomplishments were expected, not noteworthy. Revenue growth was the story. Technology was the infrastructure. Nobody celebrates the plumbing.

“I have tried to get recognition for the team,” David said, and even as the words left his mouth, he knew they were not quite true. He had tracked the metrics. He had included them in his reports. But he had not fought for the narrative. He had not insisted that the technology team’s story be told at the same volume and with the same prominence as the revenue team’s story.

Sonia looked at him with something that was not quite disappointment but lived in the same neighborhood. “David, you are a good leader in the ways that matter inside our organization. Everyone on the team knows that. But the people above you do not seem to know it, and that eventually becomes our problem.”

She left Sterling two weeks later. David replaced her, but the replacement was not as strong, and the team felt the difference.

Part Five: The Restructuring

The phone call came on a Thursday in November. Not his usual Thursday one-on-one. Margaret’s assistant had put a separate thirty-minute meeting on his calendar for 4:00 PM with the subject line “Organizational Discussion.”

David looked at the calendar invite for a long time. He felt a cold weight settle in his chest. Calendar invites with vague subject lines at unusual times were never good news. He had been a senior executive long enough to know the choreography.

He spent the afternoon trying to work and not succeeding. He rewrote the same email three times. He attended a product review and realized afterward that he had not heard anything that was said. At 3:45, he walked to the seventh-floor conference room. Helen, Margaret’s chief of staff, was coming out. She glanced at him with a fleeting expression that confirmed what he already knew: whatever was about to happen, Helen had known about it before he did.

Margaret was already in the room. So was Priya, the CFO. The presence of the CFO in what was supposed to be an organizational discussion was the second confirmation. When the CFO attends a one-on-one between a CEO and a direct report, someone’s reporting line is about to change.

“David, sit down. Thank you for making time.”

He sat. Margaret had a document in front of her, printed and paper-clipped. She did not look at it. She had prepared, which meant this conversation was scripted, which meant the decision had already been made.

“I want to talk about the organizational structure going into next year. The board and I have been discussing how to better align our technology and product investments with the company’s operational priorities. We think the right move is to have technology and product report through Tom, under the COO structure.”

David felt the floor tilt, not literally, but the sensation was physical. Everything he had built for the past eleven months, the team, the systems, the platform migration, the release process, all of it was being reframed in a single sentence. Technology and product were being moved from a strategic function reporting to the CEO to an operational function reporting to the COO. It was a demotion wrapped in the language of alignment.

“This is not a reflection of your performance,” Margaret said, in the tone people use when it is exactly a reflection of your performance. “Your team has done good work. But we need tighter integration between technology delivery and business operations, and we think this structure will enable that.”

David’s mouth was dry. He took a breath.

“Margaret, can I ask what is driving this? We have delivered every major initiative on time this year. The platform migration. The analytics platform. Our uptime is the best it has been in three years. Engineering attrition is down to nine percent. I am not sure what operational alignment problem we are solving.”

Margaret’s expression shifted almost imperceptibly. It was the look of someone who has heard a reasonable argument but has already made the decision, and the argument, however reasonable, arrives too late.

“I hear you. And those are real accomplishments. But I have been getting consistent feedback that the technology organization is not always aligned with the commercial priorities. Timelines slip. The revenue team does not always have the tools they need when they need them. I think having Tom coordinate more directly will help.”

David knew where the “consistent feedback” had come from. It had come from the Monday meeting. From James, every Monday for eleven months, shaping a narrative about technology as a function that needed closer oversight. From Tom, who had been attending product reviews at Margaret’s request and reporting back what he saw. From a steady accumulation of small moments, none of which was decisive on its own, all of which added up to a story in which the technology organization was a problem to be managed rather than a strategic asset.

He could have argued. He could have laid out the facts, the scope changes James had requested, the projects delivered on time, the metrics that showed a transformed organization. But he recognized with a clarity that felt like stepping into cold water that the time for those arguments had been eleven months ago. The story was already written. He was too late.

“When does this take effect?” he asked.

“January first.”

He nodded. He stood up. He shook Margaret’s hand and then Priya’s. He walked back to his office on the sixth floor. He sat down at his desk and looked out the window at the parking lot where, eleven months ago, he had stood in the rain feeling a sense of alignment that he now understood had been an illusion.

He did not feel angry. He felt something worse: the recognition that he had done this to himself.

Part Six: What David Understood Too Late

David did not leave Sterling. He reported to Tom Breck and continued to run the technology organization. Over the next six months, he adapted. He changed how he operated in ways that felt uncomfortable at first and then, gradually, felt necessary.

He asked Tom to include him in the Monday meeting. Tom agreed, partly because Tom was a fair-minded person and partly because having the CPTO in the room made Tom’s own job easier. David began attending in January.

The first Monday he sat in that room, he understood everything.

He watched James tell the story of the revenue organization. He watched how James selected which facts to present and which to omit. He watched how James credited allies and subtly distanced himself from problems. He watched how Margaret’s expression changed as James spoke, how she leaned forward during the wins and made notes during the concerns. He watched the story being constructed in real time, and he understood that this was the room where reality was defined, not in the products his team shipped or the code his engineers wrote or the dashboards that showed uptime and velocity and customer satisfaction.

The story was being told here. And for eleven months, he had not been in the room.

David started telling his own story. Not loudly. Not with James’s natural charisma. But clearly, consistently, and with the specificity that came from being a person who actually understood the work. He started each Monday by sharing one concrete thing the technology team had delivered that week and one thing they were working on. He brought numbers. He connected the technology team’s work to revenue outcomes. When there were delays, he explained why, with context, before anyone else could frame the delay as a failure.

He also started sending Margaret a weekly written update. Two paragraphs. What the team accomplished. What was next. One metric. It took him ten minutes every Friday afternoon. Margaret read them. He knew because she started referencing them in conversations. “I saw in your update that the API response time improved. Can you tell me more about that?”

He built a direct relationship with James. This was the hardest part. David’s instinct was to avoid James, to treat him as an adversary. But he forced himself to have lunch with James every other week. Over time, something shifted. When James understood what the technology team was actually working on, he stopped characterizing their work through the lens of what it meant for his team. Not entirely, but enough. James was not a bad person. He was a person who filled narrative vacuums with his own narrative, because that is what skilled communicators do when no one else is communicating.

The organizational structure did not change back. David continued to report to Tom. But his standing in the organization shifted. Margaret started including him in strategic discussions again. When a new board member asked about Sterling’s technology capabilities, Margaret asked David to present directly. The technology team’s work became visible in the way it should have been visible from the beginning.

David once told me, months after all of this, something I have thought about many times since.

“I spent eleven months believing that if I just did the work well enough, the organization would see it. That is like believing that if you cook a great meal, the restaurant will fill itself. Someone has to tell people about the restaurant. I thought narrative was optional. It is not optional. It is half the job.”

The Lesson

I have watched this pattern, or some variation of it, play out at every organization I have been part of or advised. A capable leader builds a strong team, delivers real results, and then is blindsided when the organization does not see what they have built. The problem is never the work. The work is usually excellent. The problem is that someone else is telling the story of the organization, and the story they are telling serves their interests, not yours.

This is not about self-promotion. I want to be specific about that, because I know the objection. “I did not get into technology leadership to spend my time marketing myself.” Neither did David. And he is right that the need to shape narrative should not exist, that in a rational organization, results would be all that matter. But organizations are not rational. They are human systems, and human systems run on stories.

The practical reality is this: in every organization, there is a story being told about each function, each team, and each leader. That story is told in hallway conversations, in executive meetings, in board discussions, and in the offhand comments that shape perception over months and years. If you are not actively shaping that story, someone else is shaping it for you. Not because they are malicious, but because narrative vacuums get filled, and the person who fills them is the person who shows up.

Some of the most capable leaders I have known have been derailed not by poor performance but by leaving their story in someone else’s hands. They did the work. Their teams delivered. Their products were strong. And they were restructured, sidelined, or replaced because the story being told about them did not match the reality of what they had built.

The work matters. Of course it does. But the work is not enough. Someone has to tell the story of the work, and if you do not do it, someone else will, and their version will serve their narrative, not yours.

Rajiv Pant