Gmail taught us to be digital hoarders. To save every email, every chat, every search. Because it might come in useful someday.

All that data might feel like a security blanket. But it creates real mental load.

Do you really need that email from 2010 coordinating movie plans? The shipping notification from 2014? Backed up files you’ll never actually look at again — files that could be a liability in a breach?

This digital clutter can have the same effect as physical clutter — overwhelm, the sense you can’t quite move on since you’re worried about what if.

I recently cleaned out years of digital detritus — tens of thousands of emails dating back more than 20 years, gigabytes of data in online storage.

One account now holds 45 total emails — just those that were particularly meaningful. Everything else? No longer a weight.

Turns out nothing I deleted was ever needed. It never was.​​​​​​​​​​​​​​​​

Twenty years ago, posting an article to the website I managed took 30 minutes. Not 30 minutes of writing but 30 minutes of work after the writing was done.

Creating the raw HTML page. Updating the HTML on every page that linked to it. Fighting with Internet Explorer 6.

And that was after I’d already paid for Dreamweaver to simplify site management and spent months learning ASP and HTML well enough to not break everything.

It was handcrafted. And it was awful.

Last week I built an entire web app on my commute. My family has been watching films together for years, and I wanted something that would track what we’d seen and suggest what to watch next.

From idea to working app: 30 minutes. The whole train ride was spent on the thing I actually cared about — the feature set and the experience. Not painstakingly centering divs, or debugging a CSS error, or digging out solutions from the snippiness on Stack Overflow.

At one point, I asked my AI collaborator to add a custom date picker. At another, I asked it to create an import-export function for the database. Each change took 20 seconds to type and only slightly longer to execute. Almost magical.

The cost of entry? Twenty dollars a month.

Some people will say it doesn’t count if you didn’t write the code yourself. My kids, discovering a film they love on a Friday night, would disagree.

The tools used to eat your time. Now they give it back. That’s genuine progress.

I’m not good at home repair. I don’t enjoy it. When something breaks, my first instinct is dread.

For a long time I thought the solution was willpower — grit my teeth, get through it, reward myself after. The task was something to endure.

But that framing made the problem worse. On top of my broken toilet, I had to deal with my resistance to fixing it.

Here’s what shifted things: realizing that the toilet doesn’t care how I feel about it. It needs fixing whether I’m frustrated or not. The frustration isn’t doing any useful work — it’s just a second unpleasant thing running alongside the first.

The solution wasn’t learning to love DIY, or steeling myself more firmly against discomfort. The solution was recognizing that my frustration was optional, and setting it aside.

Just noticing it wasn’t helping and moving on.

Step out for a one-hour meeting and you come back to dozens of project notifications.

Status updates. Comments. @mentions. Automated alerts telling you a due date changed on a project you’re barely involved in.

You weren’t gone long. But the tools kept churning out noise without you — and now they want your attention.

This is the hidden cost of systems built for transparency. They show everyone everything. All the time.

In theory, that makes coordination easier.

In practice, it means you’re always a little bit behind.

Worse, none of it tells you what to actually do next.

An inbox full of updates tells you what’s happening — not what matters, not what’s required of you, not what should happen today. Figuring that out is its own work, layered on top of the actual work.

The fix I’ve landed on: one list, maintained separately from the project tools my team uses. A filter that sits on top of the existing tools.

I treat the notifications as inputs. When something actually requires action, I pull it out and add it to the list, alongside everything else competing for my time. Then I decide what to work on next.

The project management tools tell me what’s happening. My list tells me what to do.

Only one of them should be in charge.​​​​​​​​​​​​​​​​

When you’re in marketing or fundraising, it’s tempting to treat feedback on your creative as a checklist.

A series of fixes to reconcile everyone’s conflicting edits so you can hit your deadline.

This is almost always the wrong approach.

Apply every comment and you risk creating a Frankenstein’s monster. Split the difference and you get something dry and forgettable — nobody objects, nobody’s moved.

Here’s why: the notes you get aren’t really about the words on the page.

They’re diagnostic signals. When someone says “this isn’t working,” they’re telling you they felt something — confusion, skepticism, a disconnect — before they knew why. Your job is to find the why.

Consider a common scenario: you share a draft proposal with two executives. One wants you to list key programs. The other wants more emphasis on mission and history.

Both are telling you what they care about. Neither is asking what might actually move the customer to act.

Your job isn’t to negotiate between them. It’s to diagnose what’s underneath: they both sense the piece isn’t compelling — they’re just reaching for familiar answers. The real question is what a prospective customer needs to feel before they’ll say yes.

That’s the difference between taking a note and reading a note.

Sometimes the right move is to accept an edit verbatim. More often it means applying the spirit of it. Occasionally it means rejecting it entirely — and being able to say why, in terms of what the reviewer actually felt and what the piece needs to do.

That’s what it means to own the work. Not protecting your original draft, but using others’ reactions as data to get closer to something that will actually land.

Stop trying to satisfy the room. Start asking what the customer needs.