GRIP is the process that is followed in the development of projects from conception to development to option selection to delivery to completion and has to be followed. Six Sigma always seemed a project management qualification fad that doesnt actually get mentioned much at all these days, it all seems to be LEAN, deep dives and bowtie processes now which mean even less!
Thanks for insight - Although i have never heard of these two systems:-
"We have a new initiative that is better than the current one. The old was just a fad and didn't really work"
I found a snippet about both, here goes:-
BOWTIE
The BowTie Risk Management approach is the process of looking at the case where Multiple Threats can cause a specific Undesirable Event (note the Many to one relationship between Threats and Undesirable Events). For example Contamination of food by Bacteria, Viruses and Chemical contaminants can all cause one Undesirable Event such as Food Poisoning. This would represent the LEFT side of the BowTie.
The center of the BowTie is the Undesirable event itself and between this and the Threats is where we place the Control Measures in order to Prevent the Undesirable Event. In my example we may have Temperature Controls, Cross Contamination Controls and Supplier Assurance Controls to act as Control Measures against the Threats.
On the right of the BowTie diagram are one or more Consequences. For example Consumer Illness or Death, Damage to the Manufacturers reputation and fines or imprisonment. This shows that that an Undesirable Event may result in one or more Consequences. This one to many relationship between the Undesirable Event and the Consequences gives the shape of the right hand side of the BowTie diagram.
Between the Undesirable Event and the Consequences are the Recovery Measues. These are the methods of minimising the impact of the undesirable event and in my example may include Product Recall, Hostpial Treatment and Mandatory notification to the relevant Authorities for assistance.
Thus the BowTie approach takes account of both Threats and Consequences as well as the Control Measures taken to prevent the Undesirable event as well as ways to minimise the Consequences in the form of Recovery Measures.
Deep Dive ™ (i found it hard to get a good definition - this company seems to do a good job)
Deep Dive is a focused team approach to developing solutions to specific problems or challenges. It is intended to harness the idea-power of everyone on a team in a focused, creative, energetic, fun, and ultimately useful way. A Deep Dive ™ is a combination of brainstorming and rapid prototyping melded together into an approach which any change catalyst can use to identify actions to move an issue forward. I was one of the creators of the Deep Dive ™ methodology for management, together with Andy Boynton, Bill Fischer, Marianne Vandenbosch, Ken MacLean and Peter Zahnd. We initially discovered the methodology when we began working with IDEO, in Silicon Valley.
Together with various colleagues we’ve used the Deep Dive ™ methodology on issues as diverse as improving passenger experience at Heathrow, understanding how to better use technology in the service of governments (a workshop done in parallel to the Nobel Prize ceremony in Stockholm), developing new packaging for a confectionary product in the UK, redesigning the product strategy for a business school and developing a vision and mission for one of the world’s largest chemical companies.
sure there's a few on here can answer it for you. Errrr ....... I mean shed some light on the subject for you.
