Master Artifacts for structured output. Learn multi-turn analysis patterns. Run through 4 real workflow templates: meeting prep, report writing, email handling, and code review. Complete one full work task entirely through Claude Desktop — start to finish.
Artifacts: structured output you can edit
When you ask Claude to produce a document, code file, table, or visualization, it can render the output as an Artifact — a separate panel where you can read, edit, and export the content cleanly.
Artifacts are useful when:
- The output is longer than a few paragraphs (reports, proposals, documentation)
- You need to edit it directly rather than copy-paste
- It's code you want to run or download
- It's a visualization (chart, diagram, HTML mockup)
To get Artifacts, just ask for them explicitly: "Create this as an artifact" or "Write this as a standalone document." Claude will open the artifact panel. You can ask Claude to iterate on it: "Make section 2 more concise" and it updates in place.
When NOT to use Artifacts: Quick answers, short responses, conversational back-and-forth. Artifacts add friction for simple tasks. Use them for output you're planning to use as a deliverable.
Multi-turn analysis: thinking through problems
The biggest productivity mistake with Claude: treating it like a search engine. You ask one question, get one answer, leave. That's 20% of the value.
Multi-turn analysis is the pattern of feeding Claude data over multiple messages and building to a conclusion. Here's the structure:
- Frame: Tell Claude what problem you're solving and what you need at the end
- Feed: Provide data, documents, or constraints one at a time
- Synthesize: Ask Claude to integrate everything and form a conclusion
- Challenge: Ask "what am I missing?" or "what's the strongest counterargument?"
- Finalize: Extract the output as an Artifact
Message 1 (Frame):
"I'm evaluating 3 vendors for our data pipeline. By the end of this
conversation I need a 1-page recommendation with a clear choice.
I'll give you the data in pieces."
Message 2 (Feed):
"Here's Vendor A's proposal: [paste]"
Message 3 (Feed):
"Here's Vendor B: [paste]"
Message 4 (Feed):
"Here's Vendor C. Also, our constraints:
- Budget cap: $50K/year
- Must integrate with Snowflake
- Team has no Spark experience"
Message 5 (Synthesize):
"Which vendor should we choose? Give me your recommendation
with reasoning, then list the 3 biggest risks of that choice."
Message 6 (Challenge):
"What's the case for Vendor B? Am I underweighting anything?"
Message 7 (Finalize):
"Write the recommendation as an artifact. Executive summary format.
One page. Decision + rationale + next steps."4 workflows you can run today
Before any important meeting, run this sequence:
- Paste the meeting invite or agenda
- "Who are the stakeholders and what do each of them likely want from this meeting?"
- "What are the 3 most important questions I should be prepared to answer?"
- "What questions should I ask to move the outcome I want forward?"
- "Write me a 30-second opening statement for this meeting as an artifact."
Turn raw notes or data into a polished report:
- Dump your raw notes: "Here are my notes from the past week on [project]. They're unorganized."
- "What are the 5 key themes here?"
- "Draft a status report for my manager using these themes. Executive summary + details. As an artifact."
- Iterate: "The second section is too technical. Rewrite for a non-technical audience."
- "Add a risks and next steps section."
For complex email threads:
- Paste the full email thread
- "Summarize what has been agreed, what is unresolved, and what I need to respond to."
- "Draft my response. Tone: [direct/diplomatic/urgent]. Goal: [what you want from this email]."
- Iterate until the draft is right, then copy it out
With filesystem MCP installed:
- "Read the files in /path/to/feature-branch and tell me what this feature does."
- "What are the top 3 issues with this code? Be specific with line references."
- "Are there any security concerns in how this handles user input?"
- "Write me a code review comment for the PR. Constructive, specific."
Complete a real work task end-to-end
Today's exercise is the most important one in the course. Pick a real task you were going to do this week and complete it entirely through Claude Desktop. Not a test task. An actual deliverable.
Good candidates:
- A report or document you've been procrastinating on
- A difficult email you're not sure how to write
- A decision you need to make with information you already have
- A code review or architecture review of something you've been putting off
Time yourself. Compare the result to how long it would have taken you without Claude. That delta is the return on the time you've invested in this course.
The mindset shift: Don't think of Claude as a tool you use for tasks. Think of it as a collaborator you work through. The conversation is the work environment. You direct, it executes, you refine. The output comes from the collaboration.
Complete before Day 5
- Run one workflow from the templates above on a real task
- Create at least one Artifact and iterate on it until it's deliverable quality
- Complete one full work task entirely through Claude Desktop — start to finish, nothing else open
- Note: what took the most prompts? What was surprisingly easy?
Tomorrow: the final day. Building custom MCP servers in Node.js — so Claude can connect to any tool you use.