The PDP 3-Layer Framework

People, Data, Process

AI transformation has a sequence, and the sequence is invariant. Ready your people first. Then open the data. Then let the process change. Skip a layer, or run them out of order, and you get pilots that never leave the demo stage, or a single small change in an organization that should be transforming.

The benefit of the PDP 3-Layer Framework is it creates a flywheel of innovation that can have a compounding effect on an organization. With empowered and skilled people and access to data, the organization can enter a state where AI update and improvement becomes innate to the organization.

01 · People

Find your champions. Upskill your experts.

Every organization already has people pulling AI toward them — the ones experimenting on their own before anyone asked. Those are your champions, and the first job is to find them in every function. These are not the most technical people; they are ones with curiosity and vision who are willing to try and fail and learn.

The second job is upskilling. Take the people who know how the business actually works, your best subject-matter experts, and teach them enough on AI and infrastructure technology to make a difference. This is not fast but it is effective. Expect the process to take 3–9 months; it is well worth the investment.

The reverse, hiring AI specialists and hoping they absorb twenty years of domain knowledge, mostly doesn’t. An SME who understands AI as an acceleration tool can see exactly where it belongs in their domain, because they already know where the friction is.

The moves
  • Find the champions in every function — the pull, not the push
  • Upskill SMEs on AI directly: your domain experts become your AI evangelists, supported by a quality technical team
  • Put them in the room with a real mandate to reinvent their own domain
02 · Data

Governed access, not locked doors

Champions without data produce demos. The second layer is getting real data into the hands of the people who will actually use it — inside a governance framework, not around one.

Governance is not red tape. Done right, it’s the mechanism that makes access possible: it answers the security, privacy, and compliance questions once, so every team doesn’t have to relitigate for every project.

The goal is scoped access paths that are permissioned, auditable, and fast — because a governance process that takes six months to say yes is a no. Worse, it disheartens your evangelists, and at the very worst it pushes the very data you are looking to respect into unauthorized channels.

The moves
  • Map the data your champions actually need, start from the use case, not the warehouse
  • Build governance-compliant access paths: permissioned and fast
  • Put the data in the hands of the people who will use it
03 · Process

Let the process change

Here’s the payoff of doing the first two layers in order: upskilled people with real data access start redefining their own workflows. Nobody has to impose a new process from above. The people living and running the process rebuild it, because they can now see a better version of the future.

The organization’s job at this layer is mostly to get out of the way: be flexible and anti-bureaucratic enough to let the process actually change. If every workflow adjustment needs a steering committee, you’ll automate the old process instead of discovering the new one — and, face it, automating a bad process just produces bad outcomes faster.

The moves
  • Give teams room to change the process, not just automate the existing one
  • Anti-bureaucratic defaults: short approval loops, decisions close to the work
  • Let enablement build up to full process redefinition, collaborative, not imposed
Why the order is invariant

Each layer only works on top of the one before it

Data access without upskilled people is a lake nobody swims in. Process redesign without data is guesswork. And starting with tools — the most common failure mode — is starting at a layer that isn’t even in the stack. Tools show up naturally once people, data, and process are moving; bought first, they become shelfware with a login page.

People → Data → Process. Every AI transformation I’ve seen work ran this sequence, whether or not anyone named it.

Running PDP

This is the framework I teach and run: identify the champions, upskill the experts, open governed data access, and hold the organization flexible enough for the process to change. If you want to talk through what that looks like for your company or your portfolio, see Work with me.

Join my email list

Occasional notes on AI, strategy, and building things that work. No spam.