What Leaders/Managers Can Learn from Lean UX
Marcus, a regional operations director, spent six weeks designing a new shift-scheduling system for his warehouse teams, certain that giving supervisors more scheduling control would fix chronic understaffing. He built a detailed rollout plan, trained twelve supervisors, and printed new procedure manuals before running a single shift under the new system. The unstated assumption was that supervisors wanted more control; what most of them actually wanted was less administrative burden, not more decisions to make. Within the first week, three supervisors reverted to spreadsheets, and two filed complaints that the new process took longer than the old one. Marcus had spent six weeks of his own time and his team's goodwill rolling out a fix nobody had asked to receive, and now faced a skeptical staff before he had even solved the original understaffing problem that started the whole project.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Name the assumption behind the plan before announcing it
Every management decision, from a new process to a reorganized team, rests on a belief about what people actually need or want. Stating that belief in one sentence before it becomes policy lets a leader see clearly what is being gambled on.
A director rolls out a new weekly reporting format assuming staff want more visibility into each other's work, never naming that belief separately, so when engagement drops nobody can tell if the format, the timing, or the underlying want was wrong.
Before announcing your next process change, write the one sentence belief it depends on, then ask a peer manager to poke holes in it.
Try the smallest version with one team first
A full department rollout is not required to learn whether an idea works; running it with one shift, one team, or one week first tests the belief at a fraction of the disruption.
A manager rolls a new performance-review format out to four departments at once, and when it causes confusion everywhere simultaneously, there is no unaffected group left to compare against or retreat to.
Choose the smallest team or shortest time window that could still tell you whether your idea works, and run it there first.
Ask people directly, away from the reporting line
Feedback gathered informally in a meeting the manager runs will often be politely diluted. Real reactions come from anonymous input or a trusted peer manager asking the questions instead.
A manager asks her own direct reports in a team meeting whether the new process is working, and everyone nods, while an anonymous survey run weeks later reveals most found it confusing.
Have a peer manager or an anonymous form collect reactions to your trial, rather than asking your own reports face to face.
Change the rollout based on what the pilot actually showed
A leader who commits publicly to a plan can feel that adjusting it looks like weakness, but the opposite is usually true. Revising a plan openly, citing what the pilot revealed, builds more trust than defending a decision the team can see isn't working, and it is far cheaper than a full rollout of something already known to be flawed. Teams remember which managers admitted a miss early and which ones pushed forward regardless.
Naming the assumption plainly can conflict with testing small: a leader may realize the real risk is something politically sensitive, like whether staff trust management at all, which is hard to test quietly with one team. Balance this by choosing the most neutral possible pilot group, one without a recent history of conflict with leadership, so the test measures the idea rather than existing tension.
Name one thing, honestly
Which current initiative are you defending because you already announced it, rather than because a small test has actually confirmed it works?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Have a peer manager or an anonymous form collect reactions to your trial, rather than asking your own reports face to face.