The 10 steps of problem solving like a pro. The beauty in professional problem solving.

Yes. 

I'm talking about being an Engineer.

There are 2 main trains of thought with Engineering work for non-engineers and that's trying to change the world with leading edge tech and innovations, or plain old boring math nerd type things.

Whilst, somewhat the case what this means is most content I read around Tech and Engineering are either super technical and (excruciatingly) detailed. OR really riff raff at the high level revelling at the possibilities of changing the world as we know it.

And so what we end up with is a base (engineer only details) and the topping (media innovation coverage) but what about the meat? The contents?

There's a lot of beauty and interesting things there too. And what's the centrepiece? The common ground between all engineers? Problem solving.

The number one thing an Engineer does is problem solving. Now you may say, "hey, that's the same as my profession" - well this would be true for virtually every single profession on earth. This is not saying there isn't problem solving required in other professions.

Some problems require very basic problem solving techniques such is used in every day life, but sometimes problems get more complicated, maybe they involve other parties, maybe its a specific quirk of the system in a specific scenario.

One thing you learn in engineering is that not all problems are equal. These are

 The stages of problem solving like a pro:

1. Is the problem identified (no, really, are you actually asking the right question?)
   
2. Have you applied related troubleshooting step to above problem?
   
3. Have you applied basic troubleshooting steps (i.e. check if its plugged in, turned it on and off again, checked your basics)
   
4. Tried step 2 again? (Desperation seeps in, but check your bases)
   
5. Asked a colleague or someone else that may have dealt with your problem? (50/50 at this point)
   
6. Asked DR. Google (This is still ok)
   
7. Deployed RTFM protocol (Read the F***ing Manual - Engineers are notorious for not doing this)
   
8. Repeated tests, changing slight things, checking relation to time, or number of people, or location or environment (we are getting DEEP now)
   
9. Pray
   
10. Go to the bottom level, in networking this is packet sniffers to inspect packets, in systems this is taking systems apart and testing in isolation, in software this is checking if 1 equals 1, you are trying to prove basic human facts that everyone knows. If 1 is not equal to 1, you're in deep trouble.

At this point you are at rebuild from scratch, re install, start again as your answer (extremely expensive, very rare)

And there you have it! Those are your levels of problem solving. As you go through each step, the more expensive the problem is. --BUT WAIT. 

I picked something up along the way and this is where I typically thrive. Somewhere between problem solving step 8 and 10. 

The secret step

My recommendation at this point is to try tests that are seemingly unrelated to anything to do with the problem at all.

Pull a random cable, test with a random system off/on, try it at a specific time of the day, try it specifically after restarting or replugging something in. Now, not completely random but within some sort of scope.

These test are the ones that when someone is having a problem when you suggest they say "that shouldn't fix the problem, that shouldn't be related" and they are absolutely correct.

But here's the thing -- at this stage they have already tried everything that SHOULD fix the problem. Now it's time for the hail mary's, the long shots, the clutching at straws. This method works wonders for many reasons.

1. You really are trying to try "anything" at this point. 2. Most of the time we may think we have problem solving step number 1 covered, but we really don't. 3. Triggering correlations.

This is important.

Triggering correlations

In a later post I will cover correlation vs causation, but for now understand that sometimes all you want to do is throw in new inputs to the system or problem you are solving in order to get clues or re identify problems or give new ways to approach earlier problem solving steps.

There you have it. Problem solve like a ninja. Approach that extremely experienced and smart person what their problem and as they describe all the things they've tried, throw in a random thing they haven't tried. And when they say, well that shouldn't fix it, you ask them, well if you've exhausted everything that should have worked, this is the time to try things that shouldn't.

Either they will think of more tests they haven't considered so as to avoid doing your preposterous idea OR they try it and get a new clue to their problem. Heck, at worst they confirm that they do know SOMETHING about the system.

Go out and problem solve !

As always, thanks for reading and good luck with all of your side hustles.

How to get past your creativity block and why you should try new tools for your design

Let's explore why the tool has nothing to do with the art, but why the different tools can help you open up your creativity. We can explore other ways to get you out of your rut, no matter what you are designing or trying to be creative about. What tools have you determined will help you solve your problems? Why are you stuck? Lets try beating designer's block.

"A Poor workman blames his tools"

We've all heard the saying to some effect - and it applies to engineers and designers as well, but it's not the whole story. Here's an important part not to get wrong - this doesn't mean that tools have no effect on the overall outcome. This can't be true as there would be no point of their existence at all.

So let me unpack a little bit, tools enable, they are an extension of a user, a great designer can design on a napkin if necessary. So, no, you can't always blame your bad work on bad tools, but there is merit and skill in knowing which tools actually work (not just based on reading the reviews and picking on a 5 star rating!), the most experienced professionals will know which tools would be appropriate for a job personally.

BUT. Let me interject here with a reason why there is value in using other tools, even if you have found "the one" in terms of your perfect tool for the job.

Depending on the tools you decide to work with, you are inherently locked into a certain framework, certain pros and cons that come with said device. You have likely picked the tools based on comfort first, and then perhaps some experience you have around the tool or knowledge about it for the job.
You have then determined that other tools cons are not best for the job.

That.

That is precisely where the value can come from. Here's my situation currently. In a previous post, I talked about using Gravit Designer and how I have determined that was going to be the tool I used for 10Up development.

Sometimes you get stuck

The problem is, I got a little bit stuck when designing the new graphics. Now, I'm not sitting here blatantly blaming my tools and saying the designer tool I've chosen is why I can't create the right graphics for my app. But because of the fact that I was stuck, for me it generally  means time for a change.

From another well known quote "Insanity is doing the same thing over and over again and expecting different result", well in this instance it was time to look for a new angle. And that new angle was going to come in the form of new tools.

Change it up

Think about it. You try to solve the same problem using some different tools and different places and in some cases you can expect different results. This is precisely what I was going to do. Change tools. Not because the first tool was broken, but to create a change of pace, change of angle, different perspective, whatever you want to use to explain it, but the inherent cons in the frameworks forced upon you by specific tools may just be what the doctor ordered.

Typically you hear about getting in a different mindset, going outside, looking at other solutions, mediating, etc. But I thought, no, let's try this.

Design the same problem with different tools

So, I got myself a Wacom Intuous and started playing with Piskell App for creating pixel art and Sketchbook for drawing ideas (Yes a pencil and a napkin can also suffice) and started trying to design for the same problem, starting with completely different tools.

At first I just started creating whatever I could create, but eventually that got some juices flowing onto my original problem. The great thing here is the fact that even if you don't completely solve your issue, if you have gotten past a certain design hurdle - boom - all of a sudden you are back. Reverse engineer that idea and come to the original place of work and execute.

You're simply searching for a trigger and other tools may not be where you really want to develop your idea the forced perspective may be all you need.

And 1 more reason

Changing tools may help you with your creative block but there is one more reason for the technical experts out there and it is tying back to what I said at the beginning of this writing
"the most experienced professionals will know which tools would be appropriate for a job personally"

As a professional you owe it to your self learning to use tools you never have in order gain personal, physical experience with other tools and further yourself as an expert in your craft!

As always, good luck to all on your side hustles. If this helped you or made you think at all, share it with your friends and family! You never know who could need it.