For organizational development practitioners
You found the problem. Then it stalled in the boardroom.
Good organizational work tends to get a nod and no budget. Loadmap gives you a finding the person who decides can act on.
What it gives you
A cause with an address
Knowing where a problem sits tells you who has to fix it. Loadmap names the layer where the problem starts, in words a leader already uses.
The layer where it starts
Five layers, from the daily work down to what the organization can see coming. Your finding lands on one of them.
A read on each team
Sixteen team patterns show why a fix that worked for one group can hurt the next.
The fixes to skip
When a popular method won't help this layer or this team, you can say so and show the reason.
A page for the person who decides
The free check can write a one-page brief for your decision-maker.
Getting to yes
An executive's yes is a behavior. Design it like one.
Tate's conference session, "Why Good OD Work Dies in the Boardroom and How to Make It Land," makes a short case.
A yes has to be worth it to the executive, easy to give, and tied to a reason to decide now. Executives read one page: the one with what they're measured on. So the finding has to show up there.
The pitch that works proves the leader right, then shows what being right requires. The yes never costs them an admission.
Try it and share it
Four things you can use today
The free check
About ten minutes. It gives you a first read on your own organization and a name for how your team runs.
Linden's Bridge
A step-by-step walkthrough of the five layers, told through one hospital trying to cut its emergency room waits.
Sixteen team patterns
A walkthrough of why the same program helped one half of a company and hurt the other.
The Fix That Comes Back
A four-minute game. Pick a fix for three companies and watch a year go by.
Tate also writes The Load. Its newest pieces run a story from the week's news through the Bridge. Read The Load