Don’t we all think that we get more done if we stay busy? We feel good and efficient. We get a pat on the back or a nod of approval from the managers when pulling that all-nighter once again. It may feel good and we could even get a raise for being so efficient, but is this good for the company? Is it good for our customers?
Testing Business Ideas by David Bland & Alex Osterwalder Peerasak C.
"This new Strategyzer book builds upon the Business Model Canvas and Value Proposition Canvas by integrating Assumptions Mapping and other powerful lean startup-style experiments." The Strategyzer
Free download: https://www.strategyzer.com/emails/testing-business-ideas-preview-free-download
To buy: https://www.strategyzer.com/books/testing-business-ideas-david-j-bland ; Amazon.com: Testing Business Ideas (9781119551447): David J. Bland, Alexander Osterwalder: Books https://amzn.to/2Pg7foy
Jerry Chen, partner at Greylock and former VP of Cloud and Application Services at VMware, shares his Unit of Value framework for startups building a go-to-market strategy. He developed this strategy while managing product and marketing teams at VMware that shipped many “1.0” releases, including VMware VDI, Cloud Foundry, and vFabric, and continues to use the framework to evaluate companies as an investor.
Hooks and Upsell: Bottoms-Up Product and GTM StrategyVivek Saraswat
A framework for growing bottoms-up (i.e. product-led) adoption in B2B products, along with a summary of commonly-used GTM strategies and sales models
Originally presented at Open Core Summit 2020 by Vivek Saraswat (Venture Partner at Mayfield, Product Leader at Docker/VMware/AWS)
I would like twenty minutes of your time in which I will present 50 (I know a lot) slides to review 12 Models related to Lean Startup so that I can then introduce the
‘Startup Business Planning Jigsaw’.
The twelve models are:
► Business Model Canvas - Alexander Osterwalder
► Search v's Execution - Steve Blank & Bob Dorf
► Build-Measure-Learn - Eric Ries
►Three Stages of a Startup - Ash Maurya
► MVP and Product Market Fit
►Lean Canvas - Ash Maurya
► Customer Development - Brant Cooper and Patrick Vlaskovits
► Startup Pyramid – Sean Ellis
►Get Keep Grow – Steve Blank & Bob Dorf
► Pirate Metrics – Dave McClure
►One Metric that Matters - Croll & Yoskovitz
Testing Business Ideas by David Bland & Alex Osterwalder Peerasak C.
"This new Strategyzer book builds upon the Business Model Canvas and Value Proposition Canvas by integrating Assumptions Mapping and other powerful lean startup-style experiments." The Strategyzer
Free download: https://www.strategyzer.com/emails/testing-business-ideas-preview-free-download
To buy: https://www.strategyzer.com/books/testing-business-ideas-david-j-bland ; Amazon.com: Testing Business Ideas (9781119551447): David J. Bland, Alexander Osterwalder: Books https://amzn.to/2Pg7foy
Jerry Chen, partner at Greylock and former VP of Cloud and Application Services at VMware, shares his Unit of Value framework for startups building a go-to-market strategy. He developed this strategy while managing product and marketing teams at VMware that shipped many “1.0” releases, including VMware VDI, Cloud Foundry, and vFabric, and continues to use the framework to evaluate companies as an investor.
Hooks and Upsell: Bottoms-Up Product and GTM StrategyVivek Saraswat
A framework for growing bottoms-up (i.e. product-led) adoption in B2B products, along with a summary of commonly-used GTM strategies and sales models
Originally presented at Open Core Summit 2020 by Vivek Saraswat (Venture Partner at Mayfield, Product Leader at Docker/VMware/AWS)
I would like twenty minutes of your time in which I will present 50 (I know a lot) slides to review 12 Models related to Lean Startup so that I can then introduce the
‘Startup Business Planning Jigsaw’.
The twelve models are:
► Business Model Canvas - Alexander Osterwalder
► Search v's Execution - Steve Blank & Bob Dorf
► Build-Measure-Learn - Eric Ries
►Three Stages of a Startup - Ash Maurya
► MVP and Product Market Fit
►Lean Canvas - Ash Maurya
► Customer Development - Brant Cooper and Patrick Vlaskovits
► Startup Pyramid – Sean Ellis
►Get Keep Grow – Steve Blank & Bob Dorf
► Pirate Metrics – Dave McClure
►One Metric that Matters - Croll & Yoskovitz
Ever wondered how unit economics affect your growth rate? Quantitative analysis is the most essential part of successful growth hacking. Here is a specific example.
VC Bootcamp By DFJ Gotham Ventures and Wilson Sonsini Goodrich & RosatiMark Davis
Slides from the Venture Capital Bootcamp event hosted by DFJ Gotham Ventures and Wilson Sonsini Goodrich & Rosati at Columbia University on June 3, 2009. A video of the 3 hour event is available at www.dfjgotham.com.
Eric Ries, Author/Speaker/Consultant, The Lean Startup500 Startups
Presentation by Eric Ries (Author/Speaker/Consultant, The Lean Startup) at the 'Lean Startup, Lean Investor' event on November 3, 2010 (Produced by 500 Startups & Nokia/Nokia Growth Partners)
Business Model Canvas vs Lean Canvas vs One-Page Lean StartupRod King, Ph.D.
The Business Plan is the traditional document that established businesses and non-profit organizations as well as startups, entrepreneurs, and innovators use to document their strategy and tactics for achieving goals in projects. However, the traditional business plan is voluminous, complex, filled with grand hypotheses (vision), and becomes increasingly irrelevant as a project proceeds in the real world.
In recent years, many individuals and organizations have been abandoning the traditional business/strategic plan in favor of one-page documents that present project plans, business models, and ecosystems. The most common one-page project summaries are currently the tools of the Business Model Canvas, Lean Canvas, and One-Page Lean Startup. This presentation briefly introduces and compares these three business model (ecosystem) mapping tools especially using the workflow of 8 activities for Lean Startup Project Management.
Which business model (ecosystem) mapping tool is your favorite? And why?
What other tools are you using for summarizing, presenting, and managing your project plans as well as business models and ecosystems?
We look forward to hearing from you.
Best regards.
Lean Agile Center of Excellence LACE – Drink our own ChampagneCA Technologies
How to establish a Lean Agile Center of Excellence in your organization, and lead your transformation initiative in an Agile way. Drinking our own champagne as change agents.
Create and Evolve your Lean Agile Center of Excellence!
Building the Billion dollar SaaS Unicorn for 2018Kelly Schwedland
In a Venture Capital world that is obsessed with growth, recurring revenue and software as a service, after you validate that you have a solution that people are willing to pay for, there is an entire new world ahead of you in scaling that venture. For many, this involves an entirely new language and set of metrics to manage the business. For the startup that wants to make the leap to scale up and fast growth this should serve as a starting point for key insights and metrics for that journey.
Creating a lean and agile enterprise - The Lean Product Lifecyclestrongandagile.co.uk
Exploring the Lean Product Lifecycle for Enterprise innovation and product management using Agile and Lean Startup Practices. How to capture and scale ideas across businesses.
Full Program & Tools to Accelerate an Internal Innovation Project - by Board ...Board of Innovation
By Board of Innovation (www.boardofinnovation.com) -
Full program & tools available. A step by step approach to accelerate an internal innovation project in your company.
By Board of Innovation (www.boardofinnovation.com)
Full program & tools available. A step by step approach to create an innovation platform in your company.
Best Practices for an Effective Innovation ProcessMindjet
In our webinar with Forrester VP and analyst Chip Gliedman, we discuss best practices for implementing an effective innovation process, from ideas through execution.
Phil Dillard, Black Ant, @PhilD0210
The objective of the Lean Startup 101 training is to introduce the concepts, terminology and approaches — and, to help organizations overcome resistance accepting the new approach so that exploration and learning can begin. This practical, interactive session will provide a solid foundation for advanced sessions, including the Lean Startup 201 & 301. This training is designed for practitioners in both the enterprise and in startups who are relatively new to the Lean Startup approach or who are seeking a quick refresher. Lean Startup 101 is a perfect way to kick off your week of Lean Startup!
Thanks to Lean Startup Co.’s law firm, Orrick, for being the sponsor for this track.
Dan Olsen, The Lean Product Playbook , @danolsen
Room: C260
Everyone working on a new product is trying to achieve the same goal: product-market fit. Although product-market fit is one of the most important Lean Startup concepts, it’s also the least well defined. Dan Olsen shares the top advice from his book The Lean Product Playbook, including the Product-Market Fit Pyramid: an actionable model that breaks product-market fit down into 5 key elements. Dan also explains the Lean Product Process, a 6-step methodology with practical guidance on how to achieve product-market fit, illustrated with a real-world case study.
Learn how to shift your focus from keeping people and equipment busy to having work flowing to your customers without unwanted waiting time and how that new focus will affect your meetings, process management, and metrics.
How to improve flow efficiency, remove the red bricks Agile2014Håkan Forss
Do you want to improve end-to-end feature lead-time? It is not a question of working harder. It is a question of first removing the feature wait time, the red bricks.
If you would build an end-to-end timeline for your features using red, yellow and green LEGO bricks. Where:
* Red = Non value adding waiting time
* Yellow = Non value adding activates required due to how work is organized
* Green = Value adding activities of real customer value
How would your feature end-to-end timeline look like? In most cases, you will have less than 20% green and yellow bricks and more the 80% red bricks.
In this session, you will be see how flow efficiency can be drastically improve in two concrete examples from two different domains.
First, you will see how a Swedish Breast Cancer Clinic drastically improved flow efficiency and reduced patient wait time by focusing on removing the red and yellow bricks.
In the second example, you will see how a Product Development Test Organization reduced lead-time and created time for improvements by focusing on improving flow efficiency.
We will take a close look at the three laws that define the performance of all processes:
* Little’s Law
* Law of bottlenecks
* Law of variation
By understanding how the three laws governs the performance of your processes, we can look at ways to improve your flow efficiency.
When time is gone, it is gone. Time to start removing the red and yellow bricks
Ever wondered how unit economics affect your growth rate? Quantitative analysis is the most essential part of successful growth hacking. Here is a specific example.
VC Bootcamp By DFJ Gotham Ventures and Wilson Sonsini Goodrich & RosatiMark Davis
Slides from the Venture Capital Bootcamp event hosted by DFJ Gotham Ventures and Wilson Sonsini Goodrich & Rosati at Columbia University on June 3, 2009. A video of the 3 hour event is available at www.dfjgotham.com.
Eric Ries, Author/Speaker/Consultant, The Lean Startup500 Startups
Presentation by Eric Ries (Author/Speaker/Consultant, The Lean Startup) at the 'Lean Startup, Lean Investor' event on November 3, 2010 (Produced by 500 Startups & Nokia/Nokia Growth Partners)
Business Model Canvas vs Lean Canvas vs One-Page Lean StartupRod King, Ph.D.
The Business Plan is the traditional document that established businesses and non-profit organizations as well as startups, entrepreneurs, and innovators use to document their strategy and tactics for achieving goals in projects. However, the traditional business plan is voluminous, complex, filled with grand hypotheses (vision), and becomes increasingly irrelevant as a project proceeds in the real world.
In recent years, many individuals and organizations have been abandoning the traditional business/strategic plan in favor of one-page documents that present project plans, business models, and ecosystems. The most common one-page project summaries are currently the tools of the Business Model Canvas, Lean Canvas, and One-Page Lean Startup. This presentation briefly introduces and compares these three business model (ecosystem) mapping tools especially using the workflow of 8 activities for Lean Startup Project Management.
Which business model (ecosystem) mapping tool is your favorite? And why?
What other tools are you using for summarizing, presenting, and managing your project plans as well as business models and ecosystems?
We look forward to hearing from you.
Best regards.
Lean Agile Center of Excellence LACE – Drink our own ChampagneCA Technologies
How to establish a Lean Agile Center of Excellence in your organization, and lead your transformation initiative in an Agile way. Drinking our own champagne as change agents.
Create and Evolve your Lean Agile Center of Excellence!
Building the Billion dollar SaaS Unicorn for 2018Kelly Schwedland
In a Venture Capital world that is obsessed with growth, recurring revenue and software as a service, after you validate that you have a solution that people are willing to pay for, there is an entire new world ahead of you in scaling that venture. For many, this involves an entirely new language and set of metrics to manage the business. For the startup that wants to make the leap to scale up and fast growth this should serve as a starting point for key insights and metrics for that journey.
Creating a lean and agile enterprise - The Lean Product Lifecyclestrongandagile.co.uk
Exploring the Lean Product Lifecycle for Enterprise innovation and product management using Agile and Lean Startup Practices. How to capture and scale ideas across businesses.
Full Program & Tools to Accelerate an Internal Innovation Project - by Board ...Board of Innovation
By Board of Innovation (www.boardofinnovation.com) -
Full program & tools available. A step by step approach to accelerate an internal innovation project in your company.
By Board of Innovation (www.boardofinnovation.com)
Full program & tools available. A step by step approach to create an innovation platform in your company.
Best Practices for an Effective Innovation ProcessMindjet
In our webinar with Forrester VP and analyst Chip Gliedman, we discuss best practices for implementing an effective innovation process, from ideas through execution.
Phil Dillard, Black Ant, @PhilD0210
The objective of the Lean Startup 101 training is to introduce the concepts, terminology and approaches — and, to help organizations overcome resistance accepting the new approach so that exploration and learning can begin. This practical, interactive session will provide a solid foundation for advanced sessions, including the Lean Startup 201 & 301. This training is designed for practitioners in both the enterprise and in startups who are relatively new to the Lean Startup approach or who are seeking a quick refresher. Lean Startup 101 is a perfect way to kick off your week of Lean Startup!
Thanks to Lean Startup Co.’s law firm, Orrick, for being the sponsor for this track.
Dan Olsen, The Lean Product Playbook , @danolsen
Room: C260
Everyone working on a new product is trying to achieve the same goal: product-market fit. Although product-market fit is one of the most important Lean Startup concepts, it’s also the least well defined. Dan Olsen shares the top advice from his book The Lean Product Playbook, including the Product-Market Fit Pyramid: an actionable model that breaks product-market fit down into 5 key elements. Dan also explains the Lean Product Process, a 6-step methodology with practical guidance on how to achieve product-market fit, illustrated with a real-world case study.
Learn how to shift your focus from keeping people and equipment busy to having work flowing to your customers without unwanted waiting time and how that new focus will affect your meetings, process management, and metrics.
How to improve flow efficiency, remove the red bricks Agile2014Håkan Forss
Do you want to improve end-to-end feature lead-time? It is not a question of working harder. It is a question of first removing the feature wait time, the red bricks.
If you would build an end-to-end timeline for your features using red, yellow and green LEGO bricks. Where:
* Red = Non value adding waiting time
* Yellow = Non value adding activates required due to how work is organized
* Green = Value adding activities of real customer value
How would your feature end-to-end timeline look like? In most cases, you will have less than 20% green and yellow bricks and more the 80% red bricks.
In this session, you will be see how flow efficiency can be drastically improve in two concrete examples from two different domains.
First, you will see how a Swedish Breast Cancer Clinic drastically improved flow efficiency and reduced patient wait time by focusing on removing the red and yellow bricks.
In the second example, you will see how a Product Development Test Organization reduced lead-time and created time for improvements by focusing on improving flow efficiency.
We will take a close look at the three laws that define the performance of all processes:
* Little’s Law
* Law of bottlenecks
* Law of variation
By understanding how the three laws governs the performance of your processes, we can look at ways to improve your flow efficiency.
When time is gone, it is gone. Time to start removing the red and yellow bricks
The Busy Bee Paradox Agile Tour Lille 2014Håkan Forss
Don’t we all think that we get more done if we stay busy? We feel good and efficient. We may even get a pat on the back or even a promotion.
But is this good for the company? Is it good for our customers? Are we really optimizing for the whole or are we just keeping ourselves busy?
KATA - Habits for lean learning Agile Australia 2016Håkan Forss
Learn how to build a Lean learning culture at every level of your organisation. In this presentation from the LEGO enthusiast and Agile Coach at King Hakan Forss, you will discover how the Improvement Kata and Coaching Kata can form the foundational habits of a Lean learning organisation. You will be introduced to two core habits and how they will help you to create an organisation of learners that will improve your business.
How we made three very important mental leaps to make the transition to Agile and Lean stick at Ericsson 3G including examples of what we have tried
* From methods & tools to principles & mindset;
* From resource efficiency to flow efficiency;
* From scattered experiences to continuous innovation
The red brick cancer Lean Agile Scotland 2013-09-19Håkan Forss
Time is valuable, and when it is gone, it is gone. Are you focusing on flow or just keeping yourself busy? How much has the red brick cancer spread in your processes?
In this session we will talk about time. We will explore the differences between systems with high resource efficiency and systems focused on flow efficiency. We take a look at how to remove the red brick cancer in your processes. You will learn how to understand and improve the end to end flow in your system.
Experimentation is King Lean Kanban Central Europe 2015Håkan Forss
Developing games for the high demand, fast moving mobile market, is truly a challenge. Creating moments of magic is the art of finding the right trade-off between polish and time to feedback.
King have developed over 190 games, including the world famous Candy Crush. In this session, we will share our recent experience in how to use evolutionary and experimental approaches in order to deliver disruptive innovation as well as continuous improvements. We will share insights in why Culture is King when you want to create an ever learning and evolving organization.
From Scooter to Race bike - A Toyota Kata story
This is a story of a teams Improvement Kata journey. You will see how they transitioned from a scooter to a race bike.
This presentation was given as part of the KataSummit 2015 Software Practitioners Panel in Fort Lauderdale 2015-02-19
Make the invisible visible - Visual management in agile product developmentHåkan Forss
Most of today's knowledge work is almost exclusively done digitally. If you would step into an office and try to observe the process you will most likely find it hard to understand what is really happening. Most of the work is as ones and zeros hidden in many different digital repositories.
To create a common and shared understanding in knowledge work we often need to make the invisible visible.
During this session Håkan Forss will share his experiences of creating common and shared understanding of the invisible knowledge work using visual management.
Toyota kata in knowledge work - European Lean Educator Conference 2014Håkan Forss
* What are the habits, routines, behavior patterns, needed to strive for excellence every day?
* How do we create a culture of continuous learning and improvement?
* The Improvement KATA and the Coaching KATA
* The KATA in knowledge work context
* How to start applying the Improvement KATA and Coaching KATA tomorrow
The red brick cancer ACE! Conf 2013-04-16Håkan Forss
We will explore the differences between systems with high resource efficiency and systems focused on flow efficiency. You will learn how to understand and improve the end to end flow in your system.
Toyota kata – habits for continuous improvements MIX IT 2014-04-29Håkan Forss
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
What are the habits, routines, behavior patterns, needed to strive for excellence every day? How do we create a culture of continuous learning and improvement?
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your vision, your state of awesomeness, in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
In this session, we will take Toyota Kata out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context tomorrow.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
Ideas for now
•How Toyota Kata can become the catalyst for creating a culture of continuous learning and improvement, a kaizen culture.
•How Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization.
•How the Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
•How small daily experiments lower the resistance to change and builds a kaizen culture.
•How to use the great power of habits to build a new culture.
•How to apply the Improvement Kata and Coaching Kata in a software development context
Read more at http://hakanforss.wordpress.com/tag/toyota-kata/
Toyota Kata – habits for continuous improvements Lean IT Summit 2013Håkan Forss
Toyota Kata – habits for continuous improvements
Description:
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
What are the habits, or routines, you need to put in place to continuously strive for excellence? How do we create a culture of continuous improvement?
In this session you will learn about continuous improvement routines that help you close the gap between your current condition and you desired future state. You will learn how you can probe through the unknown in small deliberate steps. You will also be introduced to the leadership routines to build a continuous improvement culture. These routines are what we call Toyota Kata.
Kanban Kata - Lean Kanban European Conference Tour 2012Håkan Forss
This SlideShare is the updated version of the presentation I gave at Lean Kanban France 2012 (#LKFR12), Lean Kanban Central Europe 2012 (#LKCE12) and Lean Kanban Netherlands 2012 (#LKNL12)
Kanban Kata is a guided approach to how to improve collaboratively using the scientific method.
In this session you will learn how combine the power of the Kanban Method and Toyota Kata. You will see how Toyota Kata is used as the scientific method that guides your improvements efforts in Kanban.
First you will be introduced to Toyota Kata, from Mike Rother's book with the same name. You will learn the different parts of the Toyota Kata and why it will help you focus your learning and improvement work. You will see how Toyota Kata can be applied in software development and how it is used as the scientific method, that in a very focused way guides you in your improvement work in Kanban.
In the second part of this session you will join a fictitious company that uses Kanban Kata in a series of dialogs. These dialogs are based on real conversations and will demonstrate how the Kanban Kata is used in practice.
Do or do not. There is no try. —Yoda
Stop doing Retrospective and Start your Toyota KataHåkan Forss
You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but nothing seems to really improve. Stop doing retrospectives!
You should shift your focus form collecting problems and start improving! It is time to take your improvement work to a whole new level! It is time to create the habits of continuous improvement. It is time to start using Toyota Kata!
Toyota Kata is two behavior patterns, or Kata’s, that is the foundation in Toyota’s continuous improvement work. In this session you will get a practical introduction to Toyota Kata. You will see how a team goes through the two Kata’s and improves its way of working.
Do or do not. There is no try. —Yoda
May the Forss be with you - Lean Kanban Centeral Europe 2012Håkan Forss
It is a period of process efficiency war. Rebel flow-based change agents, striking with hidden knowledge, have won their first victory against the evil of Resource Efficiency and Big Planning Upfront.
During the battle, Rebel spies managed to uncover the ultimate weapons, the Kanban Method and Toyota Kata.
Pursued by sinister agents of Resource Efficiency, the change agents races home to their teams, custodians of the uncovered weapons that can save the organizations and restore customer delight in the galaxy.
Let’s hear what the Rebel change agent Håkan Forss has to share…
Toyota Kata - habits for continous learning. Shingo Institue European Confere...Håkan Forss
Aristotle said, “We are what we repeatedly do. Excellence, then, is not an act, but a habit.” Building on the power of habits, Toyota Kata helps build a daily continuous learning and improvement culture – a kaizen culture.
In this session, Håkan Forss will introduce two main kata* of Toyota Kata – improvement kata and coaching kata. You will learn how the improvement kata and coaching kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive toward your state of awesomeness in small experiments focused on learning. The improvement kata will form the habits of doing small daily experiments focused on learning and improving. The coaching kata will form the habits of leaders in an organization to help the learners learn and improve.
It’s time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A kata is something you practice over and over, while striving for perfection. If the kata itself is relatively static, the content of the kata, as we execute it, is modified based on the situation and context in real-time as it happens. A kata is different from a routine in that it contains a continuous self-renewal process.
Toyota Kata ett alternativ till retrospektiv DevSum 2012Håkan Forss
Har du upplevt att det lyfts fram massor med problem på era retrospektiv men det verkar aldrig hända något. Kanske är det dags att prova Toyota Kata? Med aktiv coaching skall teamet i små experiment förflytta sig från nuvarande tillstånd till uppsatt måltillstånd. Kanske kan Toyota Kata bli motorn i ert förbättringsarbete?
Improve productivity, focus on flow - Remove the RED bricks Håkan Forss
Do you want to improve end-to-end feature lead-time? It is not a question of working harder. It is a question of first removing the feature wait time, the red bricks.
If you would build an end-to-end timeline for your features using red, yellow and green LEGO bricks. Where:
• Red = Non value adding waiting time
• Yellow = Non value adding activates required due to how work is organized
• Green = Value adding activities of real customer value
How would your feature end-to-end timeline look like? In most cases, you will have less than 20% green and yellow bricks and more the 80% red bricks.
In this session, you will be learn how flow efficiency can be drastically improved in a concrete example.
You will see how a Swedish Breast Cancer Clinic drastically improved flow efficiency and reduced patient wait time by focusing on removing the red and yellow bricks.
We will take a close look at the three laws that define the performance of all processes:
• Little’s Law
• Law of bottlenecks
• Law of variation
By understanding how the three laws governs the performance of your processes, we can look at ways to improve your flow efficiency.
When time is gone, it is gone. Time to start removing the red and yellow bricks
Don’t we all think that we get more done if we stay busy? We feel good and efficient. We may even get a pat on the back or even a promotion.
But is this good for the company? Is it good for our customers? Are we really optimizing for the whole or are we just keeping ourselves busy?
Toyota kata – Agile saturday x 2014 02-15Håkan Forss
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” – Aristotle
What are the habits, routines, behavior patterns, needed to strive for excellence every day? How do we create a culture of continuous learning and improvement?
Building on the power of habits, Toyota Kata will help you build a culture of continuous learning and improvement, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your vision, your state of awesomeness, in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the leaders of the organization to help the learners learn and improve.
In this session, we will take Toyota Kata out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context tomorrow.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
Make strategy happen with Hoshin Kanri and Toyota Kata Agile AustraliaHåkan Forss
Lean and Agile software development can help your organisation deliver early and often, but this is not sufficient. Without clear and transparent alignment on a strategy, the organisation might still just end up keeping itself busy and not achieving the desired results.
Making your strategy happen involves two major, symbiotic components: strategy alignment and strategy execution.
Aligning on the right strategy can be a challenge in today’s complex world. Hoshin Kanri is an approach to meeting this challenge by drawing for the collective brain trust in your organisation.
Organisations also need to become laboratories: constantly running experiments, generating learning, and applying that learning to continually progress towards their strategy. In this session, you will learn how to create this symbiosis of strategy alignment and strategy execution using Hoshin Kanri and Toyota Kata as one system.
Retrospective on steroids - Toyota KataHåkan Forss
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle
You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but you don't seem to really improve. Let us put your retrospectives on steroids. Start using Toyota Kata!
Building on the power of habits, Toyota Kata will help you build a daily continuous learning and improvement culture, a kaizen culture.
In this session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. You will learn how the Improvement Kata and Coaching Kata can become your “muscle memory” for continuous learning and improvements in your organization. These daily habits or routines will help you to strive towards your state of awesomeness in small experiments focused on learning. The Improvement Kata will form the habits of doing small daily experiments focused on learning and improving. The Coaching Kata will form the habits of the agile leaders for creating a culture of continuous improvement, adaption, and innovation.
In this session, Toyota Kata will be taken out of the manufacturing context and put it into the knowledge work context. You will learn how you can start applying the Improvement Kata and Coaching Kata in a software development context as a compliment or a replacement of the agile retrospective.
Time to stop collecting problems and start forming new habits of learning and improving!
(*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” – Aristotle You have been doing agile for a few years now. With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but you don’t seem to really improve. Let us put your retrospectives on steroids. Start using Toyota Kata! Building on the power of habits, Toyota Kata will help you build a daily continuous learning and improvement culture, a kaizen culture. In this intense and interactive 90 min session, you will be introduced to the two main Kata* of the Toyota Kata, the Improvement Kata and Coaching Kata. We will experience the fundamental behavior patterns at the core of the Toyota Kata methodology: the rapid experimental cycles and the Coaching Dialog. You will gain direct insight into the power of the Improvement Kata and Coaching Kata through repeated personal practice. You will experience how these daily habits or routines will help you to strive towards a state of awesomeness in small experiments focused on learning. Small teams will work together striving to achieve ever higher levels of awesomeness using the Improvement Kata and Coaching Kata, thereby gaining practical hands-on familiarity with Toyota Kata. Learning outcomes: · Provide an introduction to the core routines, mindset, and behavioral practices of Improvement Kata and Coaching Kata. · Allow you to experience the core routines of the of the Improvement Kata and Coaching Kata through interactive, hands-on exercises Who should attend? The target audience are Lean/Agile Coaches, Scrum Masters, managers and anyone interested in continuous learning and improvement methods. Anyone can attend. Prerequisites No prior knowledge needed. If you want to prepare the following two books are highly recommended: Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results by Mike Rother and Lean Enterprise: How High Performance Organizations Innovate at Scale by Jez Humble, Joanne Molesky, Barry O’Reilly Time to stop collecting problems and start forming new habits of learning and improving! (*) Kata means pattern, routine, habits or way of doing things. Kata is about creating a fast “muscle memory” of how to take action instantaneously in a situation without having to go through a slower logical procedure. A Kata is something that you practice over and over striving for perfection. If the Kata itself is relative static, the content of the Kata, as we execute it is modified based on the situation and context in real-time as it happens. A Kata as different from a routine in that it contains a continuous self-renewal process.
The red brick cancer - Modern Management Methods UK 2013 11-01Håkan Forss
Time is valuable, and when it is gone, it is gone. Are you focusing on flow or just keeping yourself busy? How much has the red brick cancer spread in your processes?
In this session we will talk about time. We will explore the differences between systems with high resource efficiency and systems focused on flow efficiency. We take a look at how to remove the red brick cancer in your processes. You will learn how to understand and improve the end to end flow in your system.
Make strategy happen with hoshin kanri and toyota kata lean agile brighton 20...Håkan Forss
Lean and Agile software development can help your organization deliver early and often, but that is not sufficient. Without clear and transparent alignment on a strategy, the organization might still end up just keeping itself busy and not achieving the desired results.
Making your strategy happen have two major components that lives in symbiosis; strategy alignment and strategy execution.
Aligning on the right strategy can be a challenge in today’s complex world. Hoshin Kanri is an approach to meeting this challenge by drawing for the collective brain trust in your organization.
Organizations also need to become laboratories, in which they are constantly running experiments, generating learning, and applying that learning to continually progress towards their strategy.
In this session you will learn how to create this symbiosis of strategy alignment and strategy execution using Hoshin Kanri and Toyota Kata as one system.
Toyota kata – habits for continuous improvements by Hakan ForssInstitut Lean France
“We are what we repeatedly do. Excellence, then, is not an act, but a habit.” - Aristotle.
What are the habits, or routines, you need to put in place to continuously strive for excellence? How do we create a culture of continuous improvement? In this session you will learn about continuous improvement routines that help you close the gap between your current condition and you desired future state. You will learn how you can probe through the unknown in small deliberate steps. You will also be introduced to the leadership routines to build a continuous improvement culture. These routines are what we call Toyota Kata. Watch the video of the presentation here: http://youtu.be/MT3qgwzj5nY
More Lean IT videos and presentations on: www.lean-it-summit.com
Similar to Are you too busy to improve #lkse 2014-05-30 (11)
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
Oprah Winfrey: A Leader in Media, Philanthropy, and Empowerment | CIO Women M...CIOWomenMagazine
This person is none other than Oprah Winfrey, a highly influential figure whose impact extends beyond television. This article will delve into the remarkable life and lasting legacy of Oprah. Her story serves as a reminder of the importance of perseverance, compassion, and firm determination.
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
7. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
8. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
9. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
10. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
11. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
12. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
13. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
14. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
15. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
16. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
17. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
18. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
19. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
20. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
21. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
22. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
23. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
24. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
25. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
26. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
27. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
28. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
29. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
30. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
31. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
32. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
33. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
34. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
35. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
36. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
37. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
38. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
39. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
40. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
41. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
42. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
43. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
44. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
45. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
46. Non value adding: Wait time
Non value adding: Required waste
Value adding: Actual demand Support team responds
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
47. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
48. “A bad system will beat a
good person every time.”
W. Edwards Deming
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
68. Capacity = 6 Capacity = 4 Capacity = 6
Throughput = 4
You can’t go faster than your bottleneck
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
69. As long as capacity in front of the bottleneck is equal to or grater
than the bottleneck you will go as fast as your bottleneck
You can’t go faster than your bottleneck
Capacity => 4 Capacity = 4 Capacity > 4
Throughput = 4
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
70. Full use of a higher capacity in front of the bottleneck will make
lead time go up
You can’t go faster than your bottleneck
Capacity = 6 Capacity = 4 Capacity > 4
Throughput = 4
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
71. As long as capacity is equal to or greater after the bottleneck you
will go as fast as your bottleneck
Higher capacity after the bottleneck than at the bottleneck will
not improve throughput over time
You can’t go faster than your bottleneck
Capacity => 4 Capacity = 4 Capacity >= 4
Throughput = 4
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
72. The three ”laws”
Little’s Law
Law of bottlenecks
Law of variation
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
95. Expect at least 50% of the
experiments will not give the
expected result
This is when we REALLY learn!
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
97. Plan
• Define hypothesis
• Make Prediction
Do
• Run Experiment
• Closely observe
Check
• What did we
learn?
Act
• Update or new
hypothesis
I told you so!
Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com
98. Created by Håkan Forss @hakanforss http://hakanforss.wordpress.com