# STEP 3: Prioritize code areas

{% hint style="info" %}
Typically, this step is done by QA Manager and the related Engineering Manager / Dev Team Lead / Tech Architect.
{% endhint %}

Facing a mountain of untested code changes with limited resources? Don't panic! Tackle it **smartly with prioritization**.

The key: **break down your codebase into manageable subsets**. Focus on one chunk at a time, addressing critical areas first. This **"divide and conquer" approach** delivers several benefits:

* **Faster results:** See quicker progress towards your quality goals.
* **Sharper focus:** Channel your limited resources effectively.
* **Increased confidence:** Gain greater trust in your software's overall quality, one step at a time.

***

There are several effective ways to prioritize code areas:

1. [**Add Code Labels**](https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-3-prioritize-code-areas/add-code-labels): Apply code labels to mark critical areas of your codebase, helping you create a subset of code that requires immediate attention.
2. [**Ignore Irrelevant Code**](https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-3-prioritize-code-areas/ignore-irrelevant-code): Exclude parts of your code that are not pertinent to the testing process. By focusing solely on the relevant sections, you can streamline your testing efforts.
3. [**Perform a Deep CSV Analysis**](https://docs.sealights.io/knowledgebase/guides/quality-improvement/quality-improvement-solution-overview/over-time-quality-improvement-guide/step-3-prioritize-code-areas/perform-a-deep-csv-analysis): Conduct a detailed analysis using a CSV file to gain more in-depth insights into the test gaps and identify high-priority areas.

We highly recommend starting with the implementation of code labels as the first step to create a subset of your code.