Goal
What should be different afterward?
Describe the outcome in practical terms. A rough target is enough to start.
Current State
What exists now?
Share the current site, documents, workflow, research, drafts, screenshots or other material that already exists.
Problem
What is getting in the way?
Name the bottleneck, confusion, delay, missing capability or quality issue that prompted the project.
Audience
Who needs the result?
Identify the people who will use, read, approve, maintain or rely on the finished work.
Constraints
What cannot be ignored?
List deadlines, platform limits, compliance needs, technical restrictions, budgets or dependencies that may shape the approach.
Access
What systems are involved?
Note any websites, hosting, files, software, shared drives or other platforms that may need access or coordination.
Decision-Makers
Who approves direction?
Knowing who has final approval helps prevent circular review and conflicting feedback.
Priority
What matters most?
If speed, depth, polish, preservation of existing work or another factor matters most, say so early.
Success
How will you know it worked?
Define the practical result: a clearer site, better workflow, usable research system, launch-ready asset or another concrete improvement.
