top of page
Logo-flat-black background-500px_edited.png
  • Instagram
  • Facebook
  • X
  • LinkedIn
  • Youtube

Creativity Symposium: Creative & Design Thinking

  • Jun 29, 2024
  • 7 min read

Updated: Feb 24



Woman in orange sweater sits at cluttered desk, facing a laptop. Walls decorated with art and notes. Warm, creative atmosphere.

A “Creativity Symposium” works when it produces real outputs in a short time: a validated problem statement, prioritized opportunities, low-fidelity prototypes, and an experiment plan. This guide shows how to design and facilitate a creativity + design thinking symposium (half-day to 2 days) using proven methods like Design Thinking (Empathize–Define–Ideate–Prototype–Test) and structured ideation tools such as SCAMPER and Creative Problem Solving (CPS).

You’ll also get copy-paste templates and a repeatable operating rhythm so this isn’t a one-off workshop.


WHAT A CREATIVITY SYMPOSIUM IS (AND WHAT IT’S FOR)

A creativity symposium is a time-boxed, facilitated working session where cross-functional participants solve a real business challenge using structured creative thinking and human-centered design.

Use it when you need to:

• unlock fresh options for a stuck product/market problem

• align stakeholders on “what problem are we solving?”

• rapidly prototype and test ideas (instead of debating them)

• build innovation habits and a shared language across teams

Avoid using it as:

• a motivational talk without work products

• a brainstorming marathon with no prioritization or next steps


THE FOUNDATIONS: CREATIVE THINKING, DESIGN THINKING, AND INNOVATION (IN PLAIN TERMS)


CREATIVE THINKING = GENERATING AND IMPROVING OPTIONS

Creative thinking typically alternates between:

• divergent thinking (generate options)

• convergent thinking (evaluate and select)

This “diverge–converge” rhythm is central to Creative Problem Solving (CPS), which traces back to Alex Osborn’s work and later evolution via the Creative Education Foundation (CEF).

See: Creative Education Foundation — What is CPS?


DESIGN THINKING = A HUMAN-CENTERED WAY TO REDUCE PRODUCT RISK

Design thinking is commonly taught as five modes: Empathize, Define, Ideate, Prototype, Test (iterative, not linear).

See: Stanford d.school — Design Thinking Bootleg and IDEO — Design Thinking


INNOVATION = A MANAGED SYSTEM, NOT A LUCKY MOMENT

If you want repeatable innovation, treat it like a management system with governance, resources, and measurement. ISO provides guidance for building an innovation management system in ISO 56002:2019.


COMMON REASONS CREATIVITY WORKSHOPS FAIL

1. No real problem framing → people ideate on symptoms.

2. No evidence → opinions dominate, customer reality is missing.

3. Too many ideas, no selection → energy without execution.

4. No prototypes → “nice ideas” that never get tested.

5. No ownership → nothing happens after the event.

This guide is designed to prevent those failure modes by engineering clear outputs and follow-through.


THE ORGEVO WAY TO RUN IT: TREAT THE SYMPOSIUM AS A MINI OPERATING SYSTEM

A high-quality symposium has:

• clear inputs (challenge, customer evidence, constraints)

• defined roles (sponsor, facilitator, scribe, prototype lead)

• time-boxed methods (diverge/converge cycles)

• explicit deliverables (problem statement, prototype, experiment plan)

• governance (who decides what happens next)

• metrics (what success looks like in 2–6 weeks)


FORMATS YOU CAN CHOOSE


OPTION A: 3-HOUR “CREATIVITY SPRINT” (FAST ALIGNMENT + IDEAS)

Best for: early-stage teams, narrow problems, quick unblock

Outputs: problem statement, opportunity list, top 3 concepts, next actions


OPTION B: 1-DAY “DESIGN THINKING SYMPOSIUM” (MOST COMMON)

Best for: product/service improvements, go-to-market friction, internal process redesign

Outputs: persona + journey snapshot, prioritized opportunities, prototype(s), test plan


OPTION C: 2-DAY “PROTOTYPE + TEST SYMPOSIUM” (HIGHEST IMPACT)

Best for: high-stakes decisions, multiple stakeholders, unclear solution space

Outputs: multiple prototypes, user testing results, decision memo, experiment backlog


STEP-BY-STEP IMPLEMENTATION GUIDE


STEP 1 — DEFINE THE CHALLENGE (BEFORE YOU INVITE ANYONE)

Inputs: business goal, constraints, target users, decision deadline

Roles: sponsor + facilitator

Time: 60–90 minutes

Deliverable: 1-page Challenge Brief

Challenge statement template

• “How might we _____ for _____ so that _____, while respecting _____ constraints?”

Quality check

If the team cannot agree on who the user is and what success looks like, you are not ready to ideate.


STEP 2 — RECRUIT THE RIGHT ROOM (8–20 PEOPLE)

Aim for representation from:

• product/engineering/design (or ops/process owners)

• sales/marketing/customer success (customer reality)

• finance/risk/compliance (constraints)

• frontline roles (what actually happens)

• a decision-maker or empowered proxy (to avoid “workshop theatre”)


STEP 3 — COLLECT EVIDENCE (MINIMUM VIABLE RESEARCH)

You don’t need a full research program, but you do need some reality.

Minimum evidence pack (pre-read)

• 5–10 recent customer calls/tickets excerpts (anonymized)

• funnel or usage drop-off points (where relevant)

• top 5 objections or failure points

• competitive alternatives users are already using


STEP 4 — RUN THE DESIGN THINKING FLOW (WITH EXPLICIT DIVERGE/CONVERGE)

Use the five-mode structure as your backbone (Stanford d.school):


1. Empathize (45–90 min)

o map user jobs/pains/gains

o capture direct quotes and observed behaviors

Output: persona snapshot + evidence list


2. Define (30–60 min)

o convert evidence into a crisp problem statement

o list assumptions to test

Output: “Point of View” problem statement + assumptions backlog


3. Ideate (45–90 min)

o run 2–3 structured ideation rounds, not open-ended chaos

o combine divergent rounds with quick clustering and voting

Output: idea inventory + top concepts


4. Prototype (60–120 min)

o low-fidelity first (paper flows, mock screens, role-play scripts)

o choose prototypes that test the riskiest assumptions

Output: prototype artifacts + what each is meant to test


5. Test (45–90 min)

o internal “role-play testing” if users aren’t available

o preferably 5 quick user tests if you can access users

Output: insights + revised prototype + decision recommendation


STEP 5 — USE STRUCTURED IDEATION TOOLS (SO CREATIVITY IS REPEATABLE)


Tool 1: SCAMPER for “improving what exists”

SCAMPER is a prompt checklist originally developed by Bob Eberle based on Osborn-style checklist thinking.

Reference: SCAMPER background (and follow the cited sources for deeper reading).

Use SCAMPER when you already have a product/process and want to innovate quickly:

• Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse


Tool 2: Creative Problem Solving (CPS) for “clarify → ideas → plan”

CPS is designed as a structured process for moving from messy challenges to workable plans.

Reference: Creative Education Foundation — CPS

Use CPS when the challenge is ambiguous and the group needs a disciplined flow.


STEP 6 — CONVERT OUTPUTS INTO AN EXECUTION PLAN (THE MISSING STEP IN MOST WORKSHOPS)

Before the event ends, produce:

A) Decision memo (1 page)

• Problem definition

• Options explored

• Prototype results

• Recommendation and tradeoffs

• What we’ll test next


B) Experiment backlog (2–6 weeks)

• hypotheses

• experiment design

• owner

• success metric

• timeline

If you want a proven sprint-style execution format, the design sprint approach popularized by GV is useful for structuring rapid prototype-and-test cycles (see: Sprint book site).


A PRACTICAL 1-DAY AGENDA (COPY-PASTE)


09:30–10:00 — Setup

• sponsor sets context, constraints, decision deadline

• facilitator explains rules (time-boxing, no “idea killing,” evidence-first)


10:00–11:15 — Empathize

• user snapshot + evidence review

• journey map or “current-state” walkthrough

• pain points + moments that matter


11:15–12:00 — Define

• craft “Point of View” statement

• list assumptions + risks


12:00–13:00 — Ideate Round 1 (diverge + cluster)

• silent idea generation (10 min)

• share + cluster (20 min)

• vote (10 min)

• combine/refine (20 min)


13:00–14:00 — Lunch


14:00–15:30 — Prototype

• build low-fi prototypes in teams

• define what each prototype tests


15:30–16:30 — Test

• role-play tests or quick user tests

• capture insights and changes


16:30–17:15 — Decide + plan

• pick 1–2 concepts to proceed

• create experiment backlog + owners


17:15–17:30 — Close

• recap, commitments, next checkpoint date


TEMPLATES AND CHECKLISTS


1) CHALLENGE BRIEF (1 PAGE)

• Problem context:

• Target user:

• Business outcome (metric):

• Constraints (time, budget, compliance):

• What’s in scope / out of scope:

• Decision deadline:

• Known evidence:

• Open questions:


2) “POINT OF VIEW” PROBLEM STATEMENT

• User:

• Need:

• Insight (because…):

• “How might we…” question:


3) EXPERIMENT CARD

• Hypothesis:

• What we’ll change:

• How we’ll test:

• Success metric:

• Owner:

• Duration:

• Risks/guardrails:


4) FACILITATION CHECKLIST

• Invite decision-maker or empowered proxy

• Evidence pack ready

• Time boxes visible

• Voting method defined

• Prototype materials prepared

• Scribe captures decisions + owners live

• Close with next checkpoint booked


HOW TO MEASURE SUCCESS (SO IT’S NOT JUST “FUN”)

Pick a small set of measures:

Innovation throughput

• no. of testable hypotheses created

• No. of prototypes built

• No. of experiments launched within 2 weeks

Customer impact

• improved conversion/activation/retention (choose one)

• reduced support tickets in the targeted area

• user test success signals (task completion, comprehension)

Execution discipline

• % of symposium action items closed

• cycle time from idea → experiment → decision


DIY VS EXPERT FACILITATION

DIY works best when the problem is narrow, stakeholders are aligned, and you already have evidence and decision rights.

Bring expert facilitation when:

• stakes are high (major product bet, major process redesign)

• politics are complex (multiple leaders, unclear ownership)

• you need a defensible decision trail and metrics

• you want to build an internal repeatable innovation system aligned with standards such as ISO 56002


RELATED ORGEVO READS (INTERNAL LINKS)


FAQ

1) WHAT’S THE DIFFERENCE BETWEEN CREATIVE THINKING AND DESIGN THINKING?

Creative thinking focuses on generating and improving options (diverge/converge). Design thinking adds a structured, human-centered loop (empathize → test) to reduce the risk of building the wrong thing. See Stanford d.school Bootleg.

2) HOW MANY PEOPLE SHOULD ATTEND A CREATIVITY SYMPOSIUM?

Usually 8–20 is ideal. Smaller groups move faster; larger groups need stronger facilitation and breakout structure.

3) DO WE NEED REAL CUSTOMERS FOR TESTING?

It’s strongly preferred. If you can’t access users quickly, do role-play testing and schedule 5 user tests within the next 1–2 weeks.

4) WHICH IDEATION METHOD SHOULD WE USE: SCAMPER, BRAINSTORMING, OR CPS?

Use SCAMPER to improve something that already exists; use CPS when the problem is ambiguous and you need a structured path from clarification to planning (CEF CPS).

5) WHAT SHOULD WE LEAVE THE SYMPOSIUM WITH?

At minimum: a validated problem statement, top concepts, at least one prototype, and an experiment backlog with owners and dates.

6) HOW DO WE PREVENT THE WORKSHOP FROM DYING AFTER DAY ONE?

Book the next checkpoint before everyone leaves, assign owners live, and track experiments as part of weekly execution—treat it like delivery, not “innovation theatre.”


CONCLUSION

A creativity symposium becomes valuable when it’s designed as a repeatable system: evidence → framing → structured ideation → prototypes → testing → execution ownership. Use the agenda and templates above to run a symposium that produces tangible outputs in days—not just inspiration.


CTA: If you want help facilitating a high-impact creativity symposium (or building a repeatable innovation system across teams), contact OrgEvo Consulting.


REFERENCES (EXTERNAL)

Comments

bottom of page