Philosophy · Design · Process

If I Have to Do It Twice, I Build a System.

I have to be honest about something first: repetition exhausts me.

Not in a dramatic way. But when I realize I have to do the same thing a hundred times, something in my brain activates that refuses to accept it as the only option. The repetitive task stops being a task and becomes a problem waiting to be solved.

In my years working as a graphic designer, I encountered two very different types of work.

The first was complex. Corporate identity. Advertising campaigns. Report layouts. Press kits. These projects required thinking, coordination, adapting to the constraints of the brief. They were demanding, but they were interesting.

The second type was repetitive. A set of 40 name badges for a sales department. 300 business cards with different information on each. A catalog of 1,000 products where name, category, code, and price repeat in the same position on every page. Five or six presentations of the same product for different regions. A session of 350 photos that needed consistent backgrounds and uniform crops before they could be used for anything.

The complex work required my full attention. The repetitive work required my patience — and I don't have much of that when the solution is sitting right there.

The tools were always available. The question was always the same: are you willing to invest the time to learn them?

The Discovery

I found genuine pleasure in spending 15 hours to automate something I could do manually in 3.

Batch processing in Photoshop. Data Merge in InDesign. Scripts in Illustrator. Mail Merge in Word. Automatic numbering in PDF. These tools existed long before I started using them. Most people in my field knew they existed. Very few invested the time to actually learn them.

I did. And I found something unexpected: genuine pleasure.

I would spend 10, 15, sometimes more hours figuring out how to automate something I could have done manually in 3 or 4. Not because I was being inefficient — but because I understood that once the system was built, I would never have to do it manually again. The investment paid for itself the next time the same problem appeared. And the time after that. And the time after that.

That moment when the automation runs for the first time and produces exactly what you needed — without you touching it — is a specific kind of satisfaction that's hard to describe. A confirmation that the hours were worth it.

The Cases

Seven problems. Seven systems. All built with tools that were already there.

350 staff photos. The institution hired an inexperienced photographer to take ID photos of all staff members for their institutional badges. Instead of a clean backdrop, she used standard A4 paper sheets as the background — inconsistent, wrinkled, and far from professional. Manual editing for 350 photos would have taken days. I set up a Photoshop Batch: automatic subject selection, standardized crop, background removal, export. All 350 processed in a fraction of the time. The imperfect input became a clean, uniform output.

Data Merge — one tool, every repetitive problem. InDesign's Data Merge became my answer to almost every repetitive design task. I used it for statistical infographics — 36 regional documents generated almost automatically from a structured data table. I used it for 10,000 field staff identifiers. I used it for full department business card sets.

But there's a benefit nobody talks about: Data Merge forces the information to arrive in a table. That means every department had to organize their data in a structured format before sending it to me. Errors were caught before they reached the design. The automation didn't just save time on output — it standardized the input.

The numbered receipts. The accounting department ran out of pre-printed numbered receipts and was waiting on a purchase order to restock. I built the template, set up automatic numbering, and exported the PDF. Printed on the laser printer already in the office. It was so efficient that the department cancelled the purchase order entirely. The cost of printing locally was lower than the procurement process. Automatic numbering is a native feature in InDesign, Illustrator, and PDF export. It just required someone to use it.

The institutional identity crisis. A government institution went through a brand identity change. The new isotype arrived 30 to 35 days late — no official stationery could be printed for 10 regional offices during that time. My solution: a Word template with the header and footer locked, containing the new identity. Every department already had a digital color printer. The purchase order for offset-printed stationery was cancelled. The files were already there.

The measurement ruler. One of the most frequent conversions I did was between inches and centimeters. I printed a custom conversion ruler and left it permanently on my desk. The next time someone arrived with a measurement question, I didn't calculate. I put the object on the ruler.

The paper form distribution. Distributing forms to field units across the country meant counting stacks constantly — always in multiples of 50. I converted the stack height into a measurable reference using the industrial copier's output. Units stopped asking me to count. They came, read the ruler on the stack, and took what they needed. Over four months, I processed approximately 750,000 copies. Counting each delivery by hand would have been impossible.

The homelab. The same instinct that built systems in professional environments eventually applied to the homelab. When a cable broke mid-run through a wall in a tenant's property, re-cabling the entire line wasn't an option. I relocated a router, converted it into an access point, and used its position as a signal relay. The wall stayed closed. OPNsense restarts automatically after a power cut. Pi-hole runs in Docker with a restart policy. Cloudflare Tunnel reconnects through systemd. I didn't build the homelab to manage it every day. I built it to manage itself.

The Honest Limit

I don't automate everything. I automate what I can control.

Some repetitive tasks require equipment or resources I don't have access to. An automatic die-cutting machine is incredibly expensive — so when I have to do die cuts, I do them by hand. No complaints.

But if I can automate it within the digital tools I already control, I will. Every time. Because once you've built the system, the work stops being repetitive. It becomes a process. And a process can be improved. A repetitive task just gets done again.

The Point

I don't work harder. I work once.

Every system I built started with the same frustration: having to do something again that I had already done before. Every automation was a decision not to solve the same problem twice. And every time I found a tool already sitting in the software I was using — already available, already documented, just waiting for someone to invest the hours — I felt the same thing.

Not efficiency. Satisfaction.

The tools were always there. The question was always the same: are you willing to invest the time to learn them, so you never have to do it manually again?

What's the most repetitive task you've ever systematized? Drop it below.

This post contains Amazon affiliate links. If you purchase through them, I may earn a small commission at no extra cost to you. Every product listed here is something I personally own and use daily.