Wednesday, March 21, 2007
Morning Prayers
While our portfolio companies are working at maximizing returns, nCompass is looking at getting the most of the programs and processes we implement. Having different companies working in different industries it is often difficult to apply a process that all the portfolio companies can effectively implement. I started going through 8 storage boxes of files, notes and articles that I have been collecting for the last 10 odd years trying to find the ideal ‘process’ to inject into our portfolio companies and realize the greatest return. I was struggling when my 2 ½ year old daughter shed light on the whole exercise when she asked me, “daddy, what are you going to do today?” It hit me right then and there; morning prayers. As an Air Force Officer, every morning, first things first; morning prayers. All the officers would stand in a circle in the middle of the hangar surrounded by fighter jets and each would take a few minutes to say “this is what I’m doing, this is why, these are the issues”. Everyone knew what was going on, everyone knew what had to be done; no excuses, just action and accountability. That was the first process we implemented at all three portfolio companies and the impact has been substantial. The “I sent an email” culture still exists but ‘morning prayers’ are really starting to drive the day to day business. Everyone knows the key is communication, morning prayers ensure that communication flows and actions are taken.
Friday, March 9, 2007
Continuous Improvement Part Deux
Continuous Improvement Part Deux
The following are 11 steps that we utilize for our continuous improvement initiatives. Feel free to borrow/steal or add comments.
Step One
1. Find a common area.
2. Set up a white board to publish issues, results, steps, comments.
3. Use the board to communicate the issue to the company and drive the schedule.
Step Two
1. Define the problem.
2. The most important step.
3. Ensure you are highly focused.
4. Implement the KISS principle.
5. Indicate a means for measuring results.
Step Three
1. Take notes.
2. Map the process.
3. Identify bottle necks.
4. Identify duplications, issues, opportunities.
5. Quantify time and $.
6. Mark rework, wip, idle times.
7. Google: PERT and implement some ideas.
Step Four
1. What’s the Objective?
2. What are the expectations?
3. Timeline?
4. Metrics?
5. Get buy-in.
Step Five
1. Analyze Data
2. Google: Cause and Effect and implement some ideas.
3. Google: Root Cause
4. Use brainstorming and pareto charts to identify issues and concentrate on heavy hitters.
Step Six
1. Develop several solutions
2. Team effort here.
3. Look under every rock and listen to every opportunity.
4. We are not looking for the root cause but a solution, look at all possibilities.
Step Seven
1. Test the solutions.
2. Pilot tests.
3. Identify areas of measurement and analyzing the results.
4. Look at cost effectiveness, cycle time reduction, quality improvement and process/outcome measures.
Step Eight
1. Implement the best solution.
2. Compare and evaluate all solutions.
Look at:
i. Cost
ii. Value
iii. ROI
iv. Implementation time
v. Commitment
vi. Change required
vii. Google: Force Field Analysis
viii. Apply to top 2 solutions
ix. Select the best solution
x. Implementation plan
xi. Training
xii. Implementation
Step Nine
1. Track Progress
2. Monitor and fine tune, are you getting what you expected
3. Collect data, chart data
Step Ten
1. Take Notes
2. Continue documenting the process
3. Effort, time, people, money, resources
4. Savings: hard and soft
5. Efficiency
Step Eleven
1. Present the Results
2. Win the organization over
3. Illustrate the win and build support for future projects
4. Highlight the how and communicate the project, other project may result, the process might be ‘usable’ in other areas.
Any Questions?
The following are 11 steps that we utilize for our continuous improvement initiatives. Feel free to borrow/steal or add comments.
Step One
1. Find a common area.
2. Set up a white board to publish issues, results, steps, comments.
3. Use the board to communicate the issue to the company and drive the schedule.
Step Two
1. Define the problem.
2. The most important step.
3. Ensure you are highly focused.
4. Implement the KISS principle.
5. Indicate a means for measuring results.
Step Three
1. Take notes.
2. Map the process.
3. Identify bottle necks.
4. Identify duplications, issues, opportunities.
5. Quantify time and $.
6. Mark rework, wip, idle times.
7. Google: PERT and implement some ideas.
Step Four
1. What’s the Objective?
2. What are the expectations?
3. Timeline?
4. Metrics?
5. Get buy-in.
Step Five
1. Analyze Data
2. Google: Cause and Effect and implement some ideas.
3. Google: Root Cause
4. Use brainstorming and pareto charts to identify issues and concentrate on heavy hitters.
Step Six
1. Develop several solutions
2. Team effort here.
3. Look under every rock and listen to every opportunity.
4. We are not looking for the root cause but a solution, look at all possibilities.
Step Seven
1. Test the solutions.
2. Pilot tests.
3. Identify areas of measurement and analyzing the results.
4. Look at cost effectiveness, cycle time reduction, quality improvement and process/outcome measures.
Step Eight
1. Implement the best solution.
2. Compare and evaluate all solutions.
Look at:
i. Cost
ii. Value
iii. ROI
iv. Implementation time
v. Commitment
vi. Change required
vii. Google: Force Field Analysis
viii. Apply to top 2 solutions
ix. Select the best solution
x. Implementation plan
xi. Training
xii. Implementation
Step Nine
1. Track Progress
2. Monitor and fine tune, are you getting what you expected
3. Collect data, chart data
Step Ten
1. Take Notes
2. Continue documenting the process
3. Effort, time, people, money, resources
4. Savings: hard and soft
5. Efficiency
Step Eleven
1. Present the Results
2. Win the organization over
3. Illustrate the win and build support for future projects
4. Highlight the how and communicate the project, other project may result, the process might be ‘usable’ in other areas.
Any Questions?
Monday, March 5, 2007
Continuous Improvement
Today I met with one of our portfolio companies and we discussed continuous improvement (CI). I dug out an interesting article from my archives and thought I would make that the blog topic for today.
The following says it all:
Improvement requires Change
Change needs Action
Action requires Knowledge
Knowledge leads to Experience
Experience results in Wisdom
Wisdom is increased by taking more Action
If your organization is taking on a continuous improvement program it has to definitely feel comfortable with Change, Taking Action and Sharing Knowledge and Best Practices.
From what nCompass has noted and many are sure to agree; many organizations decide to take on a program without regard to the ‘other’ programs that play a support role. Every program is the result of a mindset, philosophy, train of thought. Implementing any program is not as simple as saying ‘we’re doing xyz’; to be effective it has to be in line with the organization’s strategy, philosophy, driving force.
The following says it all:
Improvement requires Change
Change needs Action
Action requires Knowledge
Knowledge leads to Experience
Experience results in Wisdom
Wisdom is increased by taking more Action
If your organization is taking on a continuous improvement program it has to definitely feel comfortable with Change, Taking Action and Sharing Knowledge and Best Practices.
From what nCompass has noted and many are sure to agree; many organizations decide to take on a program without regard to the ‘other’ programs that play a support role. Every program is the result of a mindset, philosophy, train of thought. Implementing any program is not as simple as saying ‘we’re doing xyz’; to be effective it has to be in line with the organization’s strategy, philosophy, driving force.
Subscribe to:
Posts (Atom)