# Business Vision Template

## Purpose

Capture the business objectives, stakeholder needs, and success criteria that justify the project. Agents should tailor
the sections below to the current engagement and ensure traceability to stakeholder requests.

## Ownership & Collaboration

- Document Owner: Business Process Analyst
- Contributor Roles: System Analyst, Requirements Reviewer, Project Manager
- Automation Inputs: Idea brief, stakeholder roster, market research snapshot
- Automation Outputs: `business-vision.md` with completed sections and live outstanding questions

## Completion Checklist

- All personas, goals, and constraints documented
- Success metrics aligned with organizational targets
- Open issues and assumptions logged for review

## Document Sections

1. **Executive Summary**
   - Summarize the business problem, opportunity, and desired outcomes.
   - Highlight the strategic alignment with organizational goals.
2. **Stakeholder Overview**
   - Provide key stakeholders, their roles, and influence levels.
   - Note engagement expectations and communication cadence.
3. **Business Objectives and Metrics**
   - List measurable objectives (OKRs, KPIs) tied to the initiative.
   - Define how success will be tracked and reported.
4. **Target Customers and Personas**
   - Describe primary and secondary personas, jobs-to-be-done, and pain points.
   - Link to supporting research if available.
5. **Business Context and Constraints**
   - Outline market forces, regulatory demands, and operational constraints.
   - Include timeline, budget assumptions, and dependencies.
6. **Opportunity Assessment**
   - Summarize competitive landscape, differentiation, and expected benefits.
   - Provide revenue, cost savings, or strategic positioning analysis.
7. **Risks and Mitigations**
   - Identify business risks, likelihood, impact, and mitigation ideas.
   - Reference the central risk list for continuity.
8. **Outstanding Questions and Decisions**
   - Log unresolved items requiring stakeholder action.
   - Assign owners and due dates.

## Agent Notes

- Keep tone professional and concise (≤4 sentences per paragraph).
- Reference supporting artifacts with relative paths (e.g., `docs/research/*`).
- Populate **Outstanding Questions and Decisions** before signaling completion so downstream agents can act without
  re-reading.
- Verify the Automation Outputs entry is satisfied before signaling completion.
- Maintain alignment between personas, objectives, and risks across artifacts.
- Flag assumptions and decisions clearly so follow-on teams can validate them.