What Career Professionals Can Learn from Lean UX
Renata spent three months quietly preparing a full internal proposal to restructure her department's client-onboarding process, certain that the main complaint from clients was slow paperwork. She interviewed nobody outside her own team, built a forty-slide deck with a new workflow diagram, and scheduled a big reveal meeting with senior leadership. The unstated assumption was that clients wanted faster paperwork; what several actually wanted was a single point of contact instead of being passed between departments, something paperwork speed would not fix. In the meeting, the VP of Sales pointed out that client complaints, which Renata had never actually read herself, were about confusion over who to call, not delays. Renata had spent three months and burned a rare slot on the leadership calendar pitching a solution to the wrong problem, and now had to explain why she hadn't checked the actual complaint log before scheduling the meeting at all.
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
State the assumption behind your proposal before you build the deck
Every workplace proposal, whether a new process, a pitch to a client, or a project plan, rests on a belief about what colleagues or clients actually need. Writing that belief down as one sentence, before building slides around it, reveals exactly what the proposal is betting on.
An analyst proposes a new reporting dashboard assuming executives want more real-time detail, without checking that belief first, and learns in the review meeting that executives actually wanted fewer, clearer numbers, not more of them.
Before your next proposal, write the one sentence belief it depends on, then ask a colleague outside your immediate team to try to disprove it.
Pitch a rough version before building the full plan
A polished forty-slide deck is not needed to learn whether an idea has merit; a one-page outline or a short conversation with someone affected can test the same belief far more cheaply.
An employee builds a complete new client-reporting template over several weekends before showing it to a single client, then learns in the first real meeting that clients wanted a shorter summary, not a longer one.
Sketch your idea on a single page and show it to one person it would affect before investing in a full proposal.
Ask the people the idea affects, not just your manager
A manager's approval of an idea is not the same as evidence it solves the real problem. The people who would actually use the new process, whether coworkers, clients, or another department, will react very differently than a manager reviewing a slide.
A project manager gets sign-off from her own director on a new intake form, skips asking the support team who would actually use it daily, and finds out after launch that the form ignores information they need most.
Before finalizing your idea, ask one person from the group who would actually use it what they think, separately from your manager's approval.
Revise the proposal based on what people actually said, not what you already pitched
The plan built before talking to real stakeholders is a starting guess, not a commitment. When their reactions contradict the original pitch, the professional's credibility improves by adjusting the plan openly rather than defending a version already shown to miss the mark in front of the very people it was meant to help.
Stating the assumption plainly can conflict with pitching something rough: naming a bold, specific belief can make a rough one-page sketch feel too thin to defend in front of leadership. Resist adding polish to compensate, and instead pair the rough sketch with one real data point or reaction that supports testing it further.
Name one thing, honestly
Which recent proposal did you build fully before checking whether the people it affects actually wanted it?
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
Before finalizing your idea, ask one person from the group who would actually use it what they think, separately from your manager's approval.