❄️ Winter Bootcamp · July 2026 · Day 2 · Tuesday

Day 2 — Technical Visit

Immersion at the partner: see the problem where it happens

🎯 What we'll do today

Visit the partner (Azul Linhas Aéreas) and observe the real process, out of the classroom
Confirm or correct the Day 1 spec's assumptions
Listen to those who live the problem and record evidence
Come back with a sharpened spec to build tomorrow

🏁 Deliverable of the day

Spec revised with what was observed on the visit
Evaluation criteria confirmed with the partner
Record of the evidence: notes, examples and real constraints

Learning objectives

What you take from the visit

Objectives

✅ By the end, you can

Run a field observation focused on the problem in the spec
Tell what the process really is from what was assumed on paper
Ask questions that reveal real criteria, pains and constraints
Record evidence in a way that serves building the solution

🧭 Why the visit comes first

Building on assumptions costs rework — the visit anchors the solution in reality
What you see at the partner becomes a requirement and acceptance criterion
Tomorrow, the building prompt is born from this context, not from guessing

Week Roadmap

Where we are in the journey

Day 2/5

Day 1 · Mon Spec & Modeling ✅ Spec validated, acceptance criteria set

Day 2 · Tue Technical Visit Today: immersion at the partner, assumptions confirmed

Day 3 · Wed Prompts & Platform Building prompt + 1st version in Lovable

Day 4 · Thu Sprint, Refinement & Tests Working MVP, tested and refined

Day 5 · Fri Presentations Pitch to the panel

🏭 Field observation 🗂️ Day 1 Spec 📝 Evidence log

Before going — preparation

A well-prepared visit pays off three times over

Preparation

🎒 What to bring

The Day 1 spec printed or at hand — it's the observation script
A short list of assumptions to confirm
Paper or phone to take notes and record (with permission)
Roles split: who asks, who takes notes, who observes

❓ Questions worth gold

How does this process work today, step by step?
Which criteria weigh in the decision — and how do they compare?
Where is there the most manual work or rework?
What data exists and in what format does it arrive?
What can't be missing — and what must never happen?

During — what to observe

The real context of the process, out of the classroom

Field

👁️ What to observe

Bring the group's spec. The visit confirms or corrects the Day 1 assumptions against the partner's real process.

How the process happens in practice — not on paper
Which criteria the team uses and how they weigh against each other
What data exists and in what format it arrives
What the spec got right and what needs revising

🔎 Focus on the essential

Follow the data's path, from start to finish
Note exact phrases from those who live the problem
Capture concrete examples, not generalizations
Mark what surprised you — it's often a hidden requirement

Back in the room — debrief

Turn what you saw into a revised spec

Synthesis

🔄 Group debrief

Gather everyone's notes in one place
Compare with the spec: what was confirmed, what changed
Revise the evaluation criteria with what you heard
Note the new requirements and constraints that emerged

✏️ Update the spec

Adjust actors, input, output and constraints to reality
Refine the acceptance criteria: how we'll know it works there
Keep the evidence — it justifies decisions in the pitch

Bridge to tomorrow

The revised spec is the direct input of the Day 3 building prompt.

🎓 Day 2 wrap-up

Where we got and what comes next

Wrap-up

✅ Today you

Observed the partner's real process
Confirmed and corrected the spec's assumptions
Recorded evidence, criteria and real constraints

➡️ Tomorrow (Day 3)

Prompts & Platform: turn the revised spec into the prompt that builds the solution in Lovable
Every requirement you saw today becomes part of the prompt

📌 Before tomorrow

Leave the revised spec and the evidence organized. Tomorrow it becomes the platform blueprint — the more faithful to what you saw, the better what the AI builds.