Systems Thinking Service Design
Interactive service blueprints of BP’s offshore rig-verification process, made so the designers across BP’s Risk Toolkit could see how their piece connected to everyone else’s.
BP’s Risk Toolkit is four safety apps, each covering a phase of the same job: assessing risk before a well starts, verifying the rig, monitoring active operations, tracking issues over time. Four tools, four teams — and each one could run its own app without a clear picture of what the others did, or how the work connected across them. Myself included.
I was brought in on Rig Verification, the most field-intensive of the four: personnel spend 24–36 hours on offshore platforms inspecting equipment and safety systems before drilling begins.
I interviewed both ends of the process — rig verifiers with decades boarding platforms, and the developer who built the app. One knew what happens on the rig; the other, what happens in the system. I mapped the whole thing: every step, who performs it, what it produces, which checks run separately and which together, and where work crosses between BP and the rig operator — BP leases the rigs, so nearly every handoff crosses an organizational line.
It all ran on Salesforce, which held every step but never showed the shape. The blueprints did.