// resources

Notes on product, data, and regulatory tech.

Frameworks and lessons from leading product teams on complex, data-heavy systems.

15 articles · all topics

How to Write a Business Case for Software Modernization

Funding follows a clear case, not a good idea. How to frame costs, recurring savings, and risk so leadership can say yes.

When a team needs a new investigative tool, the first question is rarely technical. The framework I use to weigh building, buying, or extending.

Modernizing a system people use every day is a product problem first. A phased approach to retiring legacy software without disrupting the business.

The unglamorous document that makes or breaks every integration. What to capture, how to review it, and how to keep it current.

Alerts, investigations, escalations, audit trails. The capabilities that matter most when compliance teams evaluate case management software.

Less time drawing roadmaps, more time on portfolio decisions, funding conversations, and unblocking teams. An honest look at the role.

Automated comparisons, reconciliation checks, and checksums. Practical ways to prove your data arrived intact.

A step-by-step plan for moving data off a legacy platform, from profiling and mapping through validation and cutover.

Separating useful AI, like triage, summarization, and pattern detection, from hype in regulated investigation workflows.

Intake channels, routing, deadlines, and reporting. A checklist for scoping a complaint management system in financial services.

// contact

Send a note, or suggest a topic you'd like me to write about next.