Ted Tschopp

Technology Architect and Enterprise Architect in Los Angeles, California

Read my blog

I'm Ted Tschopp, a Senior Enterprise Architect based in Los Angeles. I spend most of my time on enterprise-scale digital automation and the practical realities of adopting AI in large organizations: platform shape, guardrails, operating models, and the work between the work.

I like the edge where strategy meets execution and where ambitious technology has to survive contact with reality. Some of the things I have worked on were once science fiction. Now they are platform problems, governance problems, and people problems, which is to say: the interesting part.

"Architecture is the unnecessary design elements of a structure that make it livable and sustainable." -- Oscar Tschopp, my dad, who was an architect that built and designed buildings. I like to think of enterprise architecture as the unnecessary design elements of a system that make it useable, sustainable, and welcoming for the users and the builders.

Note: Unless explicitly stated otherwise, everything here is personal work and opinion, not speaking for my employer.

What I Keep Coming Back To

  • Enterprise AI adoption: governance, risk, measurement, and how teams actually ship value
  • Agentic systems: orchestration, observability, controls, and workflow redesign
  • Architecture that survives contact with reality: platform thinking, integration patterns, and constraints that matter in the real world
  • Storytelling: using narrative and metaphor to make complex systems understandable
  • Creative tooling: TTRPG generators, SRDs, and hobby-grade experiments that occasionally become real tools

Writing

Most of the longer-form writing lives on TedT.org. Good entry points:

A Few Things About Me

  • Location: Los Angeles
  • Experience: 30+ years in IT, still learning
  • Current learning: Rust, product strategy, and better DX tooling
  • Fun fact: Founder of TheOneRing.com, featured in Wired and the LA Times

How I Work

  • Be explicit about the outcome and the constraints.
  • Prefer small PRs with tight feedback loops.
  • If we disagree, write down the assumptions and test them.
  • Strong ideas should survive pressure.
  • Work
    • Southern California Edison
  • Education
    • Computer Science
    • Systems Engineering