Structured thinking is a framework for solving unstructured problems — which covers just about all data science problems. Using a structured approach to solve problems not only only helps solve problems faster but also helps identify the parts of the problem that may need some extra attention. 

Think of structured thinking like the map of a city you’re visiting for the first time.Without a map, you’ll probably find it difficult to reach your destination. Even if you did eventually reach your destination, it’ll probably take you at least double the time.

What Is Structured Thinking?

Structured thinking is the process of creating a structured framework to solve an unstructured problem. As a problem-solving methodology, structured thinking involves dividing a large problem into smaller ones in order to solve the big problem faster and more efficiently.

Here’s where the analogy breaks down: Structured thinking is a framework and not a fixed mindset; you can modify these techniques based on the problem you’re trying to solve.  Let’s look at five structured thinking techniques to use in your next data science project.

5 Structured Thinking Techniques for Data Scientists

  1. Six Step Problem Solving Model
  2. Eight Disciplines of Problem Solving
  3. The Drill Down Technique
  4. The Cynefin Framework
  5. The 5 Whys Technique

More From Sara A. Metwalli3 Reasons Data Scientists Need Linear Algebra

 

1. Six Step Problem Solving Model

This technique is the simplest and easiest to use. As the name suggests, this technique uses six steps to solve a problem, which are:

  1. Have a clear and concise problem definition.

  2. Study the roots of the problem.

  3. Brainstorm possible solutions to the problem.

  4. Examine the possible solution and choose the best one.

  5. Implement the solution effectively.

  6. Evaluate the results.

This model follows the mindset of continuous development and improvement. So, on step six, if your results didn’t turn out the way you wanted, go back to step four and choose another solution (or to step one and try to define the problem differently).

My favorite part about this simple technique is how easy it is to alter based on the specific problem you’re attempting to solve. 

We’ve Got Your Data Science Professionalization Right Here4 Types of Projects You Need in Your Data Science Portfolio

 

2. Eight Disciplines of Problem Solving

The eight disciplines of problem solving offers a practical plan to solve a problem using an eight-step process. You can think of this technique as an extended, more-detailed version of the six step problem-solving model.

Each of the eight disciplines in this process should move you a step closer to finding the optimal solution to your problem. So, after you’ve got the prerequisites of your problem, you can follow  disciplines D1-D8.

  1. D1: Put together your team. Having a team with the skills to solve the project can make moving forward much easier.

  2. D2: Define the problem. Describe the problem using quantifiable terms: the who, what, where, when, why and how.

  3. D3: Develop a working plan.

  4. D4: Determine and identify root causes. Identify the root causes of the problem using cause and effect diagrams to map causes against their effects.

  5. D5: Choose and verify permanent corrections. Based on the root causes, assess the work plan you developed earlier and edit as needed.

  6. D6: Implement the corrected action plan.

  7. D7: Assess your results.

  8. D8: Congratulate your team. After the end of a project, it’s essential to take a step back and appreciate the work you’ve all done before jumping into a new project.

 

3. The Drill Down Technique

The drill down technique is more suitable for large, complex problems with multiple collaborators. The whole purpose of using this technique is to break down a problem to its roots to make finding solutions that much easier. To use the drill down technique, you first need to create a table. The first column of the table will contain the outlined definition of the problem, followed by a second column containing the factors causing this problem. Finally, the third column will contain the cause of the second column's contents, and you’ll continue to drill down on each column until you reach the root of the problem.

Once you reach the root causes of the symptoms, you can begin developing solutions for the bigger problem.

On That Note . . .4 Essential Skills Every Data Scientist Needs

 

4. The Cynefin Framework

The Cynefin framework, like the rest of the techniques, works by breaking down a problem into its root causes to reach an efficient solution. We consider the Cynefin framework a higher-level approach because it requires you to place your problem into one of five contexts.

  1. Obvious Contexts. In this context, your options are clear, and the cause-and-effect relationships are apparent and easy to point out.
  2. Complicated Contexts. In this context, the problem might have several correct solutions. In this case, a clear relationship between cause and effect may exist, but it’s not equally apparent to everyone.
  3. Complex Contexts. If it’s impossible to find a direct answer to your problem, then you’re looking at a complex context. Complex contexts are problems that have unpredictable answers. The best approach here is to follow a trial and error approach.
  4. Chaotic Contexts. In this context, there is no apparent relationship between cause and effect and our main goal is to establish a correlation between the causes and effects.
  5. Disorder. The final context is disorder, the most difficult of the contexts to categorize. The only way to diagnose disorder is to eliminate the other contexts and gather further information.

Get the Job You Want. We Can Help.Apply for Data Science Jobs on Built In

 

5. The 5 Whys Technique

Our final technique is the 5 Whys or, as I like to call it, the curious child approach. I think this is the most well-known and natural approach to problem solving.

This technique follows the simple approach of asking “why” five times — like a child would. First, you start with the main problem and ask why it occurred. Then you keep asking why until you reach the root cause of said problem. (Fair warning, you may need to ask more than five whys to find your answer.)

Expert Contributors

Built In’s expert contributor network publishes thoughtful, solutions-oriented stories written by innovative tech professionals. It is the tech industry’s definitive destination for sharing compelling, first-person accounts of problem-solving on the road to innovation.

Learn More

Great Companies Need Great People. That's Where We Come In.

Recruit With Us