workshop

Turns domain knowledge, language, and system boundaries into a tangible result by selecting a business flow, collecting domain events chronologically, and deriving models and follow-up questions.

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 our user say, think, do, and feel, how do we know this, and where are our blind spots?

30-60 min

4-8

Turns ideas, open questions, and testable next steps into a tangible result through defining a challenge, agreeing on rules, and clustering and selecting outcomes.

Core question: What range of solution ideas can we generate for the challenge before we converge and choose?

30-60 min

4-12

Turns architecture context, options, and consequences into a tangible result by collecting stakeholder goals, eliciting quality scenarios, and documenting architecture implications.

Core question: Which Quality Attributes with which concrete scenarios are architecture-critical for the system, and in which order must they be addressed?

2-4 h

5-15

Turns architecture context, options, and outcomes into a tangible result by naming the system and goals, gathering stakeholders and constraints, and documenting decisions and questions.

Core question: Which components, interfaces, decisions and cross-cutting concerns together form a consistent architecture that satisfies the quality attribute scenarios?

1-2 h

3-10

Turns group contributions, selection, and decision-making into a tangible result by asking a focus question, collecting ideas individually, and formulating consensus themes.

Core question: Which shared themes emerge from the variety of individual contributions to the focus question?

1-3 h

5-30

Turns group inputs, selection, and decision-making into a tangible result by collecting problems silently, clustering and prioritizing, and choosing experiments.

Core question: Which problem is most important right now, and which concrete first step changes it in the next 14 days?

60-90 min

4-10

Turns ideas, open questions, and testable next steps into a tangible result by defining the central challenge, deriving eight major themes, and shortlisting ideas.

Core question: Which eight thematic fields open up the solution space of the central challenge, and what concrete ideas emerge in each field?

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 risks are embedded in this architecture or plan artifact, and which of them need action before the next iteration?

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 questions around who, what, when, where, how and why must the team answer before meaningful solution work can start?

30-60 min

3-10

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

Core question: What solution sketch emerges when multiple stakeholders work on sub-questions of a complex challenge in parallel and combine results in one day?

Halber Tag bis mehrere Tage

10-50