Chapter 2: What Reference Models Are (and Are Not)

In Chapter 1, you learned why organisations need a common language. You saw the reinvention tax, the Chasm of Miscommunication, and the six objectives that reference models serve. You understand the problem.

Now we need precision. "Reference model" is a term that gets used loosely. Consultants call their frameworks reference models. Vendors call their product templates reference models. Departments call their internal process documents reference models. Some of these actually are reference models. Many are not. If we are going to build a course around this concept, we need to draw clear lines.

At Lakeshore, the term had just arrived with someone who used it precisely. Fiona's first presentation to the leadership team was twenty minutes on the HERM, and her opening slide had three words on it: model, reference model, reference architecture. "If we use these loosely," she said, "we'll spend next year arguing about what we meant."

This chapter does three things. First, it defines the taxonomy: the difference between a model, a reference model, and a reference architecture. Second, it explains the architectural strategies that make reference models useful for managing complexity. Third, it introduces the HERM suite in structural detail, so you have a concrete example to carry through the rest of the course.

By the end of this chapter, you will be able to look at any organisational artifact and say with confidence: "That is a reference model" or "That is not a reference model, and here is why."