Bea and the rest of the team identify and define the pain or problem as precisely as possible. Pain and problems always come from users.

Gabo adds Opportunities to the list, stating a clear Outcome. The order of the opportunities list defines the prioritization. Focus on opportunities in the top 10.

From the Opportunities list, Gabo creates a Projects. In the project, we maintain a proper argumentation process to surface disputes and solutions through comments and notes. Projects include small enhancements.

Gabo is responsible for ensuring that a project has an outcome, stories, and problems.

Bea adds designs and workflows to the Design section; they should include short descriptions of the User Stories.

Everybody should share their inspirations with notes and their ideas with sketches.

Developer in charge adds the software architecture definition, No Gos, and the Rabbit Holes section.

We greenlight projects at Hypertuesdays.

The assignee developer creates a Plan with Claude from the project document or codes the project himself.

The PR is generated, and a Reviewer reviews and merges it.

QA the functionality and file the corresponding bugs.

Bea reviews the implementation, giving feedback on the project before completing it.

Talk to users and check the Outcome contrasting the User Task and the Solution. If new feedback is received on a completed project, the process must be restarted.