Some of the most useful work I do leaves almost nothing behind.
A portfolio case study is an unfairly antiseptic account of a project. Here is a report. Here is an identity, a platform, a system. Everything appears as a finished object.
What disappears are the personalities, budgets, old decisions, new anxieties, unclear language, and deadlines that don’t care whether the idea is ready. For a long time, I thought of all of this as the stuff surrounding the work. The real work was what I could see. That got harder to believe as I started leading more projects.
Much of the invisible part is translation. Someone says they want “more impact.” Maybe they mean contrast. Maybe confidence. Maybe they’re worried the CEO is going to flip past the page without noticing it. The request and the actual worry are often two different animals, and asking one more question can often keep a room full of people from spending a week solving the wrong problem in excruciating detail.
There are days when I leave work having “made” almost nothing. Maybe I've clarified a decision, connected two people, moved something out of somebody’s way, given a designer another afternoon before showing the work, or written down enough context so we didn’t have go on an archaeological dig through Slack messages.
At first, those days made me vaguely guilty. I like making things. I like the haptic feedback of an idea taking shape in my hands. “I helped several conversations go better” has considerably less portfolio appeal. But I’ve come to appreciate that without nurturing the conditions for good work, no good work will happen.
You can see the symptoms of this hidden work: fewer surprises. Calmer handoffs. Decisions that still make sense a week later. Somebody else being able to pick up the thing without needing you standing beside them.
I still prefer the days when I make something I can see. But I no longer think those are the only days that count.
Last edited August 23, 2026