In our April 13, 2018, episode of QDL, we talked about anti-hacker robots, data privacy, and new product introduction.

“HoneyBot Lures in Digital Troublemakers”

MIT nerds come up with a tasty target for IoT hackers. But this one fights back.

Here’s a quick rundown of what we covered in part one of our list of top 10 mistakes to avoid when using statistical process control (SPC): training everyone, charting everything, segregating control charts from manufacturing, “pinching” the SPC coordinator, and using SPC because it’s a “good thing to do.” Let’s continue with our list.

As you think about your organization’s manufacturing quality efforts—what you’ve overcome and what you hope to accomplish in the future—there is something you need to know.

You: What? Who? Me?

Me: Yes, you. No matter how long you’ve been playing this game (and I know many of you have been playing it as long as I have), you find that there are many pitfalls to implementing a statistical process control (SPC) system.

On April 10, 2018, Facebook co-founder and CEO Mark Zuckerberg testified before Congress regarding the unauthorized sharing of 87 million Facebook users’ personal data, vacuumed up by data research company Cambridge Analytica. There were pointed questions regarding Facebook’s lack of transparency about the incident, a bit of dancing by Zuckerberg, and a lot of apologizing. All in all, it was a boring but fairly honest back and forth about the responsibilities and duties of large corporations when it comes to personal data.