Your memory should never be your only project management system.

Most of us know the feeling. You are working on one thing when your brain interrupts with another:

Remember to send that email.

Follow up with that person.

Check on that invoice.

Schedule that appointment.

Remember that idea.

You then tell yourself, “I’ll remember.” Sometimes you do. Sometimes you don’t.

Either way, you have assigned your brain another job.

Researchers refer to it as cognitive offloading. To describe using external tools or actions to reduce the cognitive demands of a task. Setting a reminder for something you need to do later is a straightforward example. Research has also found that reminders can improve performance

Middle management is where executive intent meets operational reality.

Working as both an Operations Manager and a Director of Operations has given me the opportunity to see organizations from an interesting position.

You are close enough to leadership to understand what they are trying to accomplish.

You are also close enough to the people executing the work to see what accomplishing it actually requires.

Those are not always the same picture.

Leadership may leave a meeting believing a priority is perfectly clear.

By the time that priority reaches the people responsible for executing it, there may be three different interpretations of what “priority” means.

A process may look straightforward from a high level while the person actually

Character, reputation, expertise, energy, impact, mistakes, and people are more connected than they initially appear.

I recently came across a page of Warren Buffett quotes organized around seven areas: character, reputation, expertise, energy, impact, mistakes, and people.

What interested me was not any individual quote.

It was seeing those ideas together.

Because when businesses talk about people, particularly when something is going wrong, we have a tendency to compress a complicated situation into a simple conclusion:

We have a people problem.

Maybe.

But what about the person is actually the problem?

Expertise is one part of performance. Someone either has the knowledge required for a role, can develop it, or

Businesses are usually very clear about what they need from employees. The reverse deserves just as much thought.

Show up.

Meet the deadline.

Communicate.

Take ownership.

Hit your numbers.

Follow the process.

Be adaptable.

Most businesses have no problem articulating what they expect from the people they employ.

We put expectations into job descriptions, employee handbooks, onboarding materials, performance reviews, KPIs, meetings, policies, and conversations with managers.

That makes sense. People need to know what good performance looks like.

But there is another side of that relationship that businesses do not always define with the same level of intention.

What should your employees be able

There are three questions I think businesses need to ask more often: Who is involved? How does the work happen? What information moves with it?

People and process have been part of operations conversations forever.

Privacy deserves a seat at the same table.

Businesses now operate across shared drives, CRMs, Slack channels, email accounts, AI tools, project management systems, automation platforms, cloud storage, contractor relationships, and countless integrations connecting one system to another.

That makes work easier.

It also means information can travel much farther than we realize.

Every process starts somewhere with a person.

Who owns the work?

Who needs visibility?

Who can make the

Contemplate. Convert. Complement.

There is no shortage of things a business could be doing.

A new platform. A new hire. A new service. A better process. AI. Automation. A different marketing strategy. Another idea someone saw working for another company.

The question is not always whether the idea is good. The question is whether it makes sense for your business right now.

Before adding something new, I like to think about it through three lenses:

Contemplate

Convert

Complement

Start with the idea before the implementation.

Why are we considering this?

What problem are we actually trying to solve?

What happens if we do nothing?

It is easy

A client does not care which person, department, inbox, or system owns the next step.

They care that the next step happens.

That distinction matters.

Inside a service business, transferring work can feel routine. Sales sends the client to onboarding. An executive delegates to an assistant. An account manager sends a request to operations. One team member goes on vacation and another takes over.

Internally, these are handoffs.

To the client, they are one continuous experience.

Harvard Business Review has argued that businesses often focus too heavily on individual customer touchpoints when customers actually evaluate the entire journey. A strong interaction cannot fully compensate for a fragmented experience between interactions.

That

HubSpot

CRM and marketing

Manage leads, client relationships, follow ups, and sales activity in one platform.

Pipedrive

Sales pipeline management

Visually track prospects, deals, and next actions.

Every service based business pays taxes.

Some go to the government.

Others quietly drain your business every single day.

You might not find them on your profit and loss statement, but they’re there.

They show up as five minute interruptions, repeated questions, scattered information, and work that should only need to be done once.

Individually, they seem insignificant.

Collectively, they become one of the largest barriers to growth.

I call this The Invisible Operational Tax.

The Invisible Operational Tax is the cumulative cost of inefficient work that doesn’t directly create value for your clients but consumes your team’s time, attention, and

Every organization, regardless of size or maturity, experiences operational friction.

Files become disorganized.

Processes evolve without documentation.

Questions get asked repeatedly.

Projects miss details.

People make mistakes.

Even the world’s highest performing companies encounter these realities. They simply respond differently.

Too often, leaders and teams apologize for operational issues as though they represent personal failure.

“I’m so sorry everything is a mess.”

“Sorry you had to ask again.”

“Sorry I missed that.”

While accountability matters, apologizing does not solve recurring operational problems. Systems do.

Operational maturity begins when organizations stop treating repeat issues as

Service businesses scale by adding clients, not by improving how work actually gets delivered. That gap grows every quarter it goes unexamined. By the time a client notices it, the cost is the relationship, not a process fix.

Most service businesses only run an internal audit in response to a problem. A missed deadline. A dropped handoff. A client complaint. That reactive pattern guarantees the audit always arrives after the damage, never before it.

The foundation of any internal audit is three questions, asked on a schedule instead of after an incident. What is working. What is not working. What is not broken, but could be better. That framework is the starting point.

Urgency is not information. It is noise wearing a costume.

A same day request. A reply all thread. A message marked high priority. Each one announces itself as important. Almost none of it is.

A team that treats every request this way has no way to tell which requests actually matter. That is not a mindset problem. It is the absence of a standard. Without one, a minor request and a critical one receive the same response time, because nothing in the system distinguishes them.

The NeuroLeadership Institute analyzed more than ten thousand sources of daily news and leadership commentary. Organizational change accelerated by 183

This month, Anthropic published internal data that reignited debate over recursive self improvement, the idea that AI systems could eventually design and refine their own successors. The report and the reaction to it were covered by The Batch, the newsletter published by DeepLearning.AI.

The headline numbers are specific to Anthropic. The operational lesson is not.

According to Anthropic, 80 percent of the code merged into its systems is now authored by Claude, up from under 5 percent before the research preview of Claude Code. The company reported that by the second quarter of 2026, each engineer was contributing eight times more code per quarter than engineers did in the first

Earlier in my career, I worked alongside professionals in law and real estate. I watched capable peers, some already running their own companies, delay one of the most protective documents available to them, an estate planning document. Not because of cost. Not because of complexity. The reason was almost always the same quiet belief.

I am too young for a trust.

As if protection were something earned by age instead of something required by exposure.

I found the business equivalent of that belief in Colin C. Campbell’s book Start. Scale. Exit. Repeat. A section on strategic planning, references a perspective of the same

For years, the answer to every business challenge looked the same: more effort, more hours, more output.

That model has a ceiling.

Microsoft’s 2026 Work Trend Index reports that 58 percent of professionals are now producing work they could not have created a year ago. Speed is no longer the primary constraint.

The constraint is judgment. And judgment breaks down when attention is distributed across too many initiatives with no clear standard for what actually matters.

Every business owner knows this pattern. The team is moving. Deliverables are going out. But outcomes are not shifting. The business is generating activity without generating traction.

Here is how to close that gap.

The conversation about AI adoption has been reduced to a personality split.

There are people who experiment. And there are people who wait for someone to hand them an instruction manual.

The distinction matters. But it stops short of the real problem.

Experimentation, critical thinking, and outcome driven adoption are all valid principles. What they do not address is the operational condition that determines whether any of them are actually possible.

Chris Douglass, Director of Sales, CRM at monday.com, describes a growing divide on teams. Some employees actively test, build, and adapt. Others wait. His advice is to stop waiting for the perfect process before you begin.

It assumes there is something stable enough to experiment with. It assumes there

One of the more practical uses of AI is also one of the least dramatic.

It can help you get unstuck.

When you are drafting a plan, preparing for a conversation, organizing scattered thoughts, or working through a problem, AI can create enough movement to get you out of the loop.

That has value.

But for a business, getting unstuck is not only a personal productivity issue. It is an operational issue.

AI can generate a starting point quickly.

It can outline a plan, summarize information, suggest options, or pressure test an idea before it moves forward.

But speed is not the same as progress.

If the business has no documented workflows, decision standards, policies, roles, or operating

Organizations are not failing at transformation because of weak technology.

The Process Excellence Network has published research and expert perspectives across multiple formats this year, and the pattern is consistent. Transformation stalls at the same place, in the same way, for the same reason.

The operations were not documented before the initiative began.

According to the PEX Report 2025/26, based on a global survey of more than 220 transformation, operations, and business leaders, 56 percent of organizations are deploying enterprise-wide transformation strategies. Fifty-eight percent consider transformation a mission-critical driver of growth.

Yet process inconsistency ranks among the