Field Notes
Essays drawn from applied business architecture work, organized by the kind of decision, practice problem, or professional challenge they can help you address.
Build the practice
Establish the discipline, choose a useful starting point, and grow credibility through real decisions.
Business architecture and business analysis overlap, but they are not interchangeable. One enables a particular change; the other creates and governs reusable enterprise knowledge that shapes many changes.
Practical guidance for establishing a small business architecture practice, building an initial capability, value stream, organization, and information baseline, and using it to support real business decisions.
An operations background is not a detour from architecture; it can supply the consequences, constraints, and institutional realism that abstract models lack.
A small, linked architecture package can outperform a comprehensive repository when it is designed around a real decision.
The discipline becomes difficult at the boundaries: choosing the right abstraction, linking domains, and making architecture matter to a decision.
Move strategy into action
Translate intent into choices, boundaries, operating changes, and deliverable increments.
Alfred D. Chandler Jr.'s history of the managerial enterprise is nearly half a century old. Read critically, it still clarifies the central work of business architecture: coordinating capabilities, value streams, information, decisions, and resources across enterprise boundaries.
A practical business architecture approach to the choices, boundaries, decision rights, capacity, and transition required to make strategy operational.
What business architects should do when timelines stall, sponsorship weakens, execution never arrives, or business architecture is positioned only as the front door to a larger architecture pipeline.
How to limit scope, avoid gold plating, and deliver a narrow but complete first release tied to measurable business value.
Strengthen the architecture
Improve the structures, information, governance, and platforms that support architecture work.
How business architects can govern an unruly business object model, preserve canonical business meaning, model lifecycles and states, and connect business objects to automation without collapsing business architecture into data or solution design.
Selecting an enterprise architecture platform for business architecture requires testing how well the tool supports strategy, concepts, scenarios, governance, and the daily operating model of the BA practice.
Lead the work
Use judgment, facilitation, stewardship, and influence when formal authority is limited.
Business architects often lead without formal authority. Servant leadership offers a useful model, provided service is understood as stewardship of enterprise outcomes rather than accommodation of every stakeholder request.
Stakeholder engagement is not an accessory to business architecture. Observation, meeting preparation, facilitation, humor, and the ability to read a room directly affect the quality of the architecture we produce.