Best for
Product concepts, business models, campaigns, and service design.
Problem solving · zwicky-box
Break a solution space into dimensions and recombine options.
Product concepts, business models, campaigns, and service design.
Dimension table, combinations, screening criteria, and first experiments.
Use a Zwicky Box to generate creative solution options.
Demo Gallery
Each demo maps to a real paid deliverable: a Markdown report, Mermaid diagram, or PDF-ready file. Users can inspect examples before spending their 3 free generations.
The team needs systematic option generation instead of random brainstorming.
Sample input
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
Generated output includes
Full Markdown demo
# Zwicky Box: Classic Generation Example ## Input Summary We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria. ## Classic Case Context We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria. ## Skill Used - Zwicky Box - Break a solution space into dimensions and recombine options. - Best for: Product concepts, business models, campaigns, and service design. - Can generate: Dimension table, combinations, screening criteria, and first experiments. ## Situation Judgment This is a classic situation for Zwicky Box: the input contains a goal, constraints, stakeholder judgments, and a need for action. ## Executive Summary Separate facts, assumptions, constraints, and actions first, then use Zwicky Box to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework. ## Framework Analysis | Module | Typical output | Purpose | | --- | --- | --- | | Facts | Verifiable information from the input | Avoid intuition-only judgment | | Assumptions | Unknowns that can change the conclusion | Guide validation | | Framework analysis | Structure through Zwicky Box | Create shared language | | Action | Owner, time, metric | Drive execution | ## Reusable Diagram This is a Markdown-only output. Switch to diagram or PDF-ready output to generate Mermaid. ## Recommendation Use this as the first decision or workshop artifact, then add real evidence, owners, and dates. ## Risks And Unknowns - If the input lacks real evidence, ranking and recommendations remain working assumptions. - The framework cannot replace stakeholder alignment on goals and constraints. - The diagram is a communication surface, not final truth. ## Next Actions 1. Confirm the goal and non-negotiable constraints. 2. Add the 2-3 pieces of evidence most likely to change the conclusion. 3. Share the output, collect objections, and update the version.
The team needs systematic option generation instead of random brainstorming.
Sample input
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
Generated output includes
Full Markdown demo
# Zwicky Box: Classic Generation Example
## Input Summary
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
## Classic Case Context
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
## Skill Used
- Zwicky Box
- Break a solution space into dimensions and recombine options.
- Best for: Product concepts, business models, campaigns, and service design.
- Can generate: Dimension table, combinations, screening criteria, and first experiments.
## Situation Judgment
This is a classic situation for Zwicky Box: the input contains a goal, constraints, stakeholder judgments, and a need for action.
## Executive Summary
Separate facts, assumptions, constraints, and actions first, then use Zwicky Box to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework.
## Framework Analysis
| Module | Typical output | Purpose |
| --- | --- | --- |
| Facts | Verifiable information from the input | Avoid intuition-only judgment |
| Assumptions | Unknowns that can change the conclusion | Guide validation |
| Framework analysis | Structure through Zwicky Box | Create shared language |
| Action | Owner, time, metric | Drive execution |
## Reusable Diagram
```mermaid
mindmap
root((Zwicky Box))
Facts
Evidence
Signals
Assumptions
Unknowns
Tests
Options
Preferred path
Alternatives
Delivery
Report
Diagram
Actions
```
## Recommendation
Use this as the first decision or workshop artifact, then add real evidence, owners, and dates.
## Risks And Unknowns
- If the input lacks real evidence, ranking and recommendations remain working assumptions.
- The framework cannot replace stakeholder alignment on goals and constraints.
- The diagram is a communication surface, not final truth.
## Next Actions
1. Confirm the goal and non-negotiable constraints.
2. Add the 2-3 pieces of evidence most likely to change the conclusion.
3. Share the output, collect objections, and update the version.
Mermaid demo
mindmap
root((Zwicky Box))
Facts
Evidence
Signals
Assumptions
Unknowns
Tests
Options
Preferred path
Alternatives
Delivery
Report
Diagram
ActionsThe team needs systematic option generation instead of random brainstorming.
Sample input
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
Generated output includes
Full Markdown demo
# Zwicky Box: Classic Generation Example
## Input Summary
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
## Classic Case Context
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
## Skill Used
- Zwicky Box
- Break a solution space into dimensions and recombine options.
- Best for: Product concepts, business models, campaigns, and service design.
- Can generate: Dimension table, combinations, screening criteria, and first experiments.
## Situation Judgment
This is a classic situation for Zwicky Box: the input contains a goal, constraints, stakeholder judgments, and a need for action.
## Executive Summary
Separate facts, assumptions, constraints, and actions first, then use Zwicky Box to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework.
## Framework Analysis
| Module | Typical output | Purpose |
| --- | --- | --- |
| Facts | Verifiable information from the input | Avoid intuition-only judgment |
| Assumptions | Unknowns that can change the conclusion | Guide validation |
| Framework analysis | Structure through Zwicky Box | Create shared language |
| Action | Owner, time, metric | Drive execution |
## Reusable Diagram
```mermaid
mindmap
root((Zwicky Box))
Facts
Evidence
Signals
Assumptions
Unknowns
Tests
Options
Preferred path
Alternatives
Delivery
Report
Diagram
Actions
```
## Recommendation
Use this as the first decision or workshop artifact, then add real evidence, owners, and dates.
## Risks And Unknowns
- If the input lacks real evidence, ranking and recommendations remain working assumptions.
- The framework cannot replace stakeholder alignment on goals and constraints.
- The diagram is a communication surface, not final truth.
## Next Actions
1. Confirm the goal and non-negotiable constraints.
2. Add the 2-3 pieces of evidence most likely to change the conclusion.
3. Share the output, collect objections, and update the version.
Mermaid demo
mindmap
root((Zwicky Box))
Facts
Evidence
Signals
Assumptions
Unknowns
Tests
Options
Preferred path
Alternatives
Delivery
Report
Diagram
ActionsPDF-ready HTML demo
<!doctype html>
<html>
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>Zwicky Box: Classic Generation Example</title>
<style>
body { font-family: Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", sans-serif; margin: 48px; color: #161a1d; line-height: 1.6; background: #fbfcf8; }
h1 { font-size: 34px; line-height: 1.1; margin: 0 0 18px; }
h2 { font-size: 20px; margin-top: 28px; }
pre { white-space: pre-wrap; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 18px; overflow-wrap: anywhere; }
.meta { color: #2563eb; font-size: 12px; text-transform: uppercase; font-weight: 800; letter-spacing: .08em; }
.sheet { max-width: 940px; margin: 0 auto; background: #fff; border: 1px solid #dfe3de; border-radius: 8px; padding: 32px; }
@media print { body { margin: 18px; background: #fff; } .sheet { max-width: none; border: 0; padding: 0; } }
</style>
</head>
<body>
<main class="sheet">
<p class="meta">ThinkOps AI PDF-ready output</p>
<h1>Zwicky Box: Classic Generation Example</h1>
<pre># Zwicky Box: Classic Generation Example
## Input Summary
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
## Classic Case Context
We want to build a differentiated AI writing product, but the market already has many chat-style tools. Use a Zwicky Box to split the solution space into user type, input material, output format, collaboration mode, pricing model, and distribution channel. Generate 5 promising product concepts and screening criteria.
## Skill Used
- Zwicky Box
- Break a solution space into dimensions and recombine options.
- Best for: Product concepts, business models, campaigns, and service design.
- Can generate: Dimension table, combinations, screening criteria, and first experiments.
## Situation Judgment
This is a classic situation for Zwicky Box: the input contains a goal, constraints, stakeholder judgments, and a need for action.
## Executive Summary
Separate facts, assumptions, constraints, and actions first, then use Zwicky Box to turn the material into a deliverable. The output should make an actionable judgment, not merely explain the framework.
## Framework Analysis
| Module | Typical output | Purpose |
| --- | --- | --- |
| Facts | Verifiable information from the input | Avoid intuition-only judgment |
| Assumptions | Unknowns that can change the conclusion | Guide validation |
| Framework analysis | Structure through Zwicky Box | Create shared language |
| Action | Owner, time, metric | Drive execution |
## Reusable Diagram
```mermaid
mindmap
root((Zwicky Box))
Facts
Evidence
Signals
Assumptions
Unknowns
Tests
Options
Preferred path
Alternatives
Delivery
Report
Diagram
Actions
```
## Recommendation
Use this as the first decision or workshop artifact, then add real evidence, owners, and dates.
## Risks And Unknowns
- If the input lacks real evidence, ranking and recommendations remain working assumptions.
- The framework cannot replace stakeholder alignment on goals and constraints.
- The diagram is a communication surface, not final truth.
## Next Actions
1. Confirm the goal and non-negotiable constraints.
2. Add the 2-3 pieces of evidence most likely to change the conclusion.
3. Share the output, collect objections, and update the version.
</pre>
<h2>Mermaid diagram source</h2><pre>mindmap
root((Zwicky Box))
Facts
Evidence
Signals
Assumptions
Unknowns
Tests
Options
Preferred path
Alternatives
Delivery
Report
Diagram
Actions</pre>
</main>
</body>
</html>Go back to the generator, paste meeting notes, requirements, customer feedback, or team context, and produce a deliverable.
Start generating