It’s the first step of the problem solving framework that I was taught back in Engineering school.

Not ‘Plan’. Not “Define”. “I want to and I can”.

That particular framework - the McMaster Six Step - never gained the popularity of the ones now used today, but in the end they all contain the same basic elements - research, planning & design, implementation, evaluation and iteration - just stated in different ways.

However I’ve never really seen this particular element called out explicitly since then. I guess it’s supposed to be lumped in with the definition or planning phases, but not really - this is more a gut check than a formal listing of facts.

“I want to and I can”. It’s not the greatest title - it sounds a bit flippant - I know, I know, anyone asked to solve a problem in a boring job is probably thinking “No, I don’t want to and I won’t” or “The boss told me to, so I have to and I must”. It’s also surprisingly touchy-feely for an engineer’s framework. But that’s what I like about it.

“I want to and I can” is a set of leading questions that help you to do an initial assessment of your alignment to the problem, at least as it was initially presented to you. I call it a gut check, an application of your previous experience and knowledge in evaluating what this might entail for you, whether it is a priority, if there are any ‘scary’ unknowns.

A psychological preparation before you start to gather resources and really get into defining the problem.

Let’s start with the first bit - “I want to”:

• Is this problem worth solving?
• Do I know from experience what the costs might be versus the potential benefits? The time and resources it will take?
• Does the problem really need to be solved right now? What would happen if you left it for a while? What would happen if you didn’t solve it at all?
• Are there other priorities that should be addressed first?

And the “I can” part.

• What’s my skill and experience with this type of problem? Have I dealt with something similar before, or am I wading into unknown territory?
• What are the things I know how to do to address this problem? Is there an obvious first step that should be taken?
• What are the things I don't know at all? Do I feel confident that I'll be able to discover them? Do I have a reason to fear some unknown unknowns?
• Do I need help? Should I be bringing in other resources? Do I have access to those resources? Is there another person or department altogether that should be dealing with this problem?

You might be saying “These are all questions that you answer during the problem definition phase”. The point here is that you’re pre-answering them as part of building psychological readiness and putting your biases and fears out front.

Let’s say there’s a plumbing problem in my house. If it’s a big leak that’s spraying all over the place and will cause an imminent flood, then I really want to fix it as soon as possible.

I’m not going to sit down and do a bunch of measurements or research or write out three formal proposals for addressing the problem!

I also don’t want to go into a panic and start doing a bunch of half-measures at the same time like I’m in a bad 60s comedy sketch - blocking the spray with one hand while pushing towels with my foot while trying to reach the phone to call the plumber.

I'm going to stop, take a breath and realize from experience that there is a first step I can take to minimize damage right away. Turn off the water either at the mains or at an isolation valve. Then I can plan how to approach the mess and figure out which plumber to call.

But if it's just a dripping faucet and I've got a big report due tomorrow, suddenly "I want to and I can" looks quite different. I do want it fixed - a dripping faucet is both annoying and wasteful, but I can probably just catch and use the dripping water until the weekend. I also know from experience that unless I find something really weird going on I probably don't need to spend a hundred bucks on a visit from the plumber - I can do it myself with a trip to the hardware store and maybe a YouTube video or two.

When you take some time to do a proper 'gut check' before rushing headlong into finding a solution, it can greatly increase the chances of success - creating the proper headspace, prioritizing what to work on and eliminating false starts.

So next time you're faced with a problem - at least one that's not an emergency about to wash away your bathroom - sit down and spend a couple of minutes asking yourself these "I want to and I can" questions.

For larger, more formal problems and projects, make this an explicit step in your framework. Perhaps that's a journaling session, a form, or a maybe it's a team meeting. Whatever works for the situation.

By preparing yourself before you wade into the details, you'll have a better chance of solving the right problem, with the right resources, at the right time.

Until next time, thanks for reading.

– Brendan

p.s. Enjoy this message? Read more at the Hyland Quality Systems website.