Reflection 001 | Everyone was discussing the project. Nobody was discussing what came next.

Estimated reading time: 5 minutes

If you've arrived here after reading my LinkedIn post, thank you.

The post ended with a question that has quietly followed me for more than twenty years:

"...yes, but what happens next?"

I'd like to explain why that question has become almost instinctive for me.

Everyone was doing the right thing. One of the things that has fascinated me throughout my career is that people rarely overlook important things because they are careless. More often, they overlook them because they are focused.

When a team is designing a new facility, implementing a new process, introducing a new system, or delivering a major project, everyone has a clear objective.

• Finish the design.
• Meet the milestone.
• Pass the Factory Acceptance Test.
• Complete commissioning.
• Reach handover.

Those objectives matter. Without them, projects would never finish.

The challenge is that the closer we get to those milestones, the more our attention narrows. We become very good at solving today's problems, but we gradually stop looking beyond today's finish line.

The meeting I have seen hundreds of times

I've sat in more meetings than I can count where people were discussing equipment layouts, schedules, commissioning plans, budgets, validation activities, and deadlines.

Everything sounded sensible.

Everything was progressing.

Yet something kept bothering me.

Nobody was talking about the day after handover.

• Who would own the process?
• How would operators recognise when something was slowly drifting out of control?
• What would happen when the first deviation occurred?
• Would the documentation support real decision making, or simply satisfy compliance?
• Would people understand why the process worked, or only which buttons to press?

Those questions rarely appeared on the agenda. Not because anyone disagreed with them.

Simply because everyone assumed someone else would think about them later.

And that matters.

Because what isn't discussed during the project rarely disappears. It simply waits.

• It waits until the first production day.
• Until the first operator wonders what to do.
• Until the first deviation.
• Until QA discovers that the documentation doesn't quite match operational reality.
• Until engineering receives another late-night phone call because a system that looked perfect on paper isn't yet reliable in practice.

• I've seen projects where this meant delaying a launch.
• I've seen weeks of nightly support because systems simply weren't ready to operate reliably.
• I've seen operators creating workarounds just to keep production moving.
• I've seen QA trying to reconstruct the logic behind decisions that should have been made months earlier.
• I've seen consultants staying far longer than planned because the real work only began after handover.
• I've seen managers wondering why a project that was officially finished still didn't feel finished.

None of those situations were caused by bad intentions.

Most of them started because everyone believed the project ended at handover.

The question that keeps interrupting me

That's usually when I hear myself asking:

"...yes, but what happens next?"

It has become almost an instinct.

Not because I expect something to be wrong. Because asking that question forces us to step outside today's milestone and look at the system we are actually creating.

• Projects end.
• Operations begin.
• Designs become routines.
• Documents become habits.
• Decisions become culture.

Reality usually speaks quietly first

Over the years I've learned something else.

The problems that hurt us most rarely begin when they become visible.

By the time something demands attention, the system has often been trying to tell us for weeks, sometimes months.

• Through repeated clarification questions.
• Through the same discussion returning in meeting after meeting.
• Through temporary workarounds that quietly become permanent.
• Through experienced people compensating for weaknesses the system never solved.
• Through small frustrations that everybody accepts because "the project is almost finished."

Those are rarely dramatic moments. They're easy to dismiss. Until one day they are no longer small.

By then, we call them

• Deviations.
• Or delays.
• Or operational issues.
• Or customer complaints.

But very often, those weren't the beginning. They were simply the moment the problem became visible!

This isn't about pharmaceutical manufacturing

Although many of my examples come from pharmaceutical manufacturing, I've seen exactly the same pattern elsewhere.

• Leadership teams celebrate a new strategy before discussing how decisions will change on Monday morning.
• Software teams launch new functionality before thinking about user adoption.
• Companies introduce new procedures before considering whether people can realistically follow them.
• Families make plans without talking about how those plans fit into everyday life.

The context changes.

The pattern doesn't.

The calm we're really trying to create

People sometimes assume I ask these questions because I'm looking for problems.

I'm not.

The goal isn't to predict every possible issue. That's impossible. The goal is to create an operation that people can trust.

An operation

• Where operators can focus on their work instead of compensating for the system.
• Where QA doesn't spend its time discovering yesterday's assumptions.
• Where engineering isn't solving preventable problems at two o'clock in the morning.
• Where the first weeks after handover are about building confidence, not fighting fires.

That kind of calm isn't created after go-live.

It's designed long before it.

My reflection

Projects are temporary.

Operations are not.

Every decision made during a project eventually becomes someone else's everyday reality.

That's why, before I leave almost any meeting, I find myself asking one more question:

"...yes, but what happens next?"

Perhaps that question won't change anything.

But sometimes, it changes everything.

And in my experience, those few moments are more than worth asking one extra question.

I'd like to leave you with one of my own.

Where in your work, or perhaps even in your life, have you experienced the consequences of nobody asking "...yes, but what happens next?"