AI Ready
MethodKit for AI Readiness

Get your work
ready for AI.

48 cards that walk a team from the work you do, to the context AI cannot see, to the tools you run on, to where AI can lift you, and how to put a first solution to use. Put them on the table and you can see how ready you really are.

Explore the library Free to read
48 cards for getting AI-ready
One deck · one team · honest about what AI cannot see
48cards
5areas
240questions to explore
1readiness map
01.

What this kit is

Getting AI-ready is less about tools and more about visibility. AI can only act on what it can see, and most of your work is hidden from it. Four ways to think about it.

AI can only use what it can see
Idea 01An assistant is only as good as the context it can reach. The polished documents are the easy part. The reasoning in your head, the decisions made on calls, the why behind how things get done: that is where most of your work actually lives, and AI is blind to it.
Readiness is mostly about visibility
Idea 02Getting ready is less about picking the right tool and more about surfacing what is currently trapped in heads, threads, and habits. Once it is visible and captured somewhere a tool can reach, AI can finally help with it.
Start from your real work, not the hype
Idea 03The deck begins with what you actually do all day and the context around it, then moves to where AI can realistically lift you. The map comes from the work, not from a feature list.
A shared map keeps a team honest
Idea 04Lay the whole picture on the table and everyone sees the same thing: what you do, what is hidden, what you run on, and where AI fits. One picture beats a dozen private guesses.
02.

Four moves to get AI-ready

You do not need an AI strategy to begin. You need to make one corner of your work visible enough for a tool to help. Four moves to start.

01 Surface what only you know

Spend ten minutes listing the things you do that are not written down anywhere: the judgment calls, the context, the why behind how you work. That invisible layer is the real starting point for getting AI-ready.

02 Pick one corner to make visible

Choose a single recurring piece of work and capture it where a tool could reach it: the steps, the inputs, and the context it needs. Readiness grows one captured corner at a time, not in one big push.

03 Get that corner's setup in order

Make sure the files, data, and context for that work live somewhere a tool can actually reach, not locked in one person's laptop or head. Tidy the access before you automate.

04 Hand over a small, low-risk slice

Give AI one well-described slice of that work, read the result with a critical eye, and keep the judgment with you. Note what worked and what to change, then widen only once you trust it.

03.

The library

Search freely or filter by area. Each card is one part of the readiness picture with its own page: what it covers, why AI needs it, a first move to make it visible, questions to discuss, and traps to avoid.

Filter by theme

Showing all 48 cards

Card 10: AI Motivation 10AI Motivation How you view AI & what you want to do with it Your Work Card 11: AI Usage 11AI Usage How well the team understands and uses AI today Your Work Card 1: Company 1Company A quick description of what you & your team do Your Work Card 8: Contacts 8Contacts People you interact with during the workday Your Work Card 9: Customers 9Customers Who hires you & what they get Your Work Card 7: Edge 7Edge What makes you special or skilled Your Work Card 5: Projects 5Projects Projects you're working on Your Work Card 2: Role(s) 2Role(s) The different hats you wear in your role Your Work Card 6: Skills 6Skills What you're good at and what you do Your Work Card 4: Tasks 4Tasks The kinds of things you do in your role Your Work Card 3: Workday 3Workday Describe what a typical workday looks like for you (e.g. yesterday) Your Work Card 13: Calls 13Calls Reasoning that only happens out loud, rarely saved Dark Context Card 16: Direct Messages 16Direct Messages Side conversations in DMs, SMS and chat Dark Context Card 17: Emails 17Emails The real why, hidden inside long threads Dark Context Card 19: Feedback 19Feedback What you did not ask for, but should hear Dark Context Card 14: Meetings & Workshops 14Meetings & Workshops What gets decided in the room, seldom logged Dark Context Card 18: Notes 18Notes Scraps, sketches and half-thoughts on the side Dark Context Card 21: Remote Meetings 21Remote Meetings Calls whose recordings no one keeps Dark Context Card 20: Support Tickets 20Support Tickets What people struggle with, in their own words Dark Context Card 15: Team Chats 15Team Chats Context buried in channels and group chats Dark Context Card 12: Thoughts 12Thoughts Thinking about work that never gets written down Dark Context Card 30: Archives 30Archives Old systems, archives & frozen data Your Setup Card 27: Databases 27Databases Structured stores you query Your Setup Card 24: Hardware 24Hardware Laptops, phones & shared hardware Your Setup Card 29: Passwords & Secrets 29Passwords & Secrets How you store & access logins, keys & tokens Your Setup Card 26: Personal Storage 26Personal Storage Private drives & individual workspaces Your Setup Card 23: Programs 23Programs Software & apps you run on Your Setup Card 22: Services 22Services Third-party services & SaaS you subscribe to Your Setup Card 25: Shared Storage 25Shared Storage Drives & folders the team can reach Your Setup Card 28: Website 28Website Your public-facing pages & posts Your Setup Card 33: Agents 33Agents What runs by itself vs what needs a human Level Up Card 40: AI Factory 40AI Factory What you let your system build, instead of building by hand Level Up Card 34: Boundaries 34Boundaries What AI should do and what you keep with humans Level Up Card 36: Context 36Context How much background information AI needs before taking action Level Up Card 41: Errors & Feedback 41Errors & Feedback How AI learns when it's right and when it's wrong Level Up Card 39: Integrations 39Integrations How AI connects with your other systems Level Up Card 37: Manual Work 37Manual Work What you do by hand before building systems around it Level Up Card 32: Memory 32Memory What in the company leaves traces AI can read and learn from Level Up Card 31: Operating System 31Operating System How AI systems can run the foundation of the company Level Up Card 35: Prompts 35Prompts How you formulate instructions so AI gets it right Level Up Card 38: Self-Improvement 38Self-Improvement How AI processes can measure results and get better over time Level Up Card 43: Concept 43Concept A summary of what the solution should do Put to Use Card 47: Features 47Features What features the solution should have, and what's absolutely most important Put to Use Card 42: Goal 42Goal Which task or problem the solution should fix Put to Use Card 45: Inputs 45Inputs What goes into the solution (data, material, etc.) Put to Use Card 46: Outputs 46Outputs What comes out of the solution (results, text, files) Put to Use Card 44: User Journey 44User Journey How the user uses the solution, from start to finish Put to Use Card 48: Users 48Users Who the solution is for & why they should use it Put to Use
04.

AI words, plainly

A few terms that come up in the cards, in plain language.

Context
The background information a tool can see when it works: the documents, data, and history you give it. More relevant context usually means a better result.
Prompt
The instruction you give an AI. A clear prompt that says what you want, in what form, and why tends to get a far better answer than a vague one.
Agent
An AI set up to carry out a task on its own across several steps, rather than answering a single question. Useful for work that runs without a person watching each step.
Model
The underlying AI itself (for example a large language model). Different models have different strengths, costs, and limits.
Token
The unit AI reads and writes in, roughly a chunk of a word. Cost and length limits are counted in tokens, so longer inputs and outputs cost more.
Integration
A connection that lets AI reach one of your systems directly, so it can read or act on real data instead of waiting for copy and paste.
Memory
What a system keeps from past work so it does not start from zero each time: notes, decisions, and traces it can read again later.
Hallucination
When AI states something confidently that is wrong or made up. It is why output needs checking, especially on facts and figures.
Automation
Work that runs without a person doing it by hand each time. The goal is to automate the repetitive, well-defined parts and keep the judgment human.
05.

Your AI-readiness check

A quick self-check across the five areas. Tick what is already true. The gaps are where to start. Your ticks are saved in this browser only.

Your work

Dark context

Your setup

Level up

Put to use

06.

About

A readiness check for working with AI, built on a card deck that maps your work, the context AI cannot see, your setup, and where AI fits.

Why

Most AI advice starts with a tool. This starts with your work. AI can only act on what it can reach, and most of what makes your work yours is invisible to it: the reasoning on a call, the decision in a thread, the know-how in someone's head. Getting AI-ready is mostly the work of making that visible.

AIREADY is a remix of two MethodKit decks, AI Tasks and AI Memory. It pulls the cards that map a person's work, surfaces the dark context around it, takes stock of the setup, and points to where AI can lift the work and how to put a first solution to use. The result is a readiness picture that comes from the work, not from the hype.

How to use it

Pull the cards that match where you are. Start with Your Work to get the picture, use Dark Context to surface what is hidden, take stock with Your Setup, then move through Level Up and Put to Use to decide where AI fits and ship something small. Run the readiness check at the bottom to see where you stand.

Want the cards in your hand? The decks are available from MethodKit.