The AI Playbook for Creative Workflows

A practical playbook for running creative work with an AI coworker, from project knowledge and first ideas to review, platform versions, and delivery.

Your team has a YouTube video in review, two Instagram edits waiting on feedback, and a TikTok concept the client wants to change. Someone has already used AI to draft the scripts. Someone else has generated more ideas. The producer still needs to work out which direction is approved and what everyone should do next.

An effective AI creative workflow carries the context through that entire process. The brief informs the ideas. Decisions become assignments. Feedback stays with the right version. Each deliverable has a clear state, and the next project benefits from what the team learned.

In FridayHQ, Xander participates as a coworker across that work. Project knowledge provides a foundation for decisions, while content, tasks, and conversations give Xander the context to help your team move forward. You can ask for creative input, coordinate assignments, or check what is holding up a release in the same workspace. Explore FridayHQ.

Here is a practical playbook for putting that approach to work.

Start with the goal and the knowledge behind it

Before asking for ideas, define the outcome. A campaign designed to explain a new product needs a different brief from a series designed to entertain returning viewers.

Give the project knowledge base enough detail to guide a useful decision:

• Goal and audience: who the content is for, what they should understand, and what you want them to do next.
• Creative direction: voice, recurring formats, references, and examples of work the team considers strong.
• Platform requirements: the intended YouTube, Instagram, TikTok, or other deliverables and the checks each needs.
• Source material: current product information, approved claims, brand assets, and relevant client instructions.
• Decision ownership: who chooses the concept, reviews the work, and approves the final version.

Make the current guidance easy to identify. An old client preference and a new approved brief should not carry equal weight simply because both are stored in the project.

Xander also learns from content. Include examples that show the standard you are aiming for, and explain why the team accepted or rejected a direction. That gives creative history a useful role alongside written instructions.

Turn the brainstorm into a production brief

A good brainstorming request gives Xander a problem to solve and criteria for comparing the answers.

For example:

“Xander, use this project's audience, product brief, and approved examples to suggest three concepts for our YouTube launch video. Explain the opening, the main story, and what we would need to produce each one.”

The team can then discuss the tradeoffs. One concept might communicate the product more clearly. Another might suit the available footage. A third might require an interview that cannot happen before the deadline.

Once the creative lead chooses a direction, make that choice explicit. Ask Xander to develop it into a script outline or production brief, including the central message, required assets, deliverables, and open questions.

Keep the selected direction attached to the work. An editor joining later should be able to understand both what was chosen and why.

Give every assignment an outcome and an owner

“Make the launch campaign” is too broad to be a useful handoff. Separate the work into assignments someone can complete: prepare the script, deliver the first cut, design the thumbnail, or resolve a specific client comment.

Each task needs an owner, the right attachments, a deadline, and a clear description of completion. Distinguish the editor's delivery time from the review time and planned release. For teams working across time zones, include the zone in the commitment.

Xander can help turn the agreed brief into those assignments:

“Create a task for our editor to deliver the first YouTube cut by Thursday at 2 p.m. Eastern Time. Attach the approved brief and product footage, and include the producer's notes about the opening.”

When a dependency changes, update the assignment and its explanation together. If the product footage arrives late, ask Xander to help identify the affected work, then agree on revised dates with the people responsible. The team can see how the plan changed without reconstructing the discussion.

Review the actual content against the agreed brief

Creative feedback becomes more useful when it explains the gap between the current work and the intended result.

Instead of asking whether a cut is good, give Xander a focused review request:

“Review version two against the approved launch brief. Does the opening explain the product clearly? Identify moments where the message becomes confusing, and suggest specific changes for the editor.”

Keep feedback about an exact moment beside that moment in the media. Use the related discussion for broader choices such as changing the story, removing an interview, or revising the campaign's message.

When feedback conflicts, give the decision to the person responsible. The client may prefer a different opening while the creative lead is protecting an agreed story. Xander can summarize the disagreement and the relevant context so they can resolve it.

Once a decision is made, ask Xander to turn the agreed changes into tasks. When the next version arrives, check those changes against the new cut. A comment being marked resolved should correspond to a decision or a visible correction.

Make content states mean something specific

Your workflow should answer a simple question: what has to happen before this piece of content can move forward?

A practical starting point is one main production state per deliverable, supported by tags for individual checks. For example:

Tags can add detail without replacing the main state. A YouTube video might have Thumbnail Approved and Captions Checked while remaining In Review because the closing sequence still needs a decision.

Xander can maintain these tags and states through conversation:

“The creative lead approved this thumbnail. Add Thumbnail Approved to the YouTube content item. Keep the video In Review because the closing sequence still needs approval.”

Tie the decision to the version and asset it concerns. If the thumbnail or closing sequence changes, ask Xander to mark the affected check as pending and coordinate the next review. An earlier approval should not silently become approval of a replacement.

These definitions are working conventions your team establishes. Completing an editing task means the edit was delivered; it does not automatically mean the content is approved.

Adapt the workflow to each platform

One campaign can share a goal while producing very different deliverables. Give Xander platform context so the creative direction, review questions, and checkpoints fit the work.

Use questions like these in your project brief:

These are planning questions to customize for your project. Keep current platform specifications and policies with the relevant guidance rather than relying on a single checklist for every destination.

Ask Xander to help develop the versions from the approved idea. Review each version separately, especially when shortening the content removes context. A line that explains an illustrative sequence in the YouTube cut may also be needed in an Instagram or TikTok edit.

Run the playbook on one campaign

Consider a hypothetical New York agency preparing a product launch with collaborators in several countries. The deliverables are one YouTube film, a title and thumbnail, two Instagram Reels, and two TikTok cuts.

The producer adds the approved product information and campaign goal to the project. Xander helps the team compare concepts, develop the selected direction, and create assignments with the material each person needs.

During review, the client changes the offer. The producer confirms the new wording and asks Xander to help identify the affected scripts, captions, and edits. The team updates the relevant tasks and returns the affected deliverables to review.

The thumbnail can remain approved if it is unaffected. The YouTube closing sequence and a TikTok caption may still need work. Those differences remain visible in the content states.

Before the handoff, the producer asks:

“Xander, summarize the launch deliverables. Which versions are approved, what is still blocked, and who owns each outstanding task? Link the relevant feedback so we can resolve it.”

That conversation gives the producer a starting point for the next decisions, with the supporting work close at hand.

Carry the learning into the next project

After delivery, record the decisions worth keeping. Perhaps a particular explanation helped reviewers understand the concept, or a missing reference caused repeated revisions. Save the useful example and explain what the team should do differently next time.

Xander's ability to learn from content becomes more useful when that history has clear meaning. A one-off client exception should be recorded as an exception. A new brand rule should be added to the current guidance.

Review the workflow as well as the finished content. Look at time spent waiting for review, repeated revision requests, and deadlines missed because information was missing. Use the records you actually have, and agree on what to track next.

If you bring YouTube, Instagram, or TikTok performance results into the project, Xander can help the team discuss them alongside the creative decisions. A strong result can inspire another experiment without becoming a rule that every future piece must copy.

Put the playbook into practice

Start with one active project. Give it a clear goal, current knowledge, named decision-makers, and a small set of content states. Then involve Xander in the brief, assignments, reviews, and handoffs as the team works.

FridayHQ brings those conversations and decisions together with the media itself. Your team can spend more of its attention on creative choices because the next assignment, current version, and unresolved question are easier to find.

For your next YouTube video, Instagram campaign, or TikTok series, begin with one request: “Xander, use our project knowledge to help turn this brief into a production plan.”

Explore FridayHQ with your team.