Process Improvement & Development · Operational Excellence · Independent
I help companies and organizations work faster and smarter — by improving and developing the process, not just the output.
A decade leading engineering and delivery teams across European industry — now independent. I work alongside your team to find what's really slowing work down, fix it at the root, and leave you able to keep improving without me.
I partner with leaders of growing teams — in software, tech and operations whose processes have become slow, inconsistent or hard to scale.
Where I've improved how work gets done
Each figure is from a real engagement — the full stories are below.
I've spent my whole career on one question: how do we make this work better? It started on a factory floor in Syria, tuning Siemens PLC and SCADA systems so the production line never stopped.
Over the last decade in Europe I carried that mindset into software and operations — leading engineering and delivery teams, modernizing how releases happen, and redesigning how work flows from idea to outcome. The results were consistent: faster delivery, fewer defects, and teams doing their best work instead of fighting the process.
Today I bring that experience to teams and organizations independently. I help them find the real bottleneck behind slow, inconsistent work, redesign the process around it, and build the habits that keep the improvement going after I step away.
Now working independently as a Process Improvement specialist — and I hold an M.Sc. in Computer Science from the University of Bath.
Independent engagements — from a focused diagnostic to owning your build end to end.
You have the idea or the spec but no team to ship it. I assemble and lead a hand-picked senior team and own the whole build — from discovery and planning through design and engineering to launch. You get one accountable lead driving it end to end, not a set of vendors to coordinate.
A fixed-scope review of how work actually flows from request to result. You get a clear map of where work stalls and a prioritized plan for the biggest wins.
Reshaping how work flows and automating the repetitive, error-prone steps — approvals, handoffs, CI/CD, environments — so the work becomes calm and predictable.
Putting in place the metrics, cadence and ownership that turn improvement from a one-off project into something your team runs every week without me.
Hands-on leadership when you need it — setting direction, coaching the team, and getting delivery back on track without a full-time hire.
Most engagements start small and only grow if it's working for you.
A free 30-minute call to understand what's slowing your work down and whether I'm the right fit.
A focused 1–2 week review of your process — a clear scope and a clear price, set before any work begins.
A short, ranked plan of the changes that will move the needle most — yours to keep, with or without me.
Optional hands-on help putting the changes in place and coaching the team to keep improving on their own.
A decade of fixing how teams and systems work has left me with a few convictions I don't compromise on.
Most teams optimize the wrong thing. I start by following the work end to end to find the one constraint that's actually holding everything back.
You can't improve what you don't measure. We baseline first, then prove every change with data — not opinion.
The people doing the work know where it hurts. I design improvements alongside the team, so the change sticks instead of being resisted.
A single fix fades. The real goal is a team that keeps finding and removing friction on its own — long after the engagement ends.
Real bottlenecks, redesigned processes, measurable results.
Scaling manufacturing software across web and mobile without the delivery discipline to keep it predictable.
Introduced OKR-driven delivery, Scrum rhythms and CI/CD, and coached the team toward autonomy and ownership.
Raised productivity by 40% and reduced defects by 35% — delivery the business could finally plan around.
Legacy monolithic systems and manual releases meant shipping any change was a slow, error-prone effort — and that pain stretched across several divisions.
Led the delivery-process redesign — moving to cloud-native services and continuous delivery, with DevSecOps controls built in.
Cut deployment time by 50% and gave teams a process they could change safely and confidently.
Enterprise clients with competing priorities and unclear roadmaps — delivery stalling wherever the business and the engineers had drifted apart.
Ran workshops and needs assessments to align roadmaps with business priorities, then delivered end to end across cloud, integration and automation.
Stakeholders aligned around one clear roadmap and transparent reporting — the way of working I now bring to clients independently.
A collaboration platform used daily by thousands was straining under load, with no room for downtime.
Drove targeted architectural refactoring and database optimization across the React & SharePoint stack.
Delivered 30% performance gains while keeping thousands of concurrent users productive.
The convictions behind how I help teams improve — and the conversations I value most.
When something keeps going wrong, it's rarely the people. It's the process they're forced to work inside. Fix the system and the symptoms disappear.
The fastest teams I've seen didn't try harder — they deleted steps, waiting and rework. Most of the gains are hiding in what you can stop doing.
Grand transformations stall. A team that improves a little every week compounds into something no one-off project can match.
Every step has an owner and a tracker. The gaps between them — where work sits in someone's queue, waiting on an answer or a sign-off — belong to no one and show up on no dashboard. That invisible time is where most of the delay lives.
Delivery gets predictable the moment a single person is clearly accountable for the outcome — not a committee, not a shared inbox.
Straight answers before we ever get on a call.
With a free 30-minute call, then a fixed-fee diagnostic. I'd rather earn the bigger work by being useful in a small, low-risk piece first — so almost everyone starts with the 1–2 week process diagnostic before deciding what comes next.
The diagnostic is a fixed fee for a fixed scope — you know the cost up front, with no open-ended retainer. Anything beyond it — implementation, coaching, fractional leadership — is agreed separately once we both know what's worth doing.
Both, depending on what the problem needs. I'm an engineer by background, so I'll get hands-on with your pipeline, environments and architecture where that's the fastest path — but the goal is always to leave your team able to run without me.
Always with it. I don't take work off your engineers — I help them clear what's slowing them down. We diagnose the problem and design the fix together, so when I leave, the team owns both the change and the thinking behind it.
For a full product build I assemble and lead a hand-picked senior team for that engagement — designers and engineers I trust — and stay the single accountable lead from discovery to launch. You get one person owning the outcome, not a standing agency to manage or a set of vendors to coordinate.
I work remotely across the Middle East and Europe, which overlap comfortably for real-time collaboration. I keep a clear working rhythm and regular check-ins, so distributed delivery stays just as predictable as in-person.
I'm taking on new engagements now. Email me a line about what's slowing your work down — or reach me on LinkedIn — and we'll set up a free 30-minute call.