Agentic delivery assurance
Research & proposed controls
Studying where defects enter delivery and proposing risk-tiered review and release controls. ACCORD is a working tool, not evidence that the organisational policy has been adopted.
About
I bring experience, ask questions and work alongside teams to find approaches we can explain, challenge and build together.
I lead architecture across all engineering pillars for a healthcare platform operating in the UK, US and Canada, covering regulated patient data, prescribing and real payment flows.
My specialism is safe change in regulated systems: payments, e-prescribing, FHIR interoperability, multi-jurisdiction data residency and AI-assisted delivery. I favour durable architecture over heroics and written reasoning over authority.
Before healthcare I built white-label banking platforms for Lloyds Banking Group and RBS, ingested the entire Twitter firehose for trading firms, developed mobile trading apps at HSBC, and spent a decade in document and email management for the City’s leading law firms.
My current focus is delivery assurance for AI-assisted engineering: independent review, evidence against acceptance criteria and explicit release decisions. I architected an internal development harness at eMed and wrote ACCORD, an open-source CLI and Pi extension for contract-led delivery. Alongside that tooling, I am researching delivery risk and proposing risk-tiered controls for regulated systems; those controls are not yet adopted policy.
Current focus
Last reviewed . Status describes the work, not a promise of production readiness.
Research & proposed controls
Studying where defects enter delivery and proposing risk-tiered review and release controls. ACCORD is a working tool, not evidence that the organisational policy has been adopted.
Proposed architecture
Developing a data-cell and processing-hub model for regional expansion, with explicit storage, processing and operational trade-offs. The proposal remains open for collaboration and decision.
Delivered & in progress
Medley and the backend monorepo put the developer-experience strategy into practice. Work to let authorisation scale independently is in progress, not a completed production change.
Selected outcomes
How I work
Test architectural decisions against production behaviour, migration constraints and the experience of the people building and maintaining the system.
Record the options, evidence and trade-offs in design documents, RFCs and ADRs, so decisions can be challenged and revisited when circumstances change.
Start with established patterns and the team's experience. Make build-vs-buy decisions on evidence, and introduce something new when the problem warrants it.
Work with teams to turn commercial commitments into delivery options, making costs, risks and constraints explicit and labelling exploratory work honestly.
Leadership
I lead by example and listen before I speak. Before offering a view, I want to understand the problem and hear from the people closest to it.
When I do offer one, I show my working. I write down the options, the evidence and the trade-offs, in design documents, RFCs and ADRs, so a decision can be questioned, challenged and revisited long after the meeting has ended. A written case can be improved by anyone. A confident opinion mostly can’t.
"Standing on the shoulders of giants" captures how I think about engineering. We build on other people's ideas, tools and experience. My contribution is to connect that knowledge to the problem in front of us, give credit and help the team leave something others can build on.
Set up a cross-functional guild and authored reusable patterns with template code (Strangler Fig, CQRS, Event-Driven, Adapter, Facade), built into onboarding and design-review checklists.
Revived the company-wide guild as a community of practice: performance tuning, TDD workshops, shared-library reviews and a backlog any engineer could add to.
Cross-team sessions where one team walks another through its architecture. They break down silos and surface mismatched assumptions early.
One-to-ones, pairing and domain-design walk-throughs for engineers from junior to staff level, focused on architectural thinking as much as technique.
Career
Own technical strategy and architectural direction for a global healthcare platform. As architecture lead across all engineering pillars, set cross-cutting architecture, reference patterns and standards, and bridge commercial intent and technical delivery through B2B2C expansion, GLP-1 product lines, US and Canadian market entry and the Babylon legacy sunset.
Set architectural direction and standards for the engineering organisation while hands-on in the core platform.
Led in-house and offshore teams delivering white-label small-business SaaS for Lloyds Banking Group and RBS, combining architect and lead-engineer responsibilities.
Led engineering end to end for a real-time social and market data platform serving high-frequency and electronic trading firms.
Designed and engineered a BlackBerry FX messaging and trading application.
Led the iManage WorkSite mobile team, engineered the WorkSite FileShare prototype and led the team behind server-based email management for the WorkSite suite.
Built mobile workforce and legal email management solutions; the company’s assets were acquired by Interwoven.
Document, content, knowledge and email management and enterprise search for the financial and legal sectors, including Allen & Overy, Freshfields, Linklaters, Lovells and Slaughter and May.
Delivered document and email management solutions for legal and financial clients.
Toolbox