Trilha ·

01 · Define the project with AI

5 min · WordPress Studio 1.17.x

Phase 1 · Conversation and discovery

Define the project before you build

In this lesson, a conversation about an AI event in Faro becomes context, decisions, and open questions.

Takeaway You are here: conversation and discovery

Speaker notes

Place this presentation at the beginning of the journey. Today’s deliverable is a reliable set of conversation notes. Requirements, design, build, and review appear in later phases.

1 · Listen

Start with the conversation

S

Scenario

An AI event in Faro with two tracks and community participation.

M

Conversation brief

A fictional meeting transcript + the agenda brief.

event-meeting-notes.md

Speaker notes

Introduce the simulation: the class receives notes from a conversation with the event organizers and the agenda document. The content is fictional and serves as raw material for product discovery practice. [Sources] Plano para a agenda evento (1).pdf; workshop/en/event-meeting-notes.md

2 · Interpret

AI turns discussion into decisions

Goal

What must the event make possible?

Audiences

Attendees, speakers, volunteers, and sponsors.

Capabilities

Agenda, registration, forms, contact, and venue.

Questions

Capacity, tickets, criteria, and responsible data use.

Speaker notes

Demonstrate a request to the AI tool: separate facts, needs, hypotheses, and open questions. AI organizes the material; the team confirms decisions and retains control over speaker selection and communications. [Sources] workshop/en/event-meeting-notes.md

The journey

The conversation opens three phases

1 · Discovery

Listen, record, and clarify.

2 · Requirements

Define purpose, audience, and voice.

3 · Design

Explore the experience in Claude Design.

Speaker notes

Show the progression without jumping to a solution: first understand the conversation; then record requirements in Markdown; only then explore design. Build and review follow these three phases.

Phase 1 deliverable

Good notes preserve what the conversation revealed

Context, decisions, questions, and boundaries are ready to become requirements.

Up next 02 · Create requirements.md

Speaker notes

Close by confirming that the fictional meeting notes are the raw material for the next phase. We have not chosen layouts or components yet; first we will turn the conversation into verifiable requirements.