TPDK Framework
Technology, People, Decisions, Knowledge — four interdependent pillars that determine an organisation’s capacity for transformation. Original IP bridging NLP with systems thinking.
“Most organisations try to transform through technology alone. But technology without the right people, decision structures, and knowledge architecture produces expensive failure. Transformation is a four-variable equation.”
The structure underneath
The Technology pillar assesses the organisation’s technical infrastructure, tool adoption, and digital maturity — not just what technology exists, but how effectively it’s integrated into actual workflows. Many organisations have sophisticated tools used at 20% of their capability because the other three pillars were neglected.
The People pillar examines human capability, cognitive patterns, communication structures, and the behavioural patterns that either enable or resist change. This is where NLP meets organisational development: understanding how the people in the system actually process information, make decisions, and respond to change — not how the org chart says they should.
The Decisions pillar maps the actual decision-making architecture: who decides what, through what process, with what information, and with what authority. In most organisations, the formal decision structure and the real decision structure are different. TPDK makes the real one visible.
The Knowledge pillar evaluates how organisational knowledge is created, stored, shared, and applied. It distinguishes between explicit knowledge (documented, searchable) and tacit knowledge (embodied in people, transferred through proximity and practice). When key people leave, the Knowledge pillar reveals what the organisation actually loses.
AI readiness for organisations: a worked example
The short version of how I use TPDK: organisations implement AI successfully when they fix the human operating system first. The tool is rarely the constraint. The following illustration shows why.
Imagine a mid-sized services firm that rolls out an AI assistant to draft client proposals. The licences are bought, the integration with the document system works, and a training session is run. Three months later, usage is low and proposals take as long as before. A technology-only review would recommend more training or a different product. A TPDK review looks across all four pillars.
| Pillar | What the review finds | Status |
|---|---|---|
| Technology | The tool works and is integrated with existing templates. | Ready |
| People | Staff are curious but unsure whether using AI will be seen as cutting corners. | Partly ready |
| Decisions | Nobody has decided who approves an AI-drafted proposal, or what quality bar it must meet. Drafts wait for a partner who reviews everything by hand. | Constraint |
| Knowledge | The firm’s best proposals, pricing logic and client history live in three senior people’s heads and old email threads, so the assistant drafts from generic material. | Constraint |
The stall is in Decisions and Knowledge, not Technology. The useful actions follow from that: agree a sign-off rule for AI-assisted drafts, name who owns it, and spend a few weeks turning the senior people’s tacit proposal knowledge into examples and criteria the tool and the team can both use. Only then does further training make sense. Notice the sequence: none of these actions involves changing the tool, and none of them would have been found by measuring licence usage alone. Usage was the symptom; an unmade decision and inaccessible knowledge were the cause. The People pillar improves almost as a side effect, because a clear decision rule answers the question staff were worried about.
Organisational readiness assessment: diagnostic questions by pillar
These questions are a quick first pass for any digital transformation or AI initiative. Ask them of several people at different levels; the gaps between their answers are often more informative than the answers themselves. The free organisational readiness assessment covers the same ground in more depth.
Technology
- Which of the tools we already pay for are used for their main purpose every week?
- Where do people copy data by hand between systems?
- If this new tool were switched off tomorrow, which workflow would actually stop?
People
- What do people believe will happen to them if this change succeeds?
- Who is trusted informally, and have they been involved?
- When the last change was introduced, what did people do in the first fortnight, as opposed to what they said?
Decisions
- Who can say yes to this change, and who can quietly stop it?
- Which decisions currently wait for one person?
- What information is used to make the decision, and where does it come from?
Knowledge
- If our most experienced person left next month, what would we be unable to do?
- Where is the current way of doing this written down, and is it accurate?
- How does a new joiner learn the real process?
How TPDK relates to NLP
NLP lives mainly in the People pillar, with a strong reach into Decisions. The same distinctions used with individuals scale to teams. Values explain why a change that looks rational meets resistance: it may threaten something the team ranks higher than efficiency. Meta programs explain why the same announcement lands as opportunity for some people and threat for others. Decision patterns show where approvals stall, and strategy elicitation is a practical way to capture tacit knowledge from experienced staff before it is lost.
The limits are worth stating. TPDK is a diagnostic structure, not a statistical model, and it does not score an organisation against an industry benchmark. Its value is in asking the right questions in the right order, and in stopping investment in the pillar that is already ready. If you want help applying it to a specific initiative, see work with me.
Find your own pattern: Organisational Readiness (TPDK)
Most change programmes fail on the pillar nobody measured. This shows which of Technology, People, Decisions or Knowledge will limit yours.
Where it applies
- Organisational readiness assessment — diagnosing which pillar is the actual constraint before investing in change
- Digital transformation — ensuring people and decision structures evolve alongside technology adoption
- Knowledge management — building systems that capture and transfer institutional knowledge before it walks out the door
- Strategic planning — evaluating initiatives against all four pillars to predict implementation success
Related frameworks
Continue the series
TPDK Framework: questions people ask
What is an organisational readiness assessment?
An organisational readiness assessment checks whether an organisation can absorb a planned change before money and time are committed. A useful one looks beyond technology to people, decision-making and knowledge, because those are where most initiatives stall. The TPDK framework structures the assessment across those four pillars and identifies which is the current constraint.
How do you assess digital transformation readiness?
Start by naming the specific change and the workflow it affects. Then ask, for each of Technology, People, Decisions and Knowledge, what must be true for the change to work and whether it is true today. Interview people at several levels and compare answers. The free organisational readiness assessment gives a structured starting point.
What makes an organisation ready for AI?
Working technology is necessary but not sufficient. An organisation is ready for AI when people understand what the tool means for their role, someone has decided how AI-assisted work is approved, and the knowledge the tool needs (examples, rules, context) is written down rather than held in a few people’s heads. Gaps in decisions and knowledge are the most common blockers.
Is TPDK a validated assessment?
No. TPDK is an original practitioner framework, not a psychometrically validated instrument, and it does not produce benchmark scores. It is designed to structure diagnostic conversations and focus effort on the real constraint. Its usefulness comes from the quality of the questions and the honesty of the answers, so it works best alongside direct observation of how work is actually done.
Related tools
View details