RISEN Framework
Role · Instructions · Steps · End Goal · Narrowing
Built for multi-step enterprise tasks. The Narrowing field keeps AI output on-track and within constraints.
- Definition
- The RISEN framework (Role · Instructions · Steps · End Goal · Narrowing) is a prompt engineering structure that breaks your AI request into 5 discrete fields. It is best suited for enterprise workflows with sequential steps.
The 5 Fields
Role
The expert persona the AI should adopt for this task.
Instructions
Clear directives about how the AI should approach and execute the task.
Steps
The sequential steps the AI should follow, in order.
End Goal
The final deliverable or outcome you want to achieve.
Narrowing
Constraints, exclusions, and guardrails — what the AI should NOT do or include.
Real Example
Scenario: Building a competitive analysis report
Role: Senior market analyst. Instructions: Analyze the multi-LLM tool market objectively. Steps: 1) List top 5 competitors, 2) Compare features, 3) Identify gaps. End Goal: A structured report with actionable insights. Narrowing: Do not include tools with fewer than 1000 users. Focus on tools launched after 2023.
When to Use RISEN
- ✓Enterprise workflows with sequential steps
- ✓Complex processes requiring a specific order of operations
- ✓Tasks where you need strict constraints on output
- ✓Multi-stage research or analysis tasks
- ✗Simple one-answer questions (use APE or RTF)
- ✗Tasks focused on tone and voice (use CO-STAR)
- ✗Creative writing where constraints reduce quality
Frequently Asked Questions
What does RISEN stand for?
RISEN stands for Role, Instructions, Steps, End Goal, and Narrowing — a framework designed for sequential, multi-step enterprise tasks.
What makes the Narrowing field useful?
The Narrowing field lets you define explicit constraints — what to exclude, avoid, or stay within. This prevents AI from going off-topic or including irrelevant content.
When should I use RISEN instead of SPECS?
Use RISEN when your task has a clear sequence of steps to follow. Use SPECS when you need to define complex technical requirements without a fixed step order.