Introducing impi! - Pierre Bienvenüe
I'm happy to introduce Pierre Bienvenüe, founder of impi Business Improvement Solutions Pty, a South African business improvement firm and TeamPage solution partner since 2012.
Pierre Bienvenüe writes: Since 2012, the trigger to develop impi! was primarily the realisation that mid-size companies couldn’t afford quality improvement programmes à la TRACC, 20-Keys, Mission Directed Workteam or BMGI offering.
Additionally, for a few years now we have experienced the convergence of Quality Assurance and Continuous Improvement.
Why choosing mid-size companies? Their systems are usually less mature than that of large corporations and therefore, the implementation of an IT system underpinning the BMS wouldn’t usually clash with legacy systems.
A few concepts to build a business management system
impi! is applying the Lean tools and techniques other programmes offer (and probably not as well due to my limited experience and resources to develop the content).
The question here is how to ensure that improvement results in standardisation and standardisation in sustainability.
Another tension exists between the daily operation (immediate) and its systemic improvement (essential).
My response to the two challenges is:
- A dynamic business model, the Core Cycle, summarised by Drucker definition of management: “the essence of management is to make knowledge productive”.
This model helps me to have an integrated view on how a business operates and therefore develop interlocking solutions to build its BMS. I attach a presentation of the Core Cycle, a subset of the foundation course I train my clients with;
- A technology (social media for companies: TeamPage) as an enabler of the Core Cycle that provides an integrated work environment, flexibility, ease of use and at the same time provides structure and visibility.
With the technology we can have knowledge workers and even supervisors to collaborate, share, task, project manage, create and manage documents, etc.
I experimented and now understand that the technology - social media for companies (Enterprise 2.
- Adler - Building Better Bureaucracies
- Bob Emiliani - The Toyota Half-Way
- This presentation is designed for PowerPoint 2010.
the core cycle model is animated, so don’t move forward too quickly: Core Cycle slides
I found that a two-weekly cycle of project review sets up a pace for the company and puts the right pressure on both top management and project leaders.
Everyone with a computer runs an improvement project (initially) related to their processes.
Then implementation of any system is pushed through that improvement process.
We create spaces for the systemic, strategic and selected operational mini-business units.
Sharing of knowledge is woven into the BMS.
- All impi! solutions are built on TeamPage on a wiki space and are standard documents.
Every solution starts with a Policy (the why) and a Standard Operating Procedure (the how). The SOP is the hub that links all the other documents (the spokes). The templates used for these documents are the same that the client can use for their own controlled documentation in their own wiki space called “Knowledge Central”. Two outputs of every improvement projects are a) an operational improvement and b) documentation in Knowledge Central. The project templates used to run improvement projects comprise standard articles that will naturally become elements of the BOP (e. g. SIPOC, business process maps). When the project leader reaches the Control or Adjust part of the project, large chunks of the documentation would have been written. Using the capability of TeamPage simplifies the linking and tagging of documents. The organisation steadily builds its very own Wikipedia, and it’s ISO 9001 compliant. The risk of deadwood documentation is reduced: team members create their own documentation, hyperlinking contextualises the documentation and tagging and search capability ease retrieval of information.
- Several templates are available for improvement projects (e.
g. PDCA, DMAIC). With each project milestones are associated standard articles e. g. project charter, project checklist, Fishbone diagram, business process “AS IS". To each milestone there are also associated tasks. In each task is a tutorial on its own with tips and links to glossary terms, One Point Lessons (e. g. How to use a risk assessment matrix) or external reference in the public domain, e. g. Wikipedia, Lean Institute.
Finally, here is a one page summary of impi! and the synopsis of one of the three solutions that Traction and I have released thus far and are currently being used at clients.
Voilà - I hope there is enough meat here to stimulate a conversation or two.
Since I have only developed impi! thus far with my clients and for my clients, I haven't started a public website.
Jun 2016 | ISO 9001:2015 Requirements Met By impi! Solutions - Meeting ISO 9001:2015 requirements using the impi! model
impi! What's in the name? What's in the logo? - Discipline and creativity
Why, How and What of the impi Standard Meeting Plug-in for TeamPage - A customer interview and walkthrough of one new part of the impi! BMS solution