01 — REFRAME
Ask a better question
The brief is rarely the problem. Most failed programs start as a precise answer to the wrong constraint. I test the question before I design the system.
I start by asking whether we have the right problem. Then I design the smallest system that can survive scrutiny — from engineering, from examiners, and from the P&L.
Twenty-five years in regulated financial platforms — banks, payments, credit, insurance, brokerage. Two U.S. patents that became commercial products. Former Chief Architect at Synovus. The work is less about adding technology than about making the existing system tell a consistent story.
I stay with a domain until the constraints are specific: the policy, the data lineage, the failure mode, the cost of being wrong. Then I connect the rooms that do not usually share a map — risk, product, engineering, legal — so the architecture, the operating model, and the audit trail say the same thing.
These are the tests I apply to my own recommendations. If a design fails one of them, it is not ready.
The brief is rarely the problem. Most failed programs start as a precise answer to the wrong constraint. I test the question before I design the system.
Knowing the stack is not the same as knowing why a control exists, who depends on it, and what breaks when it moves. Surface knowledge does not survive an incident or an exam.
If a board member, an engineer, and an examiner cannot each recognize the same design, it is not finished. Complicated is a smell. Complex, made simple enough to run, is the job.
Some recommendations are unpopular. I will still name the debt, the risk, or the assumption that does not hold. Consensus is not a control, and postponing the truth does not reduce the cost.
Credit, payments, identity, AI, and policy do not live in separate buildings. The useful architecture is the one that makes those maps compatible without pretending they are the same.
Enterprise & Solution Architecture, Reference Architecture, Architecture Governance, Target State Definition, Technology Roadmaps
Hybrid Cloud Strategy, AWS & Azure, Cloud-Native Architecture, Terraform, Multi-Cloud, DevSecOps & CI/CD, Infrastructure-as-Code
Core Banking, Payment Processing, Card Networks, Insurance Integration, Brokerage & Securities, Credit Decisioning, Regulatory Compliance
AI/ML Platforms, Human-in-the-Loop Workflows, LlamaIndex, Claude Code, Gemini Multimodal, Rules Engine Architecture (regtech), Predictive Analytics
Microservices, API Platform Design, Event-Driven Architecture, Technical Debt Reduction, AI/ML Platform Strategy, Zero Trust Architecture
Zero Trust Architecture, IAM, OAuth 2.0, mTLS, PCI DSS, SOC2 Type II, Regulatory Traceability, Audit-Ready Systems
Work that had to hold up under auditors, customers, and a P&L — not just a slide.
From early-stage advisory to enterprise-scale transformation programs. All engagements are customized.
I typically respond within 24 hours. Conversations stay confidential.