Start with a recurring deliverable
A content team may spend too long turning interviews into a usable brief. An account manager may assemble the same monthly report from several systems. These are better starting points than asking everyone to experiment with a blank chat window.
Choose one deliverable, name its owner and keep an example of the current process. Record the inputs, time spent preparing and reviewing it, and the errors that matter. This creates a baseline for deciding whether the new workflow helps.
| Role | Assistant’s task | Person’s review |
|---|---|---|
| Account manager | Draft a report narrative from reconciled campaign measures and recorded decisions. | Check the figures, attribution limits and proposed explanations before sharing. |
| Content specialist | Turn an approved interview and source pack into a structured brief or draft. | Check expertise, factual claims, voice and the reader’s next step. |
| Delivery coordinator | Summarise approved project updates and list unresolved dependencies. | Confirm ownership, dates and whether an action has already been completed. |
Build a brief people can reuse
Give each task a small, maintained source pack: the audience, purpose, approved facts, brand guidance, examples and the expected format. Assign someone to keep it current. Separate client workspaces and check who can access uploaded material before adding client documents.
A useful content brief states the buyer’s question, the evidence available, the intended reader’s knowledge and the action the page supports. Ask for missing information to be identified. Do not let a draft turn an aspirational result into a customer claim.
- Task: prepare an outline answering one named buyer question.
- Sources: use only the attached, approved material for company and customer claims.
- Output: proposed sections, the evidence for each, unanswered questions and a relevant next step.
- Review: the subject expert checks accuracy; the editor checks clarity and usefulness.
Keep reporting definitions intact
Search Console clicks, Analytics sessions and advertising conversions answer different questions. Do not combine them into a single number without defining the relationship. Reconcile the data first, keep time periods consistent and label attribution differences.
Use the assistant to explain verified observations and draft follow-up questions. A fall in enquiries does not, by itself, establish that a headline caused it. The account owner should separate what the report shows from what the team still needs to investigate.
Teach the review, not just the prompt
Run a workshop on a real, approved task. Let team members compare the draft with the source material, correct it and explain their reasoning. Include an example with missing evidence so people practise stopping and asking for information.
Keep feedback with the workflow: what was wrong, what source resolves it and whether the template needs a change. Agree who can update that template. Repeated corrections are useful evidence for improving the process; they are not a reason to quietly lower the acceptance standard.
Add integration when the manual pilot proves useful
A shared workspace may be sufficient for an early pilot. If copying inputs becomes the bottleneck, scope a connector that retrieves only the required records. Keep draft creation separate from publishing, campaign changes and sending client communications.
For development work, Claude Code can assist with editing and testing a codebase. A generated change still needs the normal review and release process. Choosing a coding tool does not remove the need to test the website experience.
Measure useful adoption
Compare total effort per accepted deliverable, including corrections. Track unsupported claims, missed requirements and whether people continue to use the workflow. For marketing output, connect activity to qualified enquiries and useful customer conversations rather than publishing volume alone.
Discuss a similar workflow
Bring a description of the process, the systems involved and one example of where work gets stuck. We can use discovery to establish the requirements, dependencies and next step before preparing a solution and estimate. Please leave private customer, applicant and patient records out of the website enquiry.