Choose the surface that matches the work
You will identify the right product and write a bounded brief, without installing or connecting every product. Outputs are illustrations.
Sources checked September 30, 2026 describe three distinct products: M365 add-ins inside Office apps, Claude Tag in Slack and Claude Science as a desktop research workbench. None is simply another button in ordinary Web chat.
M365: work inside the file
The official overview describes Claude for Excel, PowerPoint, Word and Outlook: cells/formulas, slides/templates, documents/tracked changes and inbox/thread work. It also describes shared conversation state across those apps. Deployment and access vary by app and administrator setup; Outlook requires an administrator Graph-consent step.
Practice with a copy of a fictional spreadsheet, not a production workbook. A useful Excel brief:
In this practice workbook only, inspect quantity and unit-cost columns.
Propose row-total formulas and a grand total before editing.
Do not send email, connect services, overwrite the original or publish.
Flag missing inputs instead of inventing prices.
Expected proposal:
Row totals: quantity × unit cost.
Grand total: SUM of row totals.
Missing prices: list the actual empty cells.
No email or publication is needed.
After an explicitly reviewed edit, inspect formulas, recalculation and presentation inside the file. Cross-app continuity does not authorize sending a workbook through Outlook.
Claude Tag: work visible in a team channel
Tag is documented in public beta for first-party Team and Enterprise, not personal plans or third-party deployments. Administrators pair Slack and configure channel/workspace access. Channel work uses organizational usage billing, while DMs follow the sender's account limits according to the source.
Do not create a real installation for this conceptual exercise. If your organization already provides Tag, first inspect its configured channel scope. A shared thread is a shared audience, not a private scratchpad.
Draft before posting:
@Claude using only this practice thread, summarize decided items and open questions.
Do not access connected services, create tickets, send messages elsewhere or schedule follow-ups.
Keep proposals separate from decisions and cite supporting messages.
Review destination and wording before posting. Even a trial channel request can consume organizational usage. A channel-level tool bundle is different from your personal Web connectors. Do not assume an individual connector's permissions govern channel work.
Claude Science: reproducible analysis, not clinical advice
The source describes a beta desktop application on macOS and Linux, requiring an eligible paid account and organizational enablement where applicable. It runs analysis code with approved folders, hosts and remote jobs, and retains versioned artifacts/provenance.
Use fabricated or public test data. A planning brief:
For this fictional CSV, propose an analysis of missing values and summary statistics.
List input columns, assumptions and checks before running anything.
No remote jobs, external database queries or clinical conclusions.
Preserve source data and distinguish calculations from interpretation.
Expected structure: input description, missingness check, proposed statistics, assumptions and a reproducible output plan. A reviewer can compare claims with execution records; the documentation says it does not rerun analyses and cannot eliminate errors. Verify results before research or publication. Science is not intended for diagnosis or clinical use.
One decision table before setup
Ask yourself: is the deliverable an Office file, shared Slack work or reproducible research? Identify account, audience, inputs, permissions, costs and result checks. If ordinary chat plus an uploaded copy suffices, do not add an enterprise deployment.
Compare these three routes for my stated task.
Separate what can be learned without setup from what needs admin access or billing.
Recommend the smallest suitable route. Do not install, connect or purchase anything.
Graded practice
Easy: choose a surface
Match formula editing, thread summary and reproducible analysis to the three products. Success: explain why, not merely name a brand.
Intermediate: bounded brief
Write one draft brief. Success: inputs, output, audience and forbidden effects are explicit.
Challenging: review a setup proposal
Identify account access and possible usage charges in a proposed setup. Success: do not mistake installation or membership for spending or disclosure permission.
Troubleshooting
Feature missing: inspect product, plan, beta and administrator enablement.
Wrong audience: stop before posting or cross-app sending.
Analysis looks convincing: inspect provenance, source data and calculations.
Connection requested too broadly: use copies or defer setup rather than widening access casually.
Billing unclear: research the product-specific route before running a paid trial. This lesson does not authorize spending.