Prompt Playbook: Blueprint Prompts PART 4
I'm standing in front of 150 professionals at a major tech company, about to kick off an AI workshop. The room's a mix of excitement and... is that fear I see? Absolutely.
Because here's the thing - implementing AI isn't just about the technology. It's about the people.
I'll never forget one participant's comment: "I thought you were here to tell us how to replace ourselves with AI"
By the end of the day that skeptical gentleman had changed his tune. More on that later.
That's what today's all about - turning AI from a threat into a superpower for your entire team.
Let’s get started
Grassroots Adoption
Summary
Grassroots Adoption
Why top-down AI implementation often fails
Getting your team excited, not worried
The systematic approach to team AI adoption
Building a sustainable prompt library
Creating a culture of AI innovation
Without buy-in it’s all for nowt
Based on the last Parts of this Playbook you are becoming a prompting master. Feels great eh?
To truly achieve leverage though we shouldn’t be the only one using these tools. We need our team on board.
This is easier said than done.
Before you even think about prompts you need to address the elephant in the room: fear.
Your team might be wondering if AI is going to make them redundant. It's a natural (and valid) concern, and ignoring it won't make it go away!
First Things First: Getting Buy-In
Instead, flip the script. Show them how AI can free them from the mundane parts of their job. I always start with a simple exercise: ask them to list their least favourite tasks. You know, the ones that make them want to bang their head against the wall.
Frame AI as a way to get rid of these ball-ache tasks. They won’t necessarily believe you yet but we’ll get there!
The Power of Paid Accounts
Second, get your team proper AI accounts. Yes, I'm talking about paid accounts. It's the best $20 per month per staff member you'll ever spend.
Why? Because free accounts mean you aren’t helping AI make its best impression. Paid accounts give you access to better models and fewer frustrating limitations.
Also: security and data protection. Paid accounts mean that your company data isn’t going to the AI companies for training their models - you can secure your data. Right now ~70-80% of work is being done on free/personal accounts, meaning all of that data is leaving the company:
Basic Training: The RISEN™ Framework
Third, once you've got the tools sorted, it's time for some basic prompt engineering training. Basically get them training on the RISEN™ framework or something similar.
But here's the key: don't overwhelm them. Start small, let them experiment, and watch the magic happen.
This is where it gets interesting. Once your team starts using AI, they'll naturally gravitate towards certain tasks. Let them! This organic adoption is far more powerful than any mandated approach.
Set up weekly shares where team members can discuss their AI wins. Create a space where they can refine their prompts together. Internal cross pollination is much better than you trying to tell them what to use it for! At least for initial uptake.
The Systematic Approach
Once you've got that organic momentum, it's time to get more systematic. This is where we bring in the quadrant framework. It's a simple 2x2 matrix:
Run workshops with your team to plot their tasks on this matrix. The sweet spot? High time savings, low risk. That's where you start building your prompt library (and then onward and upward to custom Apps etc.)
Your prompt library shouldn't be a static document. It should be a living, breathing thing that grows with your team. Set up a simple system where team members can:
Add new prompts
Refine existing ones
Share success stories
Document limitations
Make it accessible, make it searchable, but most importantly, make it theirs.
I personally use Notion for my prompt libraries but use whatever makes sense in your company. Whatever the team members are most likely to use!
Next up we're diving into something really interesting: using AI to improve our prompts. We'll look at how to build automated systems for analysing, testing, and refining your prompts. Think of it as having an AI prompt engineering assistant on your team.
Keep Prompting,
Kyle