How to use Claude well in one working afternoon.

Choose work that repeats and has a visible finish line.

Claude is easiest to manage when you can describe what “done” looks like. Begin with preparation, analysis or drafting—not a decision you would never hand to a new employee.

• Good first task: happens weekly, consumes time and produces a document, recommendation or organised set of actions.
• Weak first task: rare, poorly understood, politically sensitive or impossible to review.

Create a reusable Claude workspace.

Create one Claude Project for one function: customer support, marketing, sales proposals or weekly operations. Add only the current material that changes the quality of the work.

• Your current offer, audience and business priorities.
• The policy or procedure relevant to the job.
• Two or three examples you would happily use again.
• Project instructions covering tone, boundaries and required output.

Use one reusable brief for recurring work.

This Aenta framework packages the few details that most often separate a useful result from a generic answer.

• B — Business outcome: what should be true when the work is finished?
• R — References: which files, facts or examples should Claude use?
• I — Instructions: what steps, rules and boundaries apply?
• E — Example: what does good look like?
• F — Format: what must the finished output contain?

Business outcome: prepare a reply I can approve in under two minutes.
References: use the refund policy and tone guide in this Project.
Instructions: answer the customer's actual question. If the policy is unclear, write NEEDS REVIEW instead of guessing.
Example: match the approved replies in Project Knowledge.
Format: subject line, reply under 140 words, then a private one-line note explaining your reasoning. Do not send anything.

Manage the work through a short review loop.

Do not judge Claude by whether the first draft looks fluent. Judge it by whether the final result reaches your standard with less effort.

Before drafting, list any missing information and show me your plan. After drafting, check the result against the brief, identify the weakest part and revise it once. Flag every fact that needs human verification.

• Is every factual claim supported by the supplied material?
• Did it answer the business problem, not merely complete the wording?
• What is missing, unusually confident or inconsistent with your experience?
• Would you approve this if it came from a new employee?

Save the lesson where the next task can use it.

When the output improves, capture why. Update the Project instructions, replace the weak example, clarify the policy or save the finished prompt as a template. Claude can also place substantial reusable work in an Artifact.

Start with work you can inspect in minutes.

Approval is part of the workflow, not evidence the AI failed.

Claude can prepare consequential work, but the accountable person should still approve payments, legal or financial conclusions, employment decisions, public claims and promises to customers. Do not add sensitive client, employee or financial information unless your plan, permissions and business policies allow it.