Start Learning

Master Microsoft Foundry - Build AI Agencies

Back to Resources Game

Workflow Builder Board Game

A LEGO-style board game where you snap together colored blocks to build complete AI workflows. Like building blocks for business automation!

Game Overview

The Workflow Builder Board Game is a hands-on learning tool that transforms abstract AI workflow concepts into tangible, colorful building blocks. Just like LEGO bricks snap together to create complex structures, these cards snap together to create powerful AI automation systems.

Every complex workflow is made from a small number of simple building blocks. Master these 6 block types, and you can build ANY workflow imaginable.

Why Play This Game?

Learn by Building: Physical manipulation helps concepts stick better than reading
Debug Before Code: Find logical errors on the table, not in expensive AI tokens
Team Collaboration: Work together to design solutions to real business problems
Rapid Prototyping: Rearrange blocks instantly to explore different approaches

What's Included

Game Components
  • 12 Knowledge Blocks (Blue)
  • 15 Agent Blocks (Green)
  • 15 Tool Blocks (Purple)
  • 10 Logic Blocks (Orange)
  • 6 Mission Cards
  • 1 Game Board (optional - or use any flat surface)
  • Variable Tokens (sticky notes work great!)
Optional Extras
  • Timer for speed challenges
  • Whiteboard for sketching data flows

Building Blocks (The 6 Block Types)

Knowledge Blocks
Blue

Purpose: What the AI knows and can reference

Front Side: Knowledge Source
  • Source Name
  • Data Type (PDF/Excel/Web)
  • Update Frequency
Back Side: Variables Produced
  • retrieved_text
  • document_content
  • search_results
Available Cards:
Company Handbook Internal policies, HR rules, procedures
Product Catalog Prices, descriptions, SKUs
Customer Database Customer records, history, preferences
Web Search Results Live internet data via Bing
Email Archive Historical email correspondence
FAQ Document Common questions and answers
When your agent needs to answer questions about YOUR specific data, not general knowledge
Agent Blocks
Green

Purpose: The AI workers who do the thinking

Front Side: Agent Identity
  • Agent Name
  • Specialization
  • Brain Type (Fast/Smart)
Back Side: Input/Output
  • Receives: user_query
  • Produces: analysis_result
Available Cards:
The Analyst GPT-4o (Smart) Research, comparison, SWOT analysis $$$
The Writer GPT-4o (Smart) Creative content, emails, reports $$$
The Classifier Phi-3 (Fast) Sorting, categorizing, routing $
The Summarizer Phi-3 (Fast) Condensing long text into key points $
The Translator GPT-4o-mini Language conversion, localization $$
The Reviewer GPT-4o (Smart) Editing, fact-checking, quality control $$$
Every workflow needs at least one Agent to do the AI thinking work
Tool Blocks
Purple

Purpose: Special abilities you attach to Agents

Front Side: Tool Capability
  • Tool Name
  • Action Type
  • Requires Auth?
Back Side: What It Does
  • Searches web
  • Sends emails
  • Runs code
Available Cards:
Web Search Query the internet
Send Email Compose and send Outlook email
Teams Message Post to Teams channel
Python Code Run calculations accurately
Read Image Extract text from photos/receipts
Create Chart Generate data visualizations
When an Agent needs to DO something, not just THINK
Attach Tool blocks to Agent blocks (max 3 per agent to avoid confusion)
Logic Blocks
Orange

Purpose: Control how the workflow flows and branches

Front Side: Logic Type
  • Type (Decision/Loop/Gate)
  • Condition
Back Side: Paths
  • YES Path -> ...
  • NO Path -> ...
Available Cards:
Decision Diamond Split based on YES/NO condition If/Else
Multi-Route Split into 3+ paths Switch
Loop Back Return to earlier step Go To
Human Gate Pause for human decision Approval
For Each Repeat for every item Loop
Timer Wait Pause for set time Delay
When your workflow has decision points, repetition, or needs human approval
Every Decision block needs BOTH paths defined (YES and NO)
Trigger Blocks
Teal

Purpose: What starts the workflow

Front Side: Trigger Event
  • Event Type
  • Source
Back Side: Variables Produced
  • user_message
  • email_body
  • uploaded_file
Available Cards:
Chat Message User types in chat
Incoming Email Email arrives
File Upload Document uploaded
Scheduled Time Clock triggers
Button Click User clicks action
External Webhook API call received
Every workflow starts with exactly ONE Trigger block
Output Blocks
Red

Purpose: The final result delivered to the user

Front Side: Output Type
  • Delivery Method
  • Format
Back Side: What Gets Delivered
  • Email sent
  • Report displayed
  • Database updated
Available Cards:
Chat Reply Display in chat
Email Sent Outlook delivery
Report Generated Document created
Database Updated Record modified
Teams Notification Channel post
File Created SharePoint upload
Every path in your workflow must end at an Output block

How to Play

Setup
  1. Clear a flat surface (table, whiteboard, floor)
  2. Sort blocks by color into piles
  3. Choose or create a Mission Card
  4. Designate a Timekeeper (optional)
Phase 1: The Mission 2 minutes
  1. Read the Mission Card aloud
  2. Discuss: What is the TRIGGER? (What starts this?)
  3. Discuss: What is the OUTPUT? (What do we deliver?)
  4. Place TRIGGER on left, OUTPUT on right
Phase 2: The Build 15 minutes
  1. Work left-to-right connecting blocks
  2. For each step ask: WHO does this work? (Agent)
  3. Ask: WHAT do they need to know? (Knowledge)
  4. Ask: WHAT abilities do they need? (Tools)
  5. Ask: Are there DECISIONS? (Logic)
  6. Write variable names on sticky notes between blocks
Phase 3: The Debug 5 minutes
  1. Trace the path with your finger from Trigger to Output
  2. Check: Does each Agent have the data it needs?
  3. Check: Do all Decision blocks have BOTH paths?
  4. Check: Are we using the cheapest Agent possible?
  5. Check: What happens if something fails?
Phase 4: Present 5 minutes
  1. Explain your workflow to another team
  2. They ask clarifying questions
  3. Note any holes or improvements
  4. Revise if needed

Missions (Game Scenarios)

The Customer Helper Beginner

When a customer emails a question, automatically search your FAQ document and draft a helpful reply.

Hints:
  • Start with Email Trigger
  • Use Knowledge for FAQ
  • End with Email Output
Blocks Needed: Trigger, Knowledge, Agent, Output
The Price Checker Beginner

User asks for the price of a product. Search your catalog and respond with the current price.

Hints:
  • Use Product Catalog knowledge
  • Simple: just one Agent needed
Blocks Needed: Trigger, Knowledge, Agent, Output
The Smart Router Intermediate

Sort incoming emails into 3 categories (Sales, Support, Billing) and forward to the right team.

Hints:
  • Use Classifier Agent
  • Multi-Route Logic block
  • Three different Outputs
Blocks Needed: Trigger, Agent, Logic (Multi-Route), Output x3
The Research Report Intermediate

Given a company name, search the web for news, then write a summary report and email it.

Hints:
  • Chain two Agents: Searcher then Writer
  • Web Search Tool on first Agent
Blocks Needed: Trigger, Agent x2, Tool, Output
The Approval Loop Advanced

Generate marketing content, show it to the user, and keep regenerating until they approve. Then email it.

Hints:
  • Human Gate for approval
  • Loop Back if not approved
  • Variables carry feedback
Blocks Needed: Trigger, Agent, Logic (Human Gate), Logic (Loop Back), Output
The Expense Guardian Advanced

Process expense receipts: extract data from photos, check if over $500 (require manager approval), then record or reject.

Hints:
  • Vision Tool for receipts
  • Decision Diamond for $500 check
  • Human Gate for manager
Blocks Needed: Trigger, Agent, Tool (Vision), Logic (Decision), Logic (Human Gate), Output x2

How Blocks Connect

Valid Connections
  • Trigger -> Agent The agent receives the trigger data
  • Knowledge + Agent Stack knowledge ON TOP of agent - agent can reference it
  • Tool + Agent Stack tool BELOW agent - agent gains that ability
  • Agent -> Logic Agent output goes to decision point
  • Logic -> Agent OR Output Each path leads somewhere
  • Agent -> Output Agent result is delivered
Forbidden Patterns
  • Tool alone Tools must attach to Agents
  • Knowledge alone Knowledge must attach to Agents
  • Logic with no paths Every decision needs YES and NO
  • Dead end (no Output) Every path must complete

Optional: Competitive Scoring

Earn Points
  • +10 Completed workflow (works logically)
  • +5 Used cheapest possible Agents
  • +5 All variables properly connected
  • +3 Error handling included
  • +2 Finished first
Penalties
  • -3 Dead end path
  • -2 Missing variable connection
  • -1 Overkill Agent (using Professor for simple task)

Printable Assets

Print these on cardstock and cut out for physical play

Recommended Card Size: 2.5" x 3.5" (standard playing card)

  • Print on colored cardstock matching block colors
  • Laminate for durability
  • Use sticky notes for variable tokens
  • Keep in a deck box or zip-lock bag

Use Miro, FigJam, or Canva for virtual drag-and-drop

The Digital Workforce Academy - Building AI Agencies with Microsoft Foundry

For all with Low-Code Experiences