Prepare the work
Select representative tasks, source documents, decision points, users, and the problems the team currently encounters.
Give one team a working method for ChatGPT and Claude.
A 2-to-4-week enablement program built around the department's real documents, decisions, recurring tasks, information boundaries, and review responsibilities.
A bounded program, not a one-hour demonstration.
The work starts before the workshop and continues long enough to see whether the method survives normal team use.
- Typical timeline
- 2 to 4 weeks
- Designed for
- One department or working group
- Finish line
- A shared method the team can operate without HAWT
The enablement program.
Training follows one representative workflow from source material to final review. The team practices the full method, not isolated prompt tricks.
Set boundaries
Define what information may enter the tools, what requires approval, and which outputs need human verification.
Work live
Use ChatGPT, Claude, or both to complete real exercises, inspect weak output, revise instructions, and assign review.
Review adoption
After practice, examine usage, corrections, questions, and workarounds before setting the next team standard.
What the team keeps.
The program ends with material the department can use, update, and teach to new employees.
Role-specific live session
Exercises and discussion tied to the department's own decisions, files, communication, and recurring work.
Reusable working kit
Tested instructions, source requirements, examples, expected outputs, and review checks for the selected workflows.
Information boundary guide
A plain-language record of what may be used, what needs approval, and what should stay outside an AI tool.
30-day adoption plan
Named owners, practice tasks, support questions, and the small set of signals the team will review after rollout.
Built around the department.
The program is configured around one team's actual work. It is not the same slide deck delivered to every audience.
Operations
Procedures, recurring reports, handoffs, document review, internal questions, and process records.
Marketing
Research, briefs, campaign planning, interview material, drafts, analysis, and review.
Product and support
User research, requirements, knowledge retrieval, response preparation, escalations, and quality checks.
Managers and leaders
Meeting material, planning, policy review, scenario analysis, and responsible team adoption.
Program scope
Use the tool. Keep the judgment.
Participants learn how to give useful instructions and how to inspect the result. A named person still owns facts, commitments, approvals, and the final work.
Start a training brief- Tools
- ChatGPT, Claude, or a structured comparison
- Delivery
- Remote across the United States; local by arrangement
- Facilitator
- Certified Claude trainer with 15+ years of software experience
- Participant access
- Account requirements confirmed before the program begins
Clear instructions
Goal, context, constraints, source material, and required output.
Source review
Compare, verify, and cite important information rather than accepting fluent output as fact.
Files and documents
Work with reports, policies, spreadsheets, PDFs, notes, and longer reference material.
Repeatable review
Turn one good result into a method other employees can follow and inspect.
Not included
This engagement does not create company-wide AI policy, select and procure an enterprise platform, or build custom production software. Those needs can be scoped separately after the training evidence is reviewed.
Program questions.
Can we use our own workflows and documents?
Yes. That is the point of the program. HAWT first helps the team decide what material is appropriate to use and what should remain outside the tools.
Can we train several departments at once?
A shared introduction can include a larger group, but the working program is strongest when one department can practice against the same responsibilities and source material.
Do participants need paid accounts?
Not always. The required plan depends on the tool and exercises. HAWT confirms access requirements before the live session.
What happens if training reveals a software gap?
The findings can become the starting point for a separate Workflow Pilot. Development is not added to the training scope without a new brief and decision.
Bring one team and the work it owns.
Share the department, current tools, recurring work, and any privacy or approval constraints.