Help your team build useful work: a repeatable update, a personal work hub, or a Site for reviewing results. Pick one outcome and give the team a week to try it.
ZIP | Skills, Chief of Staff, and Sites kickoff PDFs
A practical first week
Choose one result for the first week
A team update that makes decisions and next steps clear
A work hub that keeps projects and responsibilities connected
A Site that brings results, sources, and review into one place
Three kickoff examples | Fictional details only
Choose a weekly update, work hub, or review Site
Choose the result that would help your team most. Each example includes a starting prompt and a short deck; the practical pilot below shows how to try it with approved sources and a reviewer.
Example | A reusable Skill
Turn a weekly business update into a Skill
Start with a made-up team update, review the actual draft, and capture only the method worth repeating.
Workflow and resources
Before
A manager rebuilds the same project update every week.
Approved input
Fictional milestones, one invented blocker, and an agreed update format.
Workflow
Draft the update, correct one real miss, then propose a reusable Skill.
Human review
The owner checks every claim and approves the draft before reuse.
Outcome
A candidate update Skill and a fresh case to test.
These examples use fictional details. Skills, Sites editing, app shots, connected tools, Git, and scheduling depend on your product, account, and workspace. None grants access to private information or approval to create, send, schedule, deploy, or change permissions.
Your personal Chief of Staff | Four practical Skills
Keep the work where it belongs
Start with one personal home base. Notice what changed, find the right existing project, coordinate only when asked, and learn from what actually happened.
Detect
Notice real requests and changes in sources you approved.
The complete setup manual includes all four definitions. Installing a Skill, reading a project, continuing a task, or starting a new one requires actual product support and your explicit approval.
Synthetic webinar example | A working Site takes shape
Turn one real workflow into a useful Site
Follow a fictional finance webinar workflow from approved source context to a focused working Site, with the owner reviewing the result before anything is shared.
Fictional illustration only. All figures, reviewers, and company results are synthetic, not actual OpenAI financial metrics. Creating, editing, sharing, or publishing a Site depends on your account and separate approval.
First session | 30 minutes | Fictional example
Turn project notes into a useful update
Copy the sample task into a new ChatGPT Work chat. Compare its draft with the notes below, then make the correction together.
Minutes 0–5
Read the project notes together
Sample input
Design approved. Help article ready. Support handoff blocked; the notes do not name an owner.
The project lead owns the update. The project manager needs the open decision. These fictional notes are the only approved source for this exercise.
Minutes 5–10
Ask for a small, reviewable draft
Your instruction
Draft a short update with Progress, Blocker, and Decision. Use only these project notes. Flag missing information. Don’t invent an owner or send anything.
Read the instruction aloud before trying it. The task is a draft, not permission to inspect other files or act on the team’s behalf.
Minutes 10–18
Review the first pass against the notes
Example first draft
Progress: design approved; help article ready.
Blocker: support handoff.
Next step: assign a support owner.
The progress is supported, but the final line hides the decision inside a next step. It also drops the requested Decision heading.
Minutes 18–25
Make the correction that should carry forward
Your feedback
Keep the Decision heading. Say the notes don’t name an owner and ask the manager who should own the handoff. Don’t turn an unresolved decision into an assigned action.
Corrected draft
Progress: design approved; help article ready.
Blocker: support handoff.
Decision: who owns the support handoff? The notes don’t name an owner.
Keep this review rule: preserve missing ownership as an open question. The manager makes the decision; the draft does not.
Minutes 25–30
Try the method on a different week
Fresh sample input
Design revision ready. Help article under review. Support handoff completed by the support lead; no current blockers are recorded. The manager needs to decide whether to share the update.
Example result to check
Progress: design revision ready; help article under review; support handoff completed by the support lead.
Blocker: none recorded in these notes.
Decision: should the manager share the update?
Ask for the same format. Pass only if the draft uses the new statuses, names the source-backed owner, and does not carry forward the old blocker. Pair the project lead with a reviewer for the next real test.
After the example and your corrections, decide whether a checklist or Skill would help. Test it on fresh notes before trusting it. This page does not connect accounts, create a Skill, or send anything.
Pick a recurring task, identify its audience, and record how the team does it today.
Tuesday
Teach the context
Share only approved sources, a safe example, the quality bar, and what still needs approval.
Wednesday
Correct the work
Run one real case, explain what needs to change, and capture the judgment worth reusing.
Thursday
Try a fresh example
Change the inputs or situation. Check the sources, inspect the result, and note what fails.
Friday
Decide what to keep
Share sanitized lessons, remove what did not help, and choose one useful next step.
The one-real-workflow challenge
Improve the work you would have done anyway
Bring one recurring update, meeting brief, analysis, or handoff. Show the approved inputs and a useful example. Review the result, explain the corrections, and try the method again on fresh work.
Draft a reusable Skill only after the real example and feedback exist. Automate nothing until the workflow is tested, approved, and supported by the product you actually use.
Shared team conventions
Keep the rules short enough to remember
One clear owner
Name the person responsible for the workflow, its output, and the final decision.
Approved sources only
List the systems or files the team may use. Flag missing or conflicting information, and pause any step that depends on it.
Review the actual work
Check the facts, dates, assumptions, formatting, and usefulness on a fresh example.
Humans approve actions
Sending, publishing, changing access, spending, and people decisions always need approval.
Protect people’s privacy
Do not scan private messages, compare employee activity, or retain sensitive examples.
Examples
Real workflow. Fictional details
Demonstrate the method without exposing customer information, employee data, private messages, confidential financials, or systems the team is not authorized to use.
Weekly project update
A fictional product team summarizes three invented milestones, one blocker, and a decision for its manager.
Monthly finance review
An illustrative company explains synthetic results, flags a missing source, and leaves final sign-off with Finance.
Meeting follow-up
A made-up planning session becomes a short list of owners, decisions, open questions, and next steps.
Friday retrospective
Measure the work, not the person
1
Useful evidence
What actually improved?
Review whether the output was usable, its sources were clear, a fresh example passed, and the owner needed fewer avoidable corrections. Use estimates only when the team can support them.
2
Trust and privacy
Where should we slow down?
Discuss missing sources, repeat errors, unclear approvals, and access limits. Share sanitized patterns only; do not retain private histories, employee rankings, or sensitive example content.
3
The next decision
Keep, refine, or stop
Choose one next workflow improvement, name the person who owns it, and decide what still needs a human review before anything is shared, sent, or automated.
Start your team’s pilot
Copy this prompt into a new ChatGPT conversation to plan your first week around one recurring workflow, with clear sources and review steps.
Draft a five-business-day team pilot plan around one recurring workflow.
Use the context I already supplied to draft a provisional plan. Treat the
following as a completeness checklist; ask only about essential gaps:
1. What real work does each person already repeat?
2. Who needs the output, and who owns the final decision?
3. Which sources are approved, and which information must stay private?
4. What would a useful result look like?
5. Which actions must stop for human approval?
Create a 30-minute kickoff, one Monday–Friday plan, a simple workflow brief,
and a Friday retrospective. Use fictional or sanitized examples only.
Compare the work with the team’s normal process and include one fresh example
to test. Mark that test not run unless it was actually executed.
Do not inspect private messages, rank employee productivity, send messages,
change access, create an automation, or publish anything. Ask before any
action outside planning and draft preparation.
