How I Think
I begin by defining the decision or result that is actually needed, the facts that can be supported, and the constraints that shape the available options. I separate verified information from assumptions, symptoms from root causes, and recurring patterns from exceptions before comparing possible responses. The conclusion is explained directly, together with the evidence, tradeoffs, and conditions that would require the decision to change.
Decision framework
The framework is used when the correct next step is not obvious, when multiple needs compete, or when another person must be able to understand and review the reasoning. It defines what should be decided and why; the coordinated How I Work framework then turns that decision into execution.
| Step | Focus | Guiding question |
|---|---|---|
| 01 | Define the Question | What must be decided, improved, or clarified? |
| 02 | Facts, Context & Constraints | What is supported, what is assumed, and what limits the options? |
| 03 | Patterns, Exceptions & Root Causes | What repeats, what does not fit, and what is producing the visible problem? |
| 04 | Options & Tradeoffs | Which responses best satisfy the evidence, standard, risk, and intended use? |
| 05 | Decision & Communication | What response is justified, why, and who needs the answer? |
| 06 | Record & Revisit | What reasoning, assumptions, and conditions should be preserved? |
The reasoning sequence
The sequence starts before analysis. Defining the question and intended result prevents the work from drifting into a technically correct answer to the wrong problem. Each stage reduces uncertainty, makes the judgment easier to explain, and preserves the basis for review when conditions change.
Related, but different
How I Think determines what response is justified and why. How I Work translates that decision into requirements, ownership, execution, validation, delivery, and improvement. The pages are designed as a pair: one makes judgment visible; the other makes the operating process visible.
The decision method that makes judgment visible.
The operating method that makes execution visible.
When guidance is incomplete
An unclear instruction does not automatically require a meeting, and it should not be answered with a guess. The first task is to identify the smallest unresolved point, determine how much it affects the decision, and communicate directly with the person or source that can resolve it.
Write the question in a form that can be answered. This keeps the discussion focused and prevents unrelated concerns from taking over.
Identify the exact rule, source, owner, definition, or piece of evidence that prevents a confident answer.
Determine whether timing, compliance, cost, risk, technology, or downstream use changes how much uncertainty is acceptable.
State what is known, what is unclear, and what decision is needed. A focused question gives the other person something concrete to answer.
Proceed when the evidence is sufficient, and the remaining uncertainty is within the decision authority. Escalate when the consequences of being wrong outweigh the cost of clarification.
Record the answer, its limits, and the conditions under which it applies so the next person does not have to repeat the entire discussion.
Adaptable quality
Requirements, business priorities, tools, people, and available information change. A strong decision must protect the non-negotiable standard, acknowledge the limits of current evidence, and remain sufficiently clear to be revised later. Change is not an excuse for careless judgment, but quality should not depend on pretending that one answer will remain final forever.
State what must remain accurate, compliant, safe, or usable regardless of which method is selected.
Identify which constraints govern the decision and which elements can change without compromising the intended result.
Determine how much support is required for the current decision and what level of uncertainty or risk can be accepted.
Return to the original question when facts, standards, risk, or intended use change; revise the answer without losing the reasoning that produced it.
Applied judgment
The framework is most useful where volume, ambiguity, competing needs, and real-world constraints must be managed simultaneously. It provides a consistent way to move from incomplete information to a decision that is usable, explainable, and open to review.
Choose a defensible next step when standards, deadlines, risk, cost, technology, and available information compete.
Separate a genuine defect from acceptable variation, determine the appropriate correction, and explain the distinction so another reviewer can apply it.
Evaluate whether expertise, instruction-following, error patterns, and response to feedback support approval, restrictions, retraining, or rejection.
Determine whether a repeated problem comes from performance, unclear guidance, missing information, a handoff, a tool limitation, or process design.
Assess incomplete or inconsistent records, determine what can be trusted, and define the limits of appropriate use.
Turn a resolved decision into reasoning or guidance that supports the next person without removing the need for judgment.
See the method in practice
The case studies apply this decision framework to regulated content, translation quality review, vendor qualification, legacy data recovery, workflow automation, operational documentation, and AI-assisted web development. The industries and tools differ, but the reasoning remains consistent: define the result, understand the constraints, diagnose the underlying cause, evaluate the options, explain the decision, and preserve what should be revisited.