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 your subconscious to target a specific creative design problem for you

Inspiration can come from the strangest of places.

Sometimes you think you know how you want your new app to look. But in reality you have more of a feeling that you want to get when you see the look of your new app. I know this because I thought I knew exactly how my app will look and when actually putting pen to paper (figuratively) I know it looks nowhere near anything work showing to anyone.

Okay, typically when you are getting to the point of showing your work, it is easy to be critical on yourself, but in this case, it was more the fact that it is early stage and all I really have is the feeling I want, and not the look itself.

So where do you go to find the look?

Well, firstly I go inwards, think of actually using your app, think of what would be the pieces of information you would want to see, think of what draws you in. Next its looking at others apps out there, maybe googling an app similar to yours and adding best UI. After some time it is best to go outside, maybe to an event, and just observe the world around you.

So that's exactly what I did. Tonight in Sydney the Vivid light show was on and I thought what better place to "inspirate" than an artistic light show where the city itself is the canvas!

Perfect

It turns out I did actually come away with the initial vision of how to achieve the "feel" of the app I'm going for. But you'll never guess which piece of art got me there.

Was it this nicely lit tree?

Or how about this melancholic sea of floating light bulbs?

Well it ended up being none of the above? My vision for the design came in transit sitting on a train listening to a podcast. It's interesting because much like when you are in the shower and you have those "shower thoughts" a monotonous task can get you into a different mindset, different pathways in your brain link.

But wait. Sometimes these thoughts are unique and different, but quite frankly useless thoughts such as

"When you drink alcohol you are just borrowing happiness from tomorrow"
or "clapping is just hitting yourself because you like something"
and "when you say 'Forward' or 'Back', your lips move in those directions"

Great. But it would be nice if that could apply to something I actually want to achieve. So why on this occasion on the train did the problem I was trying to solve get solved subconsciously?

Maybe it was coincidence, but maybe because my mind had locked in a future task i.e. get inspiration to solve my design problem after this train ride, that in my subconscious that was the "next" task. Then as mundane as a train ride was the subconscious has what is next and in that mind state began to solve.

I know the feel of the individual rounds in the game I want to achieve, the font style of the main message and the behavior as time runs out all appeared to me and I expanded it to the colors and the overall game flow.

By the time I got to the light show and had dinner it was out of mind and I just enjoyed the evening. Before I'd even gone out I had already locked in my idea!

The Solve

So try give this a go. The next time you try go out to get new ideas, don't focus on the problem, just focus on the fact that the next thing you are going to do is get new ideas. Lock it in. Schedule it.

But allow enough time for some monotonous tasks in between whether it be on a train (not actively driving) or perhaps the shower before you leave. The trip cannot be anything you are "organizing" and have stress factors to worry about others getting there on time etc. These things will take all of your attention.

Give it a go and let me know if you managed to trigger one of these mind states but got your subconscious targeted at a creative problem you were actually trying to solve.

As always good luck on your side hustle!