Please enable JavaScript.
Coggle requires JavaScript to display documents.
whiteboard to sale (lean history lesson (Screenshot 2019-05-02 at 07.40.31…
whiteboard to sale
lean history lesson
Instead of talking about technologies and solutions, you should spend your time focusing on the people you’re trying to help, and the problems they have. It’s here that the great ideas will reveal themselves.
-
standardized infrastructure, minimized requirements, and a team of eight capable people
-
If code is not needed now, putting it into the system is a waste. Resist the temptati
Project tracking and control systems also do not add value, and further, they may be an indication of too much work in the system. In a just-in-time manufacturing system, work moves through the factory so quickly that sophisticated tracking is unnecessary
-
Frameworks should be extracted from a collection of successful implementations, not built on speculation
Extra features add complexity, not flexibility
tell people what needs to be accomplished and why, and leave the details to them
-
-
-
-
-
Lean thinking capitalizes on the intelligence of frontline workers, believing that they are the ones who should determine and continually improve the way they do their jobs.
transferring practices from one environment to another is often a mistake. Instead, one must understand the fundamental principles
-
-
-
The best approach for designing a new architecture is to put a few of your wisest people together and have them start working on it
reeses cup, fusion, chocolate
Lean Startup
A startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.
-
-
-
Zero in vites imagination, but small numbers invite questions about whether large numbers will ever materialize. Everyone knows (or thinks he or she knows) stories of products that achieved breakthrough success overnight. As long as nothing has been released and no data have been collected, it is still possible to imagine overnight success in the future. Small numbers pour cold water on that hope.
-
-
the point is not to find the average customer but to find early adopters: the customers who feel the need for the product most acutely. Those customers tend to be more forgiving of mistakes and are especially eager to give feedback.
feedback is both qualitative (such as what they like and don’t like) and quantitative (such as how many people use it and find it valuable)
-
We also need to get it in front of potential customers to gauge their reactions. We may even need to try selling them the prototype
Most modern business and engineering philosophies focus on producing high-quality experiences for customers as a primary principle; it is the foundation of Six Sigma, lean manufacturing, design thinking, extreme programming, and the software craftsmanship movement.
If we do not know who the customer is, we do not know what quality is
a “low-quality” MVP can act in service of building a great high-quality product. Yes, MVPs sometimes are perceived as low-quality by customers. If so, we should use this as an opportunity to learn what attributes customers care about. This is infinitely better than mere speculation or whiteboard strategizing, because it provides a solid empirical foundation on which to build future products.
We must be willing to set aside our traditional professional standards to start the process of validated learning as soon as possible. But once again, this does not mean operating in a sloppy or undisciplined way.
remove any feature, process, or effort that does not contribute directly to the learning you seek
-
what do i believe
what is the truth i want to say, forget the outcome!
-
-
-
-
-
Whenever people do work, they should be doing it for an immediate customer; that is, someone, somewhere, should be eager to make use of the results of their work
-
-
-
Creative selection
Without a demo it is very difficult to discuss and compare two ideas or receive feedback. Ken provides the example of asking two people to ‘think of a cute dog’. This is a pretty straightforward and simple concept to think of. However, without a concrete demo it is very difficult to compare two people’s ideas on what a cute dog is
-
“the ability for form opinions with your gut, that you can then justify with your head”.
-
-
-
-
-
-
-
Inspired
-
-
-
-
-
-
the collaboration that we want to create is built on relationships and people, which simply works best in a co-located, stable environment
teams
-
-
-
product, design, and engineering sit side by side”. Weak teams sit in their silos and prefer to communicate through documents and work orders instead of direct interaction
In weak teams, engineers are only involved when it comes to estimating effort.
-
-
The Goal
-
-
measures
-
-
-
"Throughput is money coming in. Inventory is the money currently inside the system. And operational expense is the money we have to pay out to make throughput happen."
let the slowest kid named Herbie lead the line. He also distributes some of the extra weight that Herbie was carrying. As expected, the fluctuations of the line balance out and the hikers reaches together on time, thus increasing the “throughput” of the entire troop
A bottleneck is any resource whose capacity is equal to or less than the demand placed upon it. A non-bottleneck is any resource whose capacity is greater than the demand placed on it.
-
the new priority system is in place. The rate of flow has increased considerably, thus reducing inventory
reducing the batch sizes down to half of their current level. Doing this could potentially reduce inventory levels by half. Also, they could achieve faster response times and shorter times for orders
-
structure
-
-
17 mins, key time for exercise
-
-
-
pilot programme
-
Smaller systems should be developed by a single team that has immediate access to the people who will judge the system's integrity. The team should use short iterations and show each iteration to a broad range of people who will know integrity when they see it, so they can make course corrections based on feedback.
-
frustrations
reflective, telling stories
best bits of books....stories i loved, superheros
-
integtrity
-
-
system's central concepts work together as a smooth, cohesive whole. The components match and work well together; the architecture achieves an effective balance between flexibility, maintainability, efficiency, and responsiveness
-
excercises
-
stand up engineers, have u talked to a customer
-
-
tech, cloud native, third party
-
-
-
-
-
-
-
-
-
-
-
-
