Creating Requirements

Overview

Requirements are the foundation of your evaluation framework. They define what needs to be built, validated, and continuously improved.

Understanding the Requirements Structure

Requirements follow a hierarchical breakdown from high-level needs to specific measurable criteria:

Requirement (Product capability)
└── Use Case (User scenario)
    └── Acceptance Criteria (Specific behaviors to validate)

Each level adds more detail and specificity.

Why Requirements Matter

• Establish scope - Clarify what you're evaluating
• Enable traceability - Track how Requirements connect through Use Cases to Acceptance Criteria
• Guide evaluations - When imported into Flows, requirements become the basis for testing
• Support iteration - Run multiple evaluations on the same requirement to track progress

Two Paths to Flows

Path 1: Full Requirements Flow

1. Define Requirements
2. Break down into Use Cases
3. Write Acceptance Criteria
4. Import Use Case into Flows
5. Run Evaluations against Guideline Sets

Path 2: Direct to Flows

If you already have a defined process (like a checkout flow), you can create a Flow directly without mapping through Requirements.

Example

Requirement: Mobile pizza ordering app

This is the overall product need. It's broad, clear, and describes the main goal.

Best Practices

• Be specific - Clearly define what success looks like
• Stay focused - Avoid overly broad requirements that are hard to evaluate
• Document context - Include reasoning and background where helpful
• Track versions - Note changes over time as standards evolve
• Prioritize - Distinguish critical requirements from nice-to-have ones

Related Topics

• Use Cases - How to structure user scenarios
• Acceptance Criteria - Defining testable behaviors
• Flows - Importing use cases and running evaluations