Where is your team right now?

Think of this like Maslow's hierarchy — but for how your team works with AI. Most teams aren't at one level exclusively. Where do you spend most of your time?

The five layers

As AI handles more production load, creative energy moves up. The goal isn't to skip levels — it's to know which one you're on and what moving up looks like.

Check the level that best describes where your team spends most of its time today.

Level 5 — Thriving
Level 4 — Craft at scale
Level 3 — Collaboration
Level 2 — Consistency
Level 1 — Survival
Level 5
Thriving
Level 4
Craft at scale
Level 3
Collaboration
Level 2
Consistency
Level 1
Survival
Map your first repo

You don't have to solve the whole thing at once. Start with one person, one piece of knowledge. This works whether you're a designer, engineer, PM, or researcher — the format just looks different.

💡

How to use this: Think of one person on your team who holds knowledge that isn't written down anywhere. Fill in one row. That's your first repo. That's how you build from there.

What knowledge lives
in someone's head?
What format
could it live in?
Who owns it as
a system owner?
Example"Valerie knows what images look right for our brand." ExampleBrand brief · reference image set · generation pipeline ExampleValerie — system owner, not bottleneck
Your team · Row 1
Your team · Row 2
Your team · Row 3
Your team · Row 4
Questions to help you dig in

Not sure where to start? These prompts work across roles — designer, engineer, PM, researcher.

Find the knowledge
Who does everyone go to for judgment calls?
The person whose opinion stops the room. That's usually where the most valuable undocumented knowledge lives.
Find the bottleneck
What takes longer than it should because it lives in one person's head?
Onboarding, style decisions, QA criteria, prompt recipes — anything that can only happen when a specific person is available.
Find the format
What would it look like if that knowledge were a tool anyone could use?
Prompt library Brand brief Decision doc Style spec Reference image set Generation pipeline
Find the owner
Who should own this — not as a burden, but as something they're proud of?
The best system owners are the people who already care most about the quality of that knowledge. They become architects, not bottlenecks.