Playbook & Methodology

As your business architecture team grows and as demand for your business architecture services increases, at some point you may want to seriously consider creating a business architecture playbook. While many teams are not even aware of what a business architecture playbook is, they often experience the challenges that can occur when one is lacking as the discipline scales within their organization.

This installment will break down the what, the why, and the how of building a business architecture playbook, in the usual StraightTalk style.

As a newer role on the scene, working in a business world ubiquitous with design, digital, agile and other emerging concepts, the way we show up as business architects matters a lot. Because everything we do and say demonstrates to others what business architecture really is, and we need to be relevant and distinguish ourselves. The success of a business architect then is not just in what we know or what we do — but in our Ways of Working (WOWs), which this installment of StraightTalk explores.

StraightTalk focuses on business architecture, but we know that our discipline is part of a larger entity — the enterprise architecture (EA) umbrella. As a result, a strong partnership among every one of the architecture disciplines is critical for all of our success — and for the success of our organizations. This installment highlights the notable progress made so far by the Business Architecture Workstream, within the Open Group Architecture Forum, to align the TOGAF® enterprise architecture framework with the BIZBOK® Guide.