Pete Hazzard describes learning across generations through a project close to home. After years of encouragement to write a book, he used time during COVID to work on it. His son, Cam Hazzard, supported the process and helped him work with AI assistants and build a website.
Pete tells the story in an Athlete Spotlight interview with Dennis Yu. For an experienced professional learning new tools, the useful detail is how the collaboration formed around work Pete already wanted to do.
Choose a project with a clear owner and reader
Pete’s background includes years as a band director and work in fine-arts administration. The writing came from an educator with experience to share. The website was a way to extend that work.
That gives a collaborator a clearer starting point than a broad request to learn AI. There is something specific to work on, a person who understands the subject, and an audience the finished material needs to serve.
For a local business owner, the equivalent might be a recurring customer question or an explanation of a job they have completed.
Write a short brief in ordinary language: who the reader is, what question they have, what experience supports the answer, and what they should be able to do after reading. A real example is more helpful here than an abstract request to improve marketing.
Suppose a service owner repeatedly explains why two repair estimates differ. A useful first article could show the factors the owner actually considers. The collaborator can record the explanation, organize it and prepare a draft. The owner checks whether the distinctions survived. This is an illustrative starting project, with a result both people can inspect.
Make room for different kinds of expertise
Cam brought familiarity with tools Pete was learning. Pete brought the writing and experience behind the project. He says Cam helped him interact with AI assistants and was integral to helping him build a website.
Our earlier account of Cam’s personal-brand website build covers how recorded expertise can become an organized public presence. This conversation shows Cam contributing from the other side, helping his father with his own work.
The relationship also stayed mutual. Pete says he and Cam could take coaching from one another. Dennis’s article on reciprocal coaching between father and son explores that part of the conversation.
Use a rehearsal-sized learning loop
Pete’s public book summaries describe leadership through an ensemble: communication, coordination and collaboration shape the performance. That offers a useful way to think about a working session. Agree on one passage of the project, work through it, listen to the result and make the next correction.
A first session can follow a manageable sequence:
- Record the experienced person explaining one real question.
- Have the collaborator organize that explanation into a draft.
- Ask the experienced person to check the facts and meaning.
- Open the result on a phone and test the next step.
- Write down the correction that will matter next time.
The size of the first task matters. One complete page teaches the team more about its workflow than a large folder of unfinished outlines. It exposes where the subject expert needs to review, what the collaborator can handle and which inputs were missing.
Show the younger collaborator how to understand the business
In his account of Cam as a young AI operator, Dennis describes the division behind Cam’s own site build: real skills and stories supplied the material, while the team organized it into a findable presence. He emphasizes judgment about what should be published.
A younger collaborator can learn that judgment by spending time with the work itself. Have them listen to the questions customers ask. Explain why a detail changes the answer. Show an example of a common misunderstanding, and the evidence that resolves it. These inputs help the collaborator recognize what matters before they begin editing.
The experienced owner can learn in the other direction. Ask the collaborator to demonstrate one part of the system rather than doing every step invisibly. Reviewing a draft, finding the source recording and checking a page on a phone are useful skills to share. That makes future corrections easier for both people.
Check the work after the tool helps
A professional trying this approach can begin with one source: a useful explanation, a draft or a recorded conversation. Have the collaborator demonstrate one step, then review the result together. Check the facts, meaning and next action before extending the workflow.
That is consistent with the Content Factory production process: start with real source material and turn it into useful pieces for a defined audience. The tool helps with the work; the people still need to judge the result and give each expertise-led article a clear reader purpose.
Give review a practical definition of finished
A draft becomes useful when someone can rely on it. Check the person’s name, the example, the service explanation and the link that follows it. Read the page as a new customer would. If the article asks the reader to download something, open the download. If it links a related explanation, confirm that the explanation answers the question implied by the link.
Keep a copy of the previous version when updating existing material. Record what changed and who reviewed the subject matter. These simple habits let the team correct an error without reconstructing the whole project.
Pete also hosts The Conductor’s Circle, whose public description includes guided conversations, peer learning and practical leadership challenges. It reflects a broader theme in his work: people learn through a real problem and a useful exchange with others.
Measure whether the collaboration helped
Start with the purpose in the original brief. Can a customer now find a clear answer? Can the owner make a routine correction without starting over? Did the team finish a usable piece, and what would make the next one easier?
For a business, later measurement can include relevant visits, completed inquiries and the quality of those inquiries. Keep those results separate from the fact that the page exists. This interview supplies a starting example of people helping each other learn; the value of a new business workflow has to be demonstrated in the work it produces.