Choosing the Right Claude Surface
Claude is not one chat box — it is a set of working surfaces, like rooms in the same office. You can draft a contract standing in the hallway, but the conference room works better. Most frustration in early AI adoption is not a capability problem; it is work happening on the wrong surface.
The surface guide
| Surface | Best fit |
|---|---|
| claude.ai chat | Exploration, drafting, analysis, and one-off tasks |
| Projects | Recurring work that needs stable instructions and reference material |
| Artifacts | Outputs that benefit from a separate, editable workspace |
| Claude Code | Codebases, files, scripts, documentation, and technical workflows |
| Cowork | Collaborative knowledge work organized around shared outcomes |
| Chrome, Excel, and PowerPoint experiences | Work that should stay close to the browser, spreadsheet, or presentation |
| API and Console | Products, integrations, evaluations, and controlled programmatic use |
Product access varies by plan and administrator settings. Use only the surfaces approved for your organization.
Placeholder: replace with a map that routes one-off work, recurring work, technical work, and integrated work to the appropriate Claude surface.
How a workflow grows across surfaces
Watch how the surfaces connect in practice. Maya, an account executive at Northstar Components, needs a renewal brief for her biggest account.
Week one, chat. She pastes the account notes and asks for a brief. The result is decent; she refines the request three times before it fits how her team runs renewal calls. Chat is the right room for this stage — she is still discovering what "good" looks like.
Week three, a Project. The instructions have stabilized, and she is tired of re-pasting the playbook every time. She creates a Project holding the renewal playbook, two example briefs, and her refined instructions. Now every conversation starts warm, and a teammate can use the same Project and get the same quality.
Later, a connected workflow. The team wants briefs grounded in live CRM data instead of pasted notes. That is a different level of access and control — approved connectors, permissions, review — and it belongs in Phase 3 of this course. The value has to justify the governance work.
That progression — explore in chat, stabilize in a Project, connect only when proven — is the default path for almost every workflow in this program. Skipping stages is how teams end up automating a process they never actually understood.
Four questions that pick the room
- Is this one-off or recurring?
- Does the task need persistent knowledge — a playbook, examples, a glossary?
- Does Claude need to work with files, software, or company systems?
- Who must be able to review, reuse, or administer the result?
One-off with no special knowledge: chat. Recurring with stable context: a Project. Hands-on with files or code: Claude Code. Plugged into company systems or products: connected and programmatic surfaces, with the controls they require.
Practice
For the workflow you selected in the first lesson:
- Name the best surface for the first test, and why.
- Name the surface it should graduate to once the method is proven.
- List any plan, permission, or administrator dependency you would need to check first.
Ready to move on
You can place your workflow on the explore → stabilize → connect path and justify the current surface in terms of the work, the context it needs, and your organization's controls.