The feedback is clear: shorten the opening, tighten the middle, and try a different closing line. The next step still takes work. Someone needs to make those changes, bring the content back, and move the review forward.
The feedback is clear: shorten the opening, tighten the middle, and try a different closing line. The next step still takes work. Someone needs to make those changes, bring the content back, and move the review forward.
As teams manage more content, these everyday revisions add up. Xander 2.0 is being developed to help with that work, bringing generative capabilities, video editing, and live content changes into FridayHQ through the comments your team already uses.
Today, teams can invoke Xander in comments. With Xander 2.0, that familiar interaction will extend to creating and editing content.
The planned experience is straightforward: mention Xander, describe what you need, and use the conversation around the content to guide the work. A review comment will become a place to request an edit and continue refining it.
For example, a reviewer might write:
@Xander, trim the pause before the opening line and keep the rest of the introduction unchanged.
Another might ask:
@Xander, make a shorter version focused on the product demonstration. Keep the final call to action.
These examples illustrate the intended workflow: a specific request, a clear creative boundary, and an edited result for the team to review.
Xander 2.0 is being built to handle most basic editing flows. Trimming a section, tightening a sequence, or reshaping a piece around a clearer message are the kinds of everyday requests this direction is intended to support.
That matters when a team is working across several pieces at once. A small revision can hold up an otherwise finished video, especially when the person who needs to make it is already handling another deadline.
With editing available through comments, teams will be able to ask Xander to carry out routine changes while keeping the instructions close to the content. Editors can then spend more of their attention on pacing, storytelling, and the decisions that need their judgment.
The next version will also introduce generative capabilities. Alongside changes to existing content, teams will be able to ask Xander to help create material around the idea they are developing.
A useful request explains the audience, the intended message, and what needs to stay consistent. For example:
@Xander, create three alternative closing lines for this video. Keep the tone practical and invite viewers to try the process themselves.
The same principle applies across content work: describe the outcome clearly, give Xander the relevant context, and review the result against the brief. A focused instruction gives the next revision a clearer direction.
Live editing is central to the direction of Xander 2.0. Teams will be able to request changes as the discussion develops, review the updated content, and give the next instruction in the same working context.
“Make it stronger” leaves a lot open to interpretation. “Lead with the demonstration, shorten the setup, and keep the customer quote” gives the edit a purpose. Agreeing on those boundaries also helps reviewers judge whether the change worked.
For each revision, keep the final creative decision with the person responsible for the content. Check that the result preserves the intended meaning, follows the brief, and is ready for the next stage.
Xander 2.0 is a preview of where FridayHQ is heading: generative creation, everyday editing, and broader content handling through a familiar comment-based interaction.
The aim is to make it easier to act on feedback while the idea is still clear. Mention Xander, explain the change, and keep the work moving with your team.
