The Gap Between a BPMN 2.0 Process Map and a Screen
Most system rollouts have 2 sets of documents that never quite meet. On one side sits the process work. A BPMN 2.0 process map, current state, future state, pools and lanes showing who does what. On the other side sits the design work. Wireframes, screen flows, a prototype somebody built in a fortnight. Both are […]
Go Live Is 8 Weeks Away. Nobody Agrees How the Work Is Done Today.
The vendor has a go live date. The steering group has a budget. Then someone asks a simple question. “How does this process actually work today?” Four teams give four different answers. Nobody’s wrong. Nobody has ever written the work down end to end, so the vendor is designing against a 2019 document. That’s a […]
Where to Put Process Maps and Work Instructions So Teams Actually Use Them
Rollout day arrives. The new system goes live, the training is done, the project team is on standby. Then someone in the contact centre asks a simple question about a refund, opens 3 different folders, finds 2 versions of the same document, gives up, then asks the person next to them. That moment is where […]
The Programs I’ve Seen Fail, Failed on People
I’ve been part of digital transformation work for close to 20 years now. Some of it went well. Some of it didn’t, which is more instructive. Looking back at the ones that struggled, the causes were rarely technical. The platform usually worked. The methodology was usually sound. What went wrong was in the room, which […]
Who Documents Business Processes? The Role of a Technical Writer in Process Mapping
There’s a question that comes up early on most programs, usually as a scheduling problem rather than a role question. Who’s actually documenting the process? The business analyst assumes it’s covered. The change team thinks it’s a project deliverable. The process owner assumed someone did it years ago. Meanwhile the technical writer has been booked […]
How to Get People On Board With a Change They Didn’t Ask For
This comes up in almost every process analyst interview. How do you handle resistance to change. The honest answer is that most people aren’t resisting change itself. They’re resisting being changed by someone who hasn’t asked them anything. There’s a difference, though it takes a while to see it. Once you do, the job stops […]
Why SMEs Trust Their Own Bad Documentation More Than Your Good One
Here’s a situation that plays out on most programs. A team has a procedure they wrote themselves. It’s a Word document, slightly out of date, structurally messy, missing the prerequisites. You produce a properly written replacement. Clear steps, verified against the system, tested, well structured, findable. Six months later they’re still using their own version. […]
How Process Analysts Succeed on Massive Digital Transformation Projects
Big programs have a way of swallowing people. There’s a program board, five or six workstreams, a systems integrator, two vendors, a change team, and somewhere in the middle of it all sits you. Your job, on paper, is to map the current state and help design the future one. In practice, your job is […]
You Wouldn’t Ship Code Without Version Control. Your SOPs Have None.
Ask any engineering team how they manage change to their codebase. You’ll get a confident answer. Version control, branches, pull requests, code review, a deployment pipeline, rollback if something breaks. Every change attributable to a person, a date, a reason. Now ask the same organisation how they manage change to their standard operating procedures. The […]