It has taken me most of my life to notice that almost nothing is mine alone. The water is made safe by people I will never meet. The electricity I use crosses a grid that strangers drew, financed, and kept alive through nights I slept through. The roads outside my home were graded and paved long before I needed them. I have the privilege of waking in a world already warm because of other people’s work — most of them strangers, many of them long gone, none of them waiting to be thanked.

For the longest time, subconsciously, I kept a sort of ledger of things I had earned. The degree. The work. The hard seasons and what they bought. I was not ashamed of that ledger; I showed up for every line of it. But at some point, I began to see the second hand resting on each entry — a teacher who stayed late out of nothing but kindness, a clerk who stamped a form, a stranger on a hiring committee who read an unfamiliar name and decided to take a chance.

No one wakes up self-made. We wake up in a commonwealth.

• • •

I think about this more than I used to. I can point to the exact people and opportunities that got me here.

I came to this country as a financially struggling kid from India to study computer science. I earned my master’s at SUNY Polytechnic — a public university paid for by the citizens of the great state of New York, people who never know me. They funded a scholarship for a kid from halfway around the world. A teaching assistantship and a research assistantship. The patient hours of faculty, and behind them, a whole state system built over generations, so that a kid like me could find an on-ramp.

I did the studying. But the road I studied on was laid by other people’s generosity and handed, without constraint, to a stranger from another continent. I cannot return that generational gift to the people who paid for it. They are not collecting. It is a debt I can only carry forward.

• • •

Here is what I used to forget, in many moments, nearly every day.

I would pick up my phone and feel like I was holding a piece of pure private genius. But the internet access inside it began as a government research project. Its maps rode on satellites the public launched. The screen I tap and the assistant I speak to both started in publicly funded labs — including the one I worked in during grad school at SUNY. The real object I own is, underneath it all, a public inheritance.

This is not about gadgets. The great state universities were built by citizens. The uber exclusive famous private ones are not as private as their crests suggest: close to sixty percent of their research money comes from federal taxpayers, on top of the tax breaks and student aid the rest of us cover. No diploma in this country is entirely self-funded. Somebody I will never meet helped pay for mine, and for yours.

And under all of it sits the quietest gift — the rule of law. A contract honored — disagreements settled in courtrooms instead of in the street. Every ambition I have ever had was built on a foundation, and I did not lay any of it.

• • •

I have caught myself sliding the other way too — the small, ungrateful arithmetic that says I built this alone, so the slice is mine, so why should I be asked for any of it back. The more a system carries you, the easier it becomes to forget you were ever carried.

And in the country that accepted me as a citizen and that I have called home for more than three and one-half decades, that arithmetic has a cost you can see from the sidewalk. The United States is the richest nation in human history, and still, on a single block, you can find staggering wealth beside someone who cannot afford the medicine that would keep them well, the rent that would keep them housed, the food to carry their children to the end of the month.

That distance is not an abstraction here. It is visible, daily, up close.

What surprised me, coming from where I came from, was not the poverty. I had seen poverty. It was that in the wealthiest country on earth, the floor itself is still up for argument. In much of the developed world, a few things are simply settled: that a person should be able to see a doctor without being ruined, that a child should be schooled, whatever the parents earn, that no one should go hungry in a land of plenty, that the commonwealth should be funded and tended as a matter of course.

These are not favors a nation does for its fellow citizens. It’s not even our politics — these are the default a developed nation provides and stops re-litigating. I wonder why this baseline is contested, and the question of what each of us owes the whole is reopened every season, as if new.

Nobody enjoys being asked to pay. I don’t either. But everybody needs somebody to pay for the roads, the schools, the grid, the lab, the clinics, the courts. The fair argument is the one about how we share that obligation — what each citizen’s equitable contribution ought to be. That the bill exists at all, and that it bought the life I am living, is not really in question. The only real question is who keeps the whole thing standing — and whether those of us it carried the farthest will help carry it in turn.

• • •

This is a thank-you, and a quiet promise.

Gratitude has not made me prouder or smaller about my own work. It has only made me honest about it. To say “I worked hard, and a thousand strangers made the work possible” is not modesty. It is the truth.

It asks me to hold the door instead of letting it swing shut. To believe the pie of opportunity grows continuously, as it did for me. To pay forward what I can never pay back — the scholarship, the chance, the patient hour given to someone who has not earned it yet, the way it was once given to me.

I cannot repay the citizens of New York who educated a stranger. They are not collecting. What I can do is live as though I owe, and spend the rest of my life holding open doors for those who are seeking an on-ramp to their lives and dreams.

To everyone who built the road before I arrived, and to everyone still paying for it: thank you. I see it now. And I mean to be worthy of it.

• • •

Thank you for reading and spending some of your day with me.

Please do take a moment to share your thoughts, comments, likes, and questions.

— Adi

TL;DR — A synthetic story from my executive experience. Names, dates, and details are composed.

In Q2 2025, David Park was the product leader at the center of an AI-enabled platform transformation. He found that mission success needed a foundational fix. A fix that would improve customer experience, speed up originations, and give AI the clean data it needs. He raised it, escalated it, and waited for approval to fix – for months. He resigned in July, before it came through. Transformations rarely die from bad strategy. They die from conditions, and from capable people leaving.

• • •

I learned about David Park from his exit interview. He was already gone by then.

He had spent six years at Meridian, an equipment and dealer-finance company. In late 2024, Meridian made its biggest bet in a decade: an AI-enabled platform transformation it called Meridian One. The mission: make the dealer and customer experience so good that revenue growth is inevitable. David was the product leader at the center of it.

While the program chased visible wins, he kept returning to a problem no one wanted to own. The dealer application, called Cascade, asked for twenty-four fields before a dealer could submit a customer for financing. A result of old products and rules. Fewer than half who started the application finished in one sitting. The ones who quit took their business elsewhere — a few million dollars a quarter, the company never counted as lost, because the abandoned applications just didn’t show up on any report.

The fix was not flashy — part of why no one had done it. Cascade had to be cleaned up and redesigned before AI could do anything useful. The models would only be as good as the data the form collected. Done right, it would improve the customer experience, speed up originations, give AI clean data, and become a template for the flows that came after.

In mid-March 2025, 2025 he brought it forward. In May, he escalated it formally, numbers attached. Then it went to the part of the company that approves such things. He waited. Authorization came in August, and the redesign shipped in September. David resigned in July — a month before the approval he had chased since spring, two months before his own work went live.

In his exit interview, he was asked what Meridian could have done differently. He wrote one line, “I found problems. I could not fix them at the speed they needed to be fixed.”

• • •

I never met David Park. His story reached me through Sofia, an advisor on the program, who could not stop thinking about that exit interview.

She had read it late one night, the floor empty around her. The form was not what made her think; that was already fixed. What stayed with her was the rest of it — how a company could put its best product leader on its most important bet, watch him find the one thing that would make it pay off, then take four months to let him touch it.

She wrote down what she saw: the four months David spent waiting; the other problems he flagged that never left the queue; the way the program treated the work that mattered most as the work that could wait. By the time she stopped, she had six items.

She called me that same week. “We need to understand everything that keeps problems alive while the people who can fix them run out of patience.”

• • •

Transformation programs rarely fail because the strategy is wrong. They fail because of the conditions that slow them down — real, ordinary, practices and behaviors — the building blocks of corporate culture.

Most are built into the company over many years, on purpose. Approval chains, so money does not move without sign-off. Ownership is split across teams, so no one person can break things.

They gave Meridian the stability it needed when it was younger and growing fast, and they worked. Now they had outlived the moment that made them sensible.

An AI transformation does not tolerate these conditions; it strains them. The technology moves faster than the company’s decision-making can, and the gap between what a capable person sees and what the company lets them do becomes a failure mode.

The condition that broke David is the simplest of all: the distance between seeing a problem and being allowed to fix it. Four months does not sound fatal in a planning review. It is a different thing to live inside it — to have the fix in hand, know it is right, and watch the customer experience erode and the program idle while approvals move without urgency. Almost no one measures this distance. Yet the people best able to see what needs fixing feel the wait most, because they keep finding things worth fixing.

Five more conditions sat on Sofia’s list, and David had hit several at once. The full set is in the field guide below. They keep working to derail transformations — in the background. The cost shows up — in a slipped quarter, a stalled program, and, most expensive of all, an exit interview from someone the company could not afford to lose.

• • •

It would be easy to read this as a story about AI, because AI raised the stakes. It is really a story about judgment.

The newest technology a company can adopt still depends on an old human decision: to recognize the foundational work for what it is, put it ahead of other things, and clear the path before capable people give up. No model makes that call. It is the same decision behind every product, every mission, every problem worth solving — how fast a company moves from seeing the answer to being allowed to act on it, and who owns the friction in between.

The cheaper path is the one Sofia was pointing at. Pick one condition now — the one doing the most damage this quarter — and give it a person with a clear path, resources, and air cover.

So it is worth asking, while the answer can still change something: which of these conditions is running up the costs and delays in your transformation right now, and who are the capable people deciding whether to stick around?

• • •

Please do take a moment to share your thoughts, comments, likes, and questions.

Enjoy the companion field guide included below.

Thank you for reading,

Adi

• • •

This morning, at his home in urban India, he woke up, made himself a cup of tea, and eased into the day. After his shower, he sat for a while at the small temple he has put together in his room — a habit he picked up when I was in elementary school, and has not missed since. If you asked him what this ritual meant, he would smile and change the subject.

He has always given more than he had — first time and care, when there was little else; now, also gifts and calls and the kind of love that arrives unannounced.

The first leader many of us ever experience is from amongst our parents – real leadership, the kind that decides what we will later believe a good person looks like and follow into our own adult lives. For men and women alike, the picture of what a good man looks like comes from watching one or two men up close as we were growing up.

That picture lasts. Our partners marry into it. Our children study it before they have words.

Some men inherit empathy. Some inherit violence. Most of us inherit something more complicated. The work of fatherhood is choosing what to keep and what to let go.

It is Father’s Day. So I want to tell you about a book.

• • •

I was twelve – I think. I wanted a particular book that we could not afford that month. I walked into the bookshop with a friend after school on a Thursday, stood with the book in my hand for a long time, and then slid it into my schoolbag and walked out.

I made it home. My father returned from work and saw my face before he saw the book. He always saw the face first.

He did not raise his voice. He did not lecture. He asked me what had happened, and he listened the whole way through. When I was done, he said one sentence: “We will go back, and you will return it.”

I begged him not to make me. He said quietly that this was not punishment — only what needed to happen so I could keep being the person we both believed I was. We went back Saturday morning. The owner was an old family friend, ready to wave the whole thing away. My father would not let him. He told him, in front of me, that this needed to be made right — that I would come for several Saturdays to clean floors and shelves and organize stock.

I spent four weekends in that shop. I learned, much later, that my father had paid for the book the same day I returned it. The debt was settled before my first Saturday.

The work was for me to learn right from wrong.

He did not negotiate with the truth, even for me – Integrity. He made me make it right with my effort and time, not only with words – Accountability. He said something difficult to a kind man who would have let me off – Moral Courage. He never raised himself above anyone in the telling – Humility. He carried himself (and me) without storm or speech, the way he has carried everything for eighty-five years – Dignity. He saw, before I said it, that I had wanted the book because I was ashamed of needing it – Empathy. He drove me there and waited outside for those weekend mornings because his son needed him to – Service. He paid for the book with money that was tight, and never mentioned it – Generosity.

Eight things, from one month, from one man. My father.

• • •

The first time I felt that inheritance moving through me, my daughter was six months old, and we were forty-eight hours into a stretch we were not sure she would survive.

We had been preparing to take her to India to meet her grandfather. There was a list — vaccinations, paperwork, and a prophylactic. A pediatric dose. Somewhere between the prescription and the bottle, an adult dose was given instead. She took it twice before we understood that the way she had gone quiet was not sleep.

By the time my mind caught up with my hands, we were in the ICU. Forty-eight hours, touch and go. Strangers I had never met and would never see again sat with her through two nights, adjusting, watching her, watching the monitors, watching my wife’s face, watching mine.

I had spent the decade before becoming competent at things — how to read a room, build a plan, hold a line. None of it was any use. I could not undo what had been given to her. I could not make a number on a screen rise. I could not pretend to my wife that I was not afraid.

What I could do was sit. I could hold my wife’s hand. I could keep my voice low when a nurse came back with new numbers. I could be, for the people I loved, the still point in a room that wasn’t. At the end of the second night, when she opened her eyes and looked at us as though returning, I let her sleep on my chest the way I had when she was three days old.

I marvel, to this day, at those doctors and nurses. The grit of them. Their expertise. The generosity — strangers giving everything they had to a child not theirs, on nights when their own families were asleep without them. The pill meant to protect her on the way to her grandfather had nearly taken her. What brought her back was the thing her grandfather had been modeling all his life: presence under pressure, given freely, with skill.

That is what my father has been doing all along. The eight things were one thing in different lights — what lets a person be present when there is nothing else to give. He had been showing me, all my life, what to do when competence and confidence run out.

• • •

My daughter is twenty-six now. Her brothers are twenty-three and twenty. They watch with full awareness, the way I watch my father. My wife has lived inside that picture for three decades. We raised our three inside the limits of what we had, the way he raised me inside his — give what you have as though it is all for them, and never claim the giving, so children feel the love and not your limits.

The conversation about what it means to be a man right now is loud and all around us. In one extreme, a man is respected when he is dominant, self-centered and loud — a physically strong and violent engine who will protect his own and will be celebrated for lacking empathy, compassion, and any sense of common good. In another telling, there is a deep suspicion that anything called masculine is a problem for humanity.

I disagree with this entire spectrum of opinion – learning from my first and other great leaders in my life.

To be a man, in the only way worth aspiring to, is neither to dominate nor to disappear. It is to be present, accountable, generous, and steady — and to do it without making the doing a story; to use your strengths, resources, and powers to take care of those in your care — your family, our community, our nation, and our world.

A good man is known by his presence. By what he does on the worst day, in a waiting room, when no one is keeping score.

Happy Father’s Day, Papa!

• • •

Thank you for reading, and Happy Father’s Day!

Adi

• • •

I watched Sofia draw boxes on a whiteboard for the first time about five years ago. She was sitting across from Marcus, who runs a deal pipeline.

Sofia had written a single sentence on the board: “Walk me through a deal. First contact to contract. Every step.” And she meant every step – not the version from a process doc, but the real one, including all the parts that live in someone’s head.

Marcus started talking. Sofia drew a box for each step, arrows between them, and branches for the “unless” and “if they” moments. By the time he finished, there were fourteen boxes on the board. Three branches. Two loops where a step fed back into itself.

Then she asked: “How long does each one actually take?”

Marcus knew some precisely, some approximately, and some he had to think about. But when he got to Step 9 – a handoff that depended on whether a specific person was in the office – he said: “It waits. Usually a day, sometimes two.”

Sofia circled that box twice and kept going. When she was done, she stepped back and looked at the board in silence.

Fourteen steps. Thirty-one minutes of actual human touch time – calls, data entry, document preparation, the things that actually moved a deal forward. Calendar time from first contact to signed contract: three and a half days.

“Three point five days,” Marcus said slowly.

“For thirty-one minutes of work,” Sofia answered.

• • •

Most organizations never do what Sofia did that day. They have processes – or they think they do. They have documented workflows, assigned owners, and tools and templates. What they don’t have is a map of the distance between the work that matters and the time it actually takes.

Sofia’s framework is simple. Go through every step and every gap between steps and ask one question: is this time value-creating, wait time, or rework?

Value-creating is the work that moves the deal. The judgment calls. The decisions. The things you couldn’t automate without breaking something important.

Wait time is everything, sitting in a queue. In an inbox. Waiting for approval, waiting for another team, waiting for one person to be in. That Step 9 in Marcus’s process – the one that depended on Tina being at her desk – that was wait time. A day or two, every deal, every time.

Rework may be information being re-entered somewhere it has already been entered. Data needed to be keyed in twice because systems don’t talk. A document reformatted because it came from a source system nobody trusts. It looks like work, but it is work you are that is being redone.

When Sofia and Marcus classified every step and every gap, they found that thirty-one minutes of value-creating work sat inside roughly eighteen hours of wait and rework. Less than three percent of the time that actually mattered.

Marcus looked at the board in wonder.

Then, after a pause, he said, “It’s not a process. It’s a waiting room.”

• • •

You probably have a waiting room in your business right now. You have learned to accept it as normal. You have built your expectations around it. You have hired people to manage around it.

The biggest gains I have seen – across financial services, technology, software companies, professional services, manufacturing, anything with a workflow – come from removing the waiting, not from working faster.

The waiting traces back to the same few sources. A critical step depends on a specific person being available – Marcus and Tina, every deal, every time, and nobody calls it a problem anymore because that is just how deals work here. Information moves through multiple systems or gets checked at multiple gates before it can progress. A decision that should happen in minutes gets routed into a queue where it sits for hours or days.

Wait time is invisible until you draw it out. You can look at a deal that takes three and a half days and think, “That is just how long deals take.” You can’t change what you can’t see. But the moment you map it – the moment you write “WAIT: 1-2 days” next to Step 9 – you are no longer dealing with an acceptable part of business. You are dealing with a structural problem that has a solution.

The solution is rarely a single move. Tina’s step could be done by someone else, or earlier in the week when her calendar is lighter, or in parallel with another step, or by a script. Sometimes the real question is why the step exists at all.

Sofia’s framework does not prescribe the answer. What it does is make the waste visible.

And visible waste is the only kind that can actually be reduced.

• • •

What is the one workflow in your organization that runs constantly, that touches every customer or every revenue dollar – the one whose speed matters more than almost anything else?

When did you last walk through it from beginning to end, step by step, with someone who actually does it?

And when you do, what are the boxes you will circle twice?

• • •

Please do take a moment to share your thoughts, comments, likes, and questions.

Enjoy the companion field-guide included below.

Thank you for reading,

Adi

• • •

• • •

This story comes from IRL transformation work: most transformations do not fail because the strategy is weak or teams are incapable. They fail because major initiatives run in isolation.

At Meridian, the P4I3© Diagnostic exposed the gaps: a platform project had consumed millions, but was not clearly connected to Product, Persona, Process, Instruments, Insights, or Investment outcomes.

The work was real. The team was competent. The operating system was missing.

The leadership choice: keep funding disconnected work and hope value appears eventually, or build a coherent Transformation OS.

How is your transformation strategy running?

•••

I walked into the Meridian Capital Services conference room forty-two minutes early. I have this habit from my first real transformation: the work you do before you walk into a room is the only work you can leverage.

I took a marker and drew a circle on the whiteboard. Inside it, two words: Transformation Metabolism. Then seven spokes outward, each tipped with a name. Product. Platform. Persona. Process and Tooling. Instruments. Insights. Investment.

Priya, the Chief Product & Technology Officer, was watching intently from the far end of the table when I started explaining where the formulation came from.

“Stuttgart,” I said. “A fintech group. They’d spent three years and one hundred and eighty million dollars. Four percent improvement. Nothing fundamentally wrong with the strategy. A capable team. However, no one had ever taken a deep look to figure out whether the system, the whole system, was oriented around the same outcome.”

I had built a version of the wheel the night before my team had recommended the entire engagement be restructured. The Stuttgart CEO had stared at it for a long time and then said, “This is what we’ve been missing!”

When James, the Meridian CEO, arrived and asked what it was, I called it a diagnostic.

P4I3^©, Priya, translated from the far end. Four Ps and three Is. Transformation Metabolism at the center. How fast our organization converts inputs and learning into competitive capability. Not how fast we ship. How fast we learn and deploy value, and recover from being wrong.

That’s when we all started to build the strategy.

•••

Aligned

Marcus, the commercial group leader, started. “The plat…” — he stopped mid-word. “Wait. I’m going to say this, but I don’t actually know which spokes this maps into.”

No one in the room said anything.

“It’s called the Platform Rationalization Project,” he said. “Two million dollars. Nine months in. The goal was supposed to be faster iteration on product features, right? Lower cost of ownership. Better margins.” He trailed off, looking hopefully at his colleagues.

“Does it do that?” I asked.

“That’s the thing,” Marcus said. “It doesn’t map to Product. We’re not delivering or measuring customer value. It doesn’t map to Persona—it’s not about who we’re building for. It’s not a Process improvement because we’re not actually changing how anyone outside of the platform team works.” He sat back. “It maps to Platform, maybe. Or it should. But the Platform element isn’t connected to anything else on the wheel.”

That was a moment. A moment like many I have sat through when something clicks and brings a whole bunch of people together.

The Platform Rationalization Project was real. The money being spent was real. The team was competent. But the initiative existed in isolation. It was invisible infrastructure work without an articulation of the Product outcome it was supposed to enable. No Persona clarity. No Process redesign. No Insights infrastructure to measure whether it would actually reduce cost or iteration cycles. The Investment spoke was crowded—lots of capital going in—but none of the other spokes had moved.

“So what are we actually doing?” James asked.

“We are building a platform,” Priya said quietly, “and we never connected it to who we are supposed to serve.”

“That is a powerful insight,” I said as we started to align.

•••

Operating System

This is what people miss about transformation. You can execute beautifully on one element and produce nothing.

I’ve watched this pattern repeat. A company invests heavily in tools and technology, for example, data infrastructure and excellent Instruments. But no one builds the interpretive layer, the Insights function that converts data into decisions. So the platform ships out analysis, and dashboards track patterns that no one uses to do anything meaningful that adds customer value.

Or a team redesigns their entire operating model—Process and Tooling overhauled, completely professionalized. But nobody repositions the Product or revises the Persona focus, and they’re now moving fast in the wrong direction. Offering features that customers don’t need or want or dislike.

Meridian had done something worse. They had built the platform they thought they needed without asking the upstream questions: Who are we actually trying to serve? What product outcome is this supposed to enable? What decisions does this platform need to support? Will changing the platform actually change how fast we learn and deploy? Will this create customer delight and value? How will this create economic value?

The Platform Rationalization Project had already cost two million dollars of a three-million-dollar budget and an enormous amount of attention and relationship capital. But it wasn’t compounding or building leverage. It was just running.

I pointed at the wheel again. “Most transformations stall not because the strategy is wrong,” I said. You rationalized a platform strategy without building a transformation operating system around it. So the platform, even if it is best in class, will just sit there, isolated, demanding budget and attention while everything that was supposed to use it keeps working in a separate world. The old way.”

•••

Choice

This is when a leadership team has to choose.

You can continue the isolated initiatives. Fund the platform. Expect eventually it will find its audience, its purpose, its justification. You’ll wait, and the pressure will build, and eventually you’ll either abandon it or force teams onto it because you’ve already committed the money.

Neither will work.

Or you can stop. You can look at the seven spokes and ask, “What are we actually trying to transform? What does that require? What do we need to build together?”

You can take the Platform element and ask: What Product outcome does this enable? Whose Persona does it serve? What does our Process need to look like for teams to actually use it? What Instruments tell us it’s working? What Insights do we build on top of it? And what does this require from Investment?

You can turn the isolated initiative into a coherent system.

Your Transformation OS.

Or you can do nothing, and watch the two million become four, then five million, and watch the team rationalize why it’s still not working because the organization isn’t ready. That story has an ending, too. I’ve seen it in Stuttgart. I’ve seen it in many places.

What James Harrington chose that day—whether to treat the platform rationalization as a strategic input and build Meridian’s transformation operating system around it, or to treat it as a cost center and manage it as overhead—that choice determined the next three years of whether Meridian actually transformed.

•••

The wheel doesn’t lie about the gaps. But it only matters if you’re willing to make a choice.

Which elements of your strategy are running in isolation? And what would it cost to name that choice in front of the people who need to hear it?

Please do take a moment to share your thoughts, comments, likes, and questions.

And if you liked the story, please restack.

•••

Thank you for reading,

Adi

• • •

That first Thursday, Angie almost didn’t go up.

She stood at the bottom of the stairwell for a while, her mother’s text still open on her phone — Please. Just once. For me. She climbed the stairs. Her movements clearly reflected that she’d already decided that this was a waste of time, and she was doing this for her mom.

The room at the top was small and warm. Books on every wall, a single lamp instead of the overhead light, and beyond the window the early dark of late November. People called him the Sensei. Angie didn’t know if that had ever been a real title or just a name that stuck. It didn’t matter to her.

“My mother thinks you can fix me,” Angie said, before she’d even sat down. “I told her there’s nothing to fix. I’m just behind.”

“Behind whom?”

“Everyone.”

She sat down at last, on the edge of the chair, as if she might still leave. “I went to Minnesota. Economics and Philosophy. You know what people do with that? Consulting. Strategy. Grind for two years, get into a good graduate program, make real money. Everyone I graduated with is already on their way. I’m the only one sitting here.”

“Your mother said you’d worked. Internships?”

“Two.” Angie almost laughed. “One paid. A tech consulting firm. It was boring and easy – but mostly boring. I picked up a certification in a few weeks, and they’d have probably wanted to keep me. I couldn’t – I just did not feel or taste anything.”

“And the other?”

She was quiet for a moment. “A music production company. Unpaid. I sat in on sessions with musicians — confident ones, and terrified ones pretending they weren’t. There was one singer who couldn’t find his take – all session, and I said something to him, I don’t even remember what, and suddenly he was alive. The whole room was alive.” She could hear herself getting excited, and it embarrassed her. “But you can’t tell your family that’s what you want. ‘How’s the job hunt, Angie?’ ‘Great. I’m trying to make strangers feel alive in a room. For free.’”

The Sensei smiled, but didn’t laugh. “Then why did you come tonight, if there’s nothing to fix?”

“Because Mom asked me to.” She stopped and then added, “And because I’m tired. I wake up, and I can’t even start. I open my laptop and close it again. I’ve stopped wanting to meet all these relatives and my parents’ friends.”

“Then we won’t fix anything,” the Sensei said. “We’ll just talk. Come back Thursday if you want to. Don’t, if you don’t.”

• • •

Walking home, Angie told herself she wouldn’t go back.

She went back.

Not because she thought it would work. She just didn’t want another message from her mother – and somewhere in that week, she stopped being so sure it had been a waste of time.

She skipped the third Thursday out of spite and spent the whole evening more miserable than usual. By January, she was climbing the stairs without anyone having to ask her.

The hardest evening came in the middle of winter, snow stacked on the window ledge, the city quiet under it.

“I just want someone to give me the answer,” Angie said, angrier than she meant to be. “Make music, or don’t. Take the safe job, or don’t. Everyone says, ‘follow your passion’ or ‘be realistic,’ like those are directions. I don’t need a pep talk. I need to know which one is right, so I can stop feeling like this.”

“Which one is right?” the Sensei said, slowly. “You think there’s a single correct life. That everyone else found theirs, and you lost yours somewhere.”

Angie’s eyes stung. “…Yeah. That’s exactly it.”

“Then of course you can’t move. You’re not choosing a path. You’re trying to guess a secret – and if you guess wrong, you’ve ruined the one life you were supposed to get right.” The Sensei leaned in, and his voice was kind. “No wonder you can’t start.”

Angie didn’t say anything for a while. No one had ever put it that way before, but that was exactly how she felt.

• • •

“Let’s forget which one is right,” the Sensei said.

“If you only wanted to move toward work that makes a room come alive – not the whole journey, just one step toward it – what could you do? Not what you should do. What you could.”

“I don’t know.”

“You do. You know this world. I don’t. Humor me. One way.”

Angie let out a breath. “…I could call people. I still know a few from that summer – don’t know if they will remember me – there are some names I have collected over the years. I could ask about music work, or anything close to it. Coordinating. Helping run sessions. Even the boring jobs nobody wants. At least I’d be in those rooms.”

“That’s one. It took you four seconds.” The Sensei waited. “Another.”

“I—” She stopped, surprised at herself. “That summer, I kept noticing how badly the business runs. Scheduling, session logistics, all of it held together with tape. I used to think someone could build a real service for it. I could find out what they actually pay for and build something better. I have this habit of seeing what does not work – fix the worst of it.” She blinked. “I have the mind for that – or I could learn how to get someone to do that for me.”

“That’s two – and you came alive more on that one than the first. Worth noticing.” A small smile. “One more.”

“…Or none of it yet.” She said it slowly. “Take a solid job. Any honest job. Make some money, stop lying awake about being stuck, and build up the nerve. Then walk toward music from a steady ground.”

“That’s three. You came up with all three in five minutes, with no help from me.” The Sensei sat back. “So tell me honestly. Which of those three do you think you cannot do?”

Angie opened her mouth, then closed it.

“None of them,” she said quietly.

“None of them,” the Sensei said. “You can do any of the three. You always could. That was never the problem.”

“Then why have I been frozen for more than a year?”

“Because you’ve been waiting to feel certain before you move. You think confidence shows up first, and then you act. It works the other way around.”

The Sensei tapped the table once. “You were never short on clarity – look how fast those paths came to you. And you were never short on ability. What you didn’t do was permit yourself to choose one without a guarantee. To believe that picking a good direction, and being free to change your mind later, isn’t the same as failing.”

“What if I choose wrong?”

“Then you’ll be a capable young woman on a path she can change – instead of a capable young woman who is stuck in place.” He said it warmly. “You don’t have to find the one true life, Angie. You just have to pick a real direction, trusting you’re strong enough to walk it, and strong enough to turn around or change it if you need to.”

• • •

The last Thursday Angie went was in early spring. The snow had turned to slush, and the light stayed in the window a little bit longer.

She never told the Sensei which of the three she’d chosen.

She had chosen – you could see it in the way she sat. She’d stopped perching on the edge of the chair a while ago. But the choice was hers now.

“I don’t think I’ll need Thursdays anymore,” she said. She didn’t say it like an apology. She wasn’t scared, either.

“No,” the Sensei said. “I don’t think you will.”

At the bottom of the stairwell, Angie stopped for a second, the way she had that first night in November. Then she pushed the door open into the brisk spring evening, took out her phone, and made a call. And whatever she said when the other person picked up, she said it like someone who knew she could.

• • •

Thank you for spending some of your day with me.

Enjoy your loved ones and the rest of your day.

Warm regards,

Adi

• • •

The room was loud in a way that usually makes me want to leave. It was 1993, a winter gathering in New Delhi in an unfamiliar space that smelled of the festival season and tea. I was twenty-six, possessed by that specific arrogance of a young man who thought competence was the only meaningful pursuit in life.

Then I met her – saw her smiling eyes.

We talked for maybe twenty minutes in the entire evening. We didn’t discuss any plans or metrics. We talked about the things that actually matter – the way we saw the world, the things we refused to tolerate, and some of the quiet ambitions we hadn’t quite put a name to. By the time the twenty-first minute arrived, I knew. It wasn’t a romantic epiphany; it felt like a realization.

Thirty-two years later, that decision remains the anchor of my life.

We often treat a partnership as a series of evaluations. We check credentials, we run due diligence, we look for alignment. But often, true partnership – the kind that functions as a superpower – is rarely found in models and spreadsheets. It is found in the gaps between what we can do and what the world requires of us. It is the realization that the sheer girth of what we don’t know is too much to consider.

• • •

The Week-Long Investment

In November 2017, I made a different kind of decision.

I had met a potential professional partner through a mutual contact I trusted. He had the resume: a twenty-year successful sales and development career, a top role at a mid-cap service firm, and a way of speaking that assured me he was the real thing. We decided to build a business and platform together. I spent three months on the business strategy and architecture. I committed my personal capital, quit my C Suite role, and brought along a lieutenant who trusted me implicitly and left their thriving role to help us build.

On a Monday morning, we signed the operating agreement. We shook hands. We talked about the “100 million milestone” we were going to run to in 3 years.

The following week, on a Thursday afternoon, he called me.

“Adi,” he said. The line had that hollow quality of a long-distance call, even though he was two miles away. “I’ve been thinking. I don’t think I want to build this with you.”

I sat in my chair and watched a bird land on the windowsill. The documents were still on my desk, the ink barely dry. He didn’t offer a reconsideration or a real dialogue at the time. He didn’t offer a strategic pivot. He simply walked away from the promise because the reality of the work – the “contact sport” of actually building something – was less appealing, with me being a co-founder.

I learned more in that week than I did in two years of graduate school.

The failure wasn’t his. It was mine. I had fallen in love with the “idea” of his past successes instead of looking for the evidence of his character, discernment, and grit. I had ignored the nits – the pauses and delays in his responses, the way he spoke down to people sometimes, the subtle “follow me because I said so” register he used with associates. I thought those were just personality quirks. They weren’t. They were signals of a lack of an all-around service orientation.

• • •

The Art of Overlooking Nits

Most partnerships fail not because of a lack of talent, but because of a lack of grace.

In my advisory work, I often see leaders who are “nit-pickers.” They find a brilliant technical co-founder or a masterful operations lead, and then they spend their energy complaining about the way that person formats an email or the fact that they arrive three minutes late to a stand-up.

They confuse obedience with partnership.

A true partner is not a mirror of your own strengths. If they were, one of you would be redundant. A partner is a different set of eyes. When I work with a Board or a CEO, I look for the people in their midst who are “inconvenient.” The one who asks why when everyone else is nodding.

The superpower of partnership is the ability to accept a person’s strengths and service while intentionally overlooking the nits that don’t impact the outcome.

I have professional partners now in new ventures. They are brilliant at the things I find exhausting. They can sit with a detailed filing for six hours and find the one thing that customers may care about. They also forget to update the shared calendar and have a tendency to use jargon that I’ve spent twenty years trying to excise from my own vocabulary.

I don’t try to “fix” their calendar habits – I update the calendar for them.

Service in partnership is not about doing 50% of the work. It is about doing 100% of whatever is needed to ensure the mission survives every contact with reality. It is being more grateful than expectant.

• • •

The Platform of Oneness

Whether it is a 32-year marriage, a $500M business unit, or a small advisory alliance, the mechanics of success are the same. You are building a platform of “oneness” in an insular and local world.

A partner allows you to see the “otherness” of a situation. They provide the epistemic humility you lack on your own. When I was the only brown line leader in 1990s boardrooms, I relied on my advocates – “my partners” – to bridge the gap between my competence and the biases in the room. They didn’t do it as a favor. They did it because they knew our shared success depended on the “all” of our perspectives.

The best partners I have known all share three traits:

1. They lead with customer-obsession. Every disagreement is resolved by asking: How does this impact the person who pays us?

2. They assume positive intent. Even when the “noise” of a build or a transformation gets loud, they trust character over a momentary lapse.

3. They treat the brand as a promise. They know that if one of us fails to deliver, the promise is broken for both – for all.

• • •

The Closing Beat

I still think about that very fortunate twenty-minute conversation in 1993.

It wasn’t a perfect setting. I probably said something arrogant. She probably wondered why I was talking so fast. But we recognized something in each other that pulled us together – something sturdy.

Not because it’s sacred, but because it’s terrifying to build alone. Because the maze is real, and the gravel is sharp, and you will eventually need someone to slip you a cup of chai or coffee and say, “Don’t give up.”

I looked at my phone this morning. A message from my wife about a mundane household detail. A message from my business partner about a delayed vendor deliverable.

I answered both. I didn’t moralize the delays or complain about the mundane. I simply did the next thing required to keep the build moving.

Partnership is not a destination. It is the way you place your feet – one at a time – when the mountain gets steep. Because you know – your partners have your back and will be there to help you out when you get a bit lost.

• • •

Enjoy your loved ones and the rest of your day.

Warm regards,

Adi

We were in a private dining room — closer to seven years ago now — at the end of a long evening. The plates had been cleared. Two espressos, his black, mine with too much sugar. The Chairman of a $3B financial technology company had asked me to stay on after the others left, and we were maybe twelve minutes into that quiet stretch when he set the offer down between us.

Full rights. Full resources. His support.

The offer came with a condition.

Make sure there are no complaints.

He said it the way a careful man says things. Not a warning. Not a threat. More like a request — almost an apology — for a thing he could not, in his role, ask for any other way. He stirred his espresso once. Set the spoon down. Looked at me as if waiting to see whether I had heard.

I have thought about that sentence many times since. It is the most honest thing I have ever heard a Board member say about transformation.

Most leaders, when they ask for transformation, are not asking for transformation. They are asking for the appearance of it, delivered without disturbance to the parts of the company that are uncomfortable with change. The slides will look good. The OKRs will be new. There will be a kickoff. There will be a steering committee. The CEO will use the word agility three times in every quarterly call. And nothing — at the level that actually matters, the level where a customer feels something change — will move.

It is not because leaders are cynical. Most are well-intentioned. It is because they have never lived through real transformation — the kind that comes with necessary pain. The pain is not a side effect.

You can lower the price. You can pay it with care, with sequencing, with clean communication and a leadership team that has the stamina and discipline to tackle long builds. But you cannot make the price zero. And every leader who tries to make the price zero is, in effect, asking someone further down the org to absorb it on their behalf.

Transformation is a contact sport.

It is loud. It is resource-hungry. It breaks routines, reporting lines, and sometimes identities. It costs sleep. It costs trust before it builds it. It generates complaints — not occasionally, but as a daily byproduct, the way exercise generates lactic acid, and that nice burn the next morning that tells you something is strengthening.

If you are running a transformation and no one is complaining, you are not running a transformation. You are running a marketing exercise.

What I told the Chairman, after a longer pause than I meant to take, was this: we will execute with care, with empathy, with discipline — but everyone will need to get ready. And stay on board for a long haul. And – the complaints would come.

He gave me the half-nod that leaders often give when they don’t want to commit on the record. I took the resources, did the work, and the noise came exactly as I had warned. Some of it was necessary. Some of it cost me. The Board, in the end, stayed on board — though not all of them.

I have thought about what I would tell my younger self about that exchange.

I would say two things.

When a senior leader tells you no noise, they are telling you the truth about themselves, not about the company. They are telling you what they cannot tolerate. Take that seriously, and decide whether you want the job under those terms — because the terms are the job.

And, the noise is not the problem. The noise is proof that the transformation is creating new capability — new muscle. The absence of noise, in any meaningful change, is a problem. It means nothing is hurting, and nothing hurting means nothing is changing.

This is also why most transformation success stories you read in business books are unreliable. They are written after the fact, with the noise edited out. You read about the strategy, the framework, the breakthrough moments. You don’t read about the senior leaders who left, the regions that nearly seceded, the engineering teams that worked through three Christmases, the customer who threatened to sue and was talked back from the edge over a six-week negotiation. You don’t read about the all-hands where someone you respected stood up and said you were wrong, and was half right.

That part is the transformation.

I thanked the Chairman, walked out into the lobby, and waited for my car under a portico that smelled of rain. The driver was reading something on his phone. I sat in the back, opened my notebook, and wrote one line for the Monday call with my chief of staff: plan for noise; get the teams ready. I closed the notebook. Slipped the pen back into my jacket. Watched the streetlights pass for the next twenty minutes without saying a word.

The next morning, the work began.

♻️ If you liked this story - Restack it!

➕ Follow Adi Agrawal on LinkedIn

This is a composite story based on real advisory work I have done. Company, founder, and identifying details have been changed…

The Pitch

Gurgaon — October 21, 2025

The late afternoon sun was striking the glass towers of Cyber City, giving the whole district the look of speed and importance. From the road below, Gurgaon can make almost any business look larger than it is. The gleaming towers suggest capital, momentum, and modern ambition. Inside Rahul’s office, the feeling was smaller and more human.

The room was cramped. The desks outside were pressed close together. A few chairs made a tired sound every time someone shifted.

Rahul sat across from me with a pitch deck in his hand.

He had built this company from nothing. You could see it in the way he held the deck. It was not just a set of slides. It was his proof. Proof that he had won clients, hired people, made payroll, survived late payments, and kept the business alive through months when their bank balance fell into warning territory.

“I don’t get it,” he said. “We have one hundred people. Eighty are billable. Twenty are leadership and support, and we recover that through overhead added to the billing. We did $2.75 million last year. I’m asking for a $10 million valuation. That’s fair for what I’ve built?”

He looked at me and waited, still holding the deck as if the answer was somewhere inside it. I looked again at the revenue number. A hundred people. $2.75 million. Even before doing the math, the shape of the problem was visible. The business had grown, but it had grown by adding people.

“Rahul,” I said, “when an investor looks at your company, what do you think they are buying?”

He answered quickly. “Growth.”

“What kind of growth?”

He looked irritated now, because the question sounded too simple to be useful. “Revenue growth. Client growth. Team growth. We have added people, added accounts, and the pipeline is strong.”

“That may all be true,” I said. “But if every new dollar of revenue needs more people, more managers, more hiring, more payroll, and more pressure on you personally, then the investor has to ask a different question. Is this company scaling, or is it becoming heavy?”

Rahul frowned. Not because he disagreed. He frowned because he understood, before he wanted to admit it, that we were no longer discussing the pitch he had prepared. We were discussing the business he had built.

“I have scale,” he said.

“You have size,” I said. “That is not the same thing.”

For a few seconds, neither of us spoke. Outside the glass wall, one engineer leaned back from his screen and rubbed his eyes. Another was trying to keep his voice calm on a client call. Rahul glanced toward them, and I could see the conflict move across his face. These were his people. They were also his proof. He had spent years turning empty desks into occupied ones, and now I was telling him that the desks themselves might not persuade anyone who understood the economics of the company.

“That sounds harsh,” he said.

“It is harsh,” I said. “But it is not an insult. It is the difference between a company that grows stronger as it grows and a company that just – grows.”

He looked down at the first slide again. The chart moved upward. But the company underneath the chart was tired. Revenue had grown. Headcount had grown. All in lock step. The problem was obvious.

“The problem,” I said, “is that your story is built around headcount. Investors will not pay a premium for headcount unless they can see operating leverage behind it.”

He nodded slowly, but not in agreement yet. More like a man allowing an uncomfortable thought to be considered.

The Raise

O’Hare — November 13, 2025

Three weeks later, we met near O’Hare after Rahul had flown in for a client meeting. He had just finished a tense call with one of his senior developers in India, a young man who had been with him through several difficult projects and now wanted a market-level salary. Not an extravagant salary. Not founder-money. Just enough to make staying feel less foolish.

Rahul was pacing when I walked in.

“If I pay him what he wants, the margin on that project vanishes,” he said. “He’s good, but everyone is replaceable. I can find two juniors for the same cost.”

I waited before answering. Some sentences reveal a business more clearly than a spreadsheet.

“Do you believe that?” I asked.

“Believe what?”

“That two juniors can replace one person who understands your clients, your code, your delivery history, your past mistakes, and all the things your process documents pretend to capture but don’t.”

He looked away.

“That’s not the point,” he said. “The math does not work.”

“The math does not work because the model does not work.”

That annoyed him more than the first conversation we’d had. He was used to discussing pricing, utilization, and margins. Those were safe and logical arguments. They kept all his problems within his spreadsheets. This was different.

“You are treating him as expensive because his value is trapped inside billable hours,” I said. “If all he does is work on one client project, then yes, his salary squeezes that project. But if he builds something that improves delivery across fifty projects, he becomes one of the cheapest people in the company.”

Rahul sat down.

I showed him the comparison, not because Nvidia was a fair peer for his business, but because the contrast made the point impossible to avoid.

Rahul’s company had done $2.75 million in revenue with 100 people. That meant revenue per employee was about $27,500.

Nvidia had reported more than $60 billion in fiscal 2024 revenue with fewer than 30,000 employees, which meant revenue per employee was a little over $2 million.

Cognizant, a large services company, was a more relevant comparison. It had reported about $21 billion in 2025 revenue with roughly 351,600 employees, or about $60,000 in revenue per employee.

Rahul stared at the numbers for a while.

“I am not Nvidia,” he said.

“No one expects you to be Nvidia,” I said. “But you are not even close to Cognizant yet. And Cognizant has global delivery systems, client depth, management infrastructure, recruiting scale, and decades of operating discipline. You are asking investors to believe in scale, but your economics don’t show it.”

He rubbed his face with both hands, and for the first time, I saw the fatigue behind his confidence. Founders like Rahul often look stubborn when they are really scared. Payroll teaches them fear. Client concentration teaches them fear. A missed invoice teaches them fear.

“I thought I was protecting the business,” he said.

“You were protecting every month’s margin,” I said. “That is different from growing a strengthening business.”

He did not answer. He just sat there in silence.

The Lost Deal

Dubai — January 14, 2026

By January, the market made the point more sharply than I ever could.

We were in Dubai Internet City, in a small borrowed office on the edge of the district. Rahul had just lost a contract to a similarly sized firm from Singapore. His team had proposed twenty people and a detailed delivery process. The Singapore firm had proposed five people and an AI-enabled delivery suite with tons of innovation and options.

“They undercut me by twenty percent,” he said.

He was angry, but beneath the anger was something more useful. His fear finally had a specific reason.

“How am I supposed to compete with that?”

“By changing what you sell,” I said.

“I sell time and delivery.”

“That is the problem.”

He looked at me as if I had dismissed the entire company in four words.

I asked him what the client had actually bought from the Singapore firm.

“Unproven AI and promises,” he said.

“No,” I said. “They bought lower risk, faster delivery, fewer handoffs, and less management effort. AI-enabled tooling was one of their labels. But the real leverage was product optionality and speed.”

He turned toward the window. Dubai looked calm from up here, which is one of Dubai’s tricks. It can make even unfinished things look intentional.

“You keep selling people,” I said. “They are selling a system.”

He hated that sentence. I could see it in his face. It sounded unfair because his people were good. They worked late. They solved problems. They cared more than many employees in companies twice the size. But that was also why the sentence hurt. His best people were being used to repeat work that should have been turned into tools, automated checks, templates, reusable code, decision rules, and training systems.

“You are making talented people behave like inventory,” I said.

Rahul was quiet for a long time. “I thought being frugal made me disciplined,” he said.

“Sometimes it did,” I said. “But sometimes it made you cheap in the wrong ways.”

He gave a small laugh. “That sounds like something my wife would say.”

“She may be right.”

It was the only light moment we had that day.

Then his face changed.

“I almost lost that developer,” he said. “And if he leaves, I will tell myself he was disloyal.”

“Would that be true?”

He looked down.

“Or would it be easier than admitting he got tired of being treated like a cost?”

That was the hardest moment. Not the lost contract. Not the Singapore competitor. Not the numbers. It was the realization that the problem was not just operational. He had asked people to care like owners while managing them like replaceable inputs.

Many founders do this without meaning harm. They confuse loyalty with endurance. They mistake silence for commitment. They tell themselves that people understand the sacrifice because the company is still young, still fragile, still fighting. Then one day, a good person leaves, and the founder calls it betrayal because the alternative is harder to face.

Rahul did not defend himself this time.

He just said, “I need to fix this.”

The New Deck

Gurgaon — March 23, 2026

By March, we were back in Gurgaon.

The office looked no better in the months since my first visit. The desks were still crowded. The chairs still complained. But the room felt different because Rahul had changed.

A whiteboard near his office was covered with diagrams for a highly automated design, engineering, delivery, and testing platform. This was not client work. It was internal work, the kind founders often postpone because it does not create an immediate billable invoice. For Rahul, that had always been the excuse. There was always another client demand, another delivery problem, another cash concern, another reason to ask good people to repeat work instead of giving them time to improve and innovate.

This time, he had stopped.

He had canceled the plan to hire twenty more people in the first quarter. Instead, he gathered his five strongest developers, including the one who had asked for the raise, and told them the truth. The business could not keep growing by adding bodies. He had treated senior people as replaceable. If they could automate the core delivery process, he would share part of the savings through bonuses and profit-linked compensation.

“How did they react?” I asked.

“At first, they did not believe me,” he said.

“Why?”

“Because I have trained them not to.”

It was the most honest thing he had said in six months. Rahul had not built a bad company. He had built a company around fear, then called the fear discipline.

The early results were modest but real. The company did $800,000 in quarterly revenue with the same hundred people. Revenue per employee moved from roughly $27,500 toward $32,000. Nobody should confuse that with a transformation. But in founder-led companies, the first useful signal is often not the number itself. It is the change in behavior that produces the number.

Earlier, when a new project came in, the first question was who could be staffed on it. Now the team was asking why the project needed so many people in the first place. Earlier, Rahul had asked whether he could hire cheaper. Now he was asking whether the work could be made repeatable. Earlier, every raise felt like a threat to margin. Now, the best people were beginning to look like the only path out of the low-margin trap.

“And the investors?” I asked.

He opened his new deck.

The first slide no longer bragged about headcount. It did not try to make one hundred people sound like scale. It showed a simple operating thesis: revenue growth had to separate from headcount growth. Under that was a small chart showing where automation had already reduced delivery effort, where billing accuracy had improved, and where senior engineers were replacing manual review with reusable tools.

“This is better,” I said.

Rahul looked relieved, but not triumphant. He knew the company was still fragile. He knew one good quarter did not prove anything. He also knew, perhaps for the first time, that the old pitch had asked investors to reward the wrong thing.

“I kept telling them we had a hundred people,” he said. “As if that was the proof.”

“It was proof of effort,” I said. “Not proof of leverage.”

He looked through the glass wall at the team outside. The same people were working at the same crowded desks. But he was no longer looking at them as payroll. He was no longer using them as cogs in a scale story. He was beginning to see them as the only people who could help the business become less dependent on constant hiring, constant pressure, and constant founder heroics.

“I told the investors we are not trying to become a thousand-person service firm,” he said. “We are trying to deliver the most with the least using innovation.”

That was a clean strategy.

The office was still imperfect. The business was still early. The valuation was still uncertain. But Rahul had stopped trying to raise money on the weight of what he had built. He was starting to show how value could be reengineered.

And that is a different conversation with investors.

It is also a different conversation with yourself.

Enjoy your loved ones and the rest of your day. And thank you for spending some of your day with me.

Warm regards,

Adi

♻️ If you liked this story - Restack it!

➕ Follow Adi Agrawal on LinkedIn

Global Nexus had approved an 18-month, capital-heavy AI program meant to rebuild its consumer business. Inside the company, the program was already drifting.

The reports looked fine. The money was being spent. The CEO sounded confident. But customers were waiting, engineers were warning, and institutional investors were quietly telling the Board that management had lost control.

Then the Head of the Board Strategy and Execution Committee found Meer Singhal, a little-known builder and operator who had spent his career fixing hard businesses without becoming famous for it.

And now the story…

The Number

At 7:42 on a wet Monday morning in London, Priya Menon was still looking at the same number: 18,412.

She refreshed the file once, then again. The number did not change. The reconciliation break in Global Nexus’s European consumer payments platform had grown overnight, which meant another day of manual fixes, another day of client exceptions, another day of waiting for senior people to admit what the engineers already knew.

The issue had started six weeks earlier, when the break count was just under four thousand. Priya had flagged it in a message, then in a meeting, then in a shorter message that took longer to write because she was trying not to sound angry. The answer came back from a director two levels above her: they should avoid creating unnecessary alarm before the AI rollout.

She still had that message.

She kept it because she wanted to remember the moment when the company stopped fixing the problem and started arguing with the people who saw it.

Global Nexus was eighteen months into a large AI-enabled consumer business transformation program, the kind that boards approve to stay current and signal innovation and growth. The program was meant to modernize fraud detection, customer onboarding, credit decisioning, service routing, dispute management, and personalized financial offers across regions. It had a large capital budget, a proud name, and enough outside advisers to make every decision feel solid.

The money was real. The outcomes – they were less clear.

The CEO, Colin Voss, had sold the program as the next chapter of Global Nexus. He spoke about responsible AI, better consumer journeys, faster approvals, lower fraud losses, and deeper wallet share. The board loved the ambition. Investors liked the promise. Analysts liked the TAM slide – after all, a good TAM slide can make everyone believe in magic.

Inside the company, the people building the program were less enchanted.

The source data was messy – for two decades, no one had been able to get it fixed. The fraud models were not ready for three regions. The onboarding workflow still depended on manual reviews in several markets. The payments platform had settlement breaks that should have been fixed before any AI-enabled expansion went near it. Customer service teams were being told to trust routing logic that still could not distinguish between a high-risk complaint and a password-reset request.

But the executive reports stayed clean.

That was the talent of the management team around Voss. They could make delay sound like sequencing. They made risk sound like learning. A broken dependency was a cross-functional opportunity. Six of the eight executives on his team owed their rise to him, and over time, they had become very good at protecting the man who had protected them.

The head of consumer product spoke in an intoxicating Aussie accent about AI-native financial experiences, but could not explain why three releases had slipped after being marked ready. The head of operations, Daniel Reiss, carried himself like someone doing the company a favor by attending his own meetings. The head of risk knew the vocabulary of governance but not the actual exposure sitting in the daily exception reports. The chief people officer talked constantly about culture while the best engineers were taking calls from recruiters and leaving without drama.

Priya had joined Global Nexus seven years earlier, when the company still felt serious. It processed payments and settlement flows for banks, lenders, merchants, and consumer platforms across regions. The work was not glamorous, but it mattered. If Global Nexus failed, customers did not get paid, merchants did not settle, lenders did not book, and consumers sat on hold.

Now the company was spending hundreds of millions to make the business look smarter while the basics were getting harder to trust.

At nine, Priya walked into the incident review with a printed report in her hand, though everyone already had the file. She liked bringing paper to meetings.

Daniel Reiss arrived seven minutes late, holding a coffee and wearing the smile of a man who had never been punished for wasting other people’s time.

Around the room were engineers, product leads, risk analysts, operations managers, and two members of the AI launch team trying not to look directly involved. There was also a man Priya did not recognize at first, sitting near the end of the table with a notebook open in front of him.

Meer Singhal.

The announcement had gone out the previous week. Meer had been appointed Interim Head of Global Consumer Businesses, reporting directly to the Board, with authority over the consumer AI program, payments stability, customer recovery, and regional delivery. The title was strange enough to make people read the email twice.

Colin Voss remained CEO.

The interesting part was that Meer’s appointment had not come from Voss.

It had come from the Board Strategy and Execution Committee, led by Arvind Rao.

Arvind Rao

Arvind was not the sort of director executives dared to dismiss as just another board member.

He had built two fintech platforms before most banks understood that technology providers could become the railroads of modern finance. He had scaled a consumer credit business across Asia, sold a payments company to a global bank, run a public financial infrastructure firm through a regulatory crisis, and still had the unusual habit of reading operational reports before meetings.

People described him as quiet. Rao had been watching Global Nexus with growing discomfort for a year. He did not trust how clean the AI program looked in the board materials. Large capital programs are never that clean unless they are either exceptionally well-run or carefully narrated. He had seen both. This did not feel like the first.

The real pressure came after three large institutional investors began reaching out privately. They started asking whether the Board had enough visibility into the AI spend, whether management had the right operators in place, and whether the consumer business was missing delivery milestones because of technology debt or leadership.

That last one started concerning Rao. Leadership.

Rao took the concerns to the Technology Committee and the Risk Committee. The Tech Committee had been uneasy about platform readiness. The Risk Committee had been uneasy about model governance, settlement exposure, and customer harm if automation scaled before controls were ready. Separately, their concerns sounded manageable. Together, they sounded like a company spending a great deal of money faster than it made good decisions.

Rao pushed for an outside operator to enter the consumer business with direct authority. Voss resisted, as Rao expected him to. Weak leaders often call intervention “confusion” because they prefer everyone confused except themselves.

The search took longer than Rao wanted. The obvious candidates were too polished, too available, too practiced in saying the right things to boards. They had decks, war stories, and that faint scent of performance that wasn’t authentic. Rao did not want a celebrity fixer. He wanted someone who could sit with engineers, investors, and regulators - with ease and honesty.

Meer surfaced late in the process through another board risk chair, who told Rao, “You won’t know him. That’s part of why he works.”

Meer had been a C-suite operator, adviser, builder, and problem-solver across financial services, fintech, risk, technology, and transformation. He had led businesses, repaired delivery failures, advised boards, and walked into broken situations without turning himself into a brand. He had enough range to understand the architecture, enough commercial sense to understand the capital, enough risk judgment to understand the downside, and enough scars to distrust easy answers.

Rao interviewed him four times.

The first time was formal. The second was technical. The third was mostly silence, with Rao handing him anonymized fragments of Global Nexus reporting and watching what Meer noticed. The fourth was over breakfast, where Rao asked him why someone with his background was not better known.

Meer smiled and said, “I spent most of my career doing the work.”

Rao liked that. He also did not fully trust it, which made him like it more. By the end of the process, Rao had decided. The Technology and Risk Committees supported him. The full Board approved the appointment, though not without discomfort. It was one thing to know management was weak. It was another to put a stranger inside the machine and give him tools and authority.

Before Meer started, Rao gave him one piece of advice. “Don’t fight the theater,” he said. “Find the truth. The theater will come looking for you.”

Meer remembered that line when he entered the incident review and watched Daniel Reiss explain control without producing a number.

The Meeting

Reiss opened by saying the team had a workaround in place, the issue was being tracked, and the AI rollout remained within the revised launch path.

Meer asked for the previous day’s break count.

Reiss turned to his deputy. The deputy looked at the product lead. The product lead looked at Priya.

“18,412,” Priya said.

Meer wrote it down and asked what the count had been when the platform was marked stable. No one answered at first. Priya could feel a familiar pause, the one where the room waited to see who would accept the risk of being precise.

“Just under four thousand,” she said.

Meer asked why four thousand had been considered stable.

Priya looked at Reiss, then back at Meer. “Because the report had already gone green.”

The room went still.

Priya had not meant to say it quite that plainly. Once it was out, she felt both exposed and relieved.

Meer asked her to explain the sequence.

The partner bank had changed the file format. The internal mapping logic had not been updated properly. Exceptions were split across three categories, which made the trend look smaller in summary reporting. The team that should have fixed it had been reassigned to support the AI-enabled dispute-routing release, because Voss wanted to show progress at the next investor update. The reconciliation break was now interfering with onboarding for a major enterprise client, and if the AI program scaled on top of unstable payments data, the company would be automating confusion.

When Priya finished, Meer turned to Reiss and asked who had decided to defer the fix. Reiss said the decision had come out of the prioritization forum. Meer paused, then said a forum could not make a decision; a person had to make the decision. Reiss tried again, saying there had been broad agreement. Meer told him broad agreement did not tell him who was accountable.

Priya had seen executives ask sharp questions before. Some did it to perform. Some did it to make other people feel small. Meer seemed to be doing something else. He was looking for the exact place where the company had chosen to ignore facts.

By late afternoon, the story had moved through Global Nexus. Meer had asked for the number. Meer had asked who made the decision. Meer had not accepted “the forum” as an answer.

For people close to the work, this was not dramatic. It was better than dramatic. It was a revolution – and hopefully a shift towards how things ought to be.

The People Above the Reports

In the days that followed, Meer did not spend much time with Voss’s executive team.

That offended them.

They were used to power moving through them. They controlled calendars, summaries, interpretations, and escalations. They knew how to prepare for visiting executives. They knew which phrases worked, which concerns to acknowledge, and which people should not be invited to certain meetings.

Meer was harder to prepare for because almost no one knew him.

He had no famous book, no standard keynote, no repeated slogan, no public doctrine they could memorize and feed back to him. He had been around long enough to have seen most corporate maneuvers, but not visibly enough for them to profile his preferences. Reiss asked a former colleague if he knew Meer. The answer came back: “I know of him. People call him when something ugly needs to get fixed.”

That did not help Reiss.

Meer went to Warsaw and sat with the security architect who had been warning about access weaknesses in the AI servicing platform. The architect, Tomasz Lewek, had a dry manner and the tired eyes of someone who had already explained the same risk many times. He showed Meer how access rules had been relaxed to accelerate testing and how exceptions had become the norm. A launch planned for the following month would expose sensitive consumer case data to teams that did not need it.

“Who knows?” Meer asked.

Tomasz named three people.

“Who can stop it?”

Tomasz gave a small laugh before he could stop himself. “In theory or in the company?”

Meer did not smile. “In the company.”

No one had stopped it because stopping it would mean not launching.

In Singapore, Meer met Lian Chen, an operations director whose team had grown from three people to thirty-one to support manual reviews that the AI program was supposed to reduce. Every week, her team corrected customer records, fraud flags, and escalation queues created by systems that were described in board materials as progressing toward automation. Lian did not complain. That made her account even more damning.

In New Jersey, he met Marcus Bell, a client implementation lead who had kept his own list of customers who no longer trusted Global Nexus delivery dates. He had started the list for himself, then for his team, then because no official report seemed to match what clients were telling him.

Meer asked him why he had not escalated it.

Marcus looked at him for a long moment and said, “I did.”

Meer did not ask people to believe in him. He asked them what decisions they would make if they knew he would protect them from pushback and fallout.

Priya asked for ten days, three engineers, and a delay to the AI dispute-routing release until the reconciliation logic was fixed. Tomasz asked to stop the servicing launch until access controls were rebuilt – from scratch. Lian asked to freeze expansion in two markets until manual review volumes were understood. Marcus asked to call two major customers and reset delivery commitments before another missed date made the company look either careless or dishonest.

Meer approved all four.

And – he stayed close enough that the approvals could not be reversed in side conversations.

The Weak Circle

Voss had built his management team for his success and comfort.

He would never have described it that way. He would have said trust, chemistry, shared vision, and cultural fit. But those words were a cover for something else. He liked people who made him feel decisive. He promoted people who supported his narratives even when the facts were different.

Six of the eight top executives had risen that way.

They protected one another because everyone’s survival depended on the others’ silence. Reiss needed the product chief to keep pretending that releases were late because the business was ambitious, not because the underlying platform was unstable. The product chief needed risk to keep describing control gaps as manageable. Risk needed the people leader to keep morale concerns away from the Board. The people leader needed everyone to keep pretending attrition was part of a competitive talent market.

It was not a conspiracy in the cinematic sense. There were no secret meetings in dark rooms. It was ordinary, daily self-protection. A thousand small choices not to say the truth.

Meer’s first formal review with Voss and the executive team was held on a Thursday afternoon. Voss opened warmly, praising the importance of speed, discipline, and responsible innovation. He welcomed Meer’s partnership. He said the company needed to move as one team.

Meer let him finish.

Then he asked Reiss for the owner of the reconciliation deferral, the expected customer impact if the AI dispute-routing release proceeded on unstable data, and the reason the exception categories had been split in the executive report.

Reiss had brought a deck. Meer asked him to close it.

The meeting became uncomfortable quickly.

The chief product officer tried to explain that the business was balancing modernization with customer commitments. Meer asked which commitment required using inaccurate operational data. The head of risk said the issues were being monitored. Meer asked what threshold would trigger a stop. The people leader said teams were under stress because the transformation was difficult. Meer asked how many senior engineers had left in the past two quarters and which programs they had worked on.

Elena Park, the CFO, said little. Simon Vale, the general counsel, said even less. But both watched carefully.

After the meeting, Voss called Rao.

He said Meer was moving too fast, creating confusion, bypassing established leadership, and undermining confidence in the AI program.

Rao listened.

When Voss finished, Rao asked him whether the reconciliation break count was now below ten thousand.

Voss did not know.

The Work Takes Over

The first month was ugly.

The reconciliation fix delayed the AI dispute-routing release. The access-control rebuild delayed the servicing launch. Two customer calls were painful. One client procurement head said, “This is the first time in six months someone from Global Nexus has told us something I believe.” Marcus sent that note to Meer.

Meer sent it to Rao with no comment.

Rao replied, “Keep going.”

The Board reports changed next. Meer did not redesign them. He made it harder to hide the truth. Each major AI program workstream had to show capital spent, decision owner, customer impact, control gaps, data readiness, operational dependency, and next irreversible decision. Every red item needed a name. Every green item needed evidence. Every delayed item needed the original date, not only the revised one.

The first version was a mess.

That was the point.

The Technology Committee finally saw that several AI releases depended on data flows and quality that no one fully owned. The Risk Committee saw that model approval was being treated as a document process while operational controls lagged. The Strategy and Execution Committee saw the capital burn against work that had not earned the confidence implied by its status reports.

Investors noticed the tone change before the results changed. They heard fewer promises. They heard more specifics. Some did not like it at first. Markets enjoy confidence until they have to pay for real consequences. But the largest investors, the ones who had started the back-channel calls, understood the signal. The company was now showing them the work.

Inside Global Nexus, the change arrived in smaller ways.

Meetings became easier for people who relied on facts. Engineers brought problems earlier. Operations leads stopped waiting for permission to say what clients were already feeling. Risk analysts began attaching thresholds to their concerns. Product managers started separating what was ready for launch from what someone wished could launch.

Reiss struggled.

He sent longer emails, added more people to meetings, and began using Meer’s language without adopting Meer’s discipline. The product chief praised accountability in public and in private, fought every decision that made his roadmap less attractive. The head of risk asked for more time to review issues everyone else could already see. The people leader announced a listening tour.

Voss grew colder.

At first, he tried charm. Then process. Then, private resistance. He told directors that Meer was damaging the confidence of the executive team. Rao asked which members of the executive team he meant. Voss named the same six who had presided over the drift.

Rao later told Meer, “You are removing the screen.”

Meer understood. It mattered. He did not want a purge. He wanted the company to see who could still do the job when the old protections were gone.

The answer came faster than expected.

One executive left for what the announcement called a portfolio opportunity. Another accepted an advisory role that had no staff, no budget, and no path back to authority. A third resigned after a Board review in which he could not explain a risk approval beyond naming a recurring meeting.

Two were replaced by internal operators who had been blocked under Voss. One was a regional platform leader from Singapore who knew the consumer business deeply. The other was a product operator from London who had a reputation for being “difficult,” which in her case meant she told it like it was.

The sixth lasted longest. He had good instincts for survival. When Meer became impossible to ignore, he began praising discipline, asking for owner names, and repeating words he had once resisted. But he still could not answer the second question. He could not explain the mechanisms underlying the status. He could not trace a decision from capital request to customer impact. After a while, even his allies stopped helping him.

Voss lasted eleven months.

The announcement was graceful. It had to be. Global Nexus thanked him for his service, praised his role in growing the company, and said the Board had appointed Meer Singhal as CEO to lead the next phase of execution.

The lawyers made everything smooth.

The Review

Three days after the announcement, Priya attended a product review that would have gone differently a year earlier.

Elena Park was there. So were Tomasz from Warsaw, Lian from Singapore, Marcus from New Jersey, several product leads, two engineers, and the new head of consumer product, a woman named Amara Doyle who had spent most of her career inside complex financial platforms and had no visible patience for decorative language.

The question on the table was whether to approve the next AI-enabled onboarding release for two European markets.

The product team wanted to proceed. The fraud team had concerns. Operations was worried about the manual review volume. Priya had found a dependency in the payments data feed that could affect exception handling for a segment of customers with cross-border income.

A year earlier, the release would have moved forward with conditions impossible to safely address in production. The conditions would have been written down, assigned to several people, and slowly converted into everyone’s problem. This time, the room stayed with the issue.

Amara asked Priya to walk through the dependency. Priya did. Tomasz challenged one of her assumptions about access logs. She checked her notes and revised that part of the analysis. Lian added that her team could absorb a limited pilot but not a full launch. Marcus said two clients would accept a phased rollout if the company explained the reason directly and provided early support.

Meer listened from the end of the table.

He asked whether the release served customers better if it launched now or if it launched six weeks later with fewer manual repairs, cleaner data, and clearer exception handling.

No one tried to dress up the answer.

The release was delayed.

No one celebrated. No one needed to. People made notes, assigned work, and moved to the next decision. Near the doorway, a younger engineer who had joined during the worst period lingered for a moment. He told Meer it felt like people were allowed to speak the truth now.

Priya heard it and looked down at the packet in her hand. It was marked with notes, names, dates, and decisions. No one had asked her to soften the conclusion. No one had asked her to make the risk sound smaller. No one had praised her courage in a way that made the courage seem like the problem.

She went back to her desk and opened the reconciliation dashboard.

The break count was down to 1,932.

Still too high. But real.

The number no longer had to be dressed up.

The Repair

The year that followed did not make Global Nexus perfect.

The AI program was redesigned into fewer releases with clearer outcomes. Two markets were paused. One model was retired before launch. Customer service automation was narrowed until the data could support it. Fraud detection improved in the regions where the inputs were clean enough to trust. The consumer onboarding release eventually went live later than Voss had promised.

Transaction failures had dropped. Customer renewals stabilized. Institutional investors stopped back-channeling panic and started asking better questions in the open. The share price recovered enough for people outside the company to call the turnaround inevitable, which it had not been at any point.

Inside the company, the change was easier to see in habits.

Bad news moved earlier. Delivery dates became less exciting and more believable. Board materials got concise and clear. Customer calls got more direct. Executives who stayed learned that empty answers became more dangerous the higher they traveled. People close to the work began speaking before the meeting was over, instead of afterward in the hallway.

One evening, months after Voss left, Priya passed the conference room where that first incident review had taken place. The lights were off. Through the glass, she could see the long table, the wall screen, and the empty chairs.

Nothing about the room had changed.

She stood there for a moment, holding her laptop against her side, remembering the number on the page and the silence after she said the report had gone green.

Then she went back to her desk.

There was another release to review, another risk to test, another decision that needed a name before it moved forward. The work had not become easier. It had become possible to do it honestly and transparently.

Enjoy your loved ones and the rest of your day. And thank you for spending some of your day with me.

Warm regards,

Adi

♻️ If you liked this - Restack this!

➕ Follow Adi Agrawal on LinkedIn

Success is never a solo climb. Our greatest wins rest on the invisible “Commonwealth” of shared sacrifice and civic trust.

Now the story…

By the time the bursar finished explaining the payment options, Claire had stopped pretending to look at the pamphlet in her hand. She folded it once, then again, until it had the dense, compact shape of something she would never read and could not yet throw away. Her son Ethan was sitting beside her, long legs tucked awkwardly under a chair built for eighteen-year-olds and their parents, staring at the framed aerial photograph of the campus on the wall as if it might offer an affordable alternative of the campus he had fallen in love with.

The woman across the desk had the polished tone universities train into people who spend their days discussing devastating numbers in humane language. She slid a printed sheet forward with one finger and said, “Most families think in terms of annual cost, but many find it useful to consider the long-term return.”

Claire gave a wry smile, “That’s one way to think about it.”

I was there because Ethan had asked if I would come. I had known Claire for years, first through work, then through neighborhood dinners, then through the slow, ordinary overlap by which people become part of one another’s lives without any formal decision ever being made. She was originally from Ohio, a public-school teacher who had spent twenty years persuading other people’s children to take themselves seriously. Ethan was the first in her family with a real shot at a place like this, and there was enough pride around him that day to fill all our hearts.

There was also the bill.

The campus was beautiful in the way highly sought-after and expensive institutions often are. The stone looked old in the right places and recently repaired in the others. Nothing announced its wealth. Wealth, at that level, rarely does.

The bursar went on, talking now about grants, loans, work-study, and family responsibility. Claire listened with the stillness of someone making sure annoyance did not spill over into disrespect. Ethan said almost nothing. At eighteen, he had already learned the dangerous habit of tempering his hopes.

When we stepped outside, the air was cold and bright, the kind of spring afternoon that makes every college seem briefly worth any price. Students were crossing the quad with backpacks slung low, laughing in small clusters, holding coffee cups with the casual entitlement of people already within the system. Claire stood on the steps and looked back at the building.

“We can do it,” she said.

It was not a triumph. She meant the arithmetic.

Ethan said, “Mom, I can take loans.”

“You will,” she said. “That was never in doubt.”

Then she looked at me, not for permission but for witness. “It’s just strange. They talk like we’re buying a finished product.”

I said nothing at first. We watched a maintenance cart move slowly along the path, stopping beside a flower bed where two grounds workers were replacing early spring plants that had browned at the edges after a late frost. A tour guide was leading another family toward the library, reciting a line about alumni impact that I had now heard twice that day.

Claire said, “We’ll pay. A lot. But this” – she gestured toward the campus, the library dome, the labs, the green that had been maintained too perfectly to look accidental – “this did not begin with us.”

Later, in the car, Ethan asked whether it was worth it. Claire kept her eyes on the road. “That depends on what you think you’re paying for.”

He waited.

“We’re not paying for buildings,” she said. “Not really. We’re paying to step into something that was built before we arrived.”

There are moments when a parent says something profound. Ethan turned toward the window and did not answer, but he had heard her. I could tell.

A few weeks passed.

Our train was stalled. It was a Thursday morning, every seat taken, every standing passenger carrying some blend of caffeine and work obligations. I was on my way downtown for a board session and had already read through the briefing papers once. Across from me, a young man in a navy suit was editing slides on his laptop with the frantic precision of someone who had left too little time. Beside him, a nurse in scrubs was half asleep against the window. Two teenage boys in school blazers were arguing softly over the game from the night before.

Then the lights flickered, the train gave a low mechanical shudder, and everything stopped.

For a while, no one said much. People looked up, then back at their phones, then up again. The conductor came on with the familiar calm of a man trained to make inconvenience sound temporary and under control. There was a signal issue ahead, he said. We would be moving shortly.

We did not move shortly. After ten minutes, the suit stopped editing. Another twenty minutes – the teenagers had stopped talking.

We could feel the dependency in the air now, though most people would not have used that word. We use infrastructure all day and resent it only when it does not perform. A woman near the door, maybe in her sixties, said to no one in particular, “This city charges enough. You’d think trains would run.”

A man standing beside her, wearing a hard hat clipped to his backpack, said, “They usually do.”

It was not defensive. Just factual.

She said, “That’s not the point.”

He shrugged. “Kind of is.”

No one joined in. That is one of the more interesting things about shared inconvenience. It exposes us as people, but only in flashes.

When the train finally inched forward, there was a collective exhale too intimate for strangers and too brief to be called relief. The city emerged at the bend, and the skyline appeared like a staged set.

At the final stop, Union Station, people poured out and resumed their lives at once, stepping onto platforms, into elevators, toward meetings, classrooms, hospitals, courtrooms, and kitchens. The whole city ran on systems most of them had not built, could not repair, and barely noticed until interruption forced a kind of humility upon them.

That afternoon, I mentioned the morning delay to my colleague Tom, a former consultant from Boston who now served on two more committees than any human should and treated civic frustration as a sport.

“Transit’s broken everywhere,” he said. “Public sector. No accountability.”

Tom had worked hard for everything he had. He reminded you of this not quite often. He admired competence, especially his own, and had developed that late-career habit of speaking about institutions as if they were old employees who had disappointed him personally.

“You still took the train,” I said.

He smiled. “What’s the alternative? Helicopter?”

“We complain about systems only when they fail,” I said. “When they work, we don’t notice or feel gratitude.”

Tom gave the small, practiced laugh of a man indulging philosophy before returning to the spreadsheet. “Meer, I knew there was a sermon hiding in there.”

There wasn’t, or not the kind he meant. The older I get, the less interested I am in speeches. Most people don’t change by being told what to think.

They change. Just like I did – in an unremarkable moment.

That moment when they realize how much of what they call personal success was scaffolded by other people’s discipline, taxes, labor, restraint, patience, and invisible maintenance.

Mine came many summers ago at a dinner party in Connecticut, of all places. We were around a long table set by our hosts, Laura and David Whitmore, who made old money look accidental.

The guests were the usual mix that midlife assembles if you stay in one orbit long enough: a surgeon, a startup founder, a lawyer, a public-school teacher, someone in venture capital, someone in local government, one person between careers, two pretending not to be worried about their children, and everybody came with some version of unfinished private news.

The argument began over dessert, which is where most respectable arguments arrive. David’s daughter, Anna, had just announced she was leaving a stable consulting job to start a design studio with two friends. She said it plainly, without drama.

David set down his fork. “I’m supportive,” he said, in the tone men use just before proving they are not. “I just want to make sure this isn’t one of those romantic reinventions people make after reading too many essays on the internet.”

Anna laughed. “That’s not what this is.”

“You’ve got health insurance. A retirement plan. A path.”

“A path to what?”

There it was. The actual question.

Laura intervened with the speed of a woman who had seen this movie before. “She’s not dropping out to join a circus.”

David ignored her. “People act as if they have invented themselves. They don’t. Stability matters.”

At the other end of the table, Elena, who had spent twenty-five years teaching and had the unnerving gift of saying true things in a tone that made disagreement sound childish, said, “So does inheritance.”

The table went quiet.

David looked at her. “Meaning?”

“Meaning,” she said, “your daughter is able to take a risk partly because so much was made stable before she ever got there. Family. Schools. Roads. Contract law. The internet. The clients who trust a designer because other people have built industries where design has value. Even the idea that she can try and fail and still be respected – that came from somewhere.”

Anna looked down, not embarrassed, just thoughtful now.

David said, “No one’s denying society exists.”

Elena smiled. “That’s a very generous concession.”

A few people laughed. He did too, reluctantly.

Then Anna said, more softly than anyone else had spoken all night, “I know I didn’t build everything. That’s kind of the point. I’m trying to build something with what I was given.”

On the drive home, my wife asked why I had been so quiet through most of the dinner.

“I wasn’t quiet,” I said.

“You were Meer quiet.”

That was fair.

Outside the window, service roads curved off the highway toward neighborhoods, warehouses, schools, power lines, gas stations, distribution centers, the lit and unlit machinery of ordinary life.

It struck me in that moment that ambition often forgets context. Young people sometimes imagine they alone are making their future. Older people sometimes imagine they alone paid for their present.

What I had noticed all around me was a thinning of memory. People are becoming more fluent in ownership and pride than in inheritance and gratitude. We were losing the awe for what came before us, and that which we use every moment of our lives without thinking.

And once that happens, respect becomes optional. Shared effort starts to feel like theft. Even love, under enough pressure, becomes a list of transactions.

A few days later, Ethan called to say he had decided to accept the offer.

“How does your mom feel?” I asked.

He laughed. “Like she’s buying a country.”

“She might be.”

There was a pause. Then he said, “I think I understand what she meant that day.”

I asked what part.

“That I’m not just paying to go there,” he said. “I’m stepping into something generations before me put together, and people I will never know kept alive.”

After we hung up, I stood at the window for a while without moving. Outside, someone I would never know was repairing a water main two streets over. I could hear the machinery through the open window, steady and unheroic, the sound of one more thing being maintained before most of us had the chance to miss it.

Enjoy your loved ones and the rest of your day. And thank you for spending some of your day with me.

Warm regards,

Adi

♻️ If you liked this - Restack this!

➕ Follow Adi Agrawal on LinkedIn

This is a fictional story.

The company, names, and conversations are constructed. But the patterns are real.

Over the years, I’ve worked inside leadership teams where culture was shaped quietly, through tone, signals, and small decisions that rarely showed up in formal policy. Many of those experiences are confidential.

So I write through a composite version of myself.

Meer Singhal is not one person. He is an observer, a participant, and sometimes a challenger, drawn from years of watching how leadership teams actually behave when the stakes are real.

This story is not about any one company. But if you’ve spent enough time in executive rooms, it will feel familiar.

And now the story…

By the time I spoke, the room had already decided to move on.

Chris Gill was at the head of the table, jacket off, sleeves neat, one hand resting beside a stack of briefing papers he did not need to look at. The quarterly business review had the controlled feel these meetings often take on once a Chief Executive Officer has been in place long enough for people to stop speculating and start adjusting themselves around them.

The numbers were solid. Not brilliant, not weak, just solid in the way boards tend to reward: margins up, costs contained, no public embarrassment, no visible disorder. The slides were clean. The commentary was dull but familiar.

A regional lead had just finished describing a delay in one of Delmar’s cross-border payments programs as “timing-related but manageable,” which was accurate in the narrowest possible sense and meaningless in every other one, when I asked, “Manageable for whom?”

It was not a hostile question. I was not trying to corner him. But it had the effect those questions sometimes have in a room full of senior people who have already agreed, without saying so, what kind of conversation they want to have. A few eyes went down. Someone reached for coffee. Another executive began typing, though I doubt she was taking notes.

Chris looked at me, then at the slide, then back at me.

“I think the point,” he said, calm as ever, “is that we remain within the broader plan.”

It was an elegant answer. It was also the end of the discussion. The regional lead nodded. The next slide came up. A few people nodded their heads, and others made small affirming sounds. The meeting continued as if the question had been fully addressed.

I wrote one line in the margin of my packet and let the next twenty minutes pass.

That was how it happened at Delmar.

Not through some loud cultural rupture. Not through a restructuring memo or a speech about transformation or a dramatic clash that everyone could point to later and say, “That was the moment”.

Delmar was too old, too disciplined, and too successful for that kind of amateurism. It was a global fintech giant built over decades through scale, patience, regulatory fluency, and the kind of operational control that made smaller competitors talk about it as if it were a permanent feature of the global business landscape. Inside the company, people liked to call that discipline. Outside, depending on whether they were trying to buy us, beat us, or admire us from a safe distance, they used different words.

Chris had arrived in the CEO seat without any spectacle. The prior CEO resigned to “spend time with family,” and Chris, who had risen through legal and operations, was in the right rooms and board committee conversations when that happened.

At his first town hall, he said, “Nothing changes. We’re just getting back to discipline.”

Beautiful line. Investors liked it because it promised order. The board liked it because it implied control. Executives liked it because it sounded like protection. Middle management liked it because it suggested they would not have to relearn the company.

I remember sitting there and thinking that whenever a leader says nothing changes, the useful question is not whether he means it. It is what he is preparing to change without having to call it change.

At first, the shifts were mostly in tone.

Chris had a habit of opening leadership meetings with short reflections that did not seem strategic enough to be strategic. He would talk about the people who had built Delmar, the instincts that had carried the company through volatility, the value of alignment at scale, and the need for judgment during noisy periods. Nothing he said was unreasonable. In fact, most of it was true. That was part of what made it effective. He was not trying to convince people of something outrageous. He was slowly building a shared idea of what belonged.

Not formally. Never explicitly.

He had a gift for turning a preference into a principle. Alignment. Maturity. Discipline. Institutional Judgment. He used those words so steadily and smoothly that resisting them made you sound less like a thoughtful dissenter and more like someone needlessly attached to complication.

I saw the language move into hiring before I saw it move anywhere else.

There was no change to the interview framework. No memo to human resources. No rewritten competency model. But in debriefs, a phrase began surfacing with unusual frequency.

Feels like Delmar.

At first, it sounded harmless, one of those lazy but familiar expressions companies use when they are collapsing a hundred impressions into four words. But shorthand tends to have its most consequential impact when nobody bothers to inspect it. Candidates who mirrored the existing executives’ style, who spoke with the right level of control, who carried themselves in ways the company already recognized as credible, moved through more easily. Candidates who brought in thoughtful questions and healthy friction, in experience, in tone, in the way they reasoned, in the kinds of questions they asked, suddenly required more explanation and personal validation.

During one debrief, after a particularly strong candidate had been set aside in favor of someone safer and less capable, I asked, “Are we selecting for capability or for comfort?”

The CHRO answered quickly. “Comfort is a proxy for alignment.”

That sentence hung in the room. Chris did not say anything immediately. He gave a small nod, almost as if he appreciated the efficiency of the phrasing. Then the conversation moved on to succession timing and compensation bands, and the candidate was gone.

That was another feature of the new system. Things moved on quickly once the right words had been spoken.

Meetings changed the same way. Not structurally. Behaviorally.

They became more efficient. Less thoughtful. Less nuanced. Less layered. Discussions closed faster. Fewer threads remained open at the end. If you looked only at the surface, you might have called that efficient. Chris certainly did. He had a way of guiding the room without appearing to direct it. He rarely interrupted. He did not bully. When disagreement surfaced, he would acknowledge it, absorb it, and then narrow its range without seeming to do so.

“Let’s not overcomplicate this.”

“Stay with the stretegy,”

“The broader trajectory still holds.”

Each sentence was balanced, rational, and perfectly defensible. That was the brilliance of it. He was not crushing dissent. He was shortening its life just enough for everyone to understand what kind of disagreement was welcome and what kind would simply be absorbed and neutralized.

People learned quickly.

In a healthy culture, people bring the rough and messy truth into the room and have the confidence and trust to work on it with their colleagues. At Delmar, over time, people started doing the work before they ever entered the room. Concerns were refined in advance. Edges were smoothed. Caveats were buried deep in the materials. Risks were translated into language less likely to sound oppositional. The point was no longer to surface the sharpest version of reality. The point was to present a version of reality that could survive the meeting.

I remember the product review where that became unmistakable to me.

One of our newer offerings, strategically important, still early enough to be corrected, had started showing signs of drift. The metrics were not disastrous. That was the problem. If something is visibly broken, even a defensive company can respond. What is harder is when the numbers are just good enough to appear okay while quietly undermining the reality beneath them. Pricing assumptions were off. Customer behavior was less stable than forecast. Engagement was coming in bursts instead of building in the shape we had forecast and needed.

I laid out the gap plainly. No drama. No attempt to force urgency. I said that if we addressed it now, the correction would be manageable. If we waited, the correction would be harder and more expensive.

Chris listened closely. He asked two sensible questions. Then he said, “Let’s not overcorrect based on early data. The broader trajectory still holds.”

That sentence ended the conversation. A direct disagreement would have created an argument. This did not. It repositioned my concern as technically noted but strategically premature. Nobody pushed further. Nobody wanted to be the person arguing for instability in a room that had become increasingly organized around clean forward motion.

Afterward, I walked out with one of my colleagues. He said, “He didn’t disagree.”

I told him, “No. He closed the door.”

Once you see that pattern, you start seeing it everywhere.

Concerns did not disappear at Delmar. They changed shape. People brought in cleaner versions of what they knew. They learned which kinds of candor extended discussion and which kinds quietly ended it. They learned what gained traction and what made the room uncomfortable.

Nobody had to say, “Don’t push that point too hard” – we learned it by subtle behavior.

By midyear, externally, things looked strong. Revenue steady. Margins improving. Costs disciplined. Analysts heard what they wanted to hear. The board heard what it had hoped for. There is no more protective cover for a narrowing culture than decent numbers and a calm management script.

Internally, the effects were subtle enough to escape formal notice and clear enough to be felt by anyone paying attention. Ideas that required real debate slowed down. Decisions were made faster but came back more often because the harder stuff had not actually been worked through. Attrition rose in pockets, not enough to trigger an alarm, just enough to tell you something about where the company was losing capability.

I raised the issue once in a strategy session after watching three separate risks get translated into “execution details.”

“We’re optimizing for presentation,” I said, “not accuracy.”

Chris looked at me evenly. “I’d say we’re optimizing for clarity.”

Most people would have let that stand. I didn’t.

“Clarity without tension and analysis,” I said, “is incomplete and maybe misleading.”

There was a pause. Not an explosive one. No one lost composure. But it was long enough to reveal that the room no longer knew what to do with an unresolved statement unless Chris resolved it for them. He let the silence sit for a beat, then moved to the next item.

It was handled gracefully. That was the point. At Delmar, the most consequential things were usually handled gracefully.

By then, I knew the shift was complete, even if the company did not. Acceptance still existed, but it no longer meant what it once had. It no longer meant a leadership team strong enough to withstand disagreement and do the hard work with trust and respect.

It meant alignment without resistance. You could still challenge something, in theory. The conversation would be short. Your point would be translated into something less disruptive. You would begin, gradually, to sound like someone attached to complexity while others sounded constructive.

That is how dissent becomes useless. Not forbidden.

Just personally expensive.

When I decided to leave, nothing dramatic happened. No confrontation. No final showdown. No speech worth remembering. My exit was processed with professionalism, as these things always are in well-managed institutions. Chris thanked me graciously. The announcement said the right things. People wrote kind notes. The machinery of continuity did its work.

On one of my last days, someone asked me whether it had been worth staying as long as I had.

I told him the truth.

“That depends on what you value.”

He asked, “And you?”

I said, “I value being in rooms where the truth is welcome, and we can work on hard things with mutual respect and trust.”

After I left, I heard that meetings got smoother.

That did not surprise me. Smoothness is often what organizations get in exchange for innovation and growth. Alignment comes faster when people know, in advance, which thoughts are worth bringing into the room and which ones should be handled privately, softened, or dropped altogether. On paper, the system still worked. In fact, on paper, it may have looked better than before - but only in the immediate.

What changed at Delmar did not happen through policy. It happened through tone, repetition, timing, and the steady education of response. A phrase in a hiring debrief. A reframing in a product review. A calm sentence that made a difficult issue sound slightly immature. Small signals, individually defensible, collectively decisive.

I still think about that first question in the operating review.

Manageable for whom?

It was not a grand challenge. It was barely even dissent. It was just an attempt to be truthful and seek honest clarity.

It didn’t survive very long.

After a while, neither did much else.

I welcome your feedback on the story.

Enjoy your loved ones and the rest of your day. And thank you for spending some of your day with me.

Warm regards,

Adi

♻️ If you liked this - Restack this!

➕ Follow Adi Agrawal on LinkedIn

I was in my mid-thirties before I realized that being the most capable man in a room often means being the one who takes the heat without passing it on.

In my early career and family life, I used to think leadership was about the projection of will – about who had the loudest, most articulate voice or the final word. But then I started carefully watching leaders I actually respected, the ones who didn’t need to perform. They were the ones who could sit in the middle of a disaster and act as a buffer. They didn’t deflect or blame; they simply stayed steady so everyone else could breathe.

I clearly remember a project launch that had gone completely sideways. We were in a cramped office, and the Executive VP was pacing, looking for someone to tear into. He was shouting, his face a deep red, and he was focused on one of my leads. The lead was twenty-eight, brilliant, and visibly shaking. She was getting ready to pull up some operating logs and start pointing fingers at vendors just to save herself from the blast.

I could have let it happen. I could have joined in on the critique to protect my own standing.

Instead, I remembered those leaders I admired. I leaned forward and told the VP that the responsibility stayed with me. I didn’t offer an excuse. I just sat there and let him vent his fury at me for fifteen minutes. I felt my pulse in my throat, but I kept my voice low.

When he finally ran out of breath, the energy in the room changed. The lead’s shoulders dropped. She wasn’t afraid anymore; she was ready to work. By taking that hit, I had made the room functional again. I had added value by being the one who didn’t pass any stress down the line. I left that room feeling heavy and worked up, but the team was already back at their desks, solving the problem because they knew I was the wall between them and all that noise.

That discipline – giving more than you take – is harder to maintain when the stakes are personal.

In our family, there is a man of my generation who operates on a completely different frequency. He’s the brother who struts into every holiday like he’s the guest of honor. He is condescending to his sisters, talking over them as if their lives are hobbies, and treating the women in the family like a supporting cast for his own drama.

The worst part is the atmosphere he creates; everyone else treats him like entitled male royalty, tiptoeing around his ego just to avoid a scene.

For years, my response to him was to push back. I would demand accountability in the middle of an evening or dinner. I would be cold, or I would try to “fix” the dynamic by calling out his arrogance. I thought I was standing up for what was right, but the net result was that I wasn’t helping. Whether I spoke up or stayed in a stony silence, I wasn’t adding value. I was just adding more friction. Everyone, already disrespected by him, was now just more nervous because of the tension I was feeding. I was making our shared space heavier, not lighter.

The wake-up call came from my middle son. He’s the one who notices everything. After one of these family evenings, he took me aside. He didn’t lecture me, but he was direct. He told me that I needed to be better. He explained that when I got into that defensive, combative mode, it didn’t make him feel proud – it made him feel like he did not want to be in the same room as me. He told me he needed me to be the one who didn’t break, the one who wasn’t constantly reacting to someone else’s ego.

It was a gut-level realization. He wasn’t asking me to change that other man; he was asking me to be a better man in that man’s presence. He was telling me that my job was to be the person who absorbs the complaints and de-escalates conflict.

In an essay I read recently, the author has us think about Louis Theroux’s work as a template for this kind of restraint.

Louis is often the slightest, most unassuming person in a room full of aggressive men who are desperate to prove they are dangerous. When they turn on him, he doesn’t puff out his chest or try to match their volume. He stays in place and takes the verbal blow, remains calm, and keeps his intellect intact. He owns the room precisely because he isn’t afraid of looking weak. He knows he’s right, so he doesn’t feel the need to prove it. By allowing the other person to be the only one making noise, he keeps his dignity and his command of the situation.

There is a profound, quiet power in that kind of presence. Being a man – a dad, a brother, a neighbor – means you leave the room better than you found it. It means you notice the person who is struggling or being talked over, and you offer them a way out of the tension. You absorb the hit when you have to, and you don’t draw attention to the fact that you did it. You just provide the stability that everyone else in the room is looking for.

I am trying now. Not to fix the other men in my family, but to be the anchor. I want my daughter and sons to see a father who gives more than he takes. I want them to see a man who understands that his greatest strength isn’t his ability to correct everyone else, but his capacity to hold the space so everyone else can thrive.

And - I want to try and leave every space, team, interaction, relationship, opportunity, organization, and structure - better than when I got there.

I want to add surplus value - give more than I take. And when I fail to do so, I have the grace to forgive myself and try to do better next time.

Enjoy your loved ones and the rest of your day. Look for adding more value than you take.

And thank you for spending some of your day with me.

Warm regards,

Adi

♻️ If you liked this - Restack this!

➕ Follow Adi Agrawal on LinkedIn

The math of eighty-five and eighty is rich.

These are not just numbers; they are sacred milestones for our family. They represent sixteen decades of survival, sacrifice, and the quiet building of a family. For months, our calendar had been anchored to this single week. The gathering of the tribe. Our three young adult children were scheduled to descend into New Delhi to light the candles for their grandparents. It was the kind of plan that felt solid, inevitable, and essential.

Then, the world shifted.

Conflict erupted in the Middle East. Overnight, flight paths that bridge the West to India – trajectories usually traced in efficient air routes – suddenly looked like jagged scars on a map. Disruption rippled through the global nervous system. For us, it meant the routes my children were booked on were suddenly swerving through zones of high tension.

As a builder and a strategist, my first instinct was to deconstruct the risk. I looked at the logistics. The airlines, digging into their own rigid protocols, refused to offer refunds, cancellations or new routes – they were frozen. The flights were technically “scheduled,” even if the world beneath them was on fire. I sat in my sister’s New Delhi living room, looking at the news cycles and the flight trackers, and felt the weight of constraints.

My wife and I sat down and we made the “rational” decision. We called our children.

“The risk is too high,” we told them. “The airlines are being inflexible, the rerouting is messy, and the tension is rising by the hour. We should reschedule. Let’s aim for the end of the year when things are settled.”

The silence on the other end of the line was cold. I could feel the emotion our children were feeling – a promised moment being liquidated by logic. My parents (the grandparents), who had been counting the days, who had been moving with a newfound vitality at the prospect of seeing their grandchildren – took the news with a quiet, dignified disappointment. They are of a generation that understands sacrifice, so they didn’t argue. But the light in the house seemed to dim.

We were hiding behind constraints. We were letting the friction of the world dictate the decisions impacting our family. We were choosing a safe exit over a complicated entry.

But my children – a class act in every sense of the word – refused to accept the math.

There is a specific kind of agency that develops when you stop asking “What are the rules?” and start asking “What is the intent and what are the options?”

Somewhere along the way, we must have done something right as parents, because my kids didn’t retreat into the disappointment. They didn’t wait for the airlines to make it easy for them or for the world to become more convenient. They didn’t accept my “rational” conclusion that the trip was impossible.

Instead, they sprang into action.

They spent the next forty eight hours in an emotional war room of their own making. They mapped out alternate Pacific routes – long, sweeping arcs that avoided the conflict entirely but demanded a staggering physical toll. They traded the comfort of a 14-hour direct flight for a grueling, 40-plus hour odyssey each way. They navigated through time zones and terminals that made no sense, booking new legs, absorbing the costs, and ignoring the sheer exhaustion of the task.

They chose the 40-hour trek over a “safe” cancellation.

Why? Because they understood a truth that I, in my desire to protect them, had temporarily forgotten:

Joy is not a default setting. It is a manufactured outcome. It is something you have to build, often in the face of every reason to stop.

The arrival in Delhi was a somatic experience.

I watched them walk through the door, staggered by jet lag, their eyes bloodshot from two days of recycled airplane air, but radiant with intent. Seeing them wasn’t just a “family reunion.” It was a demonstration of a philosophy. They had made it just in time for the ceremony the next day.

The look on my parents’ faces – the recognition, the realization, and then the sudden, overwhelming flood of life that filled their eyes – was something no “rescheduled” trip in December could ever have replicated. December is a promise; today is a reality.

As I sat in that living room, watching three generations laugh over a meal that almost didn’t happen, I realized that I was the one being coached. I had looked at the global map and seen only the blockades. My children looked at the same map and saw only the destination.

In my professional life, I often talk about a “Bias to Action.” We look for it in founders, and we demand it in our teams. But we rarely talk about the Bias for Moments.

We spend so much time optimizing for risk mitigation and efficiency that we forget that the most valuable things we ever build are actually memories. And those memories are almost always the result of someone deciding to ignore a very reasonable constraint.

The world is increasingly designed to offer us excuses. The airline says no. The insurance says no. The geopolitical situation says no. The “Macro Outlook” will always find a reason for you to stay home, to stay safe, and to wait for a “better time.”

But “better times” are a mirage. There is only the time we have and the intent we bring to it.

When my kids decided to turn a 20-hour journey into a 40-hour marathon, they weren’t just traveling. They were iterating. They were finding their “Pacific Route” around a global blockade. They were refusing to be “managed” by circumstances. They proved that if the intent is strong enough, the constraints become irrelevant.

You earn the trust of the people you love by showing up when it is difficult, not just when it is convenient. You sustain the delight of a family by proving that your presence is more powerful than the world’s friction.

As I watched my eighty-five-year-old father hold his grandsons’ hands as his granddaughter hugged him, I felt a deep sense of pride – not in my own logic, which has often been flawed, but in the people my children had become. They reminded me that while Expertise and Experience often prevail in decisions, Agency is what actually moves the feet.

We all need to ask ourselves: What are we hiding behind right now?

Are we letting a “rational” obstacle kill a moment that can never be recovered? Are we choosing the safety of a cancellation over the messy, exhausting work of creating joy?

Milestones don’t wait for the world to be peaceful. They don’t wait for the logistics to be flexible. They don’t wait for schedules to be clear or for the “Macro Outlook” to be favorable.

You either choose the moment, or you choose the excuse. You cannot have both.

Our children chose the moment. They chose the 40 hours of travel each way within a week’s window. They chose the exhaustion. And in doing so, they gave my parents –and me – a gift that will outlast any strategic plan I’ve ever written.

They taught me that joy isn’t something you find; it’s something you fight for.

Enjoy your loved ones and the rest of your day. Especially the moments that require you to travel the long way around. Those are the only ones that truly count.

And thank you for spending some of your day with me.

Warm regards,

Adi

♻️ If you know that Moments are more important than Constraints - Restack this!

➕ Follow Adi Agrawal on LinkedIn

The air in a surgical waiting wing is thin. Scrubbed of everything but the scent of industrial bleach and the low-frequency hum of machines keeping the building alive.

I am sitting in a chair designed for durability, not comfort, watching a clock that seems to have its own relationship with time. An elder in the family is behind those double doors. The surgery is technically routine, but nothing is routine when it involves a person you love. In this room, you aren’t a “Chief Strategy Officer” or a “Founder.” The family is a bundle of raw nerves waiting for a signal.

In this space, the power imbalance is total.

On one side, you have Expertise. The doctors, the surgeons, the specialists – the people who hold the map. On the other side, you have the family. They own the stakes and the fear, but have zero agency. We are outsiders in an opaque process that owns our most precious reality.

On the wall of the lobby is a large, backlit sign. It features a smiling doctor holding the hand of a silver-haired patient. The text is bold and comforting: “Your health is our mission. Compassion is our core. We treat you like family.”

In the business world, we call this a Brand Promise. It is the intangible comfort the customer pays for without regret. They aren’t just buying a surgical procedure; they are buying the feeling of being in safe, intentional hands. That is where Delight lives. It isn’t a freebie or a useless add-on. It is the quiet, profound satisfaction of knowing the institution intends to do right by you.

But as the hours crawl by, the behavior of the institution reveals the reality. The doctors speak in a dialect designed to maintain distance, not to create understanding. When we ask a question about the recovery, we are met with a practiced, evasive shrug. We aren’t being treated like family; we are being treated like a ticket number in a high-volume processing plant, and fear is the lever they are using.

Then comes the “Aha!” moment—the one that should keep every builder and scaler awake at night.

Just as the surgeon stepped out to tell us the procedure was “complete but complicated,” an administrator appeared. She didn’t ask how we were holding up. She didn’t offer a chair. She slid a clipboard across the table with a series of “service authorizations” and insurance waivers. And – she was in a hurry - after all, there were a dozen more families to get papered.

They knew we wouldn’t read the fine print. They knew we couldn’t say no. They knew they were taking absolute advantage of our fear to widen their financial margin.

I call this the Desperation Premium. It is the extra value a counterparty squeezes out of you when they know you have no other choice. In that moment, the Brand Promise on the wall becomes a fiction.

It felt eerily familiar.

For twenty-five years, United Airlines, my hometown carrier, had been my go-to airline - even when the fares were a bit higher. Living in Chicago, they were my default. I flew 100s of red-eye flights, I earned their 1K status for a decade and a half, and I was “all in.” I believed we had a partnership. But over time, I watched the company’s intent shift. The rules changed constantly – often mid-year. The goalposts for loyalty moved exclusively in favor of the company. I was a captive audience. They mistook my long-term habit for loyalty, and they began to charge me their own version of a Desperation Premium. I can only imagine the analysis they’d done to assume that flyers like me, “integrated” into their hub, would never leave, no matter how much the service value eroded.

This is the greatest trap in business, especially for founders scaling at pace: mistaking a “stuck” customer for a “loyal” one.

If you are a builder, you need to look closely at the moments your customers are most vulnerable.

Maybe they’ve integrated your software into the very heart of their operations. Maybe their revenue, their reputation, and their peace of mind are tied to your uptime. They are deeply committed. They are “in the surgery.”

When a crisis hits—when the system lags or the data gets messy—how do you respond?

Too many companies use that moment of deep integration as a cage in which the customer is captive and lacks options. They hide behind opaque SLAs. They use their expertise as a shield to keep the customer in the dark. They see a customer’s desperation as a “high-leverage growth opportunity” to push a tier upgrade or a more expensive support contract.

They think they are being smart. They think they are optimizing for the quarter. But they are actually building a resentment machine.

We need to redefine what we mean by Customer Delight. Many scalers treat delight as a luxury – a “nice to have” once the numbers are settled. They think it’s about freebies or useless add-ons.

They are wrong.

Delight is the emotional result of a Brand Promise being kept every day and especially under fire. It is the intangible satisfaction that comes when a company sees your vulnerability and chooses to protect you rather than profit from it. It is the intent to do right, executed with precision, when the customer has no other place to go.

Trust is the foundation, and Delight is the architecture. You can’t have one without the other. Without trust, delight is just a bribe – a “surprise” gift sent to a customer who knows you’re overcharging them. With trust, delight becomes the reason a customer stays for twenty years – not because they are stuck, but because they wouldn’t want to be anywhere else.

And my warning for all builders and operators is that vulnerability is temporary.

Eventually, the surgery ends. The crisis passes. The “hostage” situation expires. And the moment that customer regains their agency – the moment they are no longer dependent on you for their survival – they will move their wallet and trust.

They won’t just leave; they will find an alternative they can actually trust. And because they felt “managed” rather than “partnered,” they will become your most vocal anti-evangelists. They will tell the world exactly how it felt to be squeezed when they were down. They will explain that while your marketing was about “partnership,” your behavior was about “predation.”

I reached my breaking point with United not during a flight, but during a moment of clarity. I realized that the “Brand Promise” I had paid for over two and a half decades had become a transaction of convenience for them, and a cage for me. They had the expertise, but they had lost the intent.

So, I did what every captive customer eventually does when they regain their agency: I walked away.

I moved my wallet and my trust to two Asian carriers that actually understand the architecture of Delight. They don’t just provide a seat; they provide the emotional comfort of a promise kept. They understand that every flight is an opportunity to earn trust, not an opportunity to apply leverage.

Switching after twenty-five years wasn’t about the seats or the miles. It was about finding a partner that wouldn’t charge me a Desperation Premium the next time I needed them.

The modern customer is smarter than the institutions give them credit for. They can smell the difference between a partner and a predator from a mile away. They know when your “Customer Success” department is just a “Retention Bully.”

The Value Gap in the hospital that day was the distance between the sign on the wall and the woman with the clipboard. It was a gap created by a lack of intent.

Our elder got the care she needed, but the hospital never earned her trust. Like every business, there were superstars and compassionate, caring people, and unlike a brand promise, they were the exception. She is recovering. The physical wounds will heal, but the memory of being “handled” instead of “served” will remain.

Every leader needs to ask: Are we building a brand, or are we building a cage?

Are we earning trust every day, or are we relying on the fact that it’s currently too hard for our customers to leave?

Build for the human. Earn the trust in the moments of vulnerability so that you can sustain delight in those moments of growth or fire. Taking advantage of a customer when they are down might look good on this month’s income statement, but trust is the only thing that ensures there is growing income and growth on the balance sheet.

Surprisingly, keeping brand promise costs less and earns more.

Enjoy your loved ones and the rest of your day. Especially the quiet moments. They are more fragile than we think.

And thank you for spending some of it with me.

Warm regards,

Adi

♻️ If you know that Trust is the foundation of delight, Restack this.

➕ Follow Adi Agrawal on LinkedIn

This story is based on real events from my life. I have changed the names and titles of the individuals involved to protect their privacy. I spent a large portion of my career believing that the ultimate currency of leadership was certainty. I thought my value was measured by the precision of my logic – the “rightness” of my conclusions. I had to learn, through realizations in my own home and the near-collapse of a multi-million dollar company, that you can win every argument and still lose the war. Success isn’t a trophy for the most accurate person; it is a byproduct of being the most adaptable one. And now the story…

There is a specific kind of silence that falls over an investor’s boardroom in Greenwich, Connecticut, when a “perfect” plan meets a quarterly business review.

It isn’t the high-voltage silence of Sand Hill Road where everyone is performing for their next round. In Connecticut, the silence is muted, filtered through the grey, flat light of a late winter afternoon. The air in the room felt thin, as if the oxygen was being slowly consumed by the tension between the four people sitting around a glass table.

I was there as a contract “truth-teller.” A small, high-conviction VC firm used to keep me on speed dial for when their normal investment SOPs weren’t working. When the status decks looked perfect, but the cash kept disappearing, they’d call me. I was the guy hired to uncover in four hours what a standard due diligence team would take four weeks to miss. I didn’t look at the features; I looked for where egos and hubris had replaced reality.

Sitting across from me was Mark. Mark was the archetype of the “accurate” founder. He was a former quantitative researcher with a physics degree from MIT, and he had built a risk analytics platform that promised to predict portfolio and market volatility with mathematical certainty. He was the kind of person who spoke in three-decimal-place precision, even when talking about the weather.

On paper, his models were beautiful. In the real world, the company was bleeding out.

“The predictive integrity is holding at 98.4%,” Mark said. He didn’t look at me; he looked at his laptop screen. He was pointing at a heat map that showed a massive cluster of red in his user engagement data. His voice was clipped, a flat staccato that left no room for interpretation. “The churn we are seeing is a data-collection error on the client side. They aren’t tagging the risk events correctly. If they followed the protocol I designed, the efficiency gains would be undeniable.”

I looked at the churn report. It was 40%.

In the real world, a 40% churn isn’t a “tagging error.” It’s a riot. It’s the sound of customers walking away from a tool they find useless or impossible to use.

The market was screaming at Mark, but he couldn’t hear it because he was too busy being right. He was obsessed with the “correctness” of his protocol. It appeared that he would rather the company die in accordance with his math than survive by admitting his math was not reality.

The Managing Partner of the VC firm looked at me. He had spent six months trying to be the “supportive investor,” and he was exhausted. He needed someone to break this down for Mark.

I felt a familiar, prickly heat at the back of my neck. It’s the physiological signal I get when I’m about to stop being a “visitor” and start getting into “uniform”. It is a reflex I carried over from the Naval Academy. You get into role, check-in and you own the next watch.

“Mark, the protocol doesn’t matter if the customer hates using it,” I said. My voice sounded rough in the quiet room. “You’ve built a perfect system for a world that doesn’t exist. You’re arguing for your own brilliance while your customers are walking away to a competitor because that competitor actually solves their problem.”

Mark’s jaw tightened. I could see the pulse hammering in his throat. “The competitor is guessing, Meer. They are lucky. My system is accurate.”

“Your system is accurate, and your company is failing,” I replied. “Success isn’t about the precision of the model. It’s about the result. Right now, your result is zero.”

The silence that followed was heavy. Mark’s eyes went cold. He wasn’t looking at a partner; he was looking at an intruder who was insulting his intellect. I could see the rebuttal forming in his mind – a list of three reasons why my assessment lacked statistical significance. He was preparing to win the argument.

But as I watched him prepare to fight, a memory from two weeks prior hit me. It wasn’t a boardroom memory. It was a late evening conversation with my daughter.

I was sitting in my car with my sixteen-year-old daughter, Sam. We had been arguing about her SAT prep. I had designed what I considered to be a “perfect” study schedule for her – a system based on spaced repetition and optimized time-blocks. I had proven, through three different articles and a spreadsheet I’d built, why this was the only “correct” way to study.

Sam was crying. Not the loud, dramatic crying of a child, but the quiet, exhausted sobbing of a teenager who felt like a project instead of a person.

“You’re right about the system, Dad,” she had whispered. “But I’m so burnt out that I can’t even open the book. You’re right. I don’t know what to say or do anymore.”

I had stood at her door, stunned. My “perfect” spreadsheet was glowing on my phone like a taunt. I had won the debate. I was “right.” And I was currently watching the relationship with my daughter erode in real-time because I couldn’t let go of the need to be the smartest person.

Standing in that Greenwich boardroom, looking at Mark’s defiant face, the two moments snapped together.

I saw in Mark the same pathology I had shown Sam. The need to be “right” is a defense mechanism. We use logic as armor to protect us from the messy, uncertain work of actually being successful. We’d rather hold onto our pride than admit that the world doesn’t care about our spreadsheets.

Success requires the courage to be wrong. It requires the strength to say, “The math failed, let’s find a better way.”

I looked at Mark. I forced myself to take a breath. Tongue to the roof of the mouth. Uncurl the fists. Let the “fixer” adrenaline settle.

I didn’t offer a strategy. I offered a mirror.

“Mark,” I said. “I did this two weeks ago with my daughter. I proved I was right, and I broke her trust. I won the logic, and I lost my girl when she needed me. You are doing the same thing here. You are winning the argument with the market, and you are going to lose your company. Would you rather be the smartest person in the bankruptcy court? Or would you rather be successful?”

The room went completely still. This wasn’t “due diligence.” This was a strike to the hubris that had been masquerading as “data-driven, logical leadership.”

Mark started to offer a rebuttal – something about the volatility index. Then he stopped. He looked at the Managing Partner. He looked at the report of his financial projections. He looked at the heatmap of customers who were leaving him.

The armor didn’t crack – it dissolved. For the first time in four hours, Mark wasn’t looking at a spreadsheet. He was looking at the truth.

“I don’t want to be right anymore,” he said, his voice sounding thin. “I just want this to work.”

He picked up a whiteboard marker. He didn’t draw a new architecture diagram. He didn’t talk about “predictive layers.” He just asked: “If the experience is the problem... what is it they actually need to see to trust us again?”

Later that night, I got home late after several delays at White Plains airport. The house was quiet. I found Rani in the kitchen, finishing a glass of water. She looked at me, saw the weight I was carrying, and didn’t ask about the deal.

“You’re still in ‘Truth-Teller’ mode,” she said, her voice gentle. “I can see the gears turning. You’re trying to optimize the rest of the night before it even happens.”

I put my keys on the counter. I put my phone face down.

“I’m done optimizing,” I said. “I spent the day telling a founder that his pride was the only thing standing between him and success. I think I need to take my own advice.”

I walked over and just sat down at the table. No checklist. No strategy for a “productive evening.” Just being there.

Rani sat across from me. The tension in her shoulders dropped. “How was Greenwich?”

“It was expensive,” I said. “But I think we extracted the value. Mark finally stopped arguing with the market. He’s going to pivot the platform. He realized that being right was just a hiding spot.”

Growth, I have learned, is the process of shedding your defenses. It is the realization that the armor you built to survive the climb – the certainty, the logic, the need to have the last word – is the very thing that prevents you from enjoying the view at the top.

You can be right about systems and be completely wrong about humans - your family, your customers. And in the end, the humans are the ones who will affirm and scale your value and impact.

I hope you enjoyed the story.

Enjoy your loved ones and the rest of your day!

And thank you for spending some of it with me.

Warm regards,

Adi

In the past two months, I have invited three different brand agency principals to join us in the trenches.

The pitch I made to each of them was simple. I will fly you out. I will put you up. Spend one full day in a room with my cofounders. Let’s roll up our sleeves, get whiteboard markers on our hands, and co-create our brand strategy together. Let’s figure out who we are while the engine is actually running.

Their words were different, but the responses were identical and immediate: polite and absolute refusal.

That, they explained, is not how the process works. Their process requires a brief. Their process requires distance. If we wanted to collaborate, we could fly to their cities at various intervals (and meet at a coffee shop on their schedule).

I was offering a high-stakes, collaborative war room. They countered with a polite boundary and a rigid “this is how creatives work”.

Over the last few months, as I’ve been evaluating Go-To-Market (GTM) and branding partners for my portfolio of startups, I have hit this exact same invisible wall. It is an industry-wide cartel. They all share the same rigid approach, fiercely protecting a playbook built for a corporate world that no longer exists, and aggressively selling it to startups that can’t afford to live in it.

If you are a founder, you already know the pitch.

It always starts with the legacy slide. The agency principals sit across from you and proudly list their conquests. They worked on Nike. They touched a Coca-Cola campaign. They executed a rebrand for a fifty-year-old Fortune 500 bank.

They expect you to be dazzled. But building a seasonal ad campaign for a legacy brand with a billion-dollar war chest has absolutely zero correlation to finding product-market fit for a six-month-old startup.

Nike has a legacy; a startup has a hypothesis. Nike is fighting for market share; a startup is fighting for oxygen.

When you invite these agencies to actually step into that fight – to sit with us and co-create – they recoil. They don’t want to collaborate; they want a one-way street. They demand a written brief or a one-way interview. Once they have it, they will disappear into a “Black Box.”

The unspoken subtext is arrogant and clear: Strategy is for the experts; execution is for the founders. But any builder knows that strategy without execution is just hallucination.

This “magic,” they assure you, will take place over several weeks. A team of creatives will retreat into a virtual cave. To even unlock the door to this cave, the price tag starts at $5,000, quickly escalating toward $50,000 for a full “launch.” The output of that check? A heavy, 50-page static PDF.

It is a fundamentally broken model. And here is the hard truth about what founders are actually buying:

The cartel sells “Moments.” Startups need “Motion.”

The traditional agency playbook is strictly episodic. They vanish for sixty days, return for a grand presentation, and slide the legendary “Brand Book” across the table.

But startups don’t really have launches. Startups are in a continuous, daily battle for context. You put something into the market on Tuesday, the market punches you in the mouth on Wednesday, and you have to rewrite your messaging by Thursday morning.

A 50-page static PDF is useless on Thursday morning.

The difference between an agency and an actual startup partner is stark.

The Cartel, nee Agency, thrives on isolation and theater. They want to sell you a “Big Reveal” – a static, impenetrable Brand Book delivered after sixty days of radio silence. They build isolated campaigns that look beautiful on their own portfolio websites, all while absorbing absolutely zero operational risk if your product fails to connect with the market.

Startups don’t survive on reveals; they survive on iteration. They need mechanics willing to climb into the trenches, delivering real-time context instead of polished presentations. A startup’s brand isn’t a PDF; it’s a living mutation that requires continuous, daily feedback loops and partners who are willing to share the risk – and the mutual upside – of figuring it out together. In other words, creativity with real revenue and customer impact.

This rigid adherence to the Madison Avenue playbook isn’t just frustrating – it is a massive market failure. It is leaving high-velocity global ecosystems completely neglected.

Over the past year of writing these Field Notes, I have spent time walking the ground in ecosystems that are catching fire, far outside the traditional tech bubbles.

When I was in India on a builder’s pilgrimage, I watched founders navigating a “river of paper” and pitching in rooms that rewarded theater over substance. But when the rooms emptied, I saw the real work. I learned that real founders don’t build for abstract “Customer Personas” – the kind agencies love to put on slide 14 of their PDF.

Real builders build for the Meera sitting at the reconciliation desk. They ship a clunky prototype that saves an operations lead three hours in a single week. They understand that you must ship the solution before the code. A 50-page Brand Book doesn’t know Meera. To those Indian founders outrunning big brands with raw, working code, a traditional agency isn’t a guardrail; it’s just more gravel and friction in their road to success.

And in Abu Dhabi, surrounded by the raw momentum of the AI boom at Machines Can Think, I met technical founders like Luca. Luca was 29, building unsexy, highly vital logistics models to reduce spoilage in hot climates. He didn’t need a glamorous marketing reveal.

I sat with Luca as an older, quiet investor interrogated his model. The investor didn’t ask about the “fast path to exit” or the “brand narrative.” He asked the hard things: Where does your data come from? What happens when a customer uses it in conditions you didn’t expect? Then the investor said something that every GTM professional should print out and tape to their monitor: “This doesn’t become valuable because your model is clever. It becomes valuable because someone trusts it enough to use it when the pressure is on.”

A traditional agency doesn’t build trust when the pressure is on. They build a launch deck and walk away. They leave founders like Luca alone to face the angry operations team when the system breaks.

There is a global spread of startup ecosystems currently moving at breakneck speed. These founders are building in public, iterating in real-time, and solving massive, messy problems.

And they are completely underserved by the traditional creative class.

Why? Because traditional agencies are too slow, too inflexible, and too risk-averse to keep up. You cannot serve a founder in Bangalore or Abu Dhabi who is pushing code twice a day if your internal process requires a three-week discovery phase just to pick a color palette.

We need a wake-up call on both sides of the table.

For the founders: Stop buying the wrong deliverables. Are you paying a traditional agency $50,000 to “launch” your startup? Are you buying a static PDF, or are you investing in a continuous feedback loop? Guard your runway. Demand motion.

And for the GTM professionals, the strategists, and the branding experts who are tired of the theater: The corporate playbook is dying. The cartel is losing its grip. The next generation of massive companies won’t be built by founders willing to sit quietly while you hide behind your creative process and disappear into your virtual cave.

We don’t need magicians pulling reveals out of a hat. We need mechanics.

If you are a partner who knows how to build in motion, who wants to co-create, and who isn’t afraid to get your hands dirty in the trench, there is an entire world of founders waiting for you.

I have a portfolio of fantastic businesses ready to do exactly that. So do many others I know - in India, in Abu Dhabi, in Chicago.

Enjoy your loved ones and the rest of your day!

And thank you for spending some of it with me.

Warm regards,

Adi

This story is based on real events from my life several years ago. I have changed the names and titles of the individuals involved to protect their privacy. I spent years thinking leadership was about having the right answers, only to learn – painfully – that it is actually about being strong enough to hear the hard questions.

There was a specific kind of silence that fell over a boardroom in Cabo. It was different from the silence in Chicago or New York. In Cabo, the silence was heavy, underlined by the indifference of the ocean crashing a few hundred yards away and the hum of aggressive air conditioning trying to keep twenty high-net-worth individuals from sweating through their linen shirts.

We were at an offsite. Five stars, ocean view, spouses attending “activities”. The setting was designed to foster “alignment” and “vision,” but mostly it just raised the stakes. When you are arguing about the future of a company while your wife is having margaritas with the CEO’s husband by the pool, the professional and the personal don’t just blur; they collide.

I was there as the Chief Strategy Officer. My job, on paper, was to make sense out of chaos. From the Naval Academy, where order is survival, to my years as a systems engineer, my career has been built on a simple premise: I find the signal in the noise. I fix the mess.

Jim P., our CEO, was in fine form. Jim was brilliant – a visionary in the truest, most exhausting sense of the word. But he was also rude and derisive, and he had a memory that selectively deleted the contributions of everyone else in the room.

We were deep in a session about transformation targets. Jim was tearing into the VP of Product, a good man who was currently stuttering over a roadmap. Jim didn’t just disagree; he dismantled.

“It’s lazy thinking,” Jim snapped, tossing the report onto the mahogany table. “It’s small.”

The room flinched. This was my cue. I stepped in, not because I wanted to, but because it was a reflex. It was the muscle memory of someone who has spent a decade smoothing over rough edges.

“I think the point Jim is making,” I said, keeping my voice low and even, “is that the model needs to match the market opportunity. If we look at the systems view...”

I rephrased Jim’s insult into a strategy. I turned his derision into a “challenge.” The tension in the room dissipated. The VP shot me a grateful look. I felt a familiar, tired satisfaction. I had stopped the bleeding. I had kept the machine running.

That evening, during the cocktail reception, I found myself standing next to P.G.

P.G. was a board member and a celebrated Fintech CEO. He was tall, careful, and moved with the slow, deliberate gravity of a planet. He was politically astute, warm, and often seemed indecisive only because he listened more than he spoke.

I was holding a drink, watching the sun go down, expecting a nod of approval for how I handled the afternoon session.

“You’re very good at that, Meer,” P.G. said, looking out at the Pacific.

“At what?” I asked.

“Translation,” he said. He turned to face me. His eyes were kind, which made what came next worse. “But you aren’t helping him. You’re his flak jacket. You absorb the shrapnel so he never feels the impact of his own behavior. And frankly, it makes the rest of us trust you less. We need a Chief Strategy Officer, not an enabler.”

The air left my lungs.

My chest tightened. It was a physical blow. The heat started at the back of my neck and crawled up to the tips of my ears, hot and prickly. My pulse hammered in my throat.

The instinct to fight was immediate and violent. I wanted to debate him. I wanted to tell him that without me, Jim would have fired half the executive team by lunch. I wanted to list the three crises I had averted just this week. I am the only reason this works, I thought, the indignation rising like bile.

But I froze. Because the look in P.G.’s eyes wasn’t hostile. It was disappointed. And that disappointment triggered a memory from three weeks prior, twenty-five hundred miles away, in a dark car on a rainy Thursday.

I was driving my sixteen-year-old daughter, Sam, to a friend’s house. The windshield wipers were swiping back and forth, keeping time with the uncomfortable silence in the cabin.

Sam was smart, sharp, and at that time, deep in that phase where I was less of a Dad and more of an obstacle. We had been arguing about her schedule – she was overcommitted, stressed, and dropping balls.

“You just need a schedule,” I had told her, frustration leaking into my voice. “If we map out the week, prioritize the big rocks...”

She had turned to look out the window. “Dad, stop.”

“I’m trying to help you win back your time, Sam.”

“No, you’re trying to fix me,” she said, her voice quiet. “You treat me like I’m one of your projects. You’re always managing me. You never just... hear me. You just want to get to the solution so you can stop listening.”

At the time, I had dismissed it. I told myself she was just tired. I told myself I was the responsible one, the one with the answers.

But standing on that terrace in Cabo, with P.G.’s words hanging in the humid air, the two moments snapped together.

You’re managing.

You’re an enabler.

You’re not listening.

The common denominator was me.

I realized I approach relationships the way I approach systems engineering. I look for friction, and I try to eliminate it. I look for noise, and I try to filter it. But people aren’t systems. When you “manage” a CEO’s rudeness, you aren’t fixing it; you’re hiding it. When you “manage” a daughter’s stress, you aren’t relieving it; you’re invalidating it.

I looked at P.G. I forced myself to take a breath. Tongue to the roof of the mouth. Uncurl the fists. Let the adrenaline crest and fall.

I didn’t have a clever comeback. I didn’t have a strategy.

“You’re right,” I said. My voice sounded rough.

P.G. didn’t smile, but he nodded. He didn’t offer a platitude. He just let the truth sit there between us, heavy and real.

“So,” I asked, “what does it look like if I stop translating?”

“It looks messy,” P.G. said. “It looks like Jim having to clean up his own messes. And it looks like you risking his anger to save his leadership.”

Later that night, I went back to our room. My wife, Rani, was packing. We were flying out the next morning. The room was a disaster of suitcases and clothes, the debris of a week of forced socialization.

I sat on the edge of the bed. I watched her fold a silk scarf with precise, angry movements.

“You’ve been checking emails for the last hour,” she said, not looking up.

“I’m just closing out some threads,” I said automatically. “Clearing the deck for travel.”

She stopped folding. “Meer, you’re here, but you’re not here. You’re always optimizing the next hour. You’re always in “strategy mode”, never present.”

Three strikes.

I looked at her. I looked at the chaos of the suitcase. The old Meer would have explained the importance of the emails. The old Meer would have pointed out that my work paid for this trip. The old Meer would have been right, and he would have been alone.

I put the phone on the nightstand. Face down.

“You’re right,” I said.

Rani looked at me, surprised. I usually have a rebuttal. I usually have a checklist in my head explaining why I am correct.

“P.G. kicked my ass tonight,” I admitted. “And Sam kicked it three weeks ago. And you’re kicking it now. I think... I think I’ve stopped knowing the difference between leading people and handling them.”

Rani sat down next to me. The anger in her shoulders dropped an inch. “So what’s the strategy, Strategy Officer?”

“I don’t have one,” I said. “I’m just going to sit here.”

She leaned her head on my shoulder. It wasn’t a movie moment. The AC was too loud, and I was terrified about what would happen when I stopped being the “fixer” for Jim. I didn’t know how to do it yet.

But sitting there, in the quiet, felt like a start.

Growth, I am learning, isn’t about acquiring a new skill. It’s about shedding an old defense. It’s about realizing that the armor you built to survive the Naval Academy or the corporate ladder is too heavy to wear at the dinner table.

It turns out, you can be right about the system, and wrong about the human. And the only way to fix that isn’t to think harder. It is to stop, listen, and let the hard truth change you.

I hope you enjoyed the story.

Enjoy your loved ones and the rest of your day!

And thank you for spending some of it with me.

Warm regards,

Adi

At 7:42 a.m., Maya clicked our digital ad between two check-ins. A Slack thread titled Manager support sat pinned at the top of her screen. She hadn’t opened it yet, but she already knew what it would contain: another manager asking for help with a conversation they didn’t want to mishandle.

She typed: reduce manager burnout microlearning wellness program.

She landed on our page.

Wide margins. Soft photos. Awards. Partner logos. A large headline:

A button beneath it: Learn more.

Maya scanned for the words she used at work – manager, burnout, after-hours, hard conversation. She scrolled. The page offered “Our platform,” “Our story,” “Trusted by,” and feature tiles with names that didn’t match what she was trying to fix. There was no sentence that told her who this was for. There was no sentence that told her what would be different next week.

She closed the tab.

Then she forwarded the link to her HRBP lead: “Do you know what this actually does for managers?”

Her HRBP replied, “Not sure. Want me to ask them?” – and Maya answered: “Yes. If it’s real, we need it.”

That exchange reached us because our growth team routes unclear customer messages to a shared inbox that I monitor. I’m the Chief Strategy Officer.

At 8:11 a.m., the thread hit the alias. At 8:20, someone posted a screenshot in our launch channel. By 9:00, it was on the projector beside our homepage. I walked in and saw Maya’s sentence sitting next to our headline, and the gap was obvious.

I read her line out loud.

Then I looked at the screen and asked, “Where does she get her answer?”

A designer’s hand went to the mouse. The page scrolled a little, then a little more. The room stayed focused on the screen.

The chat widget pinged. “Are you for HR teams or individuals? I can’t tell.”

Another ping: “What does this replace?”

Someone started typing a reply and stopped. The question was fair. The page wasn’t helpful.

That afternoon, Maya joined the call. Camera off. She asked the same question she’d emailed. “Does this reduce burnout for managers,” she said, “or is it general learning content?”

We answered with the sentence we always reached for when we wanted to sound solid: patent pending method, tailored programs, universal impact, any company. It was smooth, and it did not land.

Maya didn’t argue with it. She skipped past it. “Tell me what my managers do in week one,” she said. “What changes on Monday?”

After the call, her email arrived.

Subject: Follow-up — unclear fit

“Not sure this is built for manager burnout vs general L&D. If you have a concrete example for a 600-person tech org, send it.”

The CRM note was shorter: No next step. Unclear fit.

The next morning, she forwarded a screenshot from their ticketing system.

Manager support tickets, last 7 days: 18.

Under it were subject lines: difficult conversations, workload overload, team conflict, performance plan anxiety, new manager needs help.

At 9:05 a.m., I called Maya and asked if she could spare ten minutes to look at the page with us. She generously agreed.

I put her on speaker in the room.

We asked what she needed to see right away, before a demo or a deck. Maya spoke in the practical, clipped way people do when they’ve explained the same problem too many times. She didn’t want to translate our language into hers. She wanted the page to say, plainly, that it was for managers – and for the People Ops teams buying support for them. And she wanted the second sentence to be something she could repeat internally, because she would be asked, almost immediately, what changes first in their world if they pay for this.

When she described “first,” she didn’t talk about culture or transformation. She talked about evenings. She talked about the late-night pings that pull HR into a manager’s panic after hours because there wasn’t enough support earlier in the week.

We read the first screen to her. Maya listened until the end and said, “That could be anything.”

We scrolled and read the next section. She waited again, then said, “Still nothing that tells me it’s for my managers or me.”

On a laptop at the end of the table, the chat message from yesterday was still open: HR teams or individuals? Maya heard it and said, “That’s the same problem. I shouldn’t have to guess.”

We went back to the first line and replaced it while she listened. No debate; we narrowed into one job: write a sentence Maya would forward with clarity.

The first line named the buyer and the person the buyer was trying to protect: People Ops and Managers.

For the next line, Maya kept returning to the same phrase. “Late-night escalations,” she said. “After-hours.”

So that line used her words: Fewer late-night escalations to HR.

When we got to the button, Maya didn’t want another invitation to browse. She wanted proof she could picture. The button became: See a manager example.

At 11:10 a.m., I replied to Maya in the same thread. I pasted a screenshot of the updated first screen and wrote one sentence: “Is this closer to what you meant?”

At 11:47 a.m., she wrote back.

“Now I understand what it is,” she said. “Can you show this to me with a realistic situation?”

She pasted details: two new managers, a reorg, time zones, one employee on a performance plan.

A calendar invite followed from her assistant.

Title: Manager support session — your scenario

Tuesday, 2:00 p.m.

In the notes, Maya wrote: “Stay on what managers will do in the first week.”

On Tuesday, we started where she pointed: a manager at 9:12 p.m., staring at a message, deciding whether to respond now, delay, or avoid it. We stayed with the next day’s calendar and the conversation that keeps getting postponed. We showed what a ten-minute lesson looks like when the day is already full, and what the first check-in looks like when a manager doesn’t want another meeting but still needs a place to practice the words.

Afterward, Maya didn’t send a recap. She made a decision.

At 4:38 p.m., her email came in: “Pilot with product org. I want fewer late-night escalations.”

Our head of growth replied with dates. Maya’s assistant returned three options.

Later, in the launch channel, someone posted Maya’s original question next to the updated first screen. A few reactions appeared, then the channel moved on.

Folks, this is a story example I have lived through countless times. Too often we are marketing without clarity of the customer and the offer. We make it about ourselves.

I hope you enjoy this new format I am trying.

Enjoy your loved ones and the rest of your day!

And thank you for spending some of it with me.

Warm regards,

Adi

I landed in Abu Dhabi with a question I didn’t want to admit was inside me, because it makes me feel like the kind of person who can’t enjoy a good thing without cross-examining it: Is this real momentum, or is it performance?

The drive into the city from the airport didn’t answer it. Still, it did give me enough evidence to stay curious – roads that worked, construction that looked purposeful, and a certain confidence you feel when a place expects to be judged on delivery rather than on promises. I’ve seen cities that look busy and remain hollow, and I’ve seen cities that look quiet and are quietly busy building a future. The UAE is making a loud bet, so the only question that matters is whether the bet has substance behind it.

The next morning, I was at Machines Can Think, hosted at the Park Hyatt Abu Dhabi Hotel and Villas, and the venue itself offered its own kind of contrast: sunlight and water outside, panels and ambition inside, and enough people moving from room to room that you could feel something forming in real time. Between sessions, the lobby became a river of introductions—founders making their second impression, investors deciding whether to have a conversation, recruiters scanning for the next person they can place into someone’s story.

That’s where I met Luca.

Not his real name, but close enough to the truth. He’s twenty-nine, European, wicked smart in the way that makes you forget to check whether the person has ever actually run anything larger than a small team. He has never been to the United States but looks forward to it.

Luca’s map includes Brussels, Frankfurt, Berlin, and airports. Four years of building data and machine learning models had given him that particular kind of competence that’s common in young technical leaders: he knows what breaks, he knows what’s messy, he knows what people hide. What he didn’t yet have was business scar tissue – those small humiliations that come from selling, pricing, negotiating, and being told “no” by someone who does not care about your intelligence.

He wasn’t trying to dominate the room. He wasn’t overly polished. He had that look I recognize because I’ve worn it myself: a person who has done the homework, arrived in the right place, and is now trying to figure out which doors will actually open.

We were walking between sessions when he asked what I thought of the city.

I told him, almost casually, “It reminds me of the U.S. in the late nineties and the early 2000s – money, talent, ambition, people arriving with something to prove. It can be a good thing. It can also create a lot of noise.”

He stopped walking for a second, the way people do when a sentence gives shape to something they’ve been sensing but couldn’t name. Then he smiled with relief.

“That’s exactly it,” he said. “I’m trying to tell the difference.”

His startup had a narrow focus. No grand claims. He wanted to help logistics operators reduce spoilage and reroute intelligently in hot climates – unsexy work with measurable outcomes. If it worked, nobody would clap. It would simply show up in fewer losses, fewer complaints, and a reduction in small failures that everyone quietly tolerates because fixing them takes time and attention.

We kept walking. It wasn’t a dramatic conversation. It was the kind that happens in motion, when you’re both half-present because you’re trying to find the next room and you’re also trying to decide how honest to be with each other.

“What feels different here,” he said, “is that people answer. You don’t spend weeks trying to decode what a maybe means.”

That made me pause, because he wasn’t talking about friendliness. He was talking about clarity. In too many places, people keep conversations alive because it feels safer than deciding. They like the feeling of being adjacent to something interesting, and they worry that saying “no” closes a door they might want later. So you get polite drift – messages that sound warm and lead nowhere.

Here, Luca was experiencing something rarer: clean replies. Not all “yes.” Not even many “yes.” Just less of the “maybe”.

Then he said the one thing that made me understand why he was uneasy.

“I don’t know which people are real.”

He didn’t say it dramatically. He said it like someone reporting a basic fact. It was the founder’s version of a question most of us carry quietly in unfamiliar gatherings: who is actually here to build something, and who is here because the room is hot, the attention is cheap, there may be money in the room, and nobody wants to miss the moment.

Later that afternoon, he asked if I’d join him for a meeting with an investor. We walked into the main hotel lobby – pleasant, chilled air, expensive light, and the hum of people trying to be casual and calculating. We stood on one side, watching small clusters form and dissolve: founders with practiced optimism, operators with tired eyes, investors moving with that particular calm that comes from knowing you have the money and you can leave at any time.

The investor arrived friendly and polished, the kind of person who makes you feel seen while you’re talking. Luca gave him the six-minute version of his company – what it did, why customers would pay, what he had learned so far, and where he was stuck. It was a good pitch. Luca can think fast, and he doesn’t hide behind fluff. He’s the kind of technical founder who can explain a messy idea without pretending it’s simple.

The investor listened and then asked a single question that revealed his orientation: “What’s the fastest path to exit?”

You could see Luca’s mind split into two tracks. One track said: this is what money wants, this is what you’re supposed to answer to. The other track said: if I answer this too eagerly, I’m agreeing to build my company around someone else’s clock.

Fifteen minutes later, another investor joined. Older, quieter, not interested in being entertained. He didn’t start with valuation or the future. He started with what sounded hard to Luca.

Where does your data come from? How does it change? What happens when a customer uses it in conditions you didn’t expect? What happens if your best engineer leaves? What will you do when a customer says the system is wrong, and their operations team is already angry?

Luca answered well, but I could see something shift in his posture. This was a different kind of conversation. It wasn’t about the money. It was about the work.

At one point, the investor said, almost in passing, “This doesn’t become valuable because your model is clever. It becomes valuable because someone trusts it enough to use it when the pressure is on.”

After the meeting ended, Luca and I walked out together. We didn’t talk for a minute, partly because he was doing the mental sorting founders do: which feedback is real, which feedback is just words, which advice would still make sense months from now.

Then he asked me what he should do.

I hadn’t arrived intending to coach. I came to see the region, feel the energy, and test my own assumptions. But experience does this to you in rooms full of young builders: people decide you must have a map, so they ask you for directions. If you’re not careful, you start acting like you’re there to teach, when the truth is you’re still learning.

I told him the only version of the truth I could.

“Don’t build your company for the person who wants a fast ending,” I said. “That’s their preference. Build it so customers keep using you after the initial novelty wears off.”

He nodded, and then he asked the kind of question that revealed his inexperience: “How do I know which investor I should listen to?”

“You don’t,” I said. “Not at first. You learn by watching what they reward. If someone only wants to talk about the finish line, they’ll push you to cut corners you’ll later regret. If someone wants to talk about the parts that are hard – data, adoption, reliability – they may be annoying, but they’re at least living in the same reality as your customers and your engineers.”

He looked at me for a second and then said, quietly, “I’m good at the product. I’m not good at this part.”

There was no self-pity in it.

And this is where I became the accidental coach, because once someone says that, I feel compelled to give them something useful.

“Your advantage,” I told him, “is that you don’t need to fake competence. Your risk is thinking that competence is enough. This part” – I waved at the lobby, the introductions, the money – “this part is its own skill. You’ll get better. Just don’t let it decide what you build.”

We stood there for another minute, and he asked two more practical questions about hiring and how to avoid being pulled into the wrong conversations. I answered as honestly as I could, and then he said something that surprised me with its simplicity.

“I needed someone to say that. Thank you.”

I laughed because it was either that or turn it into a sentimental moment in a hotel lobby, and I’m not built for that.

“Then I’ve accidentally provided value,” I said. “Please don’t tell anyone. It’ll ruin my reputation.”

He smiled, and in that smile I saw real gratitude from someone smart enough to know what he doesn’t yet know, and brave enough to ask for it anyway.

The next morning, I had my own reminder that the story isn’t just about founders and investors. I was leaving a session when a young engineer stopped me in the hallway. He wasn’t pitching. He wasn’t networking. He was trying to understand what kind of life he could build here.

“What should I get good at,” he asked, “if I want to still matter in five years?”

That question forces the only test that counts.

A fast-growing place can import talent. It can import capital. It can generate excitement. The harder thing is turning those into continuity – careers, mentoring, companies that last long enough to teach people how to build, and institutions that make trust a normal expectation rather than a special feature.

And then there are the millions no one is looking at.

At the conference, “one million” came up more than once – not as a slogan, but as a target. The UAE has publicly talked about training one million people in AI skills by 2027 through a nationwide program launched with Microsoft, and Dubai has its own “One Million Prompters” push aimed at prompt and AI tool literacy. Those numbers are ambitious anywhere. What’s different here is that they’re stated out loud, with timelines, like something someone will be held to.

This isn’t just a UAE challenge. It’s a global one. Most countries are going to discover, late, that they have two shortages at once: deep AI specialists, and the far larger group of managers and operators who need enough practical literacy to use these tools without being fooled by them. The UAE is simply more explicit about the scale of the catch-up.

By the time I left, my answer to my own opening question had sharpened.

The energy is real. The ambition is real. The seriousness is real in enough rooms that it can’t be dismissed as just theater.

But the failure mode is also real: speed can create a lot of winners who never learn to build anything sturdy, and a lot of talent that never feels settled enough to commit.

Luca taught me that in a way no keynote could. And I learned about the UAE, the region, about the quality of its ambition, and about the kind of people it attracts when the bet is big enough.

I didn’t leave with certainty. I left with something better: a clear sense of what to watch, and a little more respect for what it takes to turn excitement into something durable.

Enjoy your loved ones and the rest of your day!

And thank you for spending some of it with me.

Warm regards,

Adi