Practical, low-tech process fixes for non-IT teams. Clear ownership, cleaner handoffs, fewer dropped balls — and systems people still follow when the week gets busy.
Most growing teams don’t need another tool or a heavy consulting project. They need fewer dropped balls, clearer ownership, and a way of working that survives a busy Tuesday.
Small and medium teams that are growing and starting to feel messy — operations, service, tourism, e-commerce, admin-heavy work, and similar businesses. Not IT departments looking for software.
If the operation still runs on reminders, shouting, or one person holding everything together, that is usually the place to start.
The work stays light on purpose. One bottleneck at a time, using the tools the team already has.
Who decides, who does the work, and who checks it is done. Named, not assumed.
What has to travel with the work so the next person can start without hunting.
The requests, follow-ups, and exceptions that quietly vanish between people.
A process simple enough that it still gets used when nobody has spare time.
Look at reality first. Change as little as possible. Make the new way easier than the old one.
How the work actually happens — not the version on the slide or in the handbook.
The one or two points that create most of the delay, errors, or stress.
A practical change that fits the team, the tools they already use, and daily pressure.
If people only follow it on a calm day, it is not finished.
The goal is not a perfect system. The goal is a system people will still follow when they are busy.
Clear limits save both sides time.
No platform to buy, implement, or maintain. If a shared inbox, checklist, or one extra field already solves it, that is the answer.
No Lean / Six Sigma program, certification language, or workshop theatre. The words stay ordinary so the team can use them.
No company-wide operating system. We fix the friction that is costing you now, then stop while it still works.
Practical problem-solver. Twenty years in operations where a dropped ball was not a small thing — payments, banking, and hospital systems.
At SWIFT I monitored the production network, wrote disaster-recovery procedures, and worked on Failure Not An Option: look at how errors actually happen, then make the next one harder. At SNS Reaal and Robeco I did 24/7 monitoring and incident handling — the shift work where a process either holds or it does not.
At Agfa HealthCare I was Global Monitoring Specialist on GRIP. The team had no real workflows, so I built them: procedures, escalations, request paths, and a Confluence knowledge base people could still use under pressure. Same pattern everywhere: make the work visible, name the owner, write it down so it survives a busy night.
I work remotely with English-speaking small and medium teams. Based in the Dominican Republic.
You do not need a long project to start. Send a short description of the main problem. I’ll say plainly whether I can help and what a first step would look like.
If I am not the right fit, I’ll say that too.
A few sentences is enough: what keeps getting dropped, who is stuck holding it, and what “better” would look like on a normal week. I’ll reply with a straight answer.