Lean Coffee by Michael de la Maza
Lean Coffee is a simple and easy-to-facilitate structure for meetings. Participants begin the meeting by creating the agenda. Then each topic is discussed in priority order using short timeboxes.
Where did 'Lean Coffee' come from?
Lean Coffee was created by Jim Benson and Jeremy Lightsmith in 2009 in Seattle.
Lean Coffee works best with groups of 10 people or less.
It is designed to be easy to facilitate.
This template was created by Michael de la Maza.
Get started with this template right now.
Lean Inception
Works best for:
Agile, Meetings
Lean Inception is a collaborative workshop for aligning teams on project goals and scope. It provides a structured framework for defining the product vision, user personas, and feature prioritization. This template enables cross-functional teams to collaborate, validate assumptions, and establish a shared understanding of the project vision and objectives. By promoting early alignment and customer-centric thinking, Lean Inception empowers teams to kickstart projects with clarity and purpose, driving efficiency and innovation from the outset.
Startup Canvas Template
Works best for:
Leadership, Documentation, Strategic Planning
A Startup Canvas helps founders express and map out a new business idea in a less formal format than a traditional business plan. Startup Canvases are a useful visual map for founders who want to judge their new business idea’s strengths and weaknesses. This Canvas can be used as a framework to quickly articulate your business idea’s value proposition, problem, solution, market, team, marketing channels, customer segment, external risks, and Key Performance Indicators. By articulating factors like success, viability, vision, and value to the customer, founders can make a concise case for why a new product or service should exist and get funded.
Sprint Review Template
Works best for:
Sprint Review, Agile
The Sprint Review Template is a vital tool in Agile project management that enhances communication between team members and stakeholders by providing a clear format for presenting the sprint's accomplishments and challenges. It encourages active participation and feedback from all attendees, leading to more informed decision-making and continuous improvement. In essence, it's a catalyst for meaningful dialogue and collaborative growth.
Design Sprint Retrogram
Works best for:
Agile, Retrospective
The Design Sprint Retrogram template facilitates retrospective sessions for Design Sprint teams to reflect on their experiences and identify improvement opportunities. It provides a structured framework for reviewing sprint outcomes, discussing what worked well, what didn't, and generating actionable insights. This template fosters a culture of continuous learning and refinement, empowering teams to enhance their sprint process and deliver better outcomes in subsequent sprints.
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.
SAFe Roam Board
Works best for:
Agile Methodology, Operations, Agile Workflows
A SAFe ROAM Board is a framework for making risks visible. It gives you and your team a shared space to notice and highlight risks, so they don’t get ignored. The ROAM Board helps everyone consider the likelihood and impact of risks, and decide which risks are low priority versus high priority. The underlying principles of SAFe (Scaled Agile Framework) are: drive cost-effective solutions, apply systems thinking, assume that things will change, build incrementally, base milestones on evaluating working systems, and visualize and limit works in progress.