Gemini becomes useful when the workflow works.

A pilot needs a finished work output

“We now use Gemini” is not a verifiable project objective. A better goal is an agreed briefing with open questions and evidenced commitments before a customer call. Write down who prepares it today, which files belong to it and what counts as complete. Choose a workflow that happens often enough to observe differences.

• One accountable department rather than an arbitrary volunteer group.
• One target artefact rather than a collection of interesting answers.

Check feature access and September rollout separately

Google distinguishes access to Gemini features from the sources available to Workspace Intelligence. The September 9 announcement also describes cross-app work such as documents, research, events and tasks. Rollout began September 2, initially in English and with edition-dependent capabilities. The announcement describes preview confirmation for external communication and calendar actions. Still record the feature set actually visible, account type and data path in the pilot. Enablement does not establish that every surface already provides the same capabilities.

Example: from project folder to meeting preparation

For a service business, a briefing can draw on the latest approved proposal, current project status and recent customer correspondence. Require three separate parts: evidenced facts, open questions and proposed next steps. Every commitment needs a reference. If current status is missing, show an open issue instead of turning an older message into a new claim.

Measure the output after correction

For comparable cases, record preparation time, necessary corrections and missing information. Assess the finished draft using the same criteria as the previous process. A fast first draft offers little value if its owner must research every statement again. A short weekly review shows whether improved instructions are enough or whether filing and responsibilities need attention first.

Working template: a one-page pilot brief

Describe the pilot so a colleague can run it without verbal explanation: “The role [owner] creates [specific output] from [approved sources] for [recipient]. We compare it with [current process]. [Person] reviews professional accuracy. If [failure condition] occurs, use [manual route].” Add a start and end date. This also makes missing prerequisites visible before the first test.

• Acceptance: required information present, sources checked, a decision possible.
• Effort: measure preparation, correction and hand-off together.

Next step: make one workflow ready for a decision

Bring an anonymised typical input, an accepted output and the tools involved to the AI System Check. This creates a concrete business question: is Gemini in your existing Workspace environment sufficient, or does the workflow need additional integration? Work requirements drive the choice. lol.marketing also considers alternatives when sources, costs or usability point elsewhere.

Do not transfer personal features into a team rollout

Custom instructions expanded on September 2 can adapt tone and formatting across additional Workspace surfaces. They do not replace access rules. September’s rollout of notebooks in the Gemini app initially excludes EEA Workspace accounts. Current help also excludes work accounts and Germany from Gemini Spark. Evaluate these three capabilities separately before treating a personal test as a template for the whole business.