I thought it was important to share my typical QA-based consulting process. Please note this outline is general, as it depends on the needs of the specific customer. This does not cover the product development/project management processes.
So here it goes! :
When a potential customer first approaches me for help, the first thing I need is background information.
Typically, the best way to get an idea of the needs of the customer is to visit the facility and get an idea of the current processes in place (if any). Depending on location and the timeline, this may also be done over the phone, however I prefer to visit the client as much as possible.
Many of my clients are small to medium, fast-growing manufacturers that either have no QA-department, or a single QA-employee. Either the client needs to improve or create a quality program and/or are preparing for a customer or certification audit with specific requirements.
Once I have a clear understanding of what the client’s objectives are, and a rough timeline, then I can draw up a detailed proposal. This proposal outlines all work packages, associated documentation, milestones, and timelines.
I like to make sure the client is comfortable with the proposal, and that a clear plan has been developed and agreed upon.
Then the work begins!!! Either I work with an employee at the company, or independently, on designing and implementing quality programs that are realistic, meeting requirements, functional, and maintainable. I also guide the company on how to use these programs.
I truly believe in maintenance! This comes in form of regular monitoring and verification/validation programs, which I can further set-up. Too often companies just ‘get audit ready’, and then after a month some bad habits creep up. Which is why I like to offer a regular ‘maintenance’ program after the audit has been achieved.
I hope this helps clarify what my QA-Consulting process looks like.
Please e-mail me at: email@example.com for more information.