Stephen Klahr

From operations into architecture

I did not enter business architecture through a conventional enterprise-architecture career path. I came out of freight operations, where architecture abstractions eventually become dispatch choices, labor plans, customer commitments, safety exposure, cost, service, and work performed by real people.

I learned the discipline in practice, helping establish a business architecture capability and supporting the separation of a Fortune 500 company.

That experience made me sympathetic to people who understand the definitions but still cannot see how the pieces fit together under delivery pressure. Business architecture is conceptually demanding because its objects are interdependent, its boundaries overlap with several mature disciplines, and its value appears only when the work changes an organizational decision.

How I approach business architecture

Start with the business and the decision it needs to make. Business architecture gives us a way to understand an enterprise, but it does not prescribe one sequence of activities or a required stack of deliverables. The work calls for judgment about what to examine, how much detail is needed, and when there is enough understanding to move forward.

I start with the smallest useful piece of architecture: enough connected understanding to help someone make a better decision. That might mean tracing a customer problem through a few capabilities, the value stream they enable, the people accountable, and the information they depend on. The scope should be small enough to use and broad enough to expose the dependencies that could change the answer.

Capabilities, value streams, organization, and information are the foundation of my approach. Their value comes from the relationships between them. I build outward as the questions demand, preserving what we learn so each engagement contributes to a more coherent picture of the business.

Small does not mean casual. Separate evidence from inference, make assumptions visible, test alternatives, and be clear about who owns the decision. Stop adding detail when it no longer changes scope, priority, accountability, risk, or direction. Return to the work when new evidence or a new decision warrants it.

Why this site exists

StephenKlahr.com is about Applied Business Architecture: reducing the distance between understanding the discipline and being able to use it. The site brings the concepts, examples, methods, and judgment together so you can see how the work fits.

Learn BA offers five short lessons built around Northstar Equipment Services, an entirely fictional enterprise created for teaching and practice. The Northstar Atlas lets you explore its architecture interactively, follow the relationships, and see how they inform business decisions.

Methods & Templates is the practical method library, developed from the Business Architecture Cookbook. Find a method for the task at hand, see a worked example, and download a reusable template. Field Notes explores the judgment, governance, incentives, and institutional realities that shape the work in practice.

SCALE: AI-Assisted Business Architecture helps you work through a real business question in your chosen AI environment. Bring the question, copy a complete starter, and supply the relevant evidence there. Start with the smallest useful result, check its reasoning, and correct what it gets wrong. The lessons, methods, and Northstar case also work without AI.

You'll also find a curated External Resource Library, an independent CBA Study Guide, and a contact page for questions about the work. The learning materials are free to use, require no sign-up, and are independent of any software vendor.