TRANSKRYPCJA 🔗
WEBVTT
00:00:00.179 --> 00:00:03.759
We can get stuck when trying to discover a solution to a problem.
00:00:04.070 --> 00:00:07.959
Sometimes it helps to expand our thinking into other avenues.
00:00:08.300 --> 00:00:11.640
We can reframe our problem within its contradictions.
00:00:12.109 --> 00:00:13.359
What is it not?
00:00:13.900 --> 00:00:18.120
We can expand our problem into how it fits into the bigger macro system.
00:00:18.620 --> 00:00:22.469
And we can think about how it fits into the smaller micro system.
00:00:22.850 --> 00:00:27.469
We can also expand our problem timewise into the past and future.
00:00:28.289 --> 00:00:30.070
Why all these alternate ways of thinking?
00:00:30.071 --> 00:00:35.030
To get us unstuck from a rut that we may find ourselves in.
00:00:35.560 --> 00:00:38.700
Let's talk more about this after this brief introduction,
00:00:40.509 --> 00:00:47.060
Hello, and welcome to Quality during Design, the place to use quality thinking to create products others love for less.
00:00:47.799 --> 00:00:48.579
My name is Dianna.
00:00:49.158 --> 00:00:55.259
I'm a senior-level quality professional and engineer with over 20 years of experience in manufacturing and design.
00:00:55.920 --> 00:01:00.170
Listen in and then join the conversation at qualityduringdesign.
00:01:00.170 --> 00:01:00.170
com.
00:01:01.320 --> 00:01:06.769
Solving new problems can be fun and invigorating and a little bit exciting.
00:01:07.209 --> 00:01:16.319
I mean, having problems is a large part of what we try to engineer out or try to resolve within whatever it is we're designing.
00:01:16.510 --> 00:01:24.799
When those problems seem to linger, and we can't seem to get a resolution to them, they can be unfun real fast.
00:01:25.519 --> 00:01:30.400
I was part of a team working on a project and we had a plating issue.
00:01:30.739 --> 00:01:35.430
The surface quality of the plating was deteriorating, and we weren't sure why.
00:01:36.049 --> 00:01:38.150
It was a really interesting case.
00:01:38.290 --> 00:01:39.430
An interesting problem.
00:01:39.569 --> 00:01:41.109
And the engineers dug right in.
00:01:41.810 --> 00:01:50.230
We even did a fishbone diagram to brainstorm and categorize all the places where we might be having problems where this problem might arise.
00:01:50.689 --> 00:01:52.980
And then we started investigating.
00:01:53.980 --> 00:01:59.859
The engineers did tests and followed up with suppliers, and did a lot of investigation.
00:02:00.159 --> 00:02:05.340
We would re-meet occasionally and discuss what was discovered and what next steps could be.
00:02:05.790 --> 00:02:12.650
Everything was going fine- until it didn't and we got stuck into a rut.
00:02:12.710 --> 00:02:18.250
We could not solve this problem or figure out what was wrong or what was causing it.
00:02:18.750 --> 00:02:22.770
So we decided to try a tool called an is/is-not matrix.
00:02:23.830 --> 00:02:32.080
Now I know we review a lot of different matrices and
Load full transcript
you may think that I'm a matrix queen, but it's really not true.
00:02:32.750 --> 00:02:33.719
I've said it before.
00:02:33.960 --> 00:02:48.030
A lot of these quality tools and methods and techniques help us to assemble the information we already know so we can identify any gaps or prioritize efforts so that we can move forward.
00:02:48.990 --> 00:02:56.189
And one of those tools, when you've got a problem that just doesn't go away and that you can't solve is an is/is-not matrix.
00:02:57.340 --> 00:03:03.400
It's a really simple matrix on the outset by just looking at it and how it's built.
00:03:04.110 --> 00:03:07.919
Its complexity is when you really try to fill it in, in earnest.
00:03:08.379 --> 00:03:11.280
And that's where the power of it really comes into play.
00:03:12.020 --> 00:03:20.389
An is/is-not matrix is set up like this: The problem statement is in the top left of the matrix.
00:03:21.599 --> 00:03:30.509
Underneath the problem statement in that first column are five questions: what, where, when, who, and how.
00:03:31.129 --> 00:03:38.180
Across the top in the three adjacent columns is: IS then IS NOT.
00:03:38.840 --> 00:03:40.500
And then finally OBSERVATIONS OR DISTINCTIONS.
00:03:43.360 --> 00:03:49.780
As far as the questions that we're asking with WHAT, we want to know what happens and what's affected.
00:03:50.870 --> 00:03:52.419
WHERE is its location?
00:03:52.750 --> 00:03:57.930
Where is the problem physically on a part, or where is it happening?
00:03:58.719 --> 00:04:01.849
WHEN is: how long has this been going on?
00:04:02.240 --> 00:04:03.250
When did it start?
00:04:03.669 --> 00:04:07.330
Was there an event that happened that started the chain of problems?
00:04:07.789 --> 00:04:10.770
And when did it happen in relation to other events?
00:04:11.360 --> 00:04:19.079
With WHO, we wanna think about who is it happening to by or near whom is it happening?
00:04:19.350 --> 00:04:28.278
This is something that we never want to assign blame, but sometimes it's important to understand who is involved when the problem is happening.
00:04:28.980 --> 00:04:33.350
And HOW is how many or how much, or how serious is it?
00:04:34.250 --> 00:04:49.430
Now since I typically use an is/is-not matrix to help us reframe a problem to better understand it if we're stuck, we're going to have data and information that we can fill in in the IS and IS NOT column.
00:04:49.009 --> 00:04:54.579
The IS is describing what happens, what occurs.
00:04:55.439 --> 00:05:00.300
And the IS NOT describes what doesn't occur, although it could.
00:05:00.870 --> 00:05:09.129
We're going to have blanks in our matrix, but we're going to fill it in as best as we can with as much information as possible That's relevant.
00:05:10.079 --> 00:05:12.569
That problem statement is in the top left of our matrix.
00:05:12.829 --> 00:05:17.569
So we're going to refer to it when we're filling in the IS and IS NOT columns.
00:05:18.040 --> 00:05:21.009
Finally, the last column is the OBSERVATIONS OR DISTINCTIONS.
00:05:22.879 --> 00:05:28.278
This is where we look at everything we filled in and we write down what is odd?
00:05:29.028 --> 00:05:30.519
What doesn't make sense?
00:05:31.470 --> 00:05:38.569
This is what happens- this is what doesn't happen, although it could- and what's special about that?
00:05:38.571 --> 00:05:48.199
For our plating problem, we noticed something's weird and missing, and it did give us some next steps to look into, to help solve the problem.
00:05:48.778 --> 00:05:56.879
And that's the whole purpose of this matrix: just to regroup, reframe, and get next steps out of it.
00:05:57.500 --> 00:06:00.278
How long does it take to fill out an is/is-not matrix?
00:06:01.338 --> 00:06:01.838
Not long.
00:06:02.740 --> 00:06:04.040
You can do it with your team.
00:06:04.300 --> 00:06:09.560
If you are a sole problem investigator, you can try to fill it in by yourself.
00:06:10.060 --> 00:06:18.069
But perspectives from other engineers and from your cross functional team might help you figure out what to do next.
00:06:19.199 --> 00:06:21.588
Again, it's a very simple matrix.
00:06:22.569 --> 00:06:44.980
The power of it is in us just stopping the manic problem solving, assessing where we are by filling in everything that we know about the problem(what it is and what it isn't), and then taking a moment with it all mapped out in front of us to evaluate what we know and what we don't know and what looks odd.
00:06:45.759 --> 00:06:49.180
My advice is just because it's simple doesn't mean it won't work.
00:06:50.240 --> 00:06:57.569
And if we're stuck on a problem and spinning our tires, this is a simple technique that may help us get unstuck.
00:06:58.560 --> 00:07:02.649
I'll include a graphic of an is/is-not matrix on the podcast blog.
00:07:03.949 --> 00:07:12.560
To conclude: an is/is-not matrix is just one tool that we can use to help us discover the solution to a problem.
00:07:13.180 --> 00:07:25.279
It helps us reframe our problem within its contradictions: what is it not, and what are some of the contradictions and observations we can make with what we already know?
00:07:25.899 --> 00:07:28.040
The point is to move on to the next step.
00:07:29.019 --> 00:07:46.589
At the top of the episode, I mentioned expanding our problem time wise and within the macro and micro system next week, I'll be talking about a different matrix that we could use to help us do this if we think it'll help us get unstuck with our problem.
00:07:47.610 --> 00:07:49.660
So, what's, today's insight to action?
00:07:50.360 --> 00:07:53.819
If you've got a problem and you're stuck, try a simple matrix.
00:07:54.350 --> 00:08:04.060
It'll put everything that you and your team know on one page in view, and you may be able to reframe what you know, so that you can move forward with next steps.
00:08:05.399 --> 00:08:13.970
If you like the content in this episode, visit QualityDuringDesign.com, where you can subscribe to the weekly newsletter to keep in touch.
00:08:14.720 --> 00:08:17.129
This has been a production of enterprises.
00:08:17.550 --> 00:08:18.490
Thanks for listening.