One Trigger, One Action: The Only Automation Rule We Need
Complex automations are fragile. If you chain 20 steps together, step 14 will break. Keep your robots small, stupid, and sturdy.
The Operations Pragmatist Stockholm
Operations Lead who bridges the gap between muddy boots on site and spreadsheets in the office. She manages the messy reality of physical work: lost tools, bad signal, and teams who hate computers. Writes here about fixing broken processes with sturdy tools—whether that's an offline app, a QR code, or a bulletproof Excel macro.
Note: “Ingrid Pipeline” is a pseudonym. We use pseudonyms so we can write honestly about real work without naming clients, employers, or teams.
Complex automations are fragile. If you chain 20 steps together, step 14 will break. Keep your robots small, stupid, and sturdy.
We spend hours clicking on 'Scan_004.pdf' to see what it is. This is madness. Let the machine name the file. Organization must be automatic.
Silence is dangerous. When an app doesn't tell you the sync failed, you find out on Monday morning. We need loud, visual status indicators.
No-code tools promise miracles. They deliver pipes. Pipes leak. Pipes clog. Treat automation like industrial plumbing, not magic tricks.
Field workers do not read PDFs. If your software requires a 'Training Day,' you have built it wrong. The interface must be as obvious as a hammer.
Buying new software to fix bad habits is expensive. If you cannot manage a list in Excel, you cannot manage it in SAP. Fix the data first.
When the client asks for proof, you should not need to search WhatsApp. Scattered data is a liability. Structured data is an asset.
Tiny dropdowns are not a design choice; they are a safety hazard. Respect the worker in the rain. Design for the glove.
Do not trust the sales demo. Put the phone in Airplane Mode. If the app breaks, do not buy it. A simple test for sturdy software.
The office has WiFi. The basement does not. Relying on the cloud for field work is negligence. Build for the disconnect.