Which utility processes are worth turning into a workflow first?
Start with the two that repeat most often and leak most value: recurring asset maintenance checks, and customer onboarding from service request through to the first meter reading. Both are simple to model and immediately visible when they slip.
Workflows can model almost any process, which is exactly why utilities stall on where to begin. A useful test is whether a process repeats, involves more than one person, and currently lives in somebody's head or notebook. Maintenance rounds and new connections fail that test daily, which is why they repay the effort first.
How to do it
Pick one process that repeats and currently depends on somebody remembering it.
Model a simple version first, such as a recurring maintenance check on an asset.
Assign each step to a role, so the right person picks it up without being chased.
Test it end to end in the Portal and in the app, since field steps happen on a phone.
Add the harder process next, such as a full connection through to the first reading.
Watch which steps stall, and change the workflow rather than chasing the people in it.