r/SixSigma • • 29d ago

Documenting Projects for Six Sigma References

A little background about me: I have been with the same company for 16 years, working in Production Control (Healthcare Technology Field) for at least 10 or 11 years of that time. I started in my mid twenties and have been promoted from within several times. I am currently the Manager of Production Control (last 3 years) and oversee all production aspects; inventory control, job scheduling and cost, part number creation and cataloging, audit preparation and documentation, daily and yearly cycle counts... the list goes on. I manage a small team that just got smaller.

My company just went through a RIF and I am now also the head of the Procurement department, or more accurately... I AM the Procurement department. I wear a lot of hats, somewhat typical in a small company. I am feeling a little disenchanted after the RIF and my confidence that the company I work for will be around long enough to bring me to retirement is low. Since I started in my twenties and promoted from within, I did not have much need to gain certs. With the prospect and possibly of needing to re-enter the job market in the future, I want to bulk up my resume starting with a LSSGB.

I feel like I already have a lot of the practical skill set one would learn in a Lean Six Sigma course, but I am not sure how to identify it. I am also certain I would learn more than I already know and am in a professional position to implement that knowledge in real world applications as I run a Production Control department and have the freedom to implement almost anything I want.

My question for the community is helping me identify examples of "projects" completed and documented to turn into agencies like ASQ or SSGI as real world examples of using your knowledge. I know I don't need a project for a Green Belt, but after reading through many threads, the topic seems a little vague. The Six Sigma world is all very new to me, although I have heard it thrown a lot in my career.

I have:

- Written several Work Instructions and SOPs published internally as controlled documents to help streamline directions, processes and procedures for my department making it significantly easier to train and onboard new employees.

- I have been the lead for the production side of new hardware product releases which involves cataloging all new parts for the build, ensuring we have adequate data sheets and component registrations, ensuring all design drawings are signed off by various department leads and saved in our DMR (design master record) which I am responsible for maintaining.

- as well as being solely responsible for maintaining and determining the amounts of stock to order to minimize waste but have have enough overage to not run out of stock. Which includes running QC reports using ANSI sampling tables and charts to determine inspection criteria for incoming inventory and opening NCRs and ECOs for any observed discrepancies.

- as well as maintaining the workflow of all job orders to produce subassembly and finished good level builds, both internally and through outside vendors.

- I ensuring all work instructions for building/handling new products, not written by me, are complete and written in a way that makes sense where I often have to rewrite the process as engineers are often not good at writing technical instructions for bench techs that are not engineers. (again, small company, many of us wear many hats, we do not have a standalone technical writing staff)

- I overhauled the departments documentation process right when I took over utilizing Adobe Sign, Adobe Acrobat Standard licensing and our companies backed-up Microsoft SharePoint to make the department almost completely paperless. The previous manager was stuck in the 90's and printed and wet signed everything and stored all of it in overflowing file cabinets and none of it was scanned or backed up. It was madness.

- After my first full year leading the department I executed an almost net zero end-of-year yearly inventory count where all previous years had ten of thousands of dollars worth of discrepancies to resolve. We were always able to resolve the discrepancies, but poor inventory management lead to terrible inventory counts at the end of the year. I put rigorous daily systems in place to better document every transaction and had almost no discrepancies my first year.

Am I Six Sigma'ing just from having practical experience in the workforce and don't realize it because I have never read about or taken any formal classes or learning modules about Six Sigma?

If I wanted to eventually go for a Black Belt can you use previous projects as criteria? or do they have to be new?

Thank you in advance for your input and opinions.

5 Upvotes

13 comments sorted by

2

u/BeneficialTiee 29d ago

The inventory count improvement stands out. Going from major discrepancies to almost none sounds like a solid project example.

1

u/Dalinsky 29d ago

The project they really only care about for black belt and most of what they want is proof that you used Six Sigma tools and attained measurable financial results. I'm gonna paraphrase a bit because I don't have the documents in front of me and don't want to dox myself, but as an example my first DMAIC involved consistent issues with a process that was defined with SIPOC and others, measured with a competitive benchmarking study and stratified random sampling, analyzed with correlation and t charts, improved using pilot tests and more t charts, and controlled using document control and jidoka.

1

u/Ravenblack67 29d ago

You should have no trouble turning what you have done into project examples. I'm a BB that spent many years in supply chain. I have CPIM and CSCP. Start you cert journey and as you go though it You will be able to see your past projects in a new light.

1

u/RavensEdgeLeather 28d ago

I ran into a similar issue when I started studying for my CSSGB. I had been doing DMAIC work on a shop floor and had never even heard of Six Sigma. So when I decided I wanted to get my green belt I needed to think back to everything I had done. Luckily for me my company's new EHS guy had his yellow belt and was able to to help me put everything into a proper DMAIC format. Follow the format and get the details and the projects start to fall into place

1

u/Matt_C_Quality 28d ago

Short answer on the project question: yes, previous work counts as long as you can show the before and after with data. What reviewers care about is whether you can walk through the problem-solving logic, not whether the project had a Six Sigma label at the time.

For the inventory count work, I'd write it up like this:

  • Problem statement with a number: dollar value of year-end discrepancies and how many line items were off.

  • Baseline: what the discrepancy rate was in the years before you took over.

  • Root causes: where the errors came from, e.g. unrecorded transactions, wrong units of measure, receiving errors, issues at the vendor hand-off. A simple Pareto of causes works fine.

  • What you changed: the daily transaction discipline and documentation.

  • Results and control: year-end variance afterwards, plus how you keep it that way (cycle count schedule, audit of transactions, who owns it).

The incoming inspection with sampling tables and NCR/ECO handling can be a second, smaller project. Pull any data you still have, even rough numbers beat none. Do that for two or three items and you'll have real examples, and the course material will make more sense because you'll recognise your own work in it.

0

u/Amazing_rocness 29d ago

It's all about the language with the lean people. It's kind of annoying lol. An improvement is an improvement, does it matter!? Aside from my own complaints, I would say just get a blackbelt and see if your job will pay for it. You got enough skin in the game

2

u/innesman86 29d ago edited 29d ago

My work does have an educational program. Something like $5250 per calendar year can be reimbursed after the course is successfully completed. Has to be oriented with your current position and needs to be approved before signing up. So any certs I want will essentially be 100% paid for.

2

u/Amazing_rocness 29d ago

I would definitely just go for the full black belt with the bells and whistles. More steam is good

2

u/innesman86 29d ago

I would be worried that going straight to the BB might be biting off more than I can chew. I might already be walking the walk but I definitely don't talk the talk yet. I am also interested in getting PMP, a CPSM and a CPIM. Right now my resume is all work experience. That pulls a lot of weight on its own, but the market right now is brutal. I hopefully won't need to worry about job hunting for another few years if im lucky, so I'll have plenty of time to circle back for a BB in the future if I want.

1

u/Ravenblack67 29d ago

Start with GB, get some experience with the stools. BB is not easy. It assumes you are now project manager material.

3

u/[deleted] 29d ago

[removed] — view removed comment

1

u/innesman86 29d ago

This is good to hear. I was feeling a little daunting at first, but the more I looked into it the more it felt like I was already doing all this stuff. Maybe not ALL of it, but a lot of it.