We've written before about the six AI adoption personas that show up in every organization rolling out AI. The enthusiast who wants to move faster than the organization can handle. The skeptic who needs data before committing. The employee who's quietly worried about their job.
That framework has been one of the most useful things we've built at Gadoci Consulting. We use it in readiness assessments, in training design, in proposals, and in conversations with executives who are trying to figure out why their AI rollout is stalling despite having the right tools in place.
But it lived in too many places. An article on our website. A slide in a pitch deck. A section of our readiness assessment methodology. Each version was slightly different, and none of them were available at the moment our team actually needed them: when they were writing, building, or preparing for a client conversation.
So we did something about it. We turned the entire persona framework into a skill inside Claude, the AI tool our team uses every day.
What that actually means
A skill, in this context, is a structured set of knowledge and instructions that Claude can pull into any conversation when it's relevant. When someone on our team is drafting a proposal and mentions they're pitching to a CFO, Claude automatically has access to our full executive buyer persona for that role, including what keeps that CFO up at night and how Gadoci's approach specifically addresses their concerns. When someone is writing an article and wants to check whether the content would resonate with a skeptical reader, the adoption personas are right there.
The skill doesn't just store the personas. It knows how to apply them. It can test content against specific personas, suggest which executive concerns a proposal should address, and flag when a piece of writing might land well with one audience but alienate another.
Two persona sets, one framework
The skill actually contains two distinct sets of personas that serve different purposes.
The first set is our seven AI Adoption Personas. These are the employee archetypes we encounter inside every client organization: the early adopter who's already experimenting, the analytical mind who needs proof before buying in, the capable professional who fears displacement, the ethics-first thinker, the pragmatic skeptic, the willing observer who just needs a starting point, and the process loyalist who values what already works. Each one represents a real attitude toward AI that requires a different message, a different onramp, and a different kind of support.
The second set is our seven Executive Buyer Personas. These are the C-suite and senior leaders we sell to and work with: the CEO under board pressure to show results, the CFO who needs ROI math before dollars move, the CTO balancing enablement with security, the COO who only cares about what works in real workflows, the CHRO trying to manage the human side of transformation, the General Counsel focused on regulatory exposure, and the Chief AI Officer who needs early wins to build internal credibility. Each one defines success differently and has a different relationship with AI.
Together, these two sets give our team a complete picture of every audience we need to reach. The leaders who buy and the people who adopt.
Why we built it this way
The obvious approach would have been to put this in a Google Doc or a Notion page and call it done. We've tried that. The problem is that reference documents only help if someone remembers to open them at the right moment. And in the middle of writing a proposal at 11pm or preparing for a client call in the morning, nobody is stopping to search for the persona guide.
Building it as a skill means it shows up when it's needed without anyone having to go looking for it. It's woven into the workflow rather than sitting next to it. That's a meaningful difference when your goal is consistency across a growing team.
It also means the framework stays canonical. There's one version, and everyone on the team gets the same one. No more drift between the version in the slide deck and the version in the article and the version someone remembers from a conversation three months ago.
What this looks like in practice
Here are a few ways our team is already using it.
When writing articles or thought leadership, we test drafts against specific personas. Does this piece address the concerns a skeptic would have? Would the CHRO find this relevant to their upskilling mandate? Would a traditionalist feel talked down to? Checking content against real audience archetypes catches blind spots that a general review misses.
When building proposals and sales decks, the executive personas shape the narrative. A proposal for a CEO emphasizes de-risked progress and board-ready results. The same engagement pitched to a CFO leads with ROI math and outcome-based pricing. The underlying services are the same. The framing changes based on who's in the room.
When designing training programs, the adoption personas determine the structure. The early adopter needs advanced content and leadership opportunities. The willing observer needs a clear, low-friction starting point. The worried professional needs concrete examples of how AI enhances their role rather than replacing it. One curriculum doesn't fit all seven.
The broader point
This isn't really an article about personas, and it's not really an article about AI skills. It's about a pattern we think more organizations should adopt: taking the institutional knowledge that lives in your team's heads and scattered documents and encoding it into the tools your team actually uses.
Every consulting firm has frameworks. Every sales team has buyer profiles. Every marketing team has audience segments. Most of that knowledge is underused because it's not accessible at the moment of work. Building it into AI tools changes that equation. The knowledge shows up when it's relevant, stays consistent across the team, and gets applied rather than forgotten.
We started with personas because they're foundational to how we think about every engagement. But the approach applies to anything your team needs to remember and apply consistently: brand guidelines, methodology, pricing philosophy, engagement models.
The question isn't whether your team has valuable frameworks. It's whether those frameworks are available at the moment they'd actually make a difference.