View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps ChatOps |  Product Discovery Pretotyping |  Innovation Reverse Brainstorming |  Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Ongoing | Stunden bis wenige Tage | 30-60 min | 45-90 min |
Participantsdifferent | 2-20 | 1-4 | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Chat Transcript, Action Log, Automations | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Reverse Ideas, Risk Themes, Solution Ideas | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | CollaborationEngineeringIncident | ValidationDemandMVP | BrainstormingIdeationCreativityRisk | BrainstormingIdeationCreativityDivergenceWorkshop |