ANALYZE PHASE

STRATEGIC PROBLEM DEFINITION

PURPOSE

Using the project vision from your START phase, let's transform your idea into a crystal-clear blueprint. This phase is about asking the right questions before writing any code. Your AI assistant will help guide this process.

Define the Problem

What specific problem are you solving? Who experiences this problem? Why does it matter?

Set Clear Goals

What will the solution do? How will users interact with it? What are the must-have features?

Plan the Approach

Break down the project into phases. Identify technical requirements. Set realistic milestones.

REQUIREMENT GATHERING

Great analysis starts with asking the right questions:

  • Users - Who will use this? What are their skill levels? What devices do they use?
  • Core Features - What are the 3-5 essential functions? What can wait for version 2?
  • Data - What information needs to be stored? How will it flow through the system?
  • Integration - Does this connect to other services? What APIs are needed?
  • Constraints - Budget? Timeline? Technical limitations? Compliance requirements?
  • Success Metrics - How will you measure if this works? User count? Performance? Revenue?

Pro tip: Write everything down. Clear requirements prevent scope creep and miscommunication.

USER STORIES

Transform requirements into user stories that AI can understand and implement:

The Formula:

"As a [type of user], I want to [action], so that [benefit]"

Examples:

  • As a customer, I want to filter products by price, so that I can find items within my budget
  • As an admin, I want to export user data to CSV, so that I can analyze trends in Excel
  • As a mobile user, I want to save articles offline, so that I can read during my commute

Acceptance Criteria:

For each story, define what "done" means:

  • User can successfully complete the action
  • Edge cases are handled gracefully
  • Performance meets requirements
  • UI provides clear feedback

ANALYZE TEMPLATE

ANALYZE Phase - Uncover Hidden Requirements

Phase 2 of 5 | START -> ANALYZE -> CREATE -> EVALUATE -> COMMIT

The #1 cause of project failure? Missing requirements. This phase uncovers the hidden complexity that derails 90% of projects, before you've invested weeks building the wrong thing.

NEXT STEPS

What you'll bring from START: Your project definition, goals, and constraints

  1. Fill out the template - Complete all sections with your requirements
  2. Submit to AI - Copy and paste into your AI assistant
  3. Review recommendations - Validate architecture and approach

Ready for CREATE when: You have at least 3 user stories defined and your AI has confirmed the technical approach

Phase 2 of 5 - Your blueprint becomes your CREATE roadmap

CONTINUE TO CREATE