A Simple Flowchart for Solving Any Technical Issue

Solving technical issues is generally simpler than most people think. In fact, by following the steps outlined in the upcoming flowchart, you will be able to solve nearly all of the issues that you encounter, whether they’re in your computer, in your phone, or in any of your other devices.

If you have a friend or a colleague whom you always thought of as a tech/computer expert, then know that this is most likely what they do each time you ask them for help. In fact, as long as you follow these steps, you can also become a local expert, even if you have no previous technical skills.

The chart itself is pretty self-explanatory, but there is a brief explanation afterward if you’re interested. Even if it looks complex at first, give it a shot; you’ll find that it’s surprisingly straightforward.


A flowchart showing the steps to follow when trying to solve technical issues.


If you’d like to print it out, here’s the PDF version.

I also want to give credit to this great flowchart from xkcd for the original idea. The chart in the current post adds a few important steps, such as restarting your device.


Flowchart walkthrough

This section contains some brief explanations regarding the different steps in the chart. These explanations can help you better understand what to do and why to do it:

Find a relevant button/menu item and click it. In most cases, something relevant should be easy to find. Try to play around with the options and settings a bit if you’re not sure what to do. Often, you can find the solution easily yourself if you’re just willing to look for it.

If you’re trying to fix a problem, restart the device. Doing this solves a huge amount of technical issues. If you’re not sure how to restart your device, search online for instructions. Make sure you’re restarting the device itself, and not just the screen (if the two are separate). It’s generally preferable to turn the device off completely, wait 10 seconds, and then turn it back on; this is because it sometimes takes a while for all the components to power down, and for the capacitors to discharge.

Search online for a solution using a few relevant keywords. Odds are that someone has encountered this issue before. If they did, there will often be a digital record of the solution online. If you’re not sure which keywords to use, pretend you’re asking a tech expert for help, and use the same keywords you would use when explaining to the expert what you’re trying to do.

Consider whether this is worth the trouble. Often, trying to figure out how to use a certain feature can be much more work than trying to do the same thing using a different feature. Similarly, some issues are so minor that they’re not really worth the time and effort. The steps up to here require only a small amount of effort and have a high success rate, which is why this is a good cutoff point for deciding whether to continue searching for a solution.

Post the question on a relevant forum or contact tech support. This can help in cases where you can’t find the solution yourself. The benefit of asking for help in a relevant forum is that you reach a high concentration of experts, and it can sometimes take them a minute to answer a question that you have spent hours trying to find the answer to. Note that these forums tend to have strict posting rules, so make sure to dedicate two minutes to read them before posting.

Ask someone for help. If you decide to ask someone for help, make sure to tell them what you already tried. This can help them find a solution, and it also shows that you put some effort into solving the issue before coming to them. Keep in mind that unless they themselves are experts on the topic, they will probably follow the same steps outlined here, though they might find something that you missed. This is also often true for hired, professional help.


Avoid learned helplessness

A lot of people have a sort of learned helpless when it comes to technological issues. This means that instead of trying to solve issues when they encounter them, they give up prematurely and simply assume that they won’t be able to find a solution. In reality however, most issues are pretty simple to solve, and once you recognize that technical experts and IT people generally follow the same steps you saw above, you will realize that you can often solve these issues yourself.


Summary and conclusions

  • Even if you are not an expert, you can solve nearly all technical issues by using a simple, systematic approach.
  • The steps you should follow are listed in the flowchart that appears at the beginning of the article.
  • The two most important things to do first are to try and find a relevant button/item to click on, and to search for a solution online using relevant keywords.
  • If you’re trying to solve a technical problem, restarting the device often helps.
  • Always consider whether it’s worth it to keep searching for a solution; sometimes it’s easier to ignore the issue, or try to solve it from a different angle (for example, by using a different feature).