Dream About Dunes – Meaning

Dunes in an organizational context describe the slow buildup of uneven terrain in how work, attention, and resources are distributed—like ridges and valleys that form from repeated small choices. They matter because these subtle shifts create predictable hotspots and blind spots that shape decisions, morale, and delivery over months or years.

What it really means

Dunes are patterns, not single events. Over time small practices, incentives, and workarounds accumulate into persistent features of an organization's landscape: teams that hoard expertise, processes that redirect requests to the same people, or product areas that receive disproportionate attention. Once formed, dunes channel future behavior because people follow the easiest paths.

How these uneven patterns develop

• Path dependence: Minor early choices (a temporary file-sharing workaround, a favored reporting line) become default ways of working.
• Local optimization: Teams prioritize immediate goals and create shortcuts that benefit them but distort the system.
• Invisible incentives: Rewards, recognition, or simple visibility bias concentrate effort in some areas and leave others neglected.
• Cognitive load and shortcuts: When people are overloaded they route work to known experts, reinforcing hotspots.

These forces are gradual and compounding. Managers who expect a single root cause often miss that dunes are emergent: they result from many small, rational decisions rather than a single policy failure.

What it looks like in everyday work

• Visible backlog ridges: Some teams have long queues of requests while other teams sit underutilized.
• Informal routing: Requests get funneled to the same people by habit rather than by design.
• Spotty knowledge: Critical knowledge lives with a few individuals, creating local power and risk.
• Uneven tooling: Certain projects gain better tools or dashboards because they’re higher profile.

These surface signs are symptoms of the underlying terrain. A manager who responds only to the visible backlog (for example, by assigning more staff to the overloaded team) can accidentally deepen the dune because the root routing pattern remains unchanged.

What helps flatten, redirect, or use dunes constructively

• Create deliberate channels: Formalize intake and triage so requests are routed by capacity and priority rather than habit.
• Rotate responsibilities: Short rotations or shared ownership reduce single-person dependencies.
• Adjust visibility and incentives: Make neglected work visible in metrics and recognition systems.
• Small structural experiments: Run time-boxed pilots that reassign a portion of work to test whether the dune shifts.
• Invest in documentation and handoffs: Reduce friction for new contributors so valleys don't rely on gatekeepers.

These actions are not one-off fixes. They work best when paired: governance to change routing, incentives to change behavior, and micro-experiments to reveal what actually shifts the terrain.

A quick workplace scenario

A concrete example

A product support function becomes a dune after a high-performing engineer starts handling escalations informally. Over months, other teams begin rerouting problems to that engineer because they get fast resolutions. The backlog around feature development grows as the engineer is pulled into firefighting, and knowledge consolidates with them.

• The immediate reaction is to hire more engineers for support, but that can simply expand the dune if the routing habit remains.
• A better approach is to formalize escalation criteria, train a small rotation of engineers in the process, and create a dashboard that surfaces request sources and response times.

This combination reduces single-person dependence while preserving quick responses.

Where dunes are commonly misread and related patterns

• Confused with resistance to change: Dunes are structural, not always intentionally resistant. People following the dune are often reacting to incentives and convenience, not stubbornness.
• Misidentified as poor performance: A team in a valley may appear inefficient, but the root cause can be lack of visibility or access, not incompetence.

Related concepts worth separating from dunes:

• Bottlenecks: A bottleneck is a point of constrained capacity; dunes are broader patterns of uneven distribution that create and sustain bottlenecks.
• Silos: Silos are insulated group boundaries; dunes can exist across silos and are created by routing and incentives rather than purely by boundary protection.

Recognizing these differences matters: fixing a silo (e.g., by adding cross-functional meetings) will not always change a dune unless routing and incentives are addressed.

Questions worth asking before reacting

• Who benefits from the current routing of work, and who is disadvantaged?
• Which small, repeatable decisions created the pattern we see today?
• What can we change quickly to test whether the dune is structural or situational?
• Which visibility or incentive changes would make neglected work easier to choose?

Asking these questions prevents knee-jerk solutions that reinforce dunes. Use them as a short diagnostic before reallocating headcount or changing job descriptions.

Short tactics a manager can start this week

• Audit the last 30 requests routed to a hotspot and map why each went there.
• Run one 2-week rotation so at least two people handle the hotspot and document the handoff.
• Publish a simple intake form that requires priority and expected impact; route by that form rather than by inbox.

Small, experimental changes reveal whether a dune is brittle (easy to shift) or entrenched (needs governance and incentive redesign).