Most process and architecture programs follow a familiar script. The tool gets treated as drawing software, three people end up using it, the Architecture Review Board earns the nickname “Committee of No,” and eighteen months later the budget is pulled. Other organizations treat architecture as a capability investment: business-led, with a clear strategy, governance defined upfront, and adoption planned from day one.
In this session, Roland shows what separates the two. Drawing on 30 years of consulting experience, including leading architecture groups, and six years as KPMG’s global representative in the TOGAF forum, he lays out a practical framework built on three areas every successful program needs: Content, Governance, and Adoption. Most programs have the first, some have the second, and almost none plan the third adequately.
What you’ll learn:
- The three warning signs that a program is heading for failure
- Four work areas for implementation (strategy, governance, technology, and content/adoption) and what failing programs skip in each
- Three questions to answer before touching the tool, and three things to define before go-live
- Why the meta model is the one technology decision to get right before you sign a contract
- Two sequencing mistakes in nearly every failing program, and how to avoid them
- A three-question diagnostic to find out which circle (Content, Governance, or Adoption) your program is weakest in
Who should attend: Process and architecture leads, program sponsors, and BPM/EA practitioners who are starting a program or trying to rescue one.
