Your Business Needs Room for the River.

01 / A name worth thinking about

Room for the River changes the question.

Ruimte voor de Rivier means “Room for the River.” It is the name of a Dutch water management programme, not an ancient proverb. Its value as a business analogy comes from the practical change in approach expressed by those words.

Rijkswaterstaat’s account of Room for the River describes measures such as moving dikes inland, creating flood channels, and lowering floodplains. These interventions provide more space for water during high flows and help reduce pressure on defenses.

The agency’s IJsseldelta example illustrates the role of a flood channel in allowing more water to pass during high-water conditions. The response changes the arrangement through which the pressure moves. That is the part I would carry into a business conversation.

Suppose a team regularly struggles to meet a delivery promise. You could ask people to work faster. You could add a manager to chase updates. Or you could investigate whether the promise, the intake process, the sequence of work, and the available capacity fit together.

The investigation may reveal that the apparent productivity problem begins with too many different types of work entering the same constrained process. Routine requests wait behind complex exceptions. Specialists are interrupted to resolve preventable confusion. The team has plenty of activity and too little uninterrupted progress.

In that situation, another motivational speech is rather like standing on the bank and encouraging the river to be more commercially minded.

Different pressure calls for a different response.

A short surge, a persistent increase in demand, and a badly designed process are different problems. They can produce similar symptoms while requiring different interventions.

A temporary surge may justify planned overflow capacity. Persistent demand may justify investment in a lasting capability. A process that repeatedly creates rework may need redesign before additional staffing will help. The answer depends on what is actually happening.

Giving a system more room also has costs. River projects involve real places and real people. In a business, spare capacity uses resources that could otherwise be committed. A useful plan weighs that cost against the consequences of having no room when conditions change.

The aim is enough capacity and flexibility for the service the business promises. That requires judgment about variability, consequences, and how quickly the organization can adjust.

02 / South Holland

Kinderdijk: the beautiful part is connected to everything else.

The windmills at Kinderdijk are visually memorable. The history becomes more interesting when we pay attention to the waterworks around them. UNESCO’s account of the Kinderdijk-Elshout mill network describes an integrated landscape of drainage channels, dikes, mills, pumping stations, discharge sluices, and water board buildings, with hydraulic work extending back to the Middle Ages.

The site makes a system visible. A mill performs a function within an arrangement of water levels, channels, storage, and discharge. Understanding the prominent component requires understanding what it connects to.

Businesses frequently buy the prominent component and overlook the connections. A new website. A customer relationship platform. A more sophisticated dashboard. A campaign that produces more inquiries. Each can be useful. Its value depends partly on what happens before and after it.

A better form will not resolve a disagreement about who responds to an inquiry. Faster reporting will not clarify a metric nobody has defined. Automation will not supply a missing decision about which customers the company intends to serve.

The question is whether the new component improves the performance of the whole. If it simply accelerates work into the next bottleneck, the business may have purchased a very efficient way to make the backlog larger.

Look at where work waits.

I would trace a representative customer request through the organization. When does it arrive? Who sees it? What information is missing? Which decision must happen next? Where does it sit untouched, and why?

That exercise often reveals a distinction between work time and waiting time. A proposal might take a modest amount of active effort while spending several days waiting for clarification or approval. Asking the writer to type faster will have limited effect.

A systems view makes those delays discussable. It helps the team see whether the constraint is information, authority, sequence, skill, or capacity. It also prevents the most visible department from receiving all the blame for a problem created elsewhere.

This is an important part of digital transformation advisory. The technology should support a workable flow of information and decisions. Before choosing a platform, understand what the organization is asking it to connect.

03 / The cost of having no room

A fully booked calendar can be a fragile operating plan.

Imagine a hypothetical team that can complete ten ordinary requests in a day. If ten arrive every day and every request is ordinary, the arithmetic looks comfortable. The difficulty begins when twelve arrive on Monday, three require investigation, and the person who handles a necessary approval is away.

The plan assumed smooth arrivals and predictable work. Reality introduced variation. Monday’s unfinished work now competes with Tuesday’s arrivals, while interruptions make it harder to concentrate on either.

There is no need to turn this into an equation to see the problem. A system with no room to absorb variation can fall behind even when its average workload appears reasonable. The appropriate margin depends on how variable the work is and how serious a delay would be.

Teams need room for learning, maintenance, exceptions, and the ordinary unpredictability of people. If all available hours are committed to planned delivery, those activities still happen. They simply borrow time from something else.

More demand is useful when the business can serve it.

This makes capacity a marketing question as well as an operating question. A campaign can succeed at attracting attention and still produce a disappointing business outcome if the organization cannot respond or deliver well.

Useful marketing strategy therefore asks what kind of demand the company can support. Which customers fit? Which services can be delivered consistently? What volume can the team handle? How quickly should the business increase its promises?

Some companies need more inquiries. Others need fewer unsuitable inquiries, better qualification, or a more realistic service offer. The commercial objective should be clear enough to distinguish those situations.

Growth should increase the organization’s ability to create value. If it depends on people repeatedly rescuing an overloaded system, leadership should examine what the growth plan is consuming along the way.

04 / Hoek van Holland

The Maeslant Barrier prepares a response before the pressure arrives.

Near Hoek van Holland, the Maeslant Barrier forms part of the Netherlands’ flood defenses. Rijkswaterstaat dates its construction to 1991–1997 and describes the automated closing process alongside the operational team available to monitor and intervene when needed.

The agency also explains that it uses risk calculations to guide testing, inspection, repair, and component replacement. The structure’s scale is striking, but those less theatrical practices belong to its usefulness.

The business lesson is to decide how you will respond before a difficult situation removes your room to think. Which signal deserves attention? Which response is appropriate? Who has authority? What must continue working while the response happens?

A company might agree to pause an advertising increase when qualified inquiries exceed what sales can handle within its promised response window. A service business might stop selling a particular delivery date when confirmed work reaches a defined limit. These are illustrative choices, not universal thresholds.

The point is that the action should be considered while people can discuss the tradeoffs calmly. Under pressure, a vague instruction to “use your judgment” can leave someone balancing responsibilities they were never given the authority to resolve.

An alert is only useful if it can lead to action.

A dashboard can show that a problem exists without helping anyone address it. The measure needs context: what changed, whether the change is meaningful, who owns the response, and what decisions are available.

That is why I approach KPI and dashboard design through the decisions it should support. A useful measure helps the team investigate or act. A number that changes color and then waits politely for next month’s meeting may be providing decoration at a very unfortunate moment.

Review the response itself, too. Did someone notice? Could they act? Did the action work? A plan can look complete in a document and still fail because one necessary decision belongs to a person who was unavailable.

05 / The work after the launch

Maintenance is how a useful decision stays useful.

Organizations are often enthusiastic about building and less enthusiastic about maintaining. A launch has a date, a presentation, and perhaps a photograph. Maintenance has a list of items someone would prefer to discuss after the more exciting agenda.

Yet the value of an asset depends on its continued usefulness. A customer database becomes less reliable when ownership is unclear. An integration can stop moving information correctly. A page can retain a promise the business no longer supports. A process can remain in place after the conditions that justified it have changed.

Rijkswaterstaat’s asset management account includes maintenance, renovation, and replacement alongside network improvement. It frames the work around balancing performance, cost, and risk, and describes the challenge of renewing infrastructure within limits on money, space, and people.

That is a useful corrective to the idea that maintenance is simply what happens when innovation stops. Maintaining a capability can require difficult choices about what to repair, improve, replace, or retire.

Ask what the business now depends on.

A practical review starts with the capabilities that matter to customers and staff. Which systems carry inquiries? Which information supports a quote? Which process establishes delivery expectations? What would become difficult if a component stopped working tomorrow?

Then ask whether each capability has an owner, a way to notice problems, and time allocated for upkeep. If the answer is unclear, the business may be relying on someone eventually noticing that something is wrong.

The relevant person is often already busy. They repair the issue because they understand it, then return to their normal workload. The fix disappears into the day, and leadership receives little evidence of how much care the system requires.

Making that work visible helps the organization plan realistically. It also allows the business to distinguish a one-time defect from a recurring maintenance burden that deserves a better design.

Sometimes the responsible choice is retirement.

Every service, tool, and exception adds something to maintain. A company can accumulate old commitments because each seems too small to question. Together they create complexity that consumes attention long after the original commercial value has faded.

A useful review asks which capabilities still earn their place. What do customers use? Which work supports the current strategy? What can be consolidated? What needs a planned transition rather than another patch?

Retiring something thoughtfully can create capacity for work that matters more. The decision deserves care for affected customers and employees, but age alone does not make an arrangement worth preserving forever.

06 / The South Holland coast

The Sand Motor starts by understanding the forces already at work.

The Sand Motor, constructed in 2011, placed a large volume of sand along the coast so wind, waves, and currents could gradually distribute it. Rijkswaterstaat describes it as an approach to coastal nourishment that also supports research into how the landscape develops.

The project is useful to consider because it treats existing forces as part of the design. It also makes observation important: the intervention changes over time, and its behavior needs to be studied rather than assumed.

In business, an analogous question is whether the proposed system fits how people actually work and buy. A company can design a beautifully logical internal process that repeatedly collides with ordinary customer behavior.

Perhaps customers need to compare options before speaking with sales. Perhaps they cannot answer a technical question on the inquiry form. Perhaps a purchasing decision involves several people, each looking for different evidence. The business can either investigate those patterns or keep wondering why visitors fail to perform the journey it drew for them.

Remove avoidable friction before adding persuasion.

Imagine a company whose customers repeatedly ask what is included in a service. The response might be clearer scope information and examples. If the company instead adds another follow-up sequence urging people to book a call, it has increased persuasion without resolving the uncertainty.

That distinction matters. A customer’s hesitation can contain useful information about the offer. The problem may be fit, clarity, timing, or confidence. Treating every hesitation as something to overcome can make the business less curious about what the customer needs.

I would look at actual inquiries, lost opportunities, and the questions staff keep answering. Then I would change something specific and examine whether the change helps. The method should give customer behavior a chance to inform the design.

The Sand Motor is a physical engineering project; the comparison does not make customers predictable natural forces. People have agency, and their circumstances change. The useful connection is the willingness to understand the conditions in which an intervention must work and to keep learning after it begins.

07 / A future with more than one possible route

Commit to the goal while preserving useful choices.

The Dutch National Delta Programme addresses flood risk, freshwater availability, and spatial adaptation. Its account places present work within a changing set of conditions, including sea-level rise, changing river flows, and water shortages.

Its explanation of adaptive delta management emphasizes linking present decisions with long-term needs, maintaining flexibility, and preparing alternative pathways. It recognizes that major measures can take a long time to implement even while future conditions remain uncertain.

That combination is particularly relevant to business. Waiting for certainty can leave too little time to prepare. Committing every resource to one forecast can make change unnecessarily expensive.

A useful plan distinguishes decisions that must happen now from those that can remain open. It asks what information would justify the next investment and what preparation is needed so the investment remains possible.

Sequence commitment according to what you can learn.

A company entering a new market might begin with a limited offer and a clear learning objective. It could investigate demand quality, delivery requirements, and the economics of serving that customer before making a much larger commitment.

That does not mean running a vague pilot indefinitely. Define what would count as useful evidence. Set a review point. Decide who can authorize the next step and what would cause the business to change direction.

A similar approach can help with technology. Before redesigning the entire organization around a tool, test a meaningful workflow, understand the maintenance burden, and examine whether the information can be moved if the arrangement later changes.

These questions belong in market expansion advisory and broader strategy because they connect ambition to the cost of future choices. Flexibility has value when it preserves a realistic route to the goal.

Decide what would change your mind.

A plan becomes easier to improve when its assumptions are visible. Perhaps it depends on a particular response rate, a certain delivery time, or a level of repeat demand. Write those assumptions down in language the team can examine.

Then ask what evidence would challenge them. A weak result may reflect poor execution, an unsuitable offer, or a mistaken assumption about the market. Those explanations should lead to different responses.

The purpose is to make revision disciplined. A company should be able to change direction because it learned something, while avoiding constant changes driven by the latest anxious conversation.

08 / An illustrative growth problem

The campaign worked. The customer experience got worse.

Consider a hypothetical specialist service company that launches a successful campaign. More inquiries arrive. Marketing reports progress. Sales begins booking additional work. For a few weeks, the numbers appear to confirm the decision.

Delivery then starts missing expectations. Qualified prospects wait for answers because the team is sorting through unsuitable requests. Specialists interrupt active projects to clarify proposals. Staff work late to recover commitments that should have been checked before they were made.

Leadership initially diagnoses a need for greater productivity. The more useful question is what the added demand revealed about the system.

The company could begin by reviewing a small sample of recent inquiries and completed jobs. Which requests fit the intended service? Which promises created difficulty? Where did work wait? Which exceptions consumed a disproportionate amount of attention?

That evidence might support clearer qualification, a separate route for complex requests, and a limit on the amount of work started at once. It might also show that the business needs additional capacity. The point is to diagnose the constraint before selecting the response.

Improve the whole result.

A revised plan should be assessed through more than inquiry volume. Did suitable customers receive timely answers? Did work finish as promised? Did rework fall? Did the team stop relying on extraordinary effort to deliver ordinary commitments?

A smaller number of well-served customers can sometimes produce a better commercial result than a larger volume the organization handles poorly. That is a question for the business’s own evidence and economics, rather than a universal argument for smaller scale.

The Dutch analogy becomes useful here: give the system an appropriate way to handle the flow. Do not assume that pushing more through the same narrow point will become sustainable because the demand is welcome.

09 / The place changes the conditions

Florida makes the subject tangible. The business lesson extends further.

Working from Florida makes water a particularly tangible starting point for thinking about constraints. But importing a Dutch engineering solution into another landscape requires local expertise and evidence. The business applications in this article concern how leaders plan capacity, maintenance, and adaptation.

For a company in Daytona Beach, I would want to understand whether demand arrives steadily or concentrates around particular events and seasons. The relevant question is how the organization prepares for its actual pattern of work.

For an Orlando business, I would examine which customers and service commitments drive the load. A visitor-facing operation and a technical business serving institutional buyers can need very different arrangements despite sharing a city.

For a company working across several regions, response coverage, delivery capacity, and local knowledge may become the constraints. The specific business determines which conditions deserve attention.

A useful market plan should explain what changes with place. Otherwise expansion can amount to reproducing the same bottleneck over a larger area and giving everyone more time zones to discuss it in.

10 / A plan that can respond

Find the pressure, then choose the intervention.

Start with one recurring problem that the business has normalized. Slow proposals. Unfinished projects. Repeated rework. A service promise that requires constant rescue. Describe it in terms someone can observe.

Trace how the work enters the system, where it waits, what it depends on, and what happens when conditions vary. Include the people who do the work. They may know exactly where the pressure accumulates, even if the reporting system has never asked.

Decide whether to protect, expand, simplify, or reroute.

Some capabilities need protection from interruption. Some need more capacity. Others need fewer exceptions, clearer information, or a different sequence. A response should address the constraint you found rather than the most familiar service you happen to know how to purchase.

Then define the commitment. What will change? Who owns it? What resources are required? What result should improve? What could be made worse, and how will the team notice?

The Dutch government’s account of water management responsibilities makes a useful supporting point: different authorities have defined roles across national and regional waters and related responsibilities. A connected system still needs identifiable ownership.

In a business, that means knowing who can make the decision when the measure changes, who maintains the capability, and who is responsible for reviewing whether the arrangement still fits. “We are all watching it” is not a particularly dependable escalation plan.

Give the improvement a life after the meeting.

Set a review point appropriate to the work. Look at the evidence and the consequences. Adjust the intervention if it is not addressing the problem. Preserve what the team learns so the organization does not need to rediscover the same lesson during its next busy period.

The most useful outcome may be quiet. Customers receive answers. Projects finish. Exceptions are handled before they become emergencies. The business can pursue growth without treating every increase in demand as a test of personal endurance.

Kinderdijk makes the connected system visible. Room for the River shows the value of changing the space available to pressure. The Maeslant Barrier makes preparation and maintenance tangible. The Sand Motor and adaptive delta management invite attention to how interventions behave over time.

Together, they support a serious form of optimism: understand the conditions well enough to build something that can work within them, and remain attentive enough to change it when necessary. Ambition becomes more credible when it has a place for the river.

If these questions connect with work you are doing, you can write to Rob.

11 / Frequently asked questions

The Dutch idea and its business application.

Explore the sources

The engineering deserves its own attention.

These official sources support the historical and water management discussion. Business scenarios are hypothetical, and the leadership applications and Dutch reflection are original writing.

• Rijkswaterstaat: Room for the River · More space for high flows.
• UNESCO: Kinderdijk-Elshout mill network · A connected hydraulic landscape.
• Rijkswaterstaat: Maeslant Barrier · Operation, inspection, and maintenance.
• Rijkswaterstaat: asset management · Performance, cost, renewal, and risk.
• Rijkswaterstaat: the Sand Motor · Coastal nourishment and observation.
• Delta Programme: adaptive delta management · Present action and future options.
• Government of the Netherlands: water management responsibilities · Who owns different parts of the work.