Define the job-to-be-done before naming features.
Description
Every workflow starts with the user job, the bottleneck, and the promised output rather than a generic feature label.
Service work
Map common jobs to product evidence: study material to review plan, market signal to campaign brief, item photos to listing draft, or notes to structured documentation.
Success signal
A visitor can match their current task to a tool result before reading implementation details.
Client needs this supports
- As a new visitor, I can identify the workflow that matches my problem.
- As a product manager, I can connect each tool to a measurable user job.