Product design question

Design a product that helps non-developers use Claude for knowledge work (Claude Cowork).

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests product design for extending an AI product beyond developers into general knowledge work.

Define the user precisely: a non developer knowledge worker, for example an analyst or operations manager, who needs Claude for research, writing, or data tasks without writing code.
Identify the core gap versus Claude Code: this audience needs task templates and guided workflows, not a blank chat box or a terminal.
Prioritize the highest value workflows first: document analysis, report drafting, and spreadsheet style data work, since these map to common knowledge work tasks.
Design around files and existing tools: seamless import from documents, spreadsheets, and email, since this audience works inside existing files rather than starting from scratch in a chat.
Add guided task structure: pre built workflows for common jobs, like summarizing a document set or drafting a report from data, rather than requiring the user to know how to prompt effectively.
Confirm with the interviewer whether the target is individual knowledge workers or teams collaborating on shared work, since collaboration features change the scope significantly.

Centers the design on file and document workflows rather than a chat interface alone, correctly matching how non developers actually do knowledge work.
Proposes guided, templated tasks instead of requiring prompt engineering skill, lowering the floor for a user who has never crafted an effective AI prompt.
Distinguishes this clearly from Claude Code by focusing on document and data artifacts instead of code and terminals.
Ties success to a measurable outcome, like percent of sessions ending in a usable saved output, rather than just engagement time.

Designing essentially a rebranded chat interface without addressing the real gap of guided, templated workflows for non technical tasks.
Ignoring file and document import as a first class need, forcing users to copy and paste content manually.
No clear differentiation from Claude Code, making the product's purpose unclear to both new and existing users.

How would you help a user who does not know how to describe the task they want done?
What would the first five templates be and how would you choose them?
How would you measure whether this product is actually replacing existing knowledge work tools?