Members
Core operators. Drive sprints, own patterns and playbooks, set the Lab's quarterly direction. Significant time commitment — a real percentage of capacity, not a side project.
A three-layer architecture — Lab, Practice, All DS — for how Design Studios builds, validates, and scales an AI-augmented craft.
Generative AI lifted the baseline of what anyone can produce. The new differentiator isn't access to tools — it's institutional craft. Studios that codify taste, build workflows others can't, and treat AI as material — not magic — will define the next decade.
The job isn't to use AI. The job is to make work that couldn't exist without it.
The Lab invents and validates. The Practice translates and operates. All DS receives, applies, and feeds back. Each layer has a different speed, a different tolerance for risk, and a different metric for success — but they share one closed loop.
~20 people. The R&D node. High tolerance for risk. Ships craft into the rest of DS as patterns and playbooks.
Regional Practice — AMR, EMESA, AP+ME. Adapts what the Lab makes for local craft, language, and case context.
Every designer in every studio. Self-paced fluency, monthly briefs, an annual festival. The user base and the feedback engine.
~20 people. Three designations: Members, Affiliates, Friends — concentric circles of involvement, each with a different commitment and reach. Six focus areas define what the Lab actually works on.
Core operators. Drive sprints, own patterns and playbooks, set the Lab's quarterly direction. Significant time commitment — a real percentage of capacity, not a side project.
Specialists who join sprints by topic. Brought in for their craft — motion, type, code, sound — when a sprint needs that skill. Time-boxed contribution, not standing membership.
External orbit. Critics, collaborators, sounding boards from the wider design and AI world. Show up when relevant, leave when not. Keep the Lab honest and outward-facing.
The Lab's beat. Each focus area has a lead, a sprint cycle, and a measurable output.
Concept exploration at high volume — text-to-image, text-to-3D, mood and direction tools. Where the broadest space gets surveyed quickly.
Pipelines, scripts, custom GPTs, and internal tools that compress repetitive work — letting designers spend more time on the parts that matter.
Using AI to push existing craft further — refined typography, cinematic motion, generative systems that feel hand-tuned, not template-output.
Long-form content, story arcs, scripts, briefs — where AI assists structure but the editorial point of view stays firmly human.
Live event visuals, real-time generative content, streaming-era formats. Fast, reactive, and built for moments that can't be pre-rendered.
Studying how AI changes the way designers work together — pairing, review, handoff, mentorship. The org-design adjacent question.
The Practice does the connective work. It exists in the regions, runs on a bi-weekly heartbeat, and structures itself around four pillars — each with its own ritual, output, and accountability.
Track what's emerging — tools, techniques, players. Surface signal, ignore noise. Bring the most interesting findings into the rest of the system.
Foundations programme, Jam Sessions (Ignite · Make · Share), workshops. Designed to move a person up the Fluency Ladder by one rung at a time.
Move patterns into live cases. The point at which research becomes craft. Tracked by adoption — workflows running, not just decks read.
Editorial board, monthly brief, the festival. The artefacts that move learning across studios and back into the Lab as feedback.
An annual rhythm. May launches the brief. August judges and ships. Every studio enters. The whole community watches.
Seven steps from "AI-curious" to "AI-leading." Self-paced. Public. Every designer can see the ladder, see where they are, and see what the next rung needs. No tests, no badges — just visible progression and shared language.
You've watched the demos, you've read the threads. Maybe you've tried a prompt or two. AI is on your radar but not in your work yet.
First real attempts inside actual work. Mostly gimmick or filler stage — but something has shipped that wouldn't have without AI in the loop.
AI is now in your pipeline, not on top of it. You know which tools fit which stages. Output quality has visibly improved.
The taste differential shows. You produce work that's recognisably AI-augmented but still distinctly yours — pattern, voice, polish that survives scrutiny.
You've built a workflow, a custom assistant, a script — something other designers can pick up and use. You've shifted from consumer to producer of leverage.
You run sessions, mentor, write up patterns. Your impact is now indirect — measured by how many people you've taken with you.
You define direction at studio or practice level. Decisions about which tools, which patterns, which work to take on — these run through you.
Six discipline areas across DS — each thinking about Creative AI from its own vantage point.
Identity systems, visual language, brand expression. AI changes ideation speed and asset breadth — but the editorial point of view is still where the value lives.
Animation, video, generative motion. The discipline most directly transformed by AI — text-to-video and runway-class tooling have collapsed entire production pipelines.
Long-form writing, scripts, narrative structure. AI is great at first drafts and structure — but the voice, the angle, the right omission still come from a human editor.
Product UX, interfaces, websites. Pair-programming with AI is now baseline. Component generation, content drafting, prototyping speed — all transformed.
Events, environments, installations, live work. The most physical of the disciplines — but real-time generative content is reshaping what's possible inside live moments.
Campaigns, social, internal comms. AI is heavily used — sometimes too much. The challenge here is editorial restraint, not output volume.
Governance sets direction — what we work on, what we don't, how we measure. Coordination runs the system — sprints, schedules, blockers, hand-offs. Confusing the two is the most common failure mode.
Tools, accounts, channels, repos. Boring on the surface but decisive in practice — most stalled rollouts die here, not in the strategy.
A standard kit — image, video, code, copy. Procured centrally. Approved for client work. The default, not the exception.
A living repo of validated patterns and playbooks — written by the Lab, used by the Practice, contributed to by All DS.
Where finished work lands — internal-facing, browseable, searchable. The library that proves the patterns work.
Slack first. Studio-level channels, regional Practice channels, a single global #creative-ai. Where the texture of daily work lives.
Bi-weekly Coordination keeps things moving. The monthly Brief reaches everyone. The annual Festival is the public moment. Slack carries the texture in between. Each has a clear sender, audience, and call to action.
Operational pulse. Sprint reviews, blockers, upcoming hand-offs. Internal to the Coordination Group. Notes posted to Slack.
Editorial. One issue per month. Highlights work shipped, pattern of the month, ladder progressions. Goes to all of DS. Read in 5 minutes.
1min.ai. May–August. The public moment. Highlights published externally. The biggest single comms event of the year.
The texture. Wins, losses, links, half-thoughts. Where the day-to-day life of the practice actually lives.
Different rhythms for different jobs. Daily Slack texture. Bi-weekly Coordination. Bi-monthly Lab sprints. Monthly Brief. Quarterly Governance review. Annual Festival. The wheel below shows how they line up across a year.
Three KPIs at the top. Each tied to a layer. Each a leading indicator, not a vanity metric. We resist the urge to measure what's easy to measure when what's measurable isn't what matters.
No model lands fully formed. These are the seams we're watching and the questions we don't yet have clean answers to. Calling them out so the system can self-correct.
Lab is small by design — but it gets pulled into Practice work that isn't really R&D. If 30% of Lab time is spent on Practice support, the Lab stops inventing. The fix is probably a clearer triage rubric, not more headcount.
The fluency ladder is self-reported. It works because it's used in good faith. If it ever becomes a promotion gate, the rungs become a lie. Keep it descriptive. Keep it public. Keep it out of HR systems.
1min.ai is a four-month commitment. If only the same studios show up year after year, it ossifies. The brief, the categories, and the editorial board need to keep rotating.
The tooling stack needs to evolve, but every change costs the practice attention. Refresh quarterly, not monthly. One studio test before broad rollout.
Source material, definitions, and the decisions behind the model. Click any section to expand.
Lab. The R&D node. ~20 designated. Owns invention, validation, and packaging of patterns and playbooks.
Practice. The regional translation layer. AMR, EMESA, AP+ME. Adapts what the Lab makes for local craft and case context.
All DS. Every designer in every studio. The user base of the system and its primary feedback engine.
Pillar. One of four operating buckets in the Practice — Explore, Learn, Apply, Share.
Designation. A formal role inside the Lab — Member, Affiliate, Friend.
Ladder. The seven-step Fluency Ladder for All DS — Curious → Trying → Working → Crafting → Building → Teaching → Leading.
Foundations. The onboarding programme. Quarterly cohorts. Self-paced after kick-off.
Brief. The monthly editorial. ~5 minutes to read. One issue, every studio, every month.
Festival. 1min.ai. Annual. May–August. Briefed, made, judged, shipped.
Why three layers, not two. A two-layer model (Lab + everyone) collapses under the weight of regional variance. The Practice exists because Lab patterns need a translator before they can work in AP+ME the way they work in AMR.
Why a ladder, not a certification. Certifications create gatekeepers. Ladders create language. We want shared vocabulary, not a credentialing apparatus.
Why a regional Practice, not a global one. One global Practice would centralise faster than it could adapt. Regional means each region's Practice has authority to shape what reaches its studios.
Twelve studios audited across all three regions. Thirty-seven practitioner interviews — split roughly 60/40 between IC designers and design directors. Nine pilot workflows ran in parallel for at least one full case cycle each.
Filtering: we ignored claims of AI use that weren't backed by an artefact. We weighted answers from people who could show their work over those who couldn't.
Each rung is described by behaviours, not capabilities. Curious: reads about it, can name three tools. Trying: has used a tool on real work; can show one artefact. Working: can describe their default pipeline, including AI steps; quality is consistent.
Crafting: their work has a recognisable hand inside an AI workflow. Building: has authored a workflow, custom assistant, or script others use. Teaching: regularly mentors or runs sessions. Leading: shapes direction at studio or practice level.
Brief released first week of May. Open theme but always paired with a craft constraint (this year: 60-second piece, generative video).
Categories rotate annually but always include: Best Solo, Best Studio Collective, Best Use of New Tooling, Best Editorial. Judging panel is a mix of Lab Members, regional leads, and one external guest critic. Winners archived in the Showcase, with editorial write-up.
Stack is reviewed quarterly by the Coordination Group, ratified by Governance. Regions can flag local additions but the canonical stack ships from the centre.
Currently includes: image generation, video generation, code-pair, copy-pair, internal pattern repo, custom GPTs for specific case workflows. Specifics rotate quarterly.
Every approved tool has a documented IP and confidentiality posture. Client work uses only approved tools — no experimental tools touch client data without explicit sign-off.
Brand consistency: all client-facing AI output goes through the same review chain as any other deliverable. Vendor lock-in: deliberately maintain redundancy across at least two providers in each major capability category.
v10.0: introduced the three-layer model. Replaced the previous flat hub-and-spokes diagram. First articulation of the seven-step Fluency Ladder.
v10.5: codified Governance vs Coordination split (was previously merged). Added Friends as a third Lab designation. Added explicit risk register and IP posture (Appendix G).