Hands-on ChatGPT Work and Codex training using real work tasks.

Try ChatGPT Work and Codex on a task from your day-to-day work. Over six working hours, you will practice writing a brief, providing useful context, choosing the right environment, and reviewing the output.

Discuss training for your team

Start with a task your team actually needs to do.

As the buyer, you choose the tasks and the people who know them with me. We check whether they can use the required accounts and materials; before the training starts, we agree on the scope, price, and working arrangements. I prepare and lead the session personally so participants can work on their own approved tasks.

For the buyer: Before the training starts, we agree on the scope, price, and access arrangements.
For participants: They practice briefing, context, and review on a task from their work.

Choose the environment based on the task and how it needs to be reviewed.

Work is designed for longer, multi-step tasks and finished work deliverables. Codex is dedicated to software development and technical work. We choose based on the task and what needs to be reviewed.

ChatGPT WorkFor longer tasks, research, analysis, and work deliverables.
It can turn source material and context into a document, spreadsheet, presentation, report, or another deliverable the team needs to use.
CodexFor software development and technical tasks.
It helps write and debug code, run tests and commands, and review changes in a repository or project.

Git can help review code changes, but it does not separate Work from Codex. The key question is whether you are creating a work deliverable or developing software. Codex remains the dedicated environment for technical work.

Set up the work in the morning. Try it in the afternoon.

The tasks and the amount of time spent in each tool depend on your team and its access. The day's structure stays the same.

Lunch falls between the blocks and sits outside the six training hours.

2 hours · morning: Choose the tasks, define the expected result, and prepare the context. Decide where ChatGPT Work fits and where Codex fits.
4 hours · afternoon: Participants work on the prepared tasks, refine their briefs, and review the outputs. We close by capturing what worked and what still needs checking or approval.

The brief, the context, and the review.

The same approach applies whether someone is preparing a decision document or changing a project file. First we define the result. Then we give the AI the work.

The brief

Define the result, who it serves, and how you will know it meets the need.

What should be different at the end?

The context

Choose the materials, rules, and examples the AI can use. Separate what is current from what is assumed or missing.

What does the AI need to know?

The review

Identify what needs to be checked against a source, tested, or approved by a person.

What still needs a person's judgment?

The training starts with a task someone in the business owns.

The session is useful when people know the current process, can access approved materials, and can decide what happens to the result. We will only use materials the company has approved for this purpose.

You can follow up with a consultation after the training. We will review what you tried in your day-to-day work and what may need adjustment. Any follow-up scope and price are agreed separately.

A good fit if

you want to move a recurring or important day-to-day task forward
participants know how the work happens today and who owns it
we can check accounts, access, and rules for sharing materials in advance

Another format may work better if

leadership, business, and technical teams need to align on an AI plan Explore the team workshops
you need to test a full business process or build a working workflow test Learn about the AI workflow sprint
you expect every task to be finished regardless of its scope, inputs, or access

Before we set a date.

We agree on the scope, people, tools, and what you want the session to accomplish.

Will the task be finished by the end?

That cannot be guaranteed. It depends on the task, the materials available, and the access in place. The aim is to move the work forward, understand the workflow, and identify what still needs a person's review.

Is Work just Codex without Git?

No. Work is designed for longer, multi-step tasks, research, analysis, and work deliverables. Codex focuses on software development, code, tests, and project work. In the desktop app, both can work from a local folder; Git is not a requirement and is most useful for tracking and reviewing changes. OpenAI's guide to Work and Codex

Will we use company materials?

Only with materials the company approves for this purpose. We will check what is safe to use and which tools and accounts are available. Do not include sensitive data in your first message.

How many people can attend, and what does it cost?

We will agree on the group size and price based on the tasks and how we need to work through them. You will receive an offer before confirming a date.

Is a follow-up consultation included?

Not automatically. We can agree on one separately, based on what the team tries and what it needs next.

What task would you like to move forward?

Tell me a little about the work your team wants to try and who would attend. Please do not attach confidential materials or passwords.

Prefer writing from your own inbox? jsem@radekduha.cz