The Heirloom Method
Harvest
Understand what already exists.
Before anything is added, we gather what is already working: the practices, the relationships, the records, the knowledge people carry in their heads. Most organisations know more than their documentation admits.
Examine
Audit the systems and the needs.
Where does the time actually go? Where is information duplicated, lost, or exposed? What is fragile because exactly one person knows how it works?
Imagine
Design better possibilities.
Now — and only now — we ask what a better version looks like. Several options, with honest effort and risk attached to each, including the option of changing nothing.
Root
Ground every decision in people, values, culture and governance.
Root is not a stage you pass through. It runs the length of the work: who decides, what must stay human, what may never leave the building, and whose knowledge this is. We list it fourth because it spells the word, but treating governance as step four is how organisations end up bolting ethics onto a finished system.
Layer
Add appropriate technology.
Technology goes on last and goes on thin. The right amount is the least that solves the problem, chosen for how easily you could leave it.
Operationalize
Make it actually work.
In production, with real data, run by the people who will run it — not demonstrated in a meeting and abandoned.
Own
Transfer knowledge, control and documentation.
Accounts in your name. Documentation in your hands. Training for your staff. If the system stops working when we leave, we did the job wrong.
Multiply
Expand capability.
What you learned on the first workflow makes the second one cheaper, and the third one yours entirely.
An honest note about the acronym
HEIRLOOM needs two words beginning with O to spell correctly, which is a mild strain, and Root sits fourth because of the letters rather than because governance belongs after design. It does not. Most responsible innovation frameworks place values and governance grounding before design, and so do we in practice. We keep the acronym because it is a useful teaching scaffold, and we flag the seam rather than hoping nobody notices it.
Inherit, interpret, build, bequeath
Inherit
What do I already know and already have?
Every tool starts from your situation, not a blank slate.
Interpret
What does this technology actually mean for me?
Capability and limitation, stated together, every time.
Build
What can I make with it?
Something you can carry out of here and use this week.
Bequeath
How does this stay useful beyond me?
Documentation, ownership and transfer are part of the deliverable.