Ackoff on Systems Thinking
/Dr. Russell Ackoff'sshort lecture on Systems Thinking is one of the best simple descriptions of the concept.
Read MoreDr. Russell Ackoff'sshort lecture on Systems Thinking is one of the best simple descriptions of the concept.
Read MorePowers of Ten takes us on an adventure in magnitudes. Starting at a picnic by the lakeside in Chicago, this famous film transports us to the outer edges of the universe. Every ten seconds we view the starting point from ten times farther out until our own galaxy is visible only a s a speck of light among many others.
Read MoreHigh performance teams reach Maturity Level 3 (ML3) in 3-4 months.
Read MoreDetermining the process maturity level for you team using the FTTM System is critical in order to drive continuous improvement towards continuous schedule acceleration.
Read MoreA summary of scheduling best practices.
Read MoreWhat’s the difference between training and coaching? We try to explain using an analogy.
Read MoreSimon Sinek’s “Start with Why” concept works well to describe the three elements of a decisionAccelerator model.
Read MoreThe ongoing challenge when managing real innovation projects at the bleeding edge of technology is,“To improve the project planning and tracking system in order to better predict schedule performance.”
Read MoreOur matrix organizes root causes of poor time-to-market performance. It is a result of our ongoing research and is a composite of our work in many different client environments.
Read MoreSuccessful teams use the "do-it, try-it, fix-it" cycle. Slow teams typically spend long periods of time trying to "get it right" for fear of failing. Some corporate cultures tend to punish for failure rather than reward for success. They don't make the trade-off between long duration and that last 10% to make something "perfect." They default to getting it right over getting it done (soon). This model means that you had better be right at the end of the cycle. If you have to rework then this will take even more time.
Read MoreBreaking-set is a key technique fast teams use to reset and accelerate.
Read MoreDriven by corporations trying to do more with less, BPM is back. If you can’t grow, the only way to maintain and improve margins are to reduce costs. Like Hammer and Champy, we are doing it from a customer’s perspective. We believe that if you focus on the customer when improving process efficiency, you will by default save time and money. These are the byproducts of a customer efficient process. Lets look at our process, at a high level.
Read MoreA macro plan is a high-level description of a project. About 50 activities or less that define the overall work that needs to be done to achieve an objective.
Read MoreThe "Fuzzy-Front-End" is the time at the beginning of the development cycle. It is the point in time when an idea is conceived to when a project is approved and a full team is formed. Don Reinertsen said that "fuzziness consumes time."
Read MoreSchedules get a bad rap. Here’s an alternative view point…
Read MoreUnderstanding how organizations provision development teams (i.e. provide necessary people, funding, information, facilities, resources, knowledge, skills, etc.) has been a foundational practice in our research work.
Read MoreThe “Host” is everything in an organization that is outside and around a team. The host can provision a team or it can interrupt it. Fast organizations design the host to "provide for" when resources, information, or "things" are needed by the team to be effective.
Read MoreOften product functions or features are confused with customer needs. In our world a customer need (also called "customer requirement") is an attribute that expresses some part of problem a customer is trying to solve. A product feature is specifically how the customer's need will be fulfilled. A product feature is also called a "how."
Read MoreDuring a recession, it can be difficult to manage your business effectively when things are in a spiral. This post describes how to select which projects to keep given your constraints.
Read MoreIncrease your new product success rate by finding the root causes of poor performance and translating these into selection criteria to pick better products (to develop). This process also uncovers issues that are causing the wrong products to be defined in the first place. Better failure analysis, i.e. why do some new products miss their targets?, can be translated into better new product selection criteria so that more good ideas get into the development pipeline than bad ones.
Read More