The Hidden Cost of "We've Always Done It This Way"
Undocumented processes quietly cost Swiss SMEs hours every week. Here's how to put a price tag on the chaos — and what it takes to fix it for good.
Ask three people on your team how the month-end invoicing run actually works, and you'll likely get three different answers. One does it from memory. One follows a half-finished checklist from 2021. One just asks a colleague every single time because "it's faster than figuring out the Visio file again." None of this feels urgent on any given day. But add it up over a year, and undocumented processes are one of the most expensive problems a small Swiss company never puts on a balance sheet.
What "no process documentation" actually costs
Consider a modest, realistic scenario common in Swiss SMEs: a five-person back office handling onboarding, invoicing, expense approvals and basic HR tasks. If each person loses even 30 minutes a day re-explaining a step, hunting for the "latest" version of a procedure, or redoing a task because a step was skipped, that's 2.5 hours per person per week — roughly 12.5 hours across the team. At a loaded cost of CHF 60-80 per hour, that's CHF 750-1,000 a week, or CHF 36,000-48,000 a year, spent not on growing the business but on simply keeping it running the same way it always has.
And that estimate doesn't include the hidden costs: the new hire who takes three extra weeks to become productive because nothing is written down, the mistake that happens when the one person who "knows the process" is on holiday, or the fiduciary partner who bills extra hours trying to understand your workflow before they can even start improving it.
Why the usual fixes don't stick
Most teams have tried to solve this before. A diagram gets drawn in Visio or Lucidchart, exported as an image, dropped into a shared drive, and forgotten within a month because it lives nowhere near the actual work. A Word document describes a procedure in prose that nobody has time to read step by step. Tools like Process Street help with checklists but disconnect the process from the systems, forms and chats where the work really happens. The documentation becomes a side project instead of a living part of operations — which is exactly why it decays.
Mapping the process where the work already lives
Flitz's Process Mapping feature starts from a different premise: a process map is only useful if it's as easy to update as it was to create, and if it sits next to the tools it describes. You get a draw.io-style canvas with the shapes you actually need — steps, decisions, documents, systems, sub-processes, manual steps, waits — that lay out automatically left to right or top to bottom, or however you prefer to arrange them.
Instead of building every diagram from a blank page, you can describe a process in one sentence — "process to delete personal data," for example — and let AI draft an As-Is or To-Be version for you. If a process already exists somewhere as a PDF, whether it's a written procedure or a flowchart someone else drew years ago, AI can import and turn it into an editable map rather than forcing you to redraw it by hand.
Editing is built for speed too: drag a step directly onto an arrow to insert it into the flow, re-attach arrows by their ends, undo and redo, and copy-paste shapes between processes — all with the keyboard shortcuts you already know from Windows or Mac. Small frictions like these are exactly what determine whether a map gets maintained or abandoned after week one.
Seeing improvement, not just documentation
Every process can exist as an As-Is and a To-Be version side by side, with improvement notes attached directly to the steps that are changing. The same diagram can be read as a SIPOC, with every supplier, input, output and customer linked to its step, or printed as a clean, numbered SOP — handy for audits, onboarding, or simply handing to a new employee on day one.
Because every step can link to where the work actually happens — an API endpoint, a Slack or Flitz Chat channel, a Flitz form, a Google Form or Doc, a web link, an uploaded document, or another process entirely — the map stops being a static picture and becomes a working index of how your company operates.
What this is worth in practice
Getting your core processes mapped once, even roughly, typically pays for itself within weeks for a small team. The 30 minutes a day lost to re-explaining, searching and redoing work doesn't disappear automatically, but it shrinks dramatically once there's one current, accessible version of the truth — shareable with colleagues as view or edit, published to the whole workspace, or shared as a public read-only link for people outside the company, such as new hires or external auditors.
Version history with one-click restore means you can let processes evolve without fear of losing a working version. Department folders and sub-folders keep things organized as the number of documented processes grows, rather than turning into the same drawer of stale files you started with.
Start with the process that hurts the most
You don't need to map your entire company in one sitting. Pick the one process that currently causes the most back-and-forth questions, the most onboarding pain, or the most "wait, how do we do this again?" moments — and draw it once, properly. The hours you save in the first month will tell you whether it's worth doing for the rest.