Event Storming
Workshop-based method to quickly find out what is happening in the domain of a software program.
What is Event Storming?
Event Storming is a communicative brainstorming method in which knowledge and understanding of a specific, delimited field of knowledge (a domain of expertise) is jointly developed and visualised in a workshop. The starting point are so-called domain events.
The 4 evolution stages of Event Storming
Step 1: Collect Domain Events - discover them.
Step 2: Refine Domain Events - placing them in sequence.
Step 3: Track causes - modelling out the broader ecosystem.
Step 4: Re-sorting & result - categorize the events and build Bounded Contexts.
This template was created by Judith Birmoser.
Get started with this template right now.
Cost-Benefit Analysis Template
Works best for:
Leadership, Decision Making, Strategic Planning
With so many day-to-day decisions to make—and each one feeling high-stakes—it’s easy for all the choices to weigh a business or organization down. You need a systematic way to analyze the risks and rewards. A cost benefit analysis gives you the clarity you need to make smart decisions. This template will let you conduct a CBA to help your team assess the pros and cons of new projects or business proposals—and ultimately help your company preserve your precious time, money, and social capital.
Empathy Map Template
Works best for:
Market Research, User Experience, Mapping
Attracting new users, compelling them to try your product, and turning them into loyal customers—it all starts with understanding them. An empathy map is a tool that leads to that understanding, by giving you space to articulate everything you know about your customers, including their needs, expectations, and decision-making drivers. That way you’ll be able to challenge your assumptions and identify the gaps in your knowledge. Our template lets you easily create an empathy map divided into four key squares—what your customers Say, Think, Do, and Feel.
I Like | I Wish | I Wonder
Works best for:
Agile
Feedback is a key part of any project development and crucial to the iterative process.
Midnight Sailboat Retrospective
Works best for:
Retrospectives, Meetings, Agile Methodology
The Midnight Sailboat Retrospective template offers a metaphorical journey through past experiences and future aspirations, likening the retrospective process to a midnight sailboat voyage. It provides elements for reflecting on challenges faced, lessons learned, and goals for the future. This template enables teams to navigate uncertainties, chart a course for success, and foster a culture of resilience. By promoting reflection and metaphorical thinking, the Midnight Sailboat Retrospective empowers teams to overcome obstacles, embrace change, and sail towards their goals effectively.
Feature Planning Template
Works best for:
Desk Research, Agile Methodology, Product Management
Features are what make a product or service fun, but adding new ones is no walk in the park. It takes many steps—ideating, designing, refining, building, testing, launching, and promoting—and just as many stakeholders. Feature Planning lets you put a smooth, sturdy process in place, so you can add a feature successfully, and spend less time and resources doing it. That makes our Feature Planning Template a smart starting point for anyone looking to add new product features, especially members of product, engineering, marketing, and sales teams.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.