Your role, mapped to the systems you run.
AI takes on a role from the bottom up. The useful question isn’t whether it takes your job, but where each part of it lands. Pick the role closest to yours, then read down each system: what a tool already does, what’s yours to write down, and the judgement no system holds.
Most of a technology leader’s work is now AI-absorbable. The value concentrates in a handful of judgement calls, and in the assets still sitting in one or two heads.
The two left columns hold the fullest part of the job, the generic skills and your field’s published practice. They’re also what AI absorbs fastest, because nothing org-specific anchors them. Your value concentrates to the right. The layout is a sketch; the systems and layers are illustrative.
What only your people can answer.
No research can answer these, whatever the role. They’re the part of the job your organisation only knows while the right person is still in the building. Read them against the terracotta column above.
Where is your operating knowledge most concentrated in one or two people, and what happens if they leave?
What would tell you something has stopped working, and is that signal written anywhere, or only felt?
Which calls get made on judgement you've never written down, and couldn't hand over tomorrow?
Where are you quietly carrying risk that no system or dashboard would ever show?
This is built from public sources. Your version has real systems, real names, real gaps.
Which judgement actually sits in one head, what to write down before it leaves, and where it lands across your architecture. That map is built with you, and it’s the start of the work we do at Reframe Technologies.
Knowledge Audit
Find the terracotta across your real decisions, name who holds it, and get it written down before it leaves.
See the engagement →The Org Lens
One role is the start. The Org Lens reads the same map across every unit at once, with nothing averaged away.
Open the instrument →