productive-thinking-model
Skill3 starsChanged 6 months agoMITView on GitHub
Use the productive thinking model to solve defined problems creatively through a structured six-step process. Use when clarifying what is going on, defining success, generating questions, and selecting solutions.
In this repository23 other files it gives its agents.
- abstraction-ladderingSkill
- balancing-feedback-loopSkill
- concept-mapSkill
- confidence-determines-speed-vs-qualitySkill
- conflict-resolution-diagramSkill
- connection-circlesSkill
- cynefin-frameworkSkill
- decision-matrixSkill
- eisenhower-matrixSkill
- first-principlesSkill
- hard-choice-modelSkill
- iceberg-modelSkill
- impact-effort-matrixSkill
- inversionSkill
- ishikawa-diagramSkill
- issue-treesSkill
- ladder-of-inferenceSkill
- minto-pyramidSkill
- ooda-loopSkill
- reinforcing-feedback-loopSkill
- second-order-thinkingSkill
- situation-behavior-impactSkill
- six-thinking-hatsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Use the DRIVE framework:
- Distinctive: line 42
Use phrases like "How might we...?" or "How can I...?"
- Distinctive: line 50
Use a decision matrix to select best solutions
- Distinctive: line 56
Create detailed execution plan
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Productive Thinking Model
Overview
- Category: Problem Solving Tool
- Created by: Tim Hurson
- Purpose: Solve problems creatively and efficiently through structured, critical thinking
When to Use
Best used when:
- A problem is already defined
- You're looking for creative solutions
6-Step Framework
1. Ask "What's Going On?"
- Understand the problem deeply
- Key questions to explore:
- What's the exact problem?
- What's the problem's impact?
- What information do you already have?
- Who is involved?
- What's the vision when the problem is solved?
2. Ask "What's Success?"
Use the DRIVE framework:
- Do: What should the solution do?
- Restrictions: What must it NOT do?
- Invest: What resources are available?
- Values: What principles matter?
- Essential outcomes: What are the key results?
3. Ask "What's the Question?"
- Generate "catalytic questions"
- Use phrases like "How might we...?" or "How can I...?"
4. Generate Answers
- Brainstorm potential solutions
- Collect ideas without judgment
5. Forge the Solution
- Evaluate ideas against success criteria
- Use a decision matrix to select best solutions
- Refine chosen solution
6. Align Resources
- Specify necessary actions
- Identify responsible people
- Create detailed execution plan
Example Scenario
Winning a prospective customer with challenging requirements:
- Understand situation
- Define success criteria
- Generate key questions
- Brainstorm solutions
- Choose best approach (e.g., hands-on product demo)
- Plan resource allocation
Source
"Think Better: An Innovator's Guide to Productive Thinking" by Tim Hurson
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.