How I Think

How I Approach Problems

When someone brings me a technical issue, I do not immediately assume I know the answer.

My process begins with gathering information and developing an accurate understanding of the situation.

Before recommending a solution, I want to understand:

• What is the goal?
• What is working correctly?
• What is not working?
• What has already been tried?
• What systems are involved?
• What does success look like?

If the problem is not clear, I ask more questions.

My priority is not to appear knowledgeable. My priority is to understand the problem correctly.

Many technical problems are described through symptoms rather than causes. Taking time to understand the environment often reveals the real source of the issue.

Once I have enough information, I identify likely points of failure. At that stage I can usually say one of two things:

• I need additional information to determine the precise cause.
• I believe the problem is occurring here, and I can help identify and resolve it.

Only after I understand the problem do I begin recommending solutions.

This approach reduces assumptions, avoids unnecessary changes, and helps ensure the solution addresses the actual cause rather than a symptom.

In Summary

1. Gather information.
2. Understand the problem.
3. Identify the cause.
4. Develop a solution.
5. Implement carefully.
6. Document the outcome.
7. Teach others what was learned.

The goal is not simply to fix problems.

The goal is to understand them, solve them correctly, document the solution, and leave behind something better than what existed before.