Claude theo vai trò — Use cases by role

Áp dụng thực chiếnCơ bản15 phút

10 bài vừa qua, bạn đã học một loạt features: Projects, Artifacts, Skills, Connectors, Research, Enterprise Search. Mỗi feature đều powerful.

Bạn sẽ học được
  • Mô tả 2-3 use cases cho Claude.ai bạn có thể thử ngay tuần này
  • Biết nơi tìm thêm inspiration cho use cases khác
  • Map được những feature đã học (Projects, Skills, Connectors, Research) vào workflow cụ thể của role mình
  • Identify 1 use case cao-ROI để dedicate ngày làm việc đầu tiên sau course

Cấu trúc bài

Mỗi role ở dưới sẽ có:

Scan qua → tìm role gần nhất với bạn → pick 1 use case → thử tuần này.

  • Top 3 use cases cao-ROI (được sắp xếp theo thứ tự priority)
  • Features liên quan (Projects / Artifacts / Skills / Connectors / Research)
  • Link tới Use Case Gallery cho step-by-step guide chi tiết

General professional (áp dụng đa role)

Những use cases apply across nhiều role + industries. Bắt đầu ở đây nếu role bạn không fit 1 category đơn lẻ.

1. Generate project status reports

Pain: Viết weekly/monthly status báo cáo stakeholders — tổng hợp từ 5+ sources, consistent format khó maintain.

Solution:

Impact: 3 giờ → 20 phút/báo cáo.

2. Analyze patterns trong user feedback

Pain: Customer feedback rải rác Zendesk tickets, NPS surveys, app store reviews. Insights buried.

Solution:

Impact: 2 ngày → 3 giờ analysis.

3. Package brand guidelines thành skill

Pain: Team write content inconsistent voice — brand guide 40 trang không ai đọc.

Solution:

Impact: Brand consistency across team. Onboarding thời gian giảm.

Use Case Gallery: claude.com/resources/use-cases

  • Project: "Status Report Hub" chứa template, past reports, stakeholder preferences
  • Connectors: Asana/Jira (task status), Slack (decisions), Gmail (communications)
  • Skill: weekly-status-generator — pull sources, format theo template
  • Research mode: synthesize across sources
  • Prompt: "Pull feedback 90 ngày qua. Cluster themes. Rank theo frequency. Provide representative quotes. Identify emerging (new 30 ngày qua) vs. persistent."
  • Custom Skill: brand-voice-review — apply guidelines automatically
  • Input: content draft → output: deviations highlighted + suggested rewrites

💼 Sales

Sales chuyên accelerate deal preparation, create compelling materials, stay on competitive intel.

1. Build battle card library

Pain: Rep thiếu tips deal với competitors. Lose deals vì không handle objections tốt.

Solution:

Impact: Win rate vs. key competitors tăng measurable.

2. Prepare cho sales deals

Pain: Prep cho demo/call mỗi khách hàng tốn 30-45 phút research.

Solution:

Impact: 45 phút → 5 phút/deal.

3. Create sales reports

Pain: Weekly pipeline report — pull data manually, format, send.

Solution:

Impact: 2 giờ/tuần → 10 phút review.

Links:

  • Project: "Competitive Battle Cards" với profile từng competitor
  • Research mode populate: feature comparison, pricing, review themes, common objections
  • Skill: battle-card-generator update cho competitor mới
  • Connectors: Salesforce + Gmail + LinkedIn (nếu enabled)
  • Skill: deal-prep — pull account history, contact background, recent news, talking points tailored
  • Output format: 1-page briefing
  • Scheduled Task (Cowork): Every Friday 4pm pull Salesforce → format → email/Slack leadership
  • Skill: pipeline-report standardize output
  • Build battle card library
  • Prepare cho sales deals
  • Create sales reports

📣 Marketing

Marketers leverage Claude cho analyze performance, repurpose content efficiently.

1. Analyze campaign performance

Pain: Campaign metrics scattered across HubSpot, GA, ad platforms. Insights late.

Solution:

Impact: Real-time anomaly detection. Catch issues < 24 giờ.

2. Adapt content across platforms

Pain: 1 blog → 5 channel format (LinkedIn, Twitter, email, slides, Instagram). 3-4 giờ/piece.

Solution:

Impact: 4 giờ → 30 phút.

Links:

  • Connectors: HubSpot / Marketo, Google Analytics, Meta Ads, LinkedIn Ads
  • Scheduled Task: Daily 9am pull metrics → compare baseline → flag anomalies → Slack digest
  • Skill: content-repurposer apply channel-specific rules
  • Project: Brand voice + examples each channel
  • Analyze campaign performance
  • Adapt content across platforms

💰 Finance

Finance builds models, drafts documents, makes sense complex spreadsheets.

1. Build financial models

Pain: DCF, scenario analysis, sensitivity tables — tốn ngày build từ đầu.

Solution:

Impact: Days → hours.

2. Draft investment memos

Pain: Structure + write memos cho IC/stakeholders 4-8 giờ.

Solution:

Impact: 8 giờ → 2 giờ.

3. Understand + extend inherited spreadsheet

Pain: Someone leaves, inherit 8-sheet Excel bạn không hiểu.

Solution:

Impact: Understanding thời gian hours → 20 phút.

Links:

  • Artifacts: Excel artifact với dynamic inputs
  • Skills: dcf-model-builder, scenario-analysis apply company methodology
  • Project: "Investment Memos" — past memos template, frameworks
  • Skill: invest-memo-drafter apply company format
  • Research: competitor + market data
  • Claude for Excel — sidebar trong actual Excel
  • Prompt: "Explain flow. What Sheet 3 dependencies? Trace formula errors."
  • Build financial models
  • Draft investment memos
  • Understand inherited spreadsheet

👥 HR / People Ops

HR teams create better onboarding experiences + documentation.

1. Create new hire onboarding guides

Pain: Custom onboarding kit mỗi new hire — 2-3 giờ customize.

Solution:

Impact: 2-3 giờ → 20 phút per hire.

Links:

  • Project: "Onboarding Central" với role-specific resources
  • Skill: onboard-role take role input → generate personalized kit
  • Artifact: Interactive checklist HTML với progress tracking
  • Create new hire onboarding guides

⚖️ Legal

Legal teams track complex timelines, manage discovery processes.

1. Track discovery timelines + analyze patterns

Pain: Case discovery — thousands docs, complex timeline, patterns hidden.

Solution:

Impact: Weeks → days of discovery analysis.

Links:

  • Project: case-specific với all documents
  • Research: synthesize across documents
  • Prompt: "Build timeline of events from documents. Identify patterns (recurring players, decision shifts). Flag inconsistencies."
  • Track discovery timelines

🔍 Research

Researchers plan literature reviews + verify data analysis.

1. Plan literature review

Pain: 80+ papers cho review — catalog, themes, gaps — weeks.

Solution:

Impact: 3 weeks → 1 week.

2. Verify statistics từ raw data

Pain: Check whether analyst's numbers are right → need reproduce analysis.

Solution:

Impact: Confidence validated. Errors caught trước ship.

Links:

  • Project: folder papers
  • Research mode: phase-based (catalog → themes → gaps)
  • Skill: lit-review-assist apply your methodology (PRISMA, narrative, etc.)
  • Claude for Excel hoặc Claude Code với data file
  • Prompt: "Here's data + analyst's conclusions. Reproduce analysis. Flag any discrepancies."
  • Plan literature review
  • Verify statistics

🛠️ Product

1. Synthesize user research

Pain: 50 user interview transcripts → insights → themes → weeks đọc.

Solution:

Impact: 3 ngày → 3 giờ.

2. Write PRDs

Pain: PRD format consistent, pull từ engineering specs, user research — hours.

Solution:

Impact: 3 giờ → 30 phút draft.

3. Generate product metrics report

Pain: Weekly product metrics across Amplitude, Mixpanel, GA.

Solution:

Impact: 4 giờ → 15 phút review.

  • Project: all transcripts
  • Research: cluster themes automatically
  • Artifact: interactive theme map
  • Project: template + past PRDs
  • Skill: prd-drafter
  • Connectors: Jira (engineering), research tool
  • Connectors + scheduled task
  • Output: unified dashboard + anomaly flags

🎧 Customer Support

1. KB-powered ticket response

Pain: Find relevant KB article cho each ticket — slow manual search.

Solution:

Impact: 15 min → 5 min/ticket.

2. Customer sentiment tracking

Pain: Weekly ticket trend analysis manual.

Solution:

Impact: 1 ngày → 30 phút.

  • Connectors: Zendesk + Confluence/Notion KB
  • Skill: ticket-triage — scan, retrieve KB, draft response
  • Scheduled task: categorize tickets, cluster themes, flag emerging

🎓 Education / Training

1. Grade essays với rubric

Pain: 30 essays/tuần — consistency + individualized feedback struggle.

Solution:

Impact: 6 giờ → 2 giờ.

2. Design curriculum module

Pain: Standards alignment + learning objectives + assessments — 2 tuần.

Solution:

Impact: 2 tuần → 3-4 ngày.

  • Skill: rubric-scorer first-pass scoring
  • Teacher polish + personalization final 30%
  • Project: standards + past modules
  • Skill: backward-design (outcomes → assessments → activities → content)

🏢 Real Estate

1. Listing presentation customization

Pain: 3-4 giờ customize per client.

Solution:

Impact: 4 giờ → 30 phút.

2. Deal screening

Pain: Evaluate 50+ properties client criteria — 3 ngày.

Solution:

Impact: 3 ngày → 4 giờ.

  • Skill: listing-prep pull comps, neighborhood data, personalize
  • Artifact: interactive presentation
  • Cowork với subagents: parallel screening
  • Output: ranked top 10 với detailed analysis

📊 Data / Analytics

1. Ad-hoc request SQL

Pain: Stakeholders request random analyses. Translate → SQL → run → format → explain.

Solution:

Impact: 2 giờ → 20 phút/request.

2. Dashboard documentation

Pain: Document existing dashboards for handoff.

Solution:

Impact: 3 ngày → 6 giờ.

  • Skill: analyze-request — business question → SQL → run → format + narrative
  • Connector: PostgreSQL/Snowflake/BigQuery
  • Skill: dashboard-docs — auto-document queries, relationships, business logic

🏥 Healthcare

1. Patient records consolidation

Pain: Aggregate lab, imaging, notes — 30 phút/patient.

Solution:

Impact: 30 min → 5 min/patient.

2. Clinical study report drafting

Pain: CSR standardized format, need expert content.

Solution:

Impact: 6 tuần → 3 tuần.

  • Skill: patient-record-aggregator — timeline-based + flag abnormal
  • Note: HIPAA considerations — Enterprise plan với BAA
  • Skill: csr-drafter template-driven
  • Flag sections need expert review

🏭 Operations / Supply Chain

1. Vendor performance review

Pain: 50+ vendors, multi-metric quarterly.

Solution:

Impact: 1 tuần → 2 ngày.

2. Weekly project status aggregation

Pain: 5+ projects status pull manually.

Solution:

Impact: 4 giờ → 30 phút review.

  • Skill: vendor-scorecard consistent framework
  • Output: scorecards + ranking + remediation plan
  • Scheduled task Cowork
  • Connectors: Asana/Jira + Slack + Gmail

👔 Executive Assistant / Chief of Staff

1. Daily executive brief

Pain: Prep boss full day — calendar, emails, travel.

Solution:

Impact: 2 giờ prep → 15 phút review.

2. Board meeting prep

Pain: Compile reports từ multiple dept heads.

Solution:

Impact: 1 tuần → 2 ngày.

  • Scheduled task daily 7am morning brief
  • Skill: exec-morning-brief
  • Project: board template + submission forms
  • Skill: auto-aggregate

Cách chọn use case để start

Không thử 10 cái cùng lúc. Pick 1 → implement fully → measure → then add next.

Scoring framework

Rate mỗi candidate use case (1-5):

Score = sum. Start với top score.

Ví dụ

Use case A: Daily morning brief

Use case B: Q-end variance memo

Choose A first. Bigger cumulative impact over time.

  • Frequency: 5/tuần × 3 = 15
  • Time saved: 30 phút × 2 = 60
  • Setup: 4 (medium) × 1 = 4
  • Variability: 5 (consistent) × 2 = 10
  • Total: 89
  • Frequency: 0.25/tuần × 3 = 0.75
  • Time saved: 2 hours × 2 = 4
  • Setup: 3 × 1 = 3
  • Variability: 5 × 2 = 10
  • Total: 17.75
CriterionWeight
Frequency (lặp lại bao nhiêu/tuần)× 3
Time saved per instance× 2
Setup effort (1=high, 5=low)× 1
Variability (1=mỗi lần khác, 5=consistent)× 2

Anti-patterns

❌ Try every feature at once

Biểu hiện: Week 1 try Projects + Skills + Connectors + Research + Artifacts simultaneously.

Tại sao sai: Cognitive overload. Nothing used deeply.

Cách đúng: 1 use case, 1-2 features. Master before expand.

❌ Generic use case "AI will save time"

Biểu hiện: "I'll use Claude cho emails." (No specificity)

Tại sao sai: Success undefined. No measurable output.

Cách đúng: Specific use case với measurable outcome. "Weekly pipeline report — goal < 30 min review thay vì 2 hours."

❌ Start với hardest

Biểu hiện: Try to automate most complex workflow first.

Tại sao sai: Fail early discourage.

Cách đúng: Start với medium complexity, high frequency. Quick wins build confidence.

❌ Không share với team

Biểu hiện: Personal skill/project useful → keep to self.

Tại sao sai: Scaling benefits limited.

Cách đúng: Share templates, skills, projects với team (Team/Enterprise plans). Impact nhân lên theo số thành viên dùng.

Áp dụng ngay

Bài tập 1: Score your top 3 use cases (15 phút)

Quay lại danh sách Bài 01. Với top 3 pain points, score theo framework trên:

Pick highest score = first use case to implement.

Bài tập 2: Implementation plan cho use case #1 (15 phút)

Fill in:

Use case #1: __________
Frequency × 3: ___
Time saved × 2: ___
Setup × 1: ___
Variability × 2: ___
TOTAL: ___

Use case #2: __________
(same scoring)

Use case #3: __________
(same scoring)

Bài tập 2: Implementation plan cho use case #1 (15 phút)

Bài tập 3: Browse Use Case Gallery (10 phút)

Visit claude.com/resources/use-cases.

Filter theo role. Pick 2 cases không trong bài này apply cho role bạn.

Save links. Reference sau.

Use case: _______________

Features cần:
- [ ] Project: ________
- [ ] Skill: ________
- [ ] Connector: ________
- [ ] Artifact: ________
- [ ] Research: ________
- [ ] Scheduled task: ________

Setup effort estimate: ___ hours
Expected time saved/week: ___

Week 1 goal: [complete basic setup]
Week 2 goal: [iterate prompt, refine]
Week 4 goal: [report: avg time saved? user satisfaction?]

Success metric: ________

Tóm tắt bài học

🎯 Map features → workflow concrete — kiến thức nằm trong role-specific use cases. Abstract feature knowledge = không impact.

🎯 Pick 1 use case đầu tiên, master nó — 1 use case deep > 10 use cases shallow. ROI compound over time.

🎯 Score framework (Frequency × 3) + (Time saved × 2) + Setup + (Variability × 2) → rational prioritization.

🎯 Features combine: Projects + Skills + Connectors — single features limited. Combined → workflows completely transform.

🎯 Use Case Gallery là inspiration bank — browse, save, reference. New ideas mỗi lần visit.

🎯 Team > individual — shared Projects/Skills nhân tác động theo số thành viên. Start personal, rồi scale team khi ổn định.

Tài liệu tham khảo
  • Use Case Gallery (complete) — full list step-by-step
  • Role-specific blog posts — customer stories
Nội dung này có hữu ích không?