Empower
Audience · New Empower staff45 min · hands-onLast reviewed 2026-04-24

First Day with Claude — a 45-Minute Sprint

You've been given a Claude account. You've read that this tool will save you time. But you've also been burned by shiny tools before that never quite clicked. This sprint is designed to get you to one real win inside 45 minutes — not a theoretical one, an actual piece of work that lands better because Claude helped.

You will:

  1. Install Claude and sign in (5 min)
  2. Try one real task in plain chat (10 min)
  3. Fix what didn't work about that attempt (10 min)
  4. Set up your first Project (15 min)
  5. Decide what you'll do tomorrow (5 min)

Do it in one sitting. No background reading required — links below the sprint if you want to go deeper.


Minutes 0–5: Install and sign in

  1. Go to https://claude.ai/download (for desktop) or install from the App Store / Google Play (for phone).
  2. Sign in with your Empower email. If you've received a workspace invite email, accept it first — the invite link lands you in the Empower workspace instead of a personal one.
  3. Confirm you see "Empower" (or whatever your workspace is named) in the top-left corner of the app.

Stuck? See Lesson 03 — Install Desktop or Lesson 04 — Install Mobile.


Minutes 5–15: Try one real task

Pick one thing from the list below that matches your day. Do it now. Real content, not a toy example.

  • Have an email to send that you're not looking forward to writing? Paste the rough idea into a new Claude chat. Tell Claude who it's going to, what you need to communicate, and what tone you want. Read the draft. Send.

  • Have a long document you need to understand? Paste it in (or attach the file). Ask: "Summarize this in 3 bullets. Flag anything that would surprise me."

  • Have a meeting later today? Ask Claude: "I have a meeting later today with {who} about {topic}. What 5 questions should I be prepared to answer? What 3 questions should I ask?"

  • Have rough notes from a meeting that already happened? Paste them in. Ask: "Clean these up into: attendees, summary, decisions, and action items by owner. Don't add anything that wasn't in my notes."

Don't skip this. Reading about Claude and using Claude feel completely different, and only one of them produces value.


Minutes 15–25: Fix what didn't work

Something in the above response probably wasn't quite right. Too long, wrong tone, missed a key point, too generic.

That's the most important moment in this sprint. Don't start over from scratch. Instead, follow up in the same conversation with a correction:

  • "This is too long. Cut it in half without losing the core point."
  • "This is too formal — rewrite with the same content but warmer."
  • "You missed X. Add a paragraph addressing that specifically."
  • "The second bullet isn't right — here's what I actually meant: {clarification}."

Notice how Claude keeps the rest and just adjusts. That's the habit: iterate, don't restart. It's the single biggest difference between people who get value from Claude and people who give up on it.

If you want to understand why vague prompts produce vague answers, skim Lesson 19 — Common Pitfalls after this sprint.


Minutes 25–40: Set up your first Project

A Project is a saved workspace. You give Claude context once and every conversation inside that Project picks it up.

  1. In the left sidebar, click Projects → New Project (or the "+" icon).

  2. Name it after the recurring task you just did. For example: "Email Drafts," "Meeting Cleanup," "Proposal Review."

  3. Open the Project's Custom Instructions / Project Instructions field.

  4. Paste this and fill in the bracketed placeholders:

    I am a {role} at Empower. When I paste {what you typically paste}, do the following:
    1. {first priority — e.g., "give me a two-sentence summary"}
    2. {second priority — e.g., "recommend an action"}
    3. {third priority — e.g., "if I ask for a draft, match a direct, professional tone"}
    
    Keep responses concise. Do not {one thing you don't want — e.g., "add corporate filler phrases"}.
    
  5. Save.

  6. Start a new chat inside the Project and run the same task you did in minutes 5–15. Compare the quality of the response to the plain-chat version.

If you want the long version of how to write system prompts, read Lesson 07 — System Prompts later. For now, a 4-line draft is enough.


Minutes 40–45: Decide what you'll do tomorrow

Don't just close the app and hope the habit sticks. It won't.

Pick one thing, concrete and small:

  • "Tomorrow morning, I'll paste my inbox backlog into Claude and ask for a triage summary before I respond to anything."
  • "Every meeting I'm in this week, I'll dictate a voice note to Claude within 15 minutes of it ending."
  • "Next proposal that comes in, I'll run it through my Project before I read it myself."

Write your commitment somewhere visible. The habit needs one anchor to form.


If it didn't click

Two common reasons, both fixable:

  1. The task you picked didn't have a clear output. Claude shines at drafting, summarizing, and reformatting. If you asked it something open-ended like "help me think about strategy," results are fuzzier. Pick something concrete tomorrow.

  2. You gave Claude too little context. Vague prompt → vague output. Before you give up, try the same task with three more sentences of context about your role, the audience, and what "done" looks like.

If neither helps, read Lesson 19 — Common Pitfalls — seven reasons people quit after two weeks, and exactly what to do about each.


What comes next

  • Today or tomorrow: read the quick-start that matches your role — Executive, Account Manager, Operations, Field Team, or Admin. Three minutes.
  • This week: skim the Prompt Library for 20 copy-paste prompts you can start using immediately.
  • This month: work through the Foundation track in the sidebar, in order. ~60 min total.

You've done the hard part. Day one is the hardest day.