methodatlas
RunsheetInnovation

TRIZ

ComplexityHigh
Time1-4 h
Participants2-8
FormatWorkshop + async
MaturityCanonical
01

Prerequisite

What needs to be finished first

Complete firstProblem Framing Workshopnot in catalog

The problem can be formulated as a conflict between two mutually blocking requirements (technical or physical contradiction).

Without: Without an identifiable contradiction, TRIZ delivers empty principles and the group searches unsuccessfully for matching invention patterns.
02

Preparation

What needs to be ready before start

Materials

TRIZ contradiction matrix (39x39); list of the 40 inventive principles with examples; whiteboard or Miro board with three areas (contradiction, principles, solution ideas); pens; timer.

People / roles

One facilitator with TRIZ experience who formulates the contradiction cleanly and interprets principles; two to eight participants from domain and technology; one scribe for solution concepts.

Pre-read

Problem statement as one sentence; known previous solution attempts and why they hit a tradeoff; constraints; availability of contradiction matrix as table or online tool.

Time needed

1-4 h

Setup

Mark three areas on the board. Provide contradiction matrix. Rule: first clean contradiction, then principles, then concepts. Keep examples for principles visible.

03

Core question

The one question this method answers

Which inventive principles resolve the identified contradiction, and which concrete concepts emerge when these principles are applied to the problem?

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Formulate problem and contradiction
20-30 minFix problem in one sentence. Name improving and worsening parameters (for example "If we improve response time, accuracy worsens"). Map both parameters clearly to the 39 standard parameters.If no worsening parameter is found, it is not a contradiction but pure optimization. TRIZ is unsuitable; choose another method.
2Phase 2: Derive principles from matrix
15-20 minLook up the intersection of the two parameters in the contradiction matrix. Note recommended principles (typically 3-4). Read definition and generic example per principle.The matrix provides a trigger, not the answer. If recommended principles sound foreign, translate them into your domain knowledge before rejecting them.
3Phase 3: Develop solution ideas
30-60 minPer principle, solo sketching for 5 min: ideas for applying the principle to the concrete problem. Then gallery, short presentation, cluster parallel ideas.Principles such as "segmentation" or "prior action" sound abstract. An analogous example from another industry helps create the aha moment.
4Phase 4: Feasibility and selection
20-30 minEvaluate top-3 concepts with three criteria: technical feasibility, cost, impact. Decider selects one direction with rationale. Note open assumptions as spikes.Concepts that feel "too wild" in this phase are often real innovations. Before discarding, evaluate again with a longer horizon.
05

Artifact

What comes out at the end

Form

Markdown document with contradiction sentence, identified standard parameters, recommended principles from matrix, developed solution concepts per principle, evaluation, and chosen direction with rationale and owner.

Versioning / ownership

Own entry per problem field with date and decider. For later TRIZ sessions on the same problem, create v2 and explicitly reference previous principles.

Tool alternatives
  • Miro with TRIZ matrix frame and voting plugin
  • Confluence page with contradiction table
  • Online tool TRIZ40 or Oxford Creativity
  • Notion page with database per principle

triz-working-template.md

Compact working template for TRIZ with contradictions, inventive principles, and solution concepts.

TRIZ Working Template

Goal

Use contradiction-driven thinking to generate solution concepts for complex problems.

Context

What problem or trade-off should the group analyze?

Input

  • Problem statement:
  • Contradiction:
  • Constraints:
  • Observations:

Working area

  • Improving factors:
  • Worsening factors:
  • Inventive principles:
  • Solution ideas:
  • Feasibility notes:

Output artifacts

  • Contradiction statement:
  • Inventive principles:
  • Solution concepts:

Open questions

  • ...

Decision / next step

Owner, date, and success signal.

06

Example output

Concrete filled scenario, fictional example

triz-beispiel.md

Concrete filled scenario, fictional example

TRIZ - Account security vs. login friction (2026-05-15)

Contradiction: If we increase account security (more factors, captchas), login conversion worsens.

Standard parameters: Improving 35 "adaptability", worsening 33 "ease of operation".

Recommended principles (from matrix): 15 dynamization, 16 partial or excessive action, 35 parameter change, 30 flexible shells.

Concepts:

  • Principle 15 dynamization: number of factors varies by risk score (known device plus IP = one factor, new device plus travel zone = three factors).
  • Principle 35 parameter change: instead of more factors at login, use harder factors for sensitive actions (for example payout instead of login).

Selection: Risk-based MFA (concept 1) plus step-up for sensitive actions (concept 2). Decider: @lisa. Spike for risk-score data model by 2026-05-30, owner: @ben.

07

Pitfalls

Recognize symptoms and steer against them

Trap

No real contradiction

Symptom

Problem is pure optimization, no tradeoff, or worsening parameter is missing.

What to do

Pause method. If no contradiction exists, TRIZ is unsuitable. Choose an alternative such as Morphological Analysis or SCAMPER.

Trap

Parameters assigned incorrectly

Symptom

Assigned standard parameters do not fit the actual conflict; recommended principles seem absurd.

What to do

Before phase 2, check two parameter assignments against definitions of the 39 parameters. If unsure, run both possible pairs and compare principles.

Trap

Principles taken too literally

Symptom

Group tries to implement principle "segmentation" literally instead of using it as thought trigger.

What to do

Put one example from a different industry on the wall per principle. Principles are analogical inspiration, not solution templates.

Trap

Solution without feasibility test

Symptom

Concept selected, but nobody checks whether it is implementable in current context.

What to do

Enforce phase 4 with three criteria (feasibility, cost, impact). Concepts with a very low criterion score become spikes, not plans.

Trap

Workshop without TRIZ experience

Symptom

Facilitator looks up matrix for the first time, principles are discarded because they are unfamiliar.

What to do

Bring a TRIZ coach or at least someone with practice. Alternatively use method after a demo session with a simpler problem.

08

Stop criteria

Done signals checkable in under a minute

No technical or physical contradiction identifiable, method unsuitable.
Standard parameters cannot be assigned after 30 min, matrix yields no meaningful principles.
No person with domain knowledge present, translation of principles fails.
Workshop scheduled under 60 min, four phases cannot be run.
Recommended principles are rejected wholesale as "do not fit", with no translation attempts.
Problem is a pure prioritization question, not an invention question.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.