Claude Co-work

Five modes. Drafting: Claude writes for you. The most common, but only the beginning. Analyzing: you give Claude a document or situation, it breaks it down. What are the patterns? What's missing?

Thinking together: you're not asking for a deliverable. You're asking Claude to think with you about a problem. The trade-offs, the angles, the things you're not seeing.

Challenging: you give Claude your plan and ask it to find the weaknesses. "What am I missing? Where could this fail?" Claude is remarkably honest when you ask it to be.

Teaching: you ask Claude to help you understand something, at your level, with examples from your domain.

Most people only use mode one. The other four are where the real value lives.

Try This Now

Think about the last five times you used Claude. Were they all drafting? Pick one of the other four modes and try it now with a real work situation.

A regular conversation is temporary. A Project is permanent. Every conversation starts with your context already loaded.

How to set up a Project that works: The identity. Who Claude is in this project. Specific, not generic. The rules. What to always do and never do. The reference material. Documents Claude needs. The format preferences. How you want output.

The investment is 30 minutes of setup. The return is months of work with a partner who knows your business.

The difference between a well-configured Project and a regular conversation is like the difference between working with a new hire and a trusted colleague who's been with you for years.

Try This Now

Create a new Project for your most important current work area. Spend 15 minutes writing real custom instructions. Upload three key documents. Compare the quality to a regular conversation.

Upload for voice matching. Three to five examples of your best writing. Claude internalizes your style. Upload for analysis. Competitor materials. Then ask Claude to find their positioning strategy and identify gaps.

Upload for process. Your SOP, your checklist. Now Claude applies your methodology to new situations. Upload for context. Meeting transcripts, project histories. Claude uses these to understand the full picture.

The structure matters. Well-organized documents with headers work dramatically better than messy ones. A 5-page structured document beats a 50-page brain dump.

Claude reads PDFs, Word docs, text files, spreadsheets, images. It can even read screenshots of whiteboards.

Try This Now

Upload a competitor's pitch deck to Claude. Then upload yours. Ask: 'Compare these. Where is the competitor stronger? Where am I stronger? What opportunity am I missing?' The answer will surprise you.

A productive conversation follows five phases. Set the stage: give Claude the context for what you're working on right now. Get the first draft: ask for what you need, be specific.

React honestly: say exactly what works and what doesn't. Not "good" or "not good." Specific feedback.

Go deeper: after the revision, push further. "Read this as a skeptical board member. What questions would you ask?" This is where most people stop. Don't.

Extract the method: "What was our process here? Can you describe it as a reusable template?" Now you have a repeatable approach.

Phases 4 and 5 are where the value multiplies. The difference between mediocre and exceptional is going past the first good enough result.

Try This Now

Start a conversation about something you're working on. Go through all five phases. Don't skip 4 and 5. Compare the final output to what a single prompt would have given you.

Most people ask Claude to "improve" their writing. That's buffing, not editing. Real editing is about what to cut, restructure, and what's missing.

Structural editing: "Don't change the words. Tell me: is the argument logical? Are sections in the right order? What's redundant?"

Audience editing: "Read this as [specific person]. What confuses you? What makes you stop reading?"

Compression editing: "This is 2,000 words. Get to 800 without losing any key argument. Show me what you cut and why."

The red team: "You are my toughest critic. Find every weakness, every unsupported claim, every gap. Be direct."

Stack these: structural first, then audience, then compression. Three rounds produces writing that feels professionally edited.

Try This Now

Take something you wrote recently. Try the red team: 'Find every weakness, unsupported claim, and logical gap. Be direct.' Fix the piece yourself using the feedback.

When was the last time you used Claude to think about a problem without producing a deliverable? For most people: never. That's the biggest missed opportunity.

Decision support: "I'm considering three options. Walk me through the trade-offs. What am I not seeing?"

Scenario planning: "We're launching in three months. Give me three scenarios: as planned, better than expected, things go wrong. What should we do now for each?"

Devil's advocate: "I've decided to do this. I'm confident. Now argue against it. Give me the three strongest reasons this is a mistake."

Pattern recognition: upload several documents and ask: "What patterns do you see across these? What's the thread?"

In these conversations, you're not delegating. You're expanding your own thinking.

Try This Now

Take the hardest decision you're facing. Open Claude. Say: 'I need to think through a decision. Don't give me an answer yet. Help me understand what I'm actually deciding.' Spend 10 minutes. Notice if your thinking changed.

A Claude system is a set of Projects covering your core work. Each tailored, loaded, ready.

Example for a marketing director: Project Strategy (competitive analysis, company strategy uploaded). Project Content (brand guidelines, tone of voice, best content examples). Project Presentations (template, previous decks, audience profiles). Project Analysis (KPI definitions, previous reports).

Four projects. Each 20-30 minutes to set up. The result: a personal AI department that knows your work, standards, and voice.

Maintenance: review monthly. Update reference files. Refine instructions. A maintained system gets better over time. A forgotten one degrades.

Try This Now

Map your work into 3-4 areas. You probably have one Project already. Create a second one. Invest 20 minutes in setup. By the end of the week, have two Projects you use daily.

Strengths: long nuanced reasoning, following complex instructions, working with large documents, maintaining consistency across long conversations, being corrected without ego.

Weaknesses: no real-time information (can't browse the web), no image generation (use ChatGPT/Midjourney), sometimes over-thinks simple tasks, can't execute code, not a therapist.

Where Claude goes next: it gets better every few months. Your Projects and instructions will produce better results over time without changing anything.

If you're bumping against limits regularly, your needs have outgrown browser-based AI. Assisted Coding is for building without limits. Studio Hyra is for having someone else build it right.

Try This Now

Think about when Claude last disappointed you. Was it a genuine limitation or did you not give enough context? Most failures are the second one. Address it accordingly.