logo

Quotes from Karen Martin

The results of taking on too much is that nothing gets done. Or it doesn't get done well.
~ Karen Martin
the most powerful metric we've seen for analyzing processes in office, service, and knowledge work environments: percent complete and accurate (%C&A)
~ Karen Martin
Failure to involve leadership, employ cross-functional teams, and include relevant metrics, for example, often results in subpar future state designs that collect dust.
~ Karen Martin
significant time and money is wasted when organizations attempt to make improvements without a clearly defined, externally focused improvement strategy that places the customer in the center.
~ Karen Martin
There's a big difference between needing to change a plan because new data or new conditions warrant it and deviating from a plan because an avoidable distraction has taken away the focus of an improvement team
~ Karen Martin
experiencing fewer problems and frustrations in their day-to-day work, the work force will become even more engaged in the improvement process
~ Karen Martin
we use the term countermeasure instead of solution, to aid in creating a continuous improvement culture, which begins with how people think and speak. The word solution smacks of an over-the-wall, permanent-fix mindset, which discounts the ever-changing world we work and live in.
~ Karen Martin
In practice, all ideas need to be viewed as merely hypotheses; testing and evaluation of the test results must precede across-the-board adoption.
~ Karen Martin
Improvements are temporary countermeasures, not permanent solutions.
~ Karen Martin
Beware leaders that want to negotiate for shorter time frames than the team feels is prudent. Most leaders have been away from the front lines for a long time and have grown out of touch with how long it takes to plan and execute well-thought-out improvements.
~ Karen Martin
In terms of overall transformation plan ownership, we recommend a sole accountable party.
~ Karen Martin
It bears repeating: in our experience, the plan review meetings are a key success factor in value stream transformation.
~ Karen Martin
We find a direct link between results and the degree to which the executive sponsor remains visibly engaged.
~ Karen Martin
Executing and sustaining change requires a different set of organizational behaviors than those required for planning.
~ Karen Martin
Whereas clarity and ingenuity are required for creating current and future state maps, focus and discipline are essential for successfully executing and sustaining improvement.
~ Karen Martin
You need to talk about it. Explain it. Let people ask questions.
~ Karen Martin
In the spirit of respect for people, and as a means to facilitate plan execution, workers who are part of the process or those who will be affected by the improvements must also be aware of the mapping activity and the plan for transformation.
~ Karen Martin
Following this scientific process assures that everyone involved in making improvements is thinking critically and breaking old habits of prematurely leaping to solutions or rushing through execution for the sake of meeting a deadline.
~ Karen Martin
When we ask leaders and improvement professionals what the most difficult aspect to making change is, they nearly always say, "Sustaining.
~ Karen Martin
We cannot empathize this enough: sustaining improvements begins with proper planning, followed by proper execution and management.
~ Karen Martin
In mature continuous improvement organizations, value stream managers are sometimes given responsibility for profit and loss across the value stream
~ Karen Martin
We're often asked how frequently a value stream should be improved. The answer is continuously. We understand that's a tall order for many organizations, but continuous improvement is your only way out of a culture of reactive firefighting, which prevents your organization from excelling on all levels.
~ Karen Martin
Learning to see and manage work from a value stream perspective is a powerful way to instill new ways of thinking into the DNA of your organization and achieve higher levels of performance.
~ Karen Martin
During the three-day mapping activity, the team had numerous discussions about the role of software testing, customer involvement and responsibility, striking the right balance of iterations, and how "minimal" a minimally viable product should be.
~ Karen Martin