collaboration

Turns ideas, open questions, and testable next steps into a tangible result through setting a prompt, writing silently, and reviewing the output.

Core question: What range of ideas can we generate when each person first writes quietly and builds on others' ideas?

15-30 min

3-12

Turns incident work, roles, and countermeasures into a tangible result by integrating tools, routing alerts, and improving the workflow.

Core question: Which recurring operational actions can be triggered safely, traceably, and across the team in chat instead of in scattered tools?

Ongoing

2-20

Turns backlog, sprint work, and team flow into a tangible result by bringing a story, checking business intent, and agreeing on next steps.

Core question: Are what, how, and what-can-break clear enough for the story to be implemented without further refinement?

15-30 min

3

Turns user actions, touchpoints, and design concepts into a tangible result by clarifying the problem and constraints, sketching individually, and iterating together.

Core question: Which solution sketch addresses the design challenge best while taking user insights and constraints into account?

1-3 h

3-8

Turns group input, selection, and decision into a tangible result by clarifying team purpose, capturing goals and stakeholders, and reviewing the charter over time.

Core question: Why does the team exist, how does it measure success, and how does it collaborate so everyone knows what to expect from each other?

2-4 h

3-12

Turns team flow, expectations, and delivery rhythm into a tangible result by clarifying work context, collecting expectations, and setting a review cadence.

Core question: Which concrete behavior expectations make collaboration easier, and which of them does the team want to commit to?

45-90 min

3-12

Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare the team list", "explain the three modes with examples", and "document agreements per pair".

Core question: Which interaction mode fits per team pair, and how do we agree modes bindingly to reduce interface friction?

Half day

Team-Leads plus Architecture

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