W.R. Berkley

Underwriters were retyping the same record. I scoped the path and got three teams to ship the replacement.

Berkley’s underwriting staff work across policy, claims, and billing. I gathered the requirements from the people doing the work and carried them through QA and DevOps to a release.

Problem

The pain was not a missing screen. It was rekeying between systems, 84 hours a week, with transcription errors as the side effect. A feature request would have added a form. The job was to remove a job.

Process

I shadowed the entry. The map of fields people copied by hand became the requirement. I wrote it as scoped work the application teams could schedule, then stayed on the handoff: QA, DevOps, and the underwriting stakeholders each had a review step. Nobody got a surprise in the release notes.

Solution

• A written workflow of the manual path, agreed with the people who performed it.
• Scoped work that replaced the path, tied to policy, claims, and billing so we did not invent a fourth system.
• A release review across three teams before it was called done.

Results

• 4,500+ Hours a year removed
• 84+ Hours a week
• 3 Teams on the release path
• 0 New system of record. We connected the ones they had

Justin Moran · Product Manager · Chicago, IL · LinkedIn · Resume (PDF)