Who this is for
HR, L&D, operations and customer-facing teams using approved Gemini features.
Start with the challenges your team faces and each person’s current skills.
Plan Gemini training for employees with practical Google Workspace exercises, account preparation, source checks and reviewed work samples for your team.
HR, L&D, operations and customer-facing teams using approved Gemini features.
Start with the challenges your team faces and each person’s current skills.
A reviewed work sample and a reusable checklist for the next task.
This is an example to help scope the learning; delivery arrangements are agreed before booking.
Confirm account access, permitted information and the task your employees need to complete.
Practise an email response, document summary or meeting action list with fictional or approved material.
Trace claims to the source, correct omissions and repeat the task with a new example.
Use these stages to discuss the learning scope. Timing, tools and exercises depend on the team’s brief.
Confirm account access, permitted information and the task your employees need to complete.
Practise an email response, document summary or meeting action list with fictional or approved material.
Trace claims to the source, correct omissions and repeat the task with a new example.
Confirm available Gemini features, accounts and permitted data with your administrator. Bring an approved source and identify who reviews the result.
Estimate the time your team needs for sessions and follow-through. Change the example to fit your people; this is not a workshop package or quote.
Compare programs against your challenge, audience and available time. Confirm the actual schedule and fees with the organizer.
Find relevant programs in AISFYYou may need to sign in. Results stay on this page and are not saved or transferred to your AISFY account. Copy your plan before continuing.
Cohorts = participants ÷ cohort size, rounded up. Per-person time = session hours + weekly practice × weeks. Team time multiplies that by participants. Delivery hours count repeated sessions across cohorts; they exclude facilitator preparation.
Defaults are illustrative inputs, not benchmarks or recommended commitments. Changing or leaving the page resets the plan.
Open a topic for the full guidance, examples and references.
Sports Basement reported a 30–35% reduction in email-writing time using Gemini, according to Google’s October 2025 customer collection. Google Workspace — customer examples, October 2025.
Evidence limits: This is a customer-reported result published by the supplier, not a controlled trial or a forecast for your team.
Choose the repetitive communication task before choosing a productivity target. Email drafting has a clear start and finish, but a shorter drafting stage may conceal longer review. Track both stages and check whether the resulting message is suitable for its intended recipient.
Provide a fictional delivery delay, an approved explanation and an escalation contact. Compare a manually written message with a Gemini-assisted version using the same facts. Record drafting minutes, correction minutes and whether both versions avoid invented dates. Use a different scenario for the assessment so participants cannot simply remember the answer.
Sources checked 20 October 2026. External examples are not AISFY customer results. Practice scenarios are editorial examples.
Start with the work employees need to complete in Google Workspace: an email response, a document summary or a meeting action list. A useful training brief names the role, the approved source, the available Gemini features and the checks required before sharing the result. Choose the exercises around those needs rather than demonstrating every application.
These are illustrative exercises to discuss when choosing a program. Confirm account access and feature availability with your administrator; the scope and delivery arrangements depend on the selected program.
A Gemini training brief should begin with the Workspace tasks employees actually perform and the features available in their accounts. Access does not establish proficiency. Choose one approved task and assess the result, including the effort needed to verify and correct it.
Gemini also handles multimodal work — reasoning over images and screenshots — which is genuinely useful for teams working with visual material. Watch-item: check consistency on long documents, and verify before sharing, as with every generative tool.
Ask participants to name a recurring Workspace task, then specify approved inputs, expected output and review responsibilities. Demonstrate the task and repeat it with new material. Include a permissions check before using organizational documents. Follow-up should examine work samples and difficulties, rather than relying only on confidence or account activity.
Compare tools using the same representative task, source material and quality standard. Existing software, permissions, cost and reviewer effort all affect fit. An assistant inside a familiar application may be convenient, but convenience alone does not establish that its output is accurate or that adoption will follow.
Confirm the features, account permissions and data settings available in the organization’s Google Workspace environment. Use a fictional meeting summary or approved document to practise converting notes into an action list. Each action should identify an owner from the source or explicitly say that the owner is unresolved.
Review invented deadlines, incorrect ownership and omitted decisions. The exercise should teach participants to distinguish helpful organization of information from unsupported completion of missing details.
A draft in a document or email still requires review before sharing. Define who checks it and whether any action requires approval. Convenience inside an existing application should not be mistaken for permission to use every document the participant can access.
Keep a reviewed example and a short checklist for the next workplace task. Evaluate whether the method produces usable work within the data boundary, then assess operational benefits separately.
For workshop options, explore enterprise AI workshops. Use the preparation checklist and evaluation guide to connect the session to a practical next step.
Use a fictional project update as one connected exercise. Start with approved notes, organize a document around progress and open decisions, then prepare a short stakeholder message. If the cohort’s approved account supports the relevant Workspace features, practise in those applications; otherwise keep the exercise within the available environment.
Maintain the same project dates, owners and status across every output. A draft message must not turn a proposed deadline into a commitment or a discussion item into an agreed action. Have the recipient check whether the update makes the next decision clear.
Provide a small fictional table with known totals and one deliberately missing value. Ask for a summary that distinguishes a blank from zero and states the reporting period. Check any suggested calculation against a manually verified example before applying it more widely.
Then turn the checked findings into a slide outline. Require a source for each number and a clear distinction between a finding and a recommendation. Visual polish cannot compensate for an incorrect denominator, omitted caveat or invented trend. Use only features confirmed for the participant accounts.
Confirm approved account access and the features needed for the selected exercise before training. Use fictional or approved source material. If access is still being arranged, agree an alternative activity and distinguish demonstration attendance from demonstrated hands-on skill.
Choose the applications that support the cohort’s recurring work, then check the available features. A document-writing team may practise in Docs; a reporting team may need a checked spreadsheet example. Include other applications only when they serve the learning objective.
Record whether participants can complete and review a new task, then agree a later manager check of workplace practice. Track continued use, error patterns and review effort separately from confidence. Any claimed time saving needs a comparable baseline and must include checking and correction.
Preview the work · illustrative resource
Inspect a deliberately flawed draft against fictional source notes. This illustrates a review method, not output from a recorded ChatGPT session.
For: Teams practising summaries with ChatGPT or Gemini
Requirements were reviewed, not approved. Testing is waiting for a sample dataset. Friday is a proposed date; the owner has not confirmed it.
Deliberately flawed draft: “Requirements are approved. Testing will finish Friday. No support is needed.” It changes the approval status, turns a proposal into a commitment and hides the dependency.
Reviewed example: “Requirements have been reviewed; approval is not confirmed. Testing awaits a sample dataset. Friday remains proposed. The project owner should confirm the date and identify who can resolve access.” Check each claim against the source before sharing.
Ask for relevant subject experience, an example exercise and the proposed review approach. Check the facilitator’s named profile and agree who will assess the work. A profile or attendance certificate alone does not demonstrate results for your team.
Confirm the audience, permitted information, tools, accessibility, format, dates, fees, practical outputs and follow-through in writing. The examples here are learning materials; they are not client case studies or fixed delivery promises.
Read the AISFY founder profileCaptioned screen walkthrough · no audio · fictional example.
Read the source. Requirements were reviewed, not approved. Testing is waiting for a sample dataset. Friday is a proposed date; the owner has not confirmed it.
Challenge the draft. Deliberately flawed draft: “Requirements are approved. Testing will finish Friday. No support is needed.” It changes the approval status, turns a proposal into a commitment and hides the dependency.
Keep the correction traceable. Reviewed example: “Requirements have been reviewed; approval is not confirmed. Testing awaits a sample dataset. Friday remains proposed. The project owner should confirm the date and identify who can resolve access.” Check each claim against the source before sharing.
Share the challenge, audience and skills you want to develop. AISFY helps you plan the learning and connect with relevant expertise.
Scope, facilitator, availability and fees are confirmed before booking.
Explore AI workshops ↗