# How to Deep-Dive

**Required Prerequisite Reading:** [**How to Enforce the Quality Bar for your Team**](https://app.gitbook.com/@remoteu/s/manager-remoteu/v/master/day-2/how-to-enforce-the-quality-bar)

## **The Real Place**

&#x20;As I’m sure you’ve noticed by now, all of the specific frameworks we teach flow from larger belief systems. Deep dives are no exception, and before diving into instructions, it’s worth taking a step back to consider why we do deep dives.&#x20;

We deeply believe that ‘the answer is in the details’ - it’s why we do deep dives and it’s why we do Gemba Walks.&#x20;

The highest leaders in the company are constantly diving deep - listening to front line calls, interviewing ICs in every corner of the company, and clicking their way through links to find details.&#x20;

Elite managers are not only comfortable but also regularly deep dive into the details.

![](https://351862628-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fmanager-remoteu%2F-Lsy3oHc1YrH3xDdExMp%2F-Lsy3uS2VSHc87CU0OMb%2F0.png?generation=1572999507232179\&alt=media)

The first thing you need to realize before doing a deep dive is that you must do ‘Enforce the Quality Bar’ first. Deep dives are based on specific units that have failed the quality bar which is exactly what ‘Enforce Quality Bar’ produces.&#x20;

* **📺** [Deep Dives - Trilogy COO Explaining](https://drive.google.com/open?id=15q4HxBlKcRuSkfqqIy-iz68nMC-4-pHw)

If you have not yet done ‘Enforce Quality Bar’, go back and do it before proceeding.

&#x20;There are 2 purposes for Deep Dives. The first is to identify the root cause and the second is to create an action plan to fix the root cause.&#x20;

To identify the root cause of the quality bar failure, you should look at a specific unit that failed and ask ‘Why?’&#x20;

It’s easy to identify the surface reason why the unit failed but this does not provide any value. The key to a good deep dive is getting all the way down to the root cause.&#x20;

Once you have your first answer to ‘Why did this unit fail?’ ask ‘Why?’ Keep asking ‘Why?’ to your answers until you are at the root.

Most managers fail Deep Dives because they get stuck in abstract layers before getting to the root cause - they don’t go deep enough.&#x20;

How do you know when you are deep enough? You know you are deep enough when you come up with the specific reason why that individual unit failed.&#x20;

If you’re in the source code or the tactical weeds of your IC’s core function, you’re probably in the right spot.&#x20;

When it comes to creating an action plan to fix the issue, there is not too much to say besides: apply your expertise to craft a solution that would have prevented this exact unit failure.

* **📺** [How to do Deep Dives](https://drive.google.com/open?id=1rCStJHEg5-kO6jpL3W_KoLnKPeViZ12Y)

## **Instructions**

1\. Create a 3-hour calendar invite to timebox your Deep Dive. During this block, turn off Skype, shut down email, and only work on your Deep Dive. If you let yourself be distracted, you will decrease the quality of your Deep Dive

2\. Identify at least 3 units which recently failed your quality bar. This will be a natural outcome after you’ve enforced the quality bar for your team.

3\. Get into the right mindset. While you are doing a deep dive you want to:

* **Objective**: every decision must be supported by concrete, proven facts, not hearsay or intuition;
* **Amplify negative feedback**: we try to solve more than what was brought to our attention; we ask
  * “Is this a deeper problem than what is immediately visible?”
  * “Is this a general problem that I may find in other tickets as well?”
  * “Setting aside the root problem, did we also uncover related problems with these tickets?”
* **Customer-oriented**: we look at each problem with the eyes of the customer; we ignore our metrics, our org chart, our convenience.
* **Seek counter-measures** rather than simple solutions: a solution is something that fixes this one issue; a counter-measure is something that you deploy and that fixes all future issues of the same type.

The counter-measures that are identified can be formulated **in terms of quality bars**. Which concrete quality bar should have prevented this issue from occurring? Does that quality bar need to be

* raised? (i.e. we should add items to the QB in order to prevent these defects)

or

* enforced? (i.e. our current QB is good enough but it was not properly enforced)

4\. For each unit, do a deep dive to identify the root cause of the quality bar failure. To help get to the right depth, you can use the ‘5 Whys’ approach.&#x20;

Ask yourself why the unit failed the quality bar. When you have your answer, ask why. Repeat this process until you’ve asked at least 5 whys.

5\. Once you’ve identified the true root cause for the quality bar failure, build an action plan to address the failure. Since this is based on individual units, the action plan should be very specific.

If you’re dying to read more, read Farnam Street’s take on Root Causes: [link](https://fs.blog/2017/05/proximate-vs-root-causes/).

* **📺** [Deep Dives - Case Studies and Examples](https://drive.google.com/open?id=1KeQu5defhIiS-1gtRdAEiTFmvf9jNI5p)
* **📺** [Deep Dives - MRU graduate explaining his experience](https://drive.google.com/open?id=13ETqEJwaA4a3ESRfNEu9NF_9Spcw98sp)
