Selected work
Proof
Composite, role-level descriptions. Client names withheld. Numbers are program metrics, not audited.
01 · AI and product development · 2024
AI Platform Development & Deployment
- Situation
- An enterprise AI programme with experiments in flight and nothing in production.
- Call
- Ship one model to production before starting a second.
- Artifact
- A model registry, a deployment pipeline, and the review process around them.
- Result
- 12 models shipped and stayed up.
- Permission
- Composite, role-level. No client name. Numbers are program metrics, not audited.
02 · Growth and capture · 2023
Navy Program Capture & Delivery
- Situation
- A Navy financial system with no product owner and no defined offering.
- Call
- Define the offering before writing the proposal.
- Artifact
- The offering definition and the capture strategy.
- Result
- One full capture cycle, delivered across eight Navy commands.
- Permission
- Self-reported. No client permission on file. Numbers are program metrics, not audited.
03 · Platform engineering · 2023
Engineering Organization Scaling
- Situation
- Two hundred engineers, five release trains, no reliable release.
- Call
- Fix the release process before hiring another engineer.
- Artifact
- One release cadence, quarterly planning, and the tooling to hold it.
- Result
- Deployments went from quarterly to weekly.
- Permission
- Composite, role-level. No client name. Numbers are program metrics, not audited.
04 · AI and product development · 2023
Real-Time Operational Analytics Platform
- Situation
- A nightly batch report was the only answer an operator could get.
- Call
- Replace the batch job with a stream, not with a faster batch job.
- Artifact
- A streaming pipeline and the dashboards on top of it.
- Result
- 10M+ events a day, answers in under a second.
- Permission
- Composite, role-level. No client name. Numbers are program metrics, not audited.
05 · Platform engineering · 2022
Cloud Platform Migration & Architecture
- Situation
- Forty applications on premises, each one migrated by hand.
- Call
- Build the landing zone and the deployment pattern once, then move the applications.
- Artifact
- A landing zone, infrastructure as code, and a reusable deployment pattern.
- Result
- 40+ applications migrated.
- Permission
- Composite, role-level. No client name. Numbers are program metrics, not audited.
The one public artifact
If any of this is close to your situation, the first step is a conversation.
Work out what to productize before you spend the money. Two weeks, a fixed scope, and the written decision.
