# 11A Finding the Part That Needs to Change

Before changing a feature, I want to find the file or component that controls the behavior I can see on the page.
A project may contain many folders, so a clear question is more useful than opening unrelated files and guessing where to begin.
I describe the visible element, name the page where it appears, and explain which action or state I am trying to understand.
For example, I may need the component that renders the course cover and the function that chooses which image to display.
The answer should connect those pieces and show how information moves from the source data into the final rendered page.
A directory name can provide a clue, but it does not prove that every file inside has the same responsibility or purpose.
I also look for existing helpers that handle the same problem, because using the established approach can keep related pages consistent.
When the relevant code is found, I ask for a short explanation of its inputs, outputs, and important connections to other modules.
This makes it easier to identify the smallest meaningful change and understand which behavior might need to be checked afterward.
The goal is not to memorize the entire repository, but to build a useful map of the parts involved in the current task.