myBusinessArchitectmyBusinessArchitectmyBusinessArchitectmyBusinessArchitectReference Models for Business Architecture
Every organisation has a language problem it doesn't know it has.
The strategy meeting where the same word means three different things to three different leaders. The initiative that reinvents the vocabulary a previous team built six months ago. The capability gap everyone can see but nobody can name. The student, the customer, the citizen who experiences a fragmented journey because the departments serving them have never agreed on what "integrated" means.
This is not a communication problem. It is an infrastructure problem. The organisation has never built a shared vocabulary for describing what it is, what it does, and what it must be capable of. Every conversation starts from scratch. Every handoff requires translation. Every decision is debated in private languages that sound like agreement but produce misalignment.
Reference models are the solution. Not another framework to learn. Not a methodology to follow. A common language: a structured, reusable vocabulary that gives everyone in the room the same picture of the organisation's business model, its capabilities, and how those capabilities must come together to produce the outcomes that matter.
This course teaches you to read that language. You will interpret a pre-populated Business Model Canvas and use it to diagnose a broken business model. You will navigate a capability hierarchy and identify the gaps between what the strategy requires and what the organisation can actually deliver. You will read a recipe card that reveals why individually adequate capabilities are producing a fragmented experience. And you will see what happens when an organisation that has this vocabulary faces a high-stakes decision under a sixty-day deadline: not scramble, but disciplined assessment in two weeks.
The course's case study is a polytechnic, so its example is a sector reference model built for universities and colleges: the HERM, the Higher Education Reference Models that CAUDIT maintains with UCISA, EUNIS and EDUCAUSE, with a business model canvas, a capability model and recipe cards. You don't need to work in higher education to learn from it: the skill is adapting and applying a sector's reference model, whichever sector you work in.
You will follow the same institution you met in COR-BA-100 through the next chapter of its story. The crisis has been navigated. The Design4 cycle has been learned. Now the question is: how do you make it repeatable? How do you transfer it from one team to the next, one initiative to the next, one leader to the next? The answer is the common language. Without it, every cycle starts from zero. With it, every cycle starts from shared understanding and moves directly to the questions that matter.
This is not a modelling course. You will not build reference models from scratch or learn formal notation. What you will gain is the ability to walk into any organisation and assess whether it has the shared vocabulary it needs to execute its strategy. If it doesn't, you will know what to look for, what questions to ask, and how to start. If it does, you will know how to evaluate whether it is working and where it needs to evolve.
You will not leave with a model. You will leave with a vocabulary that makes every model, every strategy conversation, and every governance decision sharper. The difference between forty-seven ideas on a whiteboard and an organisation that knows how to think.
See exactly where your organisation is paying the cost of missing shared vocabulary, and name it in terms leadership already feels.
Read any business model, capability hierarchy, or operational recipe card and extract the strategic insight without formal modelling training.
Evaluate a reference model against your own organisational context, and know when to consult it and when to make it your own: what to adopt, what to adapt, and what to leave behind.
Use the right reference model at each Design4 phase, from a sector theory of change in Discover to an operational pattern in Deliver, and bring its evidence to governance.
Know what it takes to build and sustain shared vocabulary over time, and what organisational conditions determine whether it takes hold.
Design a first reference model initiative scoped to deliver visible value before anyone is asked to commit to a new approach.
Practising business architects who keep rebuilding the same vocabulary for every initiative, and want a reusable one their organisation can share
Professionals moving into business architecture who have completed COR-BA-100 and want to make its discipline repeatable
Architects and planners in higher education who use the HERM, or are about to adopt it, and want to put it to work in strategy, capability and governance conversations
Your organisation has the strategic intent. It might even have the Design4 discipline. But watch what happens the next time a cross-functional team sits down to execute.
Someone says "capability" and means a system. Someone else means a skill. A third means a budget line. The meeting stalls while the room negotiates definitions that a previous team negotiated six months ago and that the next team will negotiate six months from now. Multiply that by every initiative, every governance cycle, every strategic pivot, and you begin to see the invisible tax.
Now multiply it by speed. The funding deadline that gives you sixty days. The merger that gives you six months. The regulatory change that gives you none. Organisations that lack a shared vocabulary cannot respond at the speed the environment demands, because they spend their response time rebuilding the language they need to respond with.
The organisations that move fastest are not the ones with the best strategies. They are the ones that have invested in the shared infrastructure that makes strategy executable at speed: a common vocabulary for the business model, for capabilities, for the outcomes those capabilities must produce together. That infrastructure is invisible when it works. Its absence is obvious when it doesn't.
Reference models are that infrastructure. They are not glamorous. They do not appear in keynote presentations or analyst reports. But they are the reason one institution can assess a new opportunity in two weeks while another is still arguing about definitions after two months.
The common language is not a luxury for mature organisations. It is the precondition for everything else working. And the cost of not having it is compounding every time the environment moves faster than your vocabulary can keep up.
Building the Common Language is the second course in the core business architecture series. It follows Closing the Strategy-Execution Gap (COR-BA-100) and leads into Communicating Business Architecture (COR-BA-102) and Shaping What Gets Built (COR-BA-103); Architecture That Travels (ADV-BA-401, in development) adds formal modelling, including the ArchiMate expression of the HERM.