AI Tutor
Imagine two programmers trying to build a video game together, but one codes a jump button while the other makes that same button open the inventory.
Without a shared visual map, team projects quickly turn into messy code conflicts. A flowchart is a diagram using standard shapes to map out steps, decisions, and outcomes before writing a single line of code.
How do two teammates break down a real problem so they can build a flowchart together?

Defining the Problem Together

Before drawing shapes, partners agree on the inputs (data going into the system) and the expected outputs (the final result shown to the user).
A great strategy is dividing roles: one partner maps the main path (what happens when everything goes right), while the other spots edge cases (unexpected inputs or errors).
What does this collaborative planning look like on a real school project?

Worked Example: Smart Hall Pass Kiosk

Maya and Alex want to code a digital hall pass kiosk for their middle school. The school rule says: only one student may leave the classroom at a time, and passes expire after 10 minutes.
Alex drafted the main flow: scan ID, issue pass, and start the timer. Maya reviewed it and added the decision diamond to catch what happens when someone is already out.