Workflow Automation & Digital Operations Engineering
From Manual Steps to Rules-Based Systems
Business processes were analyzed and redesigned into standardized, automated workflows, including a direct migration of a core project tracking process from manual spreadsheets to a governed SaaS platform.
Business Challenge
Core operational processes, including central project tracking, were running on manually maintained spreadsheets. This created version-control risk, made cross-team visibility difficult, and put institutional knowledge in individual files instead of a shared system.
Methodology
The redesign followed the standard automation lifecycle: discovery, process mapping, business rules, automation build, testing, deployment, and a continuous-improvement loop afterward. One concrete result was leading the migration of the central project database off Google Sheets and onto a governed SaaS platform.
- Discovery and current-state process mapping across manual workflow steps
- Business rules definition to determine what could be safely automated versus what required human judgment
- Automation build, testing, and phased deployment
- Continuous improvement loop to refine rules as edge cases surfaced post-launch
Outcomes
- Reduced manual effort across previously spreadsheet-dependent processes
- Improved data quality by removing manual re-entry and version-control risk
- Faster reporting turnaround once data lived in a governed, queryable system
- Stronger governance through defined ownership and audit trail, replacing informal spreadsheet stewardship
Exhibit 11.1
BPMN-style process view: legacy manual step re-engineered into an automated, rules-based workflow
Lessons learned
- The migration off spreadsheets was less a technology project than a trust project. Teams had informally patched around the old system's gaps for years, and those patches had to be understood before they could be replaced.
- A BPMN-style view of a process, even a simple one, surfaces exception paths that a narrative description quietly glosses over.
Consultant's note
"Every team had a slightly different unofficial workaround for the same broken step in the old spreadsheet process, which meant the real discovery work wasn't mapping the official process. It was mapping the unofficial ones running underneath it. That's usually where automation projects actually live or die."
Skills demonstrated
- Process Re-engineering
- Workflow Automation
- BPMN Process Mapping
- Change Management
Part of Volume 3 — Delivery Excellence, Product Strategy & Enterprise Transformation.