[[Driving decisions through clarity]] ## Why this training? In every software project, dozens of decisions are made every week: about architecture, product features, priorities, tools, and delivery trade-offs. Some are small, some are business-critical. Too often, these decisions remain scattered across Slack threads, meeting notes, or just in people’s heads. The result? Teams lose context, repeat the same discussions, forget why things were done a certain way, or struggle when new people join. Leaders risk becoming bottlenecks, while teams feel either disempowered or left in the dark. Recording and structuring decisions isn’t bureaucracy — it’s a way to give your team clarity, continuity, and shared ownership. ## Who is it for? This training is designed for **anyone involved in [[Software Delivery]]**, including: - Developers & Tech Leads - QA engineers - Product Managers - UX / Design roles - Project Managers and anyone facilitating delivery Whether you’re leading decisions or contributing to them, this workshop will help you understand how to approach, document, and sustain them. ## What you will learn Participants will explore real challenges of decision-making in projects, such as: - How to [[Decision-making under uncertainty|make decisions under uncertainty]] without freezing or over-controlling. - How to avoid becoming a [[How not to become bottleneck|decision bottleneck]] as a leader. - When a decision should be a **team effort** and when it can be an **arbitrary call**. - How to capture **trade-offs explicitly**, instead of discovering them too late. - How to **preserve decision knowledge** even when the team changes. - How to balance [[Arbitrary decisions vs team member autonomy|authority and autonomy]] so that teams own decisions responsibly. Along the way, you’ll practice writing and evolving **Decision Records (like ADRs)** that make choices transparent and accountable. ## How you’ll apply it The workshop is hands-on: through scenarios and exercises, you’ll write, review, and update real decision records. You’ll also co-create a “decision radar” to define which types of decisions are worth tracking in your projects. By the end, you’ll walk away with: - Confidence in leading or contributing to decisions with clarity and accountability. - A **clear framework (WHY–WHO–HOW–WHAT)** for framing decisions. - A **lightweight template** for documenting decisions in your team’s repo or backlog. - Practices for evolving decisions over time. To help teams move from **decisions lost in the noise** to **decisions that drive delivery with shared understanding**. WHY - trening miasto - po wyjdzie ze ja wszystko zapisywalem i jestem leaderem, zatem: WHO - kto jest odpowiedzialny za pamietanie decyzji WHAT - ADRy - prezka i podsumowanie po co HOW - jak