WonderLead WonderLead Practitioner Claim your seat

Cohort 2

AI-Native Practitioner Programme

Build a real product, in a real cross-functional AI-native team, under bar-raiser review by someone who ran these mechanisms at AWS.

Stop being the person with potential.
Become the person with shipped proof.

Led by Patricia Juarez · Staff AI Product Engineer, AWS · Cohort 1 already shipped to the Registry

Setup week, then 10 sprints (or 5 intensive) · pods of 4–8 · starts 1 Sep · applications open until then

PRFAQ v3 week 4 · narrative review

FOR IMMEDIATE RELEASE: your product meets its first real users

drafted with agents · defended by you

✓ survived review. Ship it
Claude · design agent week 5

> Generate 4 landing directions from the PRFAQ. Dark, data-forward, credible: no hype.

CHOSEN

4 directions in an afternoon · judgement is the differentiator

User interviews: synthesis week 6 · n=5

"I'd pay for this today if it saved me the first three validation calls."

P3 · founder, 34 · min 12:40

"The score means nothing to me without the why behind it."

P1 · PM, 29 · min 07:15

trust ×5 explainability ×4 pricing doubt ×3

transcribed & themed by agents · decisions by you

Waitlist: pre-launch weeks 7–10

212

signups before a single line of launch PR

outreach sequences drafted with agents · sent by you

demand is evidence
viable.ai · live SHIPPED
Product Validator · Viable AI, shipped by Cohort 1

week 12 · real users · registry entry C1–01

PRFAQ: written before a line of code

Chapter one The gap

Why "I use AI" stopped being enough

Most people reading this already ship demos. The gap is not access to tools. It is the system around them.

Tools without a system

You can prompt, generate, ship demos. Can you defend what you built in a review, with specs, evals, and security judgment intact?

Solo practice hits a ceiling

A personal AI workflow is not a shared system. Specs, conventions, handoffs, and review only work when the whole team runs the same operating loop.

Nobody holds the bar

Without a fixed review standard, quality drifts with whoever is available and how urgent the week feels.

Chapter two Who it's for

Built for people already in tech

If you already ship work and want operator-grade proof under a real bar, this is the room. If you want passive content, it isn't.

This is for you if

You're a tech IC or manager who wants to gather more experience or leadership skills.

You consume AI but haven't shipped under constraint with it, or you want to create AI apps.

You want proof a hiring manager can read and test, not another certificate.

You can protect the hours your pod will run at: about 4h+/week for the 10-sprint pace, or about 8h+/week for the 5-sprint intensive, including the shared setup week. Showing up to a Thursday sync without Monday's work done hurts the whole pod, not just you.

This is not for you if

You're completely new to tech or have less than 1 year of experience. Consider the €49 workshop or the free Builder Stack instead.

You want passive, fully guided content and you are not independent when learning. There are no async recordings: this is real cross-functional team project execution.

You want the intensive calendar but cannot actually give it 8 hours a week. Pick the 10-sprint pace, or wait for a later cohort. Intensive is not a shortcut.

Chapter three Why trust us

A senior in every corner of the pod

Mentors don't do the work for you. They hold the bar, unblock the team, and teach the craft, while keeping the cohort's promise: learning with fun and balance.

Patricia Juarez Muñoz

Patricia Juarez Muñoz

Programme owner · Bar raiser · Engineering & Leadership

LinkedIn

Staff AI Product Engineer at AWS. 8+ years at Amazon, 17+ in tech; ran Working Backwards, bar-raiser reviews, and AI adoption programmes inside the company. As programme owner she is in every meeting, and she owns the success of each cohort personally. She reviews every artifact and coaches the Leadership Track directly.

Nick Harutyunyan

Nick Harutyunyan

Senior mentor · UX Design & Research

LinkedIn

Sr. UX Researcher at AWS, PhD in CS. First senior UX researcher on AWS Resource Management; owns research across Cloud Operations products. Guides research plans, interview craft, synthesis, and design critique, and holds the design bar in every review.

Reni Oikonomou

Reni Oikonomou

Senior mentor · Strategy & Product Management

LinkedIn

Product leader and coach with 20 years in tech. Former Group Product Manager and fractional CPO; helps scaling teams turn ambition into clear strategy. Guides the PRFAQ, prioritisation, positioning, and the PRD, and holds the product bar in every review.

Join as a Mentor Free

Senior engineers, PMs, designers, and strategists can join at no cost to practise mentoring in a real pod: observe sessions, run bar-raiser reviews, and give graduation feedback.

Apply as a Mentor →
Chapter four The shift

The redline on your career

Ten sprints is one revision cycle. Here is the diff.

− Today

"I know the frameworks but I've never shipped end-to-end."

"I consume AI content daily but have no AI-native workflow of my own."

"My portfolio is side-projects, not operator-grade work."

"I've never led cross-functional delivery under real constraints."

+ Sprint 10

A shipped product with real users: not a mock brief. Or a COE if quality held the date.

A public PRFAQ, PRD, and the artifacts you actually delivered.

Evidence of leading cross-functional delivery under a deadline.

An AI-native workflow stack tuned to your role: agents, evals, prompt-as-code.

Your entry in the public Practitioner Registry.

accepted ✓
Chapter five The roadmap

Align first. Then ten sprints to launch.

Setup & alignment · before Sprint 1

Meet as a team before you define the product

Before this week, we match the pod by role, level, and the pace you said you can sustain. You work with peers at your level. That matching is not a sprint you attend.

Setup week is for alignment, not execution. You meet, set roles, write a team charter, and confirm one pace for the whole pod. Cohort 1 taught us people hesitate to define a product until the room is aligned. So we do that first.

You look at the proposals together (AI Marketing CRM, AI Recruiter, Travel Planner, or a teammate's own idea) and agree how you will decide. You do not write the 5 Customer Questions yet.

Sprint 1 is when execution starts: 5CQ, product selection, and the discovery work. Same ten sprints after setup, whether the pod runs 10 weeks or 5 intensive.

Sprints 1–4 · Phase I

Discover & Working Backwards

Start from the customer, not the tech. PRFAQ v1 drafted with AI support, torn apart and rebuilt if the bar raiser doesn't approve it.

team charter 5 customer questions user interviews research synthesis jobs to be done PR + problem statement FAQ (RICE / MoSCoW) tech feasibility

Sprints 5–8 · Phase II

Build & Iterate

PRD and tech design, UI/UX and a design system, frontend and backend build, usability tests, then product fixes while GTM starts.

PRD (AI spec) tech brief sprint plan + backlog design system / palette tech design product development UI / UX design usability tests

Sprints 9–10 · Phase III

Launch or COE

Go / No-Go with evidence. Public launch if the bar is met. Pre-launch COE if the deadline can't be met with quality. Your entry lands in the Registry either way.

GTM strategy Go / No-Go

The roadmap adapts to the team

Weekly roadmap reviews. Every sprint the pod reviews the plan and adapts it to what the team actually needs.

Quality holds the bar. A delivery might slip to keep the quality high, exactly as it would in a real team.

The deadline still matters. We work strategic workarounds to meet the target launch date whenever possible.

A curriculum for every seat

Role-specific resources, templates, and mechanisms, plus the two threads every role trains: AI (agents, evals, spec-driven development) and EQ (feedback, conflict, leading without authority).

Tech roles are blurring. Design Technologists, Product Engineers, and T-shaped generalists thrive by going deep in one seat while contributing across others. Check the roles you want to train. You can combine seats if you have the capacity; each additional role adds load on top of your primary.

Hover a role for the full description. Tap on mobile. Colours match the deliverable pills in each phase above.

Setup week first, then the same ten sprints either way. Standard pace: one Monday sync, about 4+ hours/week, 10 sprint weeks. Intensive pace: Monday and Thursday syncs, about 8+ hours/week, 5 sprint weeks. Monday reviews the sprint just finished; Thursday syncs the next one. The pod confirms one pace in setup week and everyone holds it. Plan execution for your primary seat; each extra seat you add increases the load. Serious bar, human pace: we learn with fun and balance.

Chapter six The practice

How the pod uses AI each week

Four things you do in the work, then defend in review. Same bar as the PRFAQ and the launch call.

01

Write the spec first

You write specs precise enough for an agent to act on, and the pod keeps a convention file in the repo so context travels with the code.

02

Delegate, review, own

The agent hands the work to specialist agents before it asks a human. You review what comes back the way you would read a pull request, and you decide what ships.

03

Add evaluations and run loops

Each piece of work has a small eval set, with metrics and errors. If the next version gets worse, you see it before the bar-raiser, not after launch.

04

Apply best practices and good judgement

Role team agents apply best practices in the workflows. You choose the stack. Security, compliance, and guardrails are built into the work, not added later.

How you'll work, every week

Agents execute. You think. The bar holds.

This is the operating loop: the difference between using AI and being AI-native. Speed from the agents, judgement from you, and standards from the mechanism.

01

Agents execute

Drafting, synthesis, generation, evals: the volume work runs on your agentic stack.

02

You think, critically

Interrogate the output: what's the evidence, the assumption, the failure mode? The agent is fast. Your job is to be right.

03

The bar holds

Every decision survives a bar-raiser review. No grade inflation, no "looks good to me."

wonderlead · pod session LIVE
week 4 · prfaq revision agents draft · humans decide

A real exchange from Cohort 1, week 4.

Chapter seven The work

AI-native execution, held to the hardest review bar in tech

Every artifact pairs how you build it, with agents, evals, and your own judgement, with the mechanism it must survive.

PRFAQ

Drafted with agentic workflows, defended by you in a live narrative review.

Held to: Working Backwards format

PRD

AI-assisted drafting; every decision in it is human-owned and defensible.

Held to: feasibility & scope review

Design generations

Landing pages and product UI generated with AI: four directions in an afternoon, one chosen with intent.

Held to: design critique

UX research

Real user interviews: transcribed and themed by agents, decided by you.

Held to: evidence over opinion

Waitlist & Final Product

Coded and reviewed with AI. A waitlist when discovery is solid, a product ready to ship by sprint 10, and a Go/No-Go call your team argues with evidence.

Held to: launch review mechanism

Launch or COE

If we don't launch on sprint 10, we write a COE: AI-augmented detection and root-cause analysis of what went wrong, owned by the team.

Held to: Correction of Errors

Bar-raiser reviews

Your work reviewed by someone whose only job is to keep the standard high. No deliveries as slides. We follow Amazon review style: read in silence first.

Held to: no grade inflation

Anyone can claim AI-native. The frameworks are publicly documented. What you can't get from a book is practicing both under review, by someone who ran these mechanisms at AWS, after 17 years in tech.

Chapter eight The record

The Practitioner Registry

A public register of what graduates actually delivered: the product, the documents, the review trail. This is the proof a certificate can't give you.

EntryPractitionerRole heldProject shippedPublic artifactsStatus
C1–02 Arturo Ortega Full Stack AI Engineer Viable AI Tech Brief Tech Design Prototype SHIPPED
C1–03 Jessica (Li-Chieh Huang) UX Researcher & Designer Viable AI Research Plan UX Synthesis User Flow SHIPPED
C2–?? Your name here Your role The product you'll defend at launch · Claim seat

Registry entries are published with each graduate's consent. Names open their congratulations page; artifacts open the Cohort 1 portfolio.

Chapter nine The people

Cohort 1, in their own words

Before joining the WonderLead program, I knew how to build projects, but I was more familiar with the way we create in startups. During the program we built the product from scratch. The turning point for me was learning how to approach problems the way they do at Amazon: focusing heavily on the customer pain point and working backwards from the client's perspective. As a result, I learned techniques that work for me in the long run, like productization, AI, and communication methods.
Arturo Ortega

Arturo Ortega

Frontend Engineer → AI Engineer · Cohort 1

LinkedIn · Video testimonial
For those who want to explore different roles while working toward a clear goal, this cohort provides an excellent training environment. It offers both guidance and a supportive space to experiment, practice, and grow. Most importantly, it enables you to turn your efforts into a tangible outcome, something real you can showcase at the end of the experience.
Jessica (Li-Chieh Huang)

Jessica (Li-Chieh Huang)

UX Designer → UX Researcher (AI augmented) · Cohort 1

LinkedIn
Tracks & pricing

Choose the seat you want credited

Same product, same reviews, same bar, same price whether the pod runs 10 sprint weeks or 5 after setup. The track decides which seat you hold in the pod. Pace is a calendar, not a discount.

Standard

Hold an IC role: PM, engineer, designer, researcher, strategist, or TPM.

€490

  • Full programme in a pod of 4–8: setup week, then 10 sprints (or 5 intensive)
  • Written review on every artifact
  • AI-native workflow stack for your role
  • WonderLead Practitioner Certificate
  • Public Registry entry on graduation
Claim a Standard seat →

Pay in 3×€170 instalments

Role Transition

The programme, plus a private path into your next title.

€1,190

  • Standard or Leadership Track included
  • 6 private 1:1 sessions across the programme
  • Positioning, portfolio, and interview strategy on your artifacts
Start Role Transition →

Standard €590 · Leadership Track €790 · Mentor free. Full refund through Sprint 1. Pace does not change the price.

3× instalments available Full refund through Sprint 1

Honest questions, honest answers

How much time does this really take?

Two calendars, same work, after a shared setup week. Standard pace: one Monday sync and about 4 hours+ a week, over 10 sprint weeks. Intensive pace: Monday and Thursday syncs and about 8 hours+ a week, over 5 sprint weeks. The real load depends on how much you already know the role and how well you use AI. Intensive is a real hours commitment, not a faster certificate. If life interrupts, the weekly roadmap review adapts the plan, and you can pause without penalty; it's in the terms, not a favour.

Can I choose how fast the programme runs?

You tell us on the application which pace you can commit to: 10 sprint weeks at ~4h/week, or 5 at ~8h/week. That is used to group people with compatible availability. The pace itself is confirmed by the whole pod together in the setup week, not individually. A PM on a 5-week calendar cannot sit next to an engineer on a 10-week calendar — the work depends on each other in the same sprint. If the pod cannot agree, it defaults to 10 sprint weeks. Same price, same artefacts, same launch review either way.

How is the project chosen?

Before kickoff we match pods by role, level, and the pace you can sustain. In the setup and alignment week you meet, write a team charter, confirm one pace, and look at the proposals together: AI Marketing CRM, AI Recruiter, Travel Planner, or a teammate's own idea. You agree how you will decide. You do not start defining the product yet. Cohort 1 taught us people freeze on 5CQ and product selection until the room is aligned.

Sprint 1 is when execution starts: 5 Customer Questions and product selection, with a team that already knows how it works together.

What if the team falls behind?

The roadmap adapts. Every week the pod reviews the plan and re-shapes it around the team's needs. A delivery might slip to keep the quality of the work high, exactly as it would in a real team, while we work strategic workarounds to still meet the target launch date whenever possible.

Can't I learn all this free with ChatGPT?

The concepts, yes. The constraints, the team, the deadline, and the shipped evidence: no. You've had free access for two years. What did you ship?

How is this different from a bootcamp, or from renting an AI-native pod?

A course teaches frameworks. A bootcamp teaches you to code. This programme makes you ship as a real cross-functional team, under senior review, with feedback on whether your work meets a professional bar. You leave with real artefacts and the judgment to defend them.

There is also a newer option in the market: agencies now rent out ready-made "AI-native pods," teams of three to seven who build for your company as a service. That can solve a short-term delivery problem, but it leaves the capability with someone else's team, not yours, so the dependency lasts as long as the invoice. This programme is the other way round: you and the people in your pod build the capability yourselves, so it stays with you after the cohort ends.

€590 seems cheap. Is this real?

Standard is €590 and Leadership Track is €790. It's cheap because it's new but the quality is high. The review bar doesn't scale with the invoice.

Who owns the work I produce?

You do. Every artifact you produce is your intellectual property. WonderLead has no commercial rights over your work.

Can we build a paid product?

Use a free product for the programme. A paid product would need IP alignment and contracts with your teammates. Any direction toward paid can wait until later, once the team agrees.

Can I join as a mentor for free?

Yes. Senior engineers, PMs, designers, researchers, and strategists can apply on the Mentor track at no cost. You still pick the craft you bring so we can match you to a pod. In return you attend team sessions, run mock bar-raiser reviews, and give individual feedback at graduation. Approval is still required; it is not an automatic seat.

What's the refund policy?

Full refund through the end of Sprint 1, no questions asked. After that, instalments simply stop if you withdraw: you never pay for sprints you don't attend.

What happens after the last sprint?

Alumni network, your permanent Registry entry, and monthly accountability sessions. The artifacts keep working for you in every interview after.

Cohort 2 · setup week starts Tuesday 1 September

The next revision of you has a deadline.

Pods are 4–8 people. Roles are assigned as seats fill. When this cohort is full, the next one is roughly two months away.

Cohort 2 starts Tuesday 1 September with the setup and alignment week. Sprint 1 execution follows. Standard €590 · Leadership Track €790. Applications stay open until then; roles are assigned as pods fill. Apply free in about 2 minutes. Payment only after your place is confirmed.

Application takes 5 minutes. Rolling review until 1 September; earlier is better for role choice.

Prefer not to meet? Send a question via the contact form.

WonderLead Practitioner · €590 Standard · €790 Leadership Track · Cohort 2
Claim your seat