Book 3 · Chapter 3 · Mission 1

Coordinate Your AI Team on a Real Project

Apply everything from Books 1–3. Not practice anymore. Real work.

⏱ 1–2 weeks, distributed sessions
Echo

This is the mission where the trilogy becomes real. You’re not practicing with a tool anymore. You’re directing Pixel, Echo, and Algo as specialists on a project you care about, for real people. Parent partnership required throughout — not just for sign-in, but for judgment calls, safety, and getting it into real hands.

This is executive-level work for a 10–14 year old. Your job is partnership, not oversight. Help them scope down if they’re going too big. Connect them to the real testers. Let them make the judgment calls that AI can’t.

What You’ll Need

  • A real problem or opportunity that excites you
  • A couple weeks of distributed work sessions
  • Your full AI team access (see AI Toolkit)
  • At least two other people affected by your project (for testing and feedback)
  • Parent partnership for implementation and safety
1

Define the Project

First session, 60 minutes

Pick ONE real challenge. Categories to consider:

  • Community problem in your school or neighborhood
  • Family challenge affecting someone you care about
  • Personal interest you want to develop into something bigger
  • Creative vision you’ve always wanted to execute
  • Learning project that helps other kids understand something

Write:

  • Vision: what you’re building (one sentence)
  • Who it serves: the real people who will benefit
  • Why it matters: the deeper purpose
  • What success looks like: how you’ll know it’s working
  • Your values: the top 3–5 that will guide every decision
2

Map the Team

First session, 30 minutes

Figure out who does what:

  • Pixel handles: (specific visual work)
  • Echo handles: (specific content and communication)
  • Algo handles: (specific research and strategy)
  • You handle: (vision, values, final decisions, human relationships)

Write down specific tasks for each team member. The clearer the assignments, the better the team performs.

3

Start With the Most Important Piece

First week

Don’t build all parts at once. Direct your AI team to the most important piece first.

Your job:

  • Give each AI clear direction on its specific task
  • Make sure each contribution aligns with your values
  • Integrate outputs into a coherent whole
  • Make the judgment calls AI can’t make
  • Keep everyone focused on the vision

Document the process. What worked? What needed refinement? What did you learn about coordination?

4

Test With Real People

Second week

Get version 1 in front of at least three people representing your audience. Watch them interact. Don’t explain. Don’t defend. Don’t ask if they like it.

Ask:

  • What do you think this is for?
  • What would you actually do with this?
  • What’s confusing?
  • What’s missing?
  • What would make it better?

Take detailed notes.

5

Iterate on Feedback

Second week

Go back to your AI orchestra with specific feedback:

  • Pixel: “Users got confused by [specific visual]. Redesign with [specific improvement].”
  • Echo: “The instructions at [specific step] weren’t clear. Rewrite with [specific approach].”
  • Algo: “Users identified [specific weakness]. Research solutions and propose improvements.”

Build Version 2. Test again if you can.

6

Launch and Measure

Final session

Your project deserves to exist in the world. Choose the right channel:

  • School project: present to class, teacher, or principal
  • Community project: connect with local organizations, libraries, councils
  • Family solution: implement with your own family first
  • Digital tool: share appropriately with parent safety guidance

Track real impact:

  • How many people use it?
  • What improvements do they report?
  • What would you change next time?

Document everything. This is portfolio material. Proof of your capability.

You’ve Succeeded When:

  • You built a real project with real impact, not a practice exercise
  • You used all three AI team members in specialized roles
  • Your values shaped every major decision
  • Real people tested and validated (or refined) your work
  • You iterated based on real feedback, not theory
  • You experienced the shift from AI user to AI coordinator
Pixel
“The trilogy becomes real here. You’re not practicing anymore. You’re doing the work.”
Echo
“Your job is the coordination, not the work itself. We do the volume. You do the judgment.”

If Something Goes Wrong

“My project is too big for a couple weeks.”

Scale it down. Build one piece of the bigger idea. A focused, finished, tested piece beats an unfinished masterpiece.

“My AI team members keep producing things that conflict with each other.”

Normal. Your job is to resolve conflicts. Refine your direction. Be more specific. Integrate outputs actively rather than expecting harmony automatically.

“I can’t find real people to test with.”

Start with family. Move to friends. Expand to classmates. Keep the circle real. Testing with made-up audiences produces made-up results.

“The feedback I got is harsh.”

Harsh feedback is valuable feedback. People who don’t care about you often don’t give real feedback. If someone tells you what’s actually wrong, they’re investing in your improvement. Thank them.

“This is taking much longer than expected.”

Real projects take longer than estimates. Always. Not a failure. Adjust your timeline. Keep conducting.

Talk About It

For Kids

  • What did you learn about yourself as a coordinator?
  • What’s the biggest difference between using AI individually versus combining multiple tools?

For Parents

  • Your child just executed a real project using advanced AI coordination.
  • Ask what they learned about themselves and what they’d tackle next with these skills.

Next Steps

← Back to Pax Ember