The Drift You Do Not See

When Rufus first called me, I could hear the strain in his voice.

It was not panic. Not collapse. Not the sound of a man whose company was visibly failing.

It was something more difficult to name.

His business was doing well by the measures most people trust. The company had passed $4 million a year in subscription revenue. They had raised a major round of outside funding eight months earlier. From the outside, the story looked strong. Growth. Momentum. Confidence. On paper, it was the sort of company others might envy.

Yet Rufus said, “I don’t know what’s wrong. We’re hitting our numbers. But something feels off. The team feels off. I feel off.”

I have learned to take that sentence seriously.

Very often, it points to drift.

Not spectacular failure. Not the kind that announces itself in headlines or boardroom drama. Drift is quieter than that. It is the gradual movement away from an original intention through small concessions, tolerated inconsistencies, and reasonable decisions that slowly accumulate into a different life.

That is one of the hardest things about drift. By the time it shows up in the visible measures, much of the damage has already been done elsewhere. In judgment. In culture. In the quality of attention people bring to their work. In the subtle weakening of self-trust.

I agreed to spend three days with Rufus and his team.

What I found was not chaos. It was something more common, and in many ways more dangerous: a capable company slowly becoming shaped by what pressed on it, rather than by what it had chosen to build.

Day one: the room was busy, but the centre was missing

The company operated out of a converted warehouse in an industrial part of the city. When I arrived, the place had that familiar atmosphere of modern effort: internal messages firing, people moving quickly, brief standing meetings happening in corners, a wall thick with sticky notes mapping several major initiatives at once.

Everything looked active.

That afternoon I sat in on the leadership meeting. Rufus was there with Elena, his co-founder who led product, Raj, who led engineering, and Damon, who led sales. The agenda was full: a feature request from a larger client, a hiring push, a possible partnership, a customer complaint that had escalated.

What struck me was not the volume of work, but the shape of the conversation.

Every item was treated as urgent. Decisions came quickly, often from whoever spoke with the most confidence. Nothing seemed absurd. Yet nothing seemed clearly ordered either.

So I asked a simple question:

What is the company’s main priority this quarter?

I got four answers.

Rufus said growth.

Elena said proving they could serve larger business customers well.

Raj said fixing the old design problems in the system that were slowing everything down.

Damon said closing three specific deals already underway.

None of the answers were foolish.

But they were not aligned.

That is one of the first signs of drift I often see. Not a lack of goals, but a lack of ordering among goals. A team can be full of aims and still lack a governing priority strong enough to rank them. When that happens, effort scatters. People remain diligent. They remain sincere. They may even remain impressive. But their work no longer builds in one direction. It loses force because it is being spent across too many fronts at once.

Research on goal-setting helps explain this. Clear and demanding goals usually produce better results than vague aspirations. But there is another side to the matter. When several important goals compete for the same limited attention, the result is often not disciplined excellence. It is fragmentation.

The team still looked productive. Revenue was growing. Features were being released. From the view of a dashboard, the company appeared to be advancing.

Then I asked Rufus how much of the previous quarter’s work had directly advanced the main direction they had set for the company and explained to investors.

He paused.

“Maybe forty percent,” he said. “Maybe less.”

The rest had been reactive. Customer requests. Internal problems. Opportunities that looked too attractive to ignore. Each decision made sense in the moment. Taken together, they told another story.

The company was no longer being formed chiefly by a chosen direction. It was being formed by response.

Day two: no one had chosen drift, but everyone had helped build it

I spent the second day in one-to-one conversations with the leadership team.

What emerged was not one decisive mistake. It was a long chain of smaller allowances that had slowly become normal.

Raj told me about a serious weakness in the underlying design of the product. The team had identified it six months earlier. At the time, fixing it properly would have taken about three months of concentrated work. Instead, they kept patching around it, because something more urgent always stood in front of it.

Each patch solved the immediate problem.

Each patch also made the system more tangled.

“We kept saying we’d get to it next quarter,” he said. “Now it would take six months, and we still don’t have the time.”

That is how drift raises its price.

A poor choice does not merely cost what it costs in the moment. It changes the conditions of future choice. The temporary workaround becomes the new baseline. The problem settles in. What once required moderate correction later requires painful reconstruction.

Elena described a related problem from the product side.

In the beginning, the company had been sharply focused. They solved one specific workflow problem for one specific kind of logistics company. That clarity had given the product force. But over time, customer requests pulled them into nearby problems. Each added feature could be defended on its own. Each one answered some genuine demand. Yet together they blurred the centre of the product.

Now the company was trying to compete across three different categories, and it was not clearly the best in any of them.

I asked her when they had decided to widen their scope.

“We didn’t decide,” she said. “It just built up over time.”

That sentence stayed with me, because it captures the nature of drift precisely.

Drift rarely arrives as a declared policy. It enters through accommodation. Through the easy yes. Through the refusal postponed. Through the pressure of the immediate. One customer asks for something slightly outside the company’s real direction. One competitor launches a new feature and creates anxiety. One internal problem makes a shortcut feel justified. Each choice seems small enough to absorb.

Yet each choice also changes the frame for the next one.

What was once an exception becomes expectation.

What was once a departure from the plan becomes the plan.

Damon, who led sales, added another piece of the picture. In the company’s earlier years, the team had been disciplined about the customers they pursued. They knew who they served best and they stayed close to that.

But after taking outside funding, the pressure to grow rose. They loosened their standards.

“We started taking deals that didn’t really fit,” he told me. “The revenue looked good, but those customers churned, or they wanted special treatment. Now half our support capacity is going to accounts that are never going to grow with us.”

This is what hidden cost looks like in real life.

The revenue from those deals was visible. It appeared on the board, in the updates, in the numbers that reassured everyone. But the cost remained harder to see. The better customers they no longer had time to pursue. The support team carrying a heavier burden. The product getting dragged further from its proper centre. The energy consumed by customers who would never really fit.

The visible numbers looked healthy.

The structure underneath them was becoming weaker.

Day three: bringing the hidden pattern into the room

On the third day, I gathered the leadership team for a working session.

I was not there to hand down a clever formula. The first task was more basic than that. I needed to help them see together what each of them had partly felt on their own.

So I began with a question:

What was the company you set out to build, and how does that compare with the company you are now running?

The room went quiet.

Elena spoke first.

“We set out to be the best solution for a specific problem. Focused. Sharp. Now we’re becoming a general tool trying to do too much for too many people.”

Raj followed.

“We said we’d build something clean and technically strong. Now the shortcuts are piling up, and every new feature takes twice as long as it should.”

Then Damon:

“We wanted customers who loved us and would grow with us. Now we’ve got customers who mostly tolerate us and complain constantly.”

Rufus listened. Then he said something that seemed to me the central sentence of the whole engagement.

“I think we drifted because we stopped noticing. Every individual decision seemed reasonable. We never stepped back and looked at the pattern.”

That is the diagnostic problem.

Most systems of measurement are built to track outcomes: revenue, customer loss, delivery speed, growth. They are much weaker at tracking alignment with purpose. A company can continue to meet visible targets while steadily moving away from the very position, discipline, and clarity that made those targets possible.

By the time the visible outcomes worsen, the deeper damage has often been accumulating for a long while.

So I gave them a simple exercise.

I asked each leader to estimate what share of their team’s effort in the previous quarter had gone toward work that directly advanced the company’s original direction. Then I asked them to estimate the cost of the remaining work, not only in money, but in time, morale, attention, and lost future options.

The exact numbers differed.

The pattern did not.

Roughly half of their effort had been consumed by reaction, widened scope, and maintaining choices that should have been made differently in the first place. Once they began tracing the longer-term cost, the picture became sobering. They had been paying a hidden tax every quarter. Worse still, because they had postponed the deeper structural corrections, that tax had been growing.

Elena put it plainly:

“We’ve been borrowing against the future to keep the present going.”

That line named it with unusual precision.

The way back was not intensity. It was structure.

One of the common misunderstandings about drift is that people think the answer is more force. More discipline. More urgency. More motivational language.

That is usually wrong.

In cases like this, the problem is seldom a lack of sincerity. The team was not lazy. They were not cynical. They were not indifferent. The problem was that the structure around their attention was too weak to withstand pressure.

So we worked on structure.

First, they needed one governing priority.

Not a long list of goals. Not a values poster. One central question strong enough to rank the rest:

Does this action make us better at solving our core customer’s main problem?

Every new feature, partnership, sales opportunity, and internal initiative had to pass through that question. The answer would not always be no. But the question itself needed to become unavoidable.

Second, they needed to decide in advance how they would respond to the situations that had repeatedly pulled them off course.

A team may know what matters in theory and still fail when pressure arrives in concrete form. So we identified the recurring moments of drift and built pre-decided responses.

If a customer requested something outside the company’s real direction, the default answer would be no, unless there was a compelling strategic reason otherwise.

If a sales opportunity did not fit their ideal customer, they would walk away.

This matters because tired judgment is unreliable. Clear prior commitment often succeeds where moment-by-moment resolve fails.

Third, they needed regular review, not merely of performance, but of alignment.

Each month they would ask:

What did we do?
How much of it actually moved the company in the direction we chose?
Where did we drift?
What did that drift cost us?

This was not designed as a ritual of blame. Its purpose was simpler: shorten the time between deviation and correction.

Fourth, they needed to watch earlier warning signs, not just late outcomes.

Revenue and customer loss are slow signals. By the time they move, many formative choices have already been made. So the team began reviewing more immediate indicators: how much product work was serving the core problem rather than side requests, which kinds of customers were consuming support, and whether the sales pipeline was filling with good-fit or poor-fit accounts.

Finally, they needed permission to stop.

This sounds obvious, but it is not. Teams often continue pouring time into an initiative simply because they have already invested so much in it. So each quarter, active projects had to justify themselves again from the present, not merely from the past.

The question was:

Knowing what we know now, would we start this today?

That single question can save a company months of waste.

Six months later: the company was not transformed, but it was becoming coherent again

When I checked in with Rufus six months later, the headline numbers had not changed dramatically.

But the quality of the work had.

They had cut two feature lines that were consuming engineering time without strengthening the company’s position.

They had exited three customer accounts that were taking too much support and giving too little in return.

They had begun addressing the old design problem they had postponed for so long. Not fully, but enough to restore a more reasonable pace of progress.

More importantly, the team felt different.

There was more coherence in their decisions. Meetings were shorter. Priorities were clearer. There was less argument because there was less confusion about what deserved the company’s energy.

Rufus said, “The biggest change is that we see the drift now. We catch it early. We still make mistakes, but we don’t let them keep building.”

That is a real victory.

The goal is not a company that never deviates. The goal is a company that notices deviation sooner, names it more honestly, and corrects it before it hardens into structure.

The founder had been drifting too

There was another part of the story that mattered just as much.

After the team sessions ended on the third day, Rufus asked whether we could speak privately. We sat in his office, a glass-walled room overlooking the main floor. He was quiet for a while.

Then he said he had been thinking about what Elena had said. They had not sat down one day and chosen to widen the company’s scope. It had simply built up. Then he added:

“That’s true. But I’m the one who let it build up. I’m the one who said yes when I should have said no.”

That is the point where company drift and personal drift meet.

The business had moved away from its original direction. Rufus had too.

The founder who had started the company had been clearer, firmer, more willing to make hard decisions. Over time, that version of him had been displaced by someone more reactive, more managerial, more ruled by immediate pressure.

I asked him to describe a normal week.

He listed investor updates, customer escalations, hiring interviews, board preparation, one-to-ones, conversations about the next funding round, media requests, speaking invitations. Somewhere inside all that, strategic thought was supposed to happen.

In practice, it barely did.

“I haven’t had an uninterrupted hour to think in months,” he said. “I’m always moving. I’m not sure the movement is taking me anywhere.”

That sentence reaches beyond business.

Many leaders know what they ought to be doing. They know they should be setting direction, protecting the team’s focus, and making decisions that shape the future rather than merely pacify the present. They believe these things sincerely. Yet each day, the immediate demand pushes the deeper responsibility aside.

Modern psychology helps explain why.

The cost of saying no to a present demand is felt now. An unhappy investor. A frustrated customer. A waiting colleague. The cost of neglecting deeper strategic work is felt later, spread across future months, harder to trace to any one choice.

So the urgent keeps defeating the important.

Not because people are stupid.

Because they are human.

I asked Rufus when he had last made a decision that genuinely hurt in the short term because it was right in the long term.

He sat with it.

“Maybe a year ago,” he said. “We turned down a big customer because they wanted changes that would have pulled us away from what we were building. It was hard. But after that, I think we stopped making those calls. The pressure got higher. The stakes felt bigger. It became easier to accommodate.”

The older moral traditions understood this well.

Aristotle described the condition of acting against one’s better judgment because immediate appetite overpowers reason. The Stoics warned against scattered attention and against surrendering one’s life to what is loud rather than what is rightfully within one’s charge. Confucian practice placed such weight on daily self-examination because small departures, if not checked, become habits, and habits become character.

Old wisdom and modern research converge here.

Repeated deviation does not remain mere behaviour. It becomes formative. It changes the person. Each time Rufus chose accommodation over discipline, the next accommodation became easier, and the next hard decision became harder.

He was not only leading a drifting company.

He was becoming a drifting leader.

Then he said something more revealing still:

“I used to trust my own judgment. I knew what mattered. I wasn’t afraid to make unpopular decisions. Somewhere along the way I lost that. I started second-guessing myself. Waiting for more data. Deferring to whoever sounded most confident in the room.”

This is one of the less discussed costs of drift: the erosion of self-trust.

When there is a persistent gap between the person you believe you ought to be and the person you keep finding yourself to be, the strain accumulates. It shows up not simply as tiredness, but as a subtler exhaustion. A man becomes weary because too much of what he is doing no longer matches what he knows matters.

No dashboard captures that well.

Yet it is real.

A leader who no longer trusts his own judgment makes weaker decisions, even with good information. A leader who has drifted from his own standards struggles to call others back to theirs. What the company had become was, in part, an expression of what Rufus had been permitting in himself.

Review was the beginning of repair

One of the practices I proposed to Rufus was strikingly simple.

Every Sunday evening, for thirty minutes, he would sit with three questions:

What did I intend to do this week?
What did I actually do?
Where is the gap, and what caused it?

There is nothing novel in this. Variations of it appear in Stoic writing, in Ignatian spiritual practice, and in the habits of serious leaders across centuries. Its strength lies not in novelty but in regularity.

Drift hides in blur.

Review restores outline.

At first Rufus was doubtful.

“I already know I’m not doing what I should be doing. Why would writing it down help?”

Because vague awareness is not the same as disciplined attention.

Most people who drift are not completely ignorant of it. They know, in the loose and uncomfortable way a person knows something he keeps pushing aside. What they lack is sustained contact with the particulars. Review forces contact. It turns a clouded sense of wrongness into a more exact knowledge of what happened, when, and why.

Over time, it also leaves a record.

Patterns emerged that Rufus could not see in the rush of the week itself. His drift worsened in weeks with board meetings. It worsened during travel. It worsened when delivery pressure rose. He began to see which kinds of requests and which kinds of people most often pulled him off course. He saw, with increasing clarity, that his stated priorities and his calendar were badly misaligned.

Later he told me, “The thing I didn’t expect was how much it changed my decisions in the moment. When I know I’ll have to account for my week on Sunday, I think twice before saying yes to something that doesn’t matter.”

That is not surprising.

Review does not merely measure behaviour. It alters behaviour. The future moment of honest accounting begins to stand inside the present moment of choice.

What happens when drift is left alone

It is worth imagining the other version of this story.

In that version, Rufus and his team never name the drift.

The company keeps growing for another year or two. Revenue rises. Complexity rises with it. The product becomes a broad collection of features without a clear centre. The customer base becomes a difficult mix of groups with conflicting needs. The old shortcuts in the system build up until every new initiative moves at half the speed it should.

At some point, perhaps during the next funding round, perhaps when a more focused competitor enters the market, the weakness becomes visible. Investors ask sharper questions. Customers begin to leave, not because the product is awful, but because it is no longer clearly the best answer to any one specific problem. The team burns out supporting too many use cases with too little clarity and too few resources.

By then, the cost of correction is much higher.

What could once have been repaired with moderate effort now requires painful reconstruction. A customer you could once have released gracefully is now woven into your operations. A strategic turn that would once have been clarifying now feels desperate.

This is why the older traditions insisted so strongly on vigilance.

The Buddhist call to heedfulness, the Confucian discipline of self-examination, the Stoic practice of daily review, all circle the same practical truth: catch the small departure early, before it grows roots.

Modern research says much the same.

Drift does not merely add up.

It compounds.

What stayed with me

I have worked with many teams over the years. Some recovered dramatically. Some failed despite serious effort. Most landed somewhere in between. They improved, though imperfectly, and the work remained unfinished.

What stayed with me most from Rufus and his team was something Elena said as we were wrapping up the initial engagement.

“I think the hardest part,” she said, “is accepting that we did this to ourselves. Not through malice. Not through stupidity. Through a thousand small surrenders. We knew better, and we didn’t act on what we knew.”

There was grief in that sentence.

There was also clarity.

It is painful to realise that drift is not always something imposed on us from outside. Often it is something built by our own repeated choices. Yet that recognition is also where agency returns. What we have tolerated can be challenged. What we have normalised can be unsettled. What we have allowed to become ordinary can be made strange again.

The hidden cost of drift is real. It appears in value never realised, in effort wasted, in options quietly lost, in self-trust worn down over time.

But it is not fate.

The work of leadership, and the work of coaching leaders, is to make that hidden cost visible before it hardens into something much harder to repair. It is to build structures that catch drift early. It is to help people do what they already know matters, instead of what pressure and fatigue make easiest in the moment.

In the end, the work is plain.

Shorten the distance between intention and life.