Vision Mode: Think Bigger

Vision Mode is about expansion—exploring what could be, not just what is. It’s the mode for big-picture thinking, long-term possibilities, and challenging the assumptions that constrain your current perspective.

While other modes work within defined boundaries, Vision Mode questions and expands them.

What Vision Mode Is For

Vision Mode excels at:

  • Future exploration: “What could my business look like in 5 years?”
  • Possibility mapping: “What are all the ways we could solve this problem?”
  • Assumption challenging: “What am I assuming that might not be true?”
  • Blue-sky thinking: “If resources weren’t constrained, what would we build?”
  • Trend analysis: “How might AI change our industry in the next decade?”
  • Identity clarification: “What kind of company do we want to become?”

The common thread: expanding thinking before narrowing to decisions.

Vision vs. Strategy vs. Plan

flowchart LR
    A[Vision] --> |"What could be?"| B[Possibilities]
    B --> C[Strategy]
    C --> |"What should we do?"| D[Decision]
    D --> E[Plan]
    E --> |"How do we execute?"| F[Roadmap]

Vision comes first in the strategic thinking process. You explore before you decide, and you decide before you plan.

Vision: “What could our product become?” Strategy: “Should we go direction A or B?” Plan: “Here’s how we execute direction A over 12 months”

The Vision Mode Mindset

Vision Mode requires a different mental stance:

  • Suspending judgment: Don’t dismiss ideas too quickly
  • Embracing uncertainty: You don’t need answers, you need possibilities
  • Removing constraints: “What if” is more useful than “but we can’t”
  • Thinking long-term: Months and years, not days and weeks
  • Welcoming divergence: More options, not fewer

Vision Mode Patterns

The Future State Pattern

Explore what success could look like in the future.

Template:

Imagine it's [future date]. [Goal/Change] has been achieved.

Context: [current situation]
Area of exploration: [what aspect to focus on]

Explore:
- What does this look like concretely?
- What had to happen to get here?
- What unexpected opportunities emerged?
- What did we stop doing?
- What are we doing that we couldn't imagine now?

Example:

Imagine it's 2030. Our small dev agency has become a 
product company generating $10M ARR.

Context: We're currently a 5-person agency doing client work
Area of exploration: The transformation journey

Explore:
- What products are we known for?
- What was the turning point in our transition?
- How did our team and skills evolve?
- What did we stop doing that we thought was essential?
- What opportunities did we capitalize on that we couldn't see in 2025?

The Possibility Mapping Pattern

Generate a comprehensive map of options before narrowing.

Template:

Map the possibility space for [challenge/opportunity].

Current approach: [what you're doing now]
Constraints you're willing to question: [list them]

Generate:
- Conventional approaches (what most would do)
- Unconventional approaches (what few would try)
- Hybrid approaches (combinations)
- "Crazy" ideas worth exploring
- Approaches from other industries that might transfer

Example:

Map the possibility space for customer acquisition.

Current approach: Content marketing + Google ads
Constraints willing to question: 
- Must be digital-first
- Must be scalable before high-touch

Generate wide-ranging possibilities:
- What are 10+ conventional approaches?
- What unconventional approaches might work?
- What do companies outside our industry do?
- What "crazy" ideas might actually work?

The Assumption Audit Pattern

Surface and challenge hidden beliefs constraining your thinking.

Template:

Audit the assumptions behind [belief/approach/situation].

Current belief: [what you currently think is true]
Stakes: [why this matters]

Identify:
- Explicit assumptions (ones I know I'm making)
- Implicit assumptions (ones I might not realize)
- Which assumptions are most likely wrong?
- What becomes possible if each assumption is false?
- How could I test the questionable assumptions?

Example:

Audit the assumptions behind our belief that "we need to hire senior developers."

Current belief: Only senior devs can ship quality code quickly
Stakes: Hiring decisions affect our runway and team culture

Identify:
- What am I assuming about seniors vs. juniors?
- What am I assuming about training and growth?
- What am I assuming about code quality and review?
- What becomes possible if some assumptions are wrong?
- How could I test these assumptions cheaply?

The Blue Sky Pattern

Explore without constraints to find breakthrough directions.

Template:

If [constraint] didn't exist, what would be possible?

Current constraint: [what limits you now]
Area: [what you're exploring]

Explore freely:
- What would you do differently?
- What would become possible?
- What would the ideal version look like?
- What elements of this vision could work even with constraints?

Example:

If we had unlimited engineering resources, what would our product become?

Current constraint: 3-person engineering team
Area: Product vision for next 3 years

Explore:
- What features would we build?
- What platforms would we expand to?
- What technical debt would we eliminate?
- What new markets would we enter?
- Which of these visions could we partially achieve with current resources?

The Trend Implications Pattern

Explore how external changes affect your situation.

Template:

Analyze implications of [trend] for [your context].

Trend: [what's changing]
Your context: [your situation]
Time horizon: [how far to look]

Explore:
- First-order effects (direct impacts)
- Second-order effects (consequences of consequences)
- Who wins and loses?
- What capabilities become more/less valuable?
- What should you start doing now to prepare?

Example:

Analyze implications of AI coding assistants for our software agency.

Trend: AI tools that can write functional code from descriptions
Our context: 20-person agency focused on custom software development
Time horizon: 5 years

Explore:
- How does this change what we deliver?
- What happens to billing models (hourly → value-based)?
- What skills become more/less valuable?
- What new services become possible?
- What should we start doing now?

The “What If” Scenario Pattern

Explore alternative scenarios systematically.

Template:

Explore "what if" scenarios for [decision/situation].

Base case: [expected outcome]
Key uncertainties: [things that could go differently]

For each uncertainty, explore:
- What if it goes better than expected?
- What if it goes worse?
- What would we do differently in each case?
- How should this affect our current decisions?

Example:

Explore "what if" scenarios for our product launch.

Base case: 500 signups in first month, 10% conversion to paid
Key uncertainties:
- Customer interest level
- Competitor response
- Pricing sensitivity

For each uncertainty:
- Best case scenario and implications
- Worst case scenario and implications
- How should we prepare for each?

Using Vision Mode Effectively

Start Wide, Then Narrow

Vision Mode is for exploration. Don’t rush to conclusions:

First: "What are all the possible directions we could take?"
Then (Strategy Mode): "Given these possibilities, which should we pursue?"

Remove “But We Can’t”

Constraints are important—but they should be questioned, not assumed:

Instead of: "We can't do X because..."
Try: "If we could do X, what would change? How might we actually do it?"

Use Time Travel

Mentally moving to the future creates useful perspective:

"It's 2030. Our company has achieved [vision].
Looking back from there, what decisions mattered most?"

Seek Contradictions

The most interesting insights come from exploring tensions:

"We believe X and Y. But if X is true, does Y still hold?
What happens if they're in conflict?"

Generate Volume

In Vision Mode, quantity enables quality:

"Generate 20 possible solutions before evaluating any of them."
"What are 10 ways we could approach this?"

Common Vision Mode Mistakes

1. Narrowing Too Fast

Vision Mode is for expansion. If you’re immediately eliminating options, you’re in Strategy Mode.

2. Staying Too Abstract

Vision should eventually connect to action:

"Given this vision, what's the first concrete step?"
"How would we know we're moving toward this?"

3. Ignoring Reality Entirely

Blue-sky thinking is useful, but eventually needs grounding:

"Of these possibilities, which are most feasible given our resources?"
"What's the version of this vision we could actually pursue?"

4. Solo Vision

Vision work often benefits from multiple perspectives:

"What would someone with [different background] see here?"
"What's the opposite view to each of these ideas?"

Practice Exercise

Create three Vision Mode prompts for expanding your thinking:

1. Future State Exploration Pick a goal and project to a specific future date. Write a prompt that:

  • Places you in that successful future
  • Asks what it looks like concretely
  • Explores what had to happen to get there

2. Assumption Audit Pick a belief you hold strongly. Write a prompt that:

  • States the belief clearly
  • Asks for hidden assumptions underneath
  • Explores what changes if assumptions are wrong

3. Possibility Mapping Pick a challenge you’re facing. Write a prompt that:

  • Describes your current approach
  • Asks for wide-ranging alternatives
  • Includes unconventional and “crazy” ideas

Review: Did you resist narrowing? Did you explore broadly? Did you challenge constraints?

Key Takeaways

  • Vision Mode expands thinking before Strategy Mode narrows it
  • Use for: future exploration, possibility mapping, assumption challenging, blue-sky thinking
  • Key mindset: suspend judgment, remove constraints, think long-term
  • Generate volume before evaluating—quantity enables quality
  • Eventually ground visions in reality and connect to action
  • Vision → Strategy → Plan is the natural thinking sequence

Next lesson: Putting it all together—when and how to combine modes for maximum effectiveness.

When should Vision Mode be used in the thinking process?

Before Strategy and Planning—to explore possibilities
After Planning—to validate execution
Only at the end of projects
It can be used at any time interchangeably

What mindset is required for effective Vision Mode?

Quick evaluation and elimination of ideas
Focus on immediate constraints
Suspending judgment and embracing uncertainty
Detailed implementation focus

What's a key difference between Vision Mode and Strategy Mode?

Vision Mode is longer
Vision Mode expands possibilities, Strategy Mode narrows to decisions
Vision Mode is for technical topics only
Strategy Mode explores more options

What's a common Vision Mode mistake?

Generating too many ideas
Thinking too far ahead
Challenging assumptions
Narrowing too fast to 'practical' options