What Career Professionals Can Learn from The Design of Everyday Things
Nadia built an internal wiki to document her team's onboarding process, organizing pages the way her own mind worked: by project, then by date, then by owner. She was proud of how thorough it was. Three months later, a new hire named Owen spent his entire first week clicking through outdated pages, unable to find the one document that actually mattered, because nothing on the wiki's homepage told him where to start or what was current. He assumed the confusion meant he wasn't picking things up fast enough, and said as much in his first check-in, apologizing for being slow. His manager quietly noted it as a concern about his ramp-up speed. Nadia never learned that her tidy, logical wiki had cost a new colleague a week of confidence, because from her side of the screen, everything about it had always been perfectly easy to find.
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
Making a work process visible at a glance
A shared document, workflow, or reporting template should show a new colleague what to do and where things stand without requiring a private explanation from whoever built it. If understanding a system depends on catching its creator in the hallway, the system hasn't actually documented itself.
A shared spreadsheet uses color highlighting to mean "in progress," but no legend exists anywhere, so new team members guess at the color code for months.
Ask the newest person on your team to use one of your core work documents unassisted, and note every point where they pause to guess.
Giving feedback the instant someone acts
When a colleague submits a request, updates a status, or completes a handoff, the system needs to confirm it clearly and immediately, not leave people wondering whether something actually went through. Ambiguity here quietly produces duplicated work and missed deadlines that look like individual failures but are really structural ones.
An approval request sits in a queue with no visible status, so the requester follows up twice, unaware it was actually approved on day one.
For your team's most-used request process, confirm that every submission produces an immediate, visible acknowledgment before anything else changes.
Matching workplace tools to habits people already carry
A new tool or process adopts faster when it resembles the shape of something colleagues already know, rather than introducing an entirely unfamiliar structure for a familiar task. Borrowing a layout, naming convention, or workflow shape people already trust reduces the relearning cost of every rollout.
A department switches to a new project tool with its own unique status labels, and staff keep quietly translating them back into the old vocabulary for months.
When introducing a new work tool, map its terms directly onto whatever the team called the same thing before, and keep that mapping visible.
Treating a colleague's repeated confusion as a system flaw, not a skill gap
When several colleagues stumble over the same step in a shared process, the fair conclusion is rarely that they lack the skill for the job; it is that the process itself never clearly showed what to do. Professionals who redesign the process after noticing this pattern spare every future teammate the same private embarrassment, while those who chalk it up to individual competence let the same silent failure repeat with each new hire.
Visibility and workflow speed can compete at work: documenting every option keeps a process transparent but can slow people down with more to read than they need. The balance is to keep the everyday path short and obvious, while making the fuller documentation easy to find for the moments that call for it.
Name one thing, honestly
What work process have you assumed was self-explanatory, that a newer colleague may have quietly struggled through alone?
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
When introducing a new work tool, map its terms directly onto whatever the team called the same thing before, and keep that mapping visible.