Stephen Klahr · Independent practitioner resourceBusiness architecture / methods, models & judgment

Applied Business Architecture

Business Architecture, Made Practical.

Business architecture isn't a prescriptive discipline. Learning to put it to work still deserves a practical starting point.

New to business architecture? Start here.

Five short lessons. One case. Try the work yourself.

Start learning →

Free to use. No sign-up. No AI tool required.

A working point of view

Start with the question. Make the work useful.

Identify the smallest useful piece of work. Examine the relevant business relationships. Produce something that helps someone act.

There's no single sequence of activities, required set of artifacts, or universal method that works for every organization. And that's part of what makes it valuable. The discipline gives us ways to understand a business, but it leaves room for judgment about which questions to ask, which relationships to explore, and how much architecture is actually needed.

My approach is to start with the business, not the deliverable.

What is the organization trying to accomplish? What capabilities does it depend on? How does it deliver value? Who does the work, and what information do they need? Those four perspectives, capabilities, value streams, organization, and information, form the foundation of how I practice business architecture.

The real value comes from connecting them. A capability map by itself doesn't tell you where to invest. A value stream alone doesn't explain why a process is failing. But when you begin to understand how these pieces relate, you can ask better questions, expose dependencies, evaluate choices, and help an organization make more informed decisions.

That's the philosophy behind this site. I've brought together practical methods, worked examples, an interactive enterprise case study, and resources to help you learn the discipline and put it to work. Whether you're just getting started or refining an established practice, the goal is the same: understand the business well enough to help it make better decisions.

Keep within reach

A reference for the work.

Field Notes

Field Notes from practice.

A useful method can structure the work, but it cannot replace judgment about scope, evidence, ownership, politics, timing, or when to stop. Field Notes is where I write about those parts of the practice and the lessons that only become visible while doing the work.

Stephen Klahr · Senior Business Architect
Certified Business Architect®

Background & approach