“Though we all know that technology is continuously improving. But we shouldn’t put all our trust in it just yet. Yes, Google’s AI has nearly twice the IQ of Siri, but a 6-year-old child is still smarter than both. And even if it does improve further, 75% if customers, like you, still say that they would want to interact with a real person more as technology improves. child.”
I’d still like to talk about this a bit more, especially on why AI is still considered “Primitive.”
For #wisdomwendesdays I’ve been asked by someone trying to learn Data Science what the difference is between Variance and Standard Deviation in terms of purpose.
Here are 10 Process Improvement Mistakes you Don’t Want to Make.
I was actually going to create a list myself, but my friends Karlo and Tracy at GoLeanSixSigma.com have already put this together, and I agree 100% to all of what they said!
So I thought I would just share it with you!
My personal favorites are:
1. The Glory Hoarder
An example of is when Project Leads take all the recognition, and the team members are not given any credit whatsoever.
Sometimes, Project Leads tend to do this unknowingly too. Like when it’s time to present and demonstrate the project results, the Leads feel they should always be the one to take stage, while somehow leaving the rest of the team out of the spotlight.
How about letting the team members who actually developed the solutions take center stage?
2. The Pet Solution
This is where people already have a preferred solution to the problem.
In my experience, what happens here is that people tend to reverse-engineer their Pet Solution into the DMAIC approach just for them to be able to complete a Lean Six Sigma project.
That’s just wrong!
3. Passing the Buck
This happens when you try to eliminate steps within the process you’re looking to improve, only for another department upstream or downstream to end up taking on that piece of work.
Continue on to see the rest of the mistakes you don’t want to make, along with some great examples.
For today’s #wisdomwednesdays I’ll talk about the difference between Robotic Process Automation (RPA) and Artificial Intelligence (AI).
In a sense, they can both be categorized as forms of software automation. But the major difference is their purpose.
The short explanation is that RPA is used to automate repetitive rules-based tasks, such as repetitive clicks and keystrokes, copying and pasting, if-then types of processes.
On the other hand, AI is used to automate tasks that require judgment, such as reading unstructured documents, identifying patterns, making decisions based on what you see in photos, or getting context based on what you hear in conversations.
Read on to find out the long explanation as well as some examples. This will also touch on Machine Learning.
For #wisdomwendesdays I’m sharing some quick tips that will be helpful, especially for process improvement professionals growing a team or have frequent organizational changes.
You know when you’ve been working with a client for at least year or two, and then there are so many changes in their organization happening, perhaps due to growth, movement, or restructuring?
Often times you’ll be assigned to work with new faces. And usually they are either younger in age, or have less tenure than the previous people you were working with.
While your clients may say that it’s for the better, or that it’s good to have a fresh set of eyes, even though I agree to that, it does present itself with a challenge.
The challenge with having new people in the organization is that the
History usually repeats itself. So find pain points based on history.
Read on as I share 3 quick tips to allow you to work with new team members and alleviate this challenge.
For today’s #wisdomwednesdays, you gotta choose which statement makes more sense to you:
“Build it and they will come” or
“People adapt to what they helped build”
Think of a scenario in your your past when you tried to deploy initiatives that you think would benefit a lot of people.
Which strategy worked best?
The one where you built it, and then tried to push it to market? How did that go? Did they love it immediately soon as they saw it? Did they thank you for creating such a wonderful product or service?
Or did the strategy where you involved your audience in creating it work better for you?
If you’d want to find out what worked in my experience, then read on.