Skip to main content

Resume

Corinna Cohn

Enterprise Architect | Integration & Modernization Strategy

linkedin.com/in/corinna-cohn-83026a24

Enterprise Architect with deep insurance-domain experience governing architecture standards, shaping business-capability strategy, and directing integration and modernization programs across a delivery organization of 20 teams and roughly 100 managed solutions. Recognized for identifying governance gaps and building the structures needed to fill them without waiting for top-down sponsorship.

How I Work

The toolkit is standard EA fare: TOGAF and Kotusev frameworks, ArchiMate modeling in ADOIT, business capability and domain modeling, event-driven architecture and API strategy, and lately AI-assisted analysis. The through-line is integration governance: building the standards, committees, and roadmaps that keep a middleware stack coherent while it modernizes.

Three Stories

Governance, built from scratch. No structured EA practice existed, and integration compliance had no oversight. Established the organization's first EA framework as its product owner, a repository of architecture decisions, standards, and patterns grounded in Kotusev and TOGAF, then founded the Integration Governance Committee and designed its charter and compliance monitoring. The committee's baseline work surfaced missing API contracts and informed platform rationalization decisions.

Modernizing the messaging backbone. The legacy message broker couldn't support the organization's event-driven, cloud-native direction. Directed a cross-functional evaluation with parallel assessment tracks, producing a consensus recommendation for Solace PubSub+. Then led the acquisition, vendor and internal developer training, and publication of the event topic naming and metadata standards teams needed to build on it.

The 90% problem. Mainframe searches and record retrievals were consuming expensive CPU and slowing customer-facing response times. Delivered a materialized-view system that cut mainframe CPU utilization for those operations by 90% and response times by 95%, improving customer experience while easing infrastructure cost pressure.

Elsewhere on the Record

Business capability and domain models adopted into strategic planning and distributed to business-unit leadership. AI-assisted documentation of legacy COBOL systems that surfaced logic gaps and became a repeatable discovery methodology. Developer training in architecture diagramming and AI-assisted development for roughly 40 developers, with a 100% post-session recommendation rate.

Publications & Speaking

Manning Books technical reviewer; conference speaker (CamundaCon).

Education

BS Economics, University of Nevada, Reno

Comments

Post a Comment

Popular posts from this blog

I Built a Search Engine for My Unread Books (and You Can Too)

What do you do with 100 technical books you'll never finish reading? I built an MCP. I've been collecting high-quality technical books for years, mostly from Humble Bundle sales (IYKYK). Some I've read. Some I keep meaning to. But they're all sitting right there on my hard drive, over 100 of them, so the question became: how do I get more value out of what I already own? Keyword search doesn't cut it. If I want to answer "how do I justify decoupling to a skeptical executive?", the relevant passages say things like "selling architecture" or "business risk." You'd have to already know the answer to find it. And there was a second motivation: I'd been circling RAG at a theoretical distance for a while. I wanted to understand the patterns firsthand, not from diagrams. So I built a semantic search engine over my own library, exposed as an MCP server that Claude can query. Everything runs locally: embedding, vector storage, retrieval....
Post a Comment
Read more

How I Made the Book Library Search Better (and Proved It!)

A sequel to the architecture guide. Part 1 explained how the search engine was built. This one explains how we found out whether it was any good, tried four ideas to improve it, and shipped the two that actually worked. If you read Part 1, you know the setup: I'd been collecting technical books for years — mostly Humble Bundle hauls — and had over 100 of them sitting on a hard drive, mostly unread. So I built a semantic search engine over the whole library, exposed as an MCP server Claude could query. Ask a question, get back real passages from Neal Ford or Vaughn Vernon, instead of an AI's vague recollection of them. By the end of Part 1, it worked. But "it worked" and "it's good" are different claims, and I'd only ever checked the first one. This post is the story of taking the second one seriously. The whole thing follows from one sentence, taken literally: You cannot improve what you cannot measure. The question that started this Whe...
Post a Comment
Read more