Loadmap

How it works

How Loadmap finds where a problem starts

A problem tends to show up in one part of an organization and start in another. Loadmap's job is to find the second place before anyone picks a fix.

  1. We ask how the work gets done

    You've probably surveyed your people before. You learned how they feel, and nothing about what to fix. We ask a different kind of question.

    Your staff and your leaders each tell us how and why work gets done: how decisions get made, how far information travels, what happens when a process stops working.

  2. We read how each team runs

    A fix that works for one team can break the next. Loadmap sorts teams with four simple switches. Each switch has two settings, so a team can run sixteen ways.

    • Fast or careful
    • Learn by doing or learn before doing
    • Open or need-to-know
    • Own way or shared method

    Each of the sixteen has a plain name, like Pit Crew or Crime Lab. A well-known American manufacturer rolled a single program across the whole company. Its Production group got better and its Innovation group got worse, because the two groups ran in opposite ways.

    Step through the sixteen team patterns

  3. We find the layer that's carrying too much

    Linden's Bridge pictures an organization as five layers carrying a load. The gaps between what leaders and staff tell us, and the patterns within each, show which layer the load is landing on.

    • Delivery & ResultsThe daily work. Problems show up here first.
    • Tools & MethodsThe software, workflows, and handoffs people use every day.
    • Guardrails & IncentivesWho makes which calls, and what gets rewarded or punished.
    • Mission & DirectionWhat the organization protects when two goals collide.
    • Visibility & UnderstandingWhat gets noticed, and how fast a warning reaches someone who can act.

    The damage shows at the top. The crack usually starts lower down, which is why a fix aimed at the daily work so often fades.

    Step through Linden's Bridge

  4. We point to the fix that fits

    Fixes get matched to the layer where the problem starts and to how your teams run. You also see which popular fixes to skip. A respected method can still be the wrong one for this layer or this team.

    Try it on three companies in The Fix That Comes Back

  5. You get a plan in a few weeks

    The plan can be built around new investment, or it can run on the people and budget you already have.

    The work starts with analysis. It ends with fixes that stick, so you fix once instead of repeatedly, and can get back on the path to where you're trying to go.

Why a fix snaps back

When behavior changes but the structure under it doesn't, the improvement fades. Loadmap calls this snapback.

It can look like stubbornness. The cause is structural: the layers still reward the old behavior. The useful question is which layer never changed.

If you're tired of paying to solve the same problem twice, let's talk.

The work starts with analysis. It ends with fixes that stick, so you fix once instead of repeatedly, and can get back on the path to where you're trying to go.

Email Tate Linden