Stop Rebuilding the Work You've Already Done
This post originally appeared in my Substack newsletter, The Work Behind the Work. Subscribe here.
Somewhere around the third time you build the same thing from scratch, you notice.
Not a similar thing. The same thing — same structure, same sections, same decisions made again in the same order, because the previous two versions are somewhere in a folder you can’t find, in a state you don’t trust.
And the strange part isn’t the wasted time. It’s that rebuilding doesn’t feel wasteful. It feels productive. You’re making something. The calendar looks full. The work ships.
Photo by Danist Soh on Unsplash
Mine is PowerPoint decks. I’d like to say it was one deck. It was a habit.
I’d start with what I was sure was the right template and spend hours — sometimes days — getting it exactly right. Alignment, type, spacing, brand consistency, formatting adjusted and readjusted until it landed. The result was usually a deck I was proud of.
Then the next month or quarter would come around and it was time to update it. But in between, I’d built decks for other projects, each one slightly or completely different from the last. The branding was there. The consistency wasn’t. So rather than reconcile them, I’d start over. Layout, type, graphics, all of it, again.
And it felt great. I was busy. I was creating something. Every hour of it looked like work, and almost none of it was.
What finally fixed it wasn’t complicated. I built one reusable template and committed to it for a year — no rebuilding, no starting fresh because I’d had a better idea about the title slide. The payoff was bigger than I expected. Updating a deck became updating copy and graphics. Everything structural was already decided.
The template was the easy part. Sticking to it was the work.
Why rebuilding disguises itself as work
Reusing is administrative. Rebuilding is creative.
Finding the old version means searching a drive, opening three candidates, figuring out which is current, discovering the fonts are missing, and deciding whether it’s still good. That’s twenty minutes of unsatisfying detective work with no visible output.
Starting fresh means opening a blank file and immediately making things. It feels better. It looks better on a status update. And it takes four hours instead of forty minutes.
Multiply that across a team and a year and the number gets genuinely uncomfortable — not in hours, but in what those hours displaced. Every rebuild is a piece of new thinking that didn’t happen.
The rule of three
Not everything should be systematized. Building a template for something you’ll make once is its own form of procrastination.
The threshold I use is three. The first time you make something, just make it. The second time, notice. The third time, stop and build the reusable version — because if you’ve needed it three times, you’ll need it again, and you’re now at the point where the investment pays back inside the same quarter.
What’s worth building at that point is smaller than people assume. Not a full system. Usually just:
the structure, with the decisions already made and the placeholder text explaining what goes where
the constraints baked in — correct dimensions, correct fonts, correct legal line
one worked example of the thing done well
a name that describes what it’s for, not what it is
That last one matters more than it should. A file called “Template_Master_v3” doesn’t get reused, because nobody knows what it’s the master of.
Then leave it alone
The rule of three tells you when to build. It says nothing about the harder part, which is what you do for the twelve months afterward.
Build it on the third occurrence, then commit to it for a full cycle. A year, if the thing is annual. Whatever the natural cycle is if it isn’t.
Because the urge to improve a template mid-year is the same urge that caused the rebuilding in the first place. It just arrives wearing better clothes. You’re not starting over — you’re refining. And the outcome is identical: an afternoon spent on structure again, and now two versions that are slightly different, which is exactly how the drift starts.
Improvements go on a list. The list gets addressed once, at the end of the cycle, in a single pass. That way the changes are deliberate and they happen everywhere at once, instead of accumulating one good idea at a time until nothing matches.
One template used imperfectly for a year beats four perfect ones.
The library nobody maintains
Most teams have already tried this. There’s a shared folder somewhere with “Templates” in the name. It’s full of things from two brand refreshes ago.
An asset library isn’t a folder. It’s a folder plus a habit, and the habit is the part that fails.
Two things have made the difference for me. First: the library gets updated as part of finishing a project, not as a separate cleanup task. When work ships, the reusable version goes back — same day, while the file is still open and you still remember what’s in it. A cleanup task scheduled for “later” is a task that will not happen.
Second: someone owns it. Not as a title, just as a fact. Shared ownership of a library means nobody notices when it goes stale, because everyone assumes someone else did.
What compounding actually looks like
We talk about compounding as though it applies mainly to audience and reputation. It applies just as much to the machinery.
A team that reuses well starts every project further along. Not because they’re faster at the making, but because the first 30% of the work is already done before anyone opens a file. Over a year that’s not a small efficiency — it’s the difference between a team that’s always producing and a team that occasionally gets to think.
And there’s a quality effect that’s easy to miss. When the structure is already solved, attention goes to the part that’s actually specific to this project. The baseline rises, because nobody is spending their good hours re-deciding margins.
The work you’ve already done is an asset or it’s a cost. It’s a cost by default. Making it an asset takes about forty minutes at the end of a project, on the day you least feel like doing it.
Question for you: Which reusable asset saved you the most time this year — and why did it take you so long to build it?
