Workshop

Makes domain knowledge visible as a chronological wall of events, from domain events through commands to bounded contexts.

Core question: Which business events, triggers, and boundaries shape the flow, and where do friction, risk, or learning needs arise?

• 2-8 h
• 5-12

Sorts user perspectives into say, think, do, and feel, separating observed facts from assumptions.

Core question: What does this user type say, think, do, and feel, what is evidenced, and which assumption needs testing?

• 30–60 min
• 4-8

Opens the idea space, bundles contributions into theme clusters, and condenses them into a shortlist for the next step.

Core question: Which ideas could address the defined challenge?

• 30-60 min
• 4-12

Gathers quality goals, prioritizes risks, and turns them into architecture topics evaluated together.

Core question: Which quality scenarios matter architecturally to business goals and need clarification first?

• 2-4 h
• 5-15

Gathers system goals, constraints, and building blocks into a compact view for early architecture decisions.

Core question: Which business and functional context bounds the solution space, and which architecture hypotheses must be tested?

• 1-2 h
• 3-10

Condenses individual ideas into clusters, themes, and priorities so consensus grows out of individual contributions.

Core question: What shared picture emerges from our different answers to the focus question?

• 1-3 h
• 5-30

Sorts problems, reframes the top issue, and derives experiments that quickly turn frustration into movement.

Core question: Which most important problem will we address with which solution as the next experiment?

• 60-90 min
• 4-10

Expands a core question into topic fields, filters out patterns, and condenses interesting paths into a shortlist.

Core question: Which 64 concrete ideas emerge when we fully expand eight main themes?

• 45-90 min
• 3-10

Moves architecture context, options, and consequences toward a concrete result through "place the architecture diagram or plan in the center", "set risk categories such as technical, organizational, and external", and "assign an owner and next steps for each top risk".

Core question: Which concrete failure scenarios sit where in the architecture, which matter collectively, and how will we reduce or test them?

• 60-90 min
• 4-12

Moves ideas, open questions, and testable next steps toward a concrete result through "place the core idea in the center", "label the six points with who, what, when, where, how, and why", and "mark gaps and follow-up questions".

Core question: Which decision-relevant questions about this idea still need answers?

• 30-60 min
• 3-10

Parallel design teams turn a shared challenge into comparable concepts, open questions, and a consolidated direction.

Core question: Which integrated design option best satisfies the agreed criteria?

• Halber Tag bis mehrere Tage
• 10-50