TL;DR
Gemini’s brainstorming advantage is not idea volume — every model generates ten options fast. It is that the Gemini app can @-reference the half-written Doc, last quarter’s deck, and the customer-feedback Sheet already sitting in your Drive, then frame the problem against your real material. This guide is a repeatable 30-minute session: write a one-sentence problem, ask for 10 framings (not 10 solutions), drill 3, ground the finalists in an @-referenced source, and close with a premortem. Works on the free Gemini app for short sessions; @-Drive references and Gemini-inside-Docs need Google AI Pro at $19.99/month (as of June 2026).
What this covers
Every LLM can hand you a list of ten ideas. Gemini’s actual edge for brainstorming is context: in the Gemini app you can type @ and pull in a specific Drive file by name, so the model frames against your real customer quotes and prior decks instead of internet averages. As of June 2026 the model behind this is Gemini 3.1 Pro, with a 1M-token context window on Google AI Pro.
Key tools and concepts:
- Gemini app: Google’s assistant, running Gemini 3.1 Pro, connected to Workspace and Search.
@-mentions: type@and a filename to reference a specific Doc, Sheet, folder, or other Drive file inline, so Gemini grounds its ideas in that material rather than generic patterns.- Framings: different ways to phrase the same underlying problem — the cheapest way to escape the first-idea trap.
- Gems: saved Gemini configurations (a name, an instructions block, optional knowledge files, and a default tool) that turn this whole sequence into a one-click reusable assistant. Gems are free on every plan.
Who this is for
Anyone deciding or planning — PMs picking a feature name, founders sequencing a launch, marketers framing a campaign, writers stuck on the angle for a piece. If you brainstorm alone with a blank Doc more than twice a week, this workflow is for you.
Free vs. paid: what you actually need
You can run a basic version of this session on the free Gemini app, but the Drive-grounding that makes it worth doing has tier limits. Here is the practical breakdown as of June 2026.
| Capability | Free Gemini app | Google AI Pro ($19.99/mo) |
|---|---|---|
| Model | Gemini 3.1 Pro (tight limits) | Gemini 3.1 Pro |
| Context window | ~32,000 tokens (~50 pages) | 1M tokens (~1,500 pages) |
@-reference Drive files in chat | Yes (connect Workspace app, Keep Activity on) | Yes |
| Gemini inside Docs / Sheets / Gmail | No | Yes |
| Files per prompt | Up to 10 | Up to 10 |
| Gems (custom assistants) | Yes | Yes |
| Storage | 15 GB | 5 TB |
The two paid-only lines that matter for brainstorming: the 1M-token context (so a long brainstorm plus several referenced docs does not get truncated) and Gemini running inside Docs, so you can keep building in the same file you started from. To @-reference Drive files at all, connect the Google Workspace app to Gemini Apps and keep Gemini Apps Activity on — otherwise the @ picker will not see your files.
When to reach for it
Strategy, naming, framing, sequencing — anywhere the cost of picking the wrong direction is bigger than the cost of generating ten more options. Skip Gemini for hard analytical problems with a single right answer; reach for it when the space is wide and your first three ideas all feel obvious.
Before you start
- Write a one-sentence problem statement. If you cannot, the brainstorm will be unfocused — the model will pattern-match to whatever sounds adjacent.
- Pull the supporting artifacts into Drive: customer quotes, prior decks, the half-baked Doc. You will
@-reference them, not paste them. (Free accounts cap each prompt’s text at ~32,000 tokens, so a giant pasted transcript gets truncated; referencing a file is both cleaner and gets around that for short docs.) - Decide your output format up front: a ranked list of 10, a 2x2 matrix, three framings with a one-paragraph drill-down each. Format constrains the model to useful structure.
- Time-box to 30 minutes. Brainstorming with an LLM has no natural stopping point; the timer is yours to enforce.
Step by step
- State the problem in one sentence, then add a constraints line:
We must ship before September; the audience is mid-market ops leaders; we cannot use the word "platform". - Ask for 10 framings, not 10 solutions:
Give me 10 different ways to frame this problem. Vary the unit of analysis — user, system, business, time.Framings break the first-idea trap better than solution lists. - Pick 3 framings that feel non-obvious and drill:
For framing 4, give me 5 concrete approaches. For each, name the strongest objection. - Push back on the weak spots:
Approach 2 assumes attribution is solved — defend it or replace it.Refusal to defend is a signal to drop the idea. - Reference your real material:
Now reconcile approaches 2 and 5 with the customer quotes in @Q3-feedback-summary. Which holds up?Type the@, then pick the file from the Drive list that appears. - Close by asking for the inverse:
What would have to be true for none of these to work?The premortem catches the framing-level error.
Turn the sequence into a Gem (do this once)
If you run this more than occasionally, save it as a Gem so you stop re-typing the scaffolding. Open the Gemini app, go to Gems → New Gem, and fill in the builder:
- Name:
Brainstorm partner. - Instructions: paste your house rules — for example,
Always answer with framings before solutions. Vary the unit of analysis. For every approach, name the strongest objection. Never tell me which option to pick; surface trade-offs instead. - Knowledge files: attach any standing context you reuse (brand voice doc, ICP definition, the constraints you always carry).
- Default tool: set it to Canvas so each session opens in an editable surface you can iterate in side by side, instead of a linear chat.
Now every new chat with that Gem starts pre-loaded with your rules and opens in Canvas. Gems work on the free plan too, so this is the highest-leverage free upgrade to your workflow.
First-run exercise
- Pick a real decision you owe someone a recommendation on this week. Not a thought experiment.
- Run all six steps in one sitting, no notes app, just the Gemini conversation.
- Save the transcript into a Doc. Highlight in green the lines that genuinely surprised you, in red the ones that read like LinkedIn filler.
- Re-run only step 2 with a different framing axis (
vary the timeframe instead of unit of analysis) and compare the green-highlight count.
Quality check
- Did the session produce framings you would not have reached alone, or just polished versions of your starting point?
- Are the strongest two ideas grounded in something specific — a real quote, a real number, a real constraint — or in generic best practice?
- Did you press on the weakest spot of each finalist, or did you fall in love with the first decent option?
How to reuse this workflow
- The Gem above is the reusable artifact — the structure travels even when the topic changes.
- For recurring decisions (quarterly naming, weekly campaign framing), keep a “framings I have used” log so you do not converge to the same axis every time.
- Keep the failures: brainstorms where Gemini produced ten variations of the same idea usually mean your problem statement was too narrow.
- Refresh quarterly — model defaults shift, and a framing prompt that worked six months ago on Gemini 2.x may now return cliches on 3.1.
Recommended workflow
Problem statement (1 sentence) → 10 framings → pick 3 → drill 5 approaches each → reconcile with one @-referenced source → premortem. End with a single Doc that lists the chosen direction, the two runner-ups, and the assumption that would kill it. That Doc is the artifact you share with a teammate to get a real second opinion.
Common mistakes
- Stating the problem too generically (
how do we grow) — every LLM will hand you LinkedIn fluff. - Stopping after the first 3 framings because they sound smart. The 7th-10th are where the non-obvious moves usually live.
- Ignoring the
@integration. A brainstorm grounded in your real customer quotes is far more useful than one grounded in averages — and it is the one thing a generic ChatGPT session cannot match without setup. - Asking Gemini to “decide” — it will pick the option that sounds safest in writing, not the one that fits your context.
- Skipping the premortem. The framing-level error is the most expensive one, and the only one a fast brainstorm can catch.
FAQ
- Is Gemini better than ChatGPT for brainstorming?: Roughly tied on raw idea generation. Gemini wins when your context already lives in Drive and you want to
@-reference it; ChatGPT wins when you have heavy custom instructions and persistent memory. See ChatGPT brainstorming for that side. - Do I need to pay to brainstorm with Gemini?: No. The free Gemini app runs Gemini 3.1 Pro and supports
@-Drive references and Gems. You hit the wall on long sessions (the ~32,000-token context truncates) and you cannot run Gemini inside Docs — both of which Google AI Pro ($19.99/month as of June 2026) unlocks. - Should I use Deep Research for brainstorming?: No — it is for synthesis, not divergence. Use plain chat (or a Canvas Gem) for brainstorming and switch to Gemini Deep Research once a direction is chosen.
- How do I keep Gemini from being generic?: Constraints, examples, and
@-referenced material. Bake the first two into a Gem so they apply automatically, then add the third per session. - Why does the
@picker not see my Drive files?: Connect the Google Workspace app to Gemini Apps and keep Gemini Apps Activity on. Without that connection the@menu only sees what you have uploaded in the current chat.