Deconstruct and Reconstruct Innovation Framework

Problem it addresses

When product, business model, or personal growth work hits a bottleneck, teams often jump to feature stacking, slogan swapping, or unstructured brainstorming. This skill is for scenarios where the goal is to turn a complex problem into an operable structure. It helps identify user pain points, separate hard constraints from industry habits, find cross-domain patterns, and converge ideas into an MVP and iteration plan.

How it works

It follows Disassembly -> Insight -> Reassembly -> Iteration across 12 steps:
- Disassembly: strip away surface assumptions, decompose elements, and audit boundaries, distinguishing physical/legal constraints from industry conventions and self-imposed limits.
- Insight: dig into friction points, map cross-domain solutions, and extract the underlying logic instead of staying at surface features.
- Reassembly: use removal, substitution, strengthening, weakening, addition, and re-linking to form a new proposal and design its value-delivery path.
- Iteration: stress-test the idea, collect quantitative and qualitative feedback, and re-decompose when assumptions fail.

The output is an innovation proposal in a Word-document-style structure, including an executive summary, decomposition analysis, insight findings, reassembly plan, iteration plan, and action checklist.

Boundaries and cautions

It fits best when there is a clear business object and structured innovation is needed, such as product redesign, service workflow optimization, or business-model hypothesis testing. It may be less effective than open brainstorming when inputs are thin or the goal is purely divergent ideation. Prepare case studies, user journeys, and competitor data where possible, and split the 12 steps across multiple rounds instead of forcing a complete proposal in one pass.