TJ Walker explains how to define a decision before analyzing it. Most people ask vague yes-no questions that mix multiple choices together. Instead, state what outcome you want over what time period, then list the actual options. Maria wondering whether to take a project, or Daniel thinking about quitting his job, both need to separate the real decision from the emotional noise around it.
Chapters
Ultimize. A consultant named Maria gets an email from a client. Can you take on an additional project this month? Her first reaction is simple. Should I say yes or no? That feels like the decision. It's not. And this is where most people go wrong. They think they're making one decision when in reality they're dealing with 3 or 4 different decisions layered on top of each other. Maria starts thinking, if I say yes, I make more money. If I say no, I protect my time. If I say yes, I strengthen the relationship. If I say no, I might lose future work. Now she's stuck because she hasn't defined the real decision. She's mixing outcomes, fears, and assumptions into one vague question. So instead of deciding, she loops. Now, let's clean this up. Instead of thinking, should I say yes or no, she defines the decision properly. What am I optimizing for over the next 30 days? Now the situation changes because now the options become clear. Option 1, maximize short-term income. Option 2, Protect time and energy. Option 3, balance income and workload with a modified scope. Now she can actually see the trade-offs. Before, it was emotional. Now it's structured. Let's take another example. A software engineer named Daniel is thinking about leaving his job. He keeps asking himself, should I quit? The question's too big, too vague, Too loaded, so he avoids it. He scrolls job boards, he talks to friends, he complains, but he doesn't actually decide. Now watch what happens when he defines the real decision instead of, should I quit? He reframes it, what specific outcome would make leaving worth it within the next 6 months? That's the question he poses to to his AI. Now everything becomes clear. Higher salary, better manager, remote flexibility. Now he can evaluate real options against real criteria instead of just reacting to frustration. This is the first step of the system, and it's the most important, because if you don't define the decision correctly, everything that follows is flawed. You can run the best analysis in the world on the wrong question and still end up with a bad decision. So before you use AI, before you ask anyone for advice, before you think about pros and cons, you must do one thing: define the real decision. What exactly am I choosing between? What outcome am I optimizing for? What are the actual options in front of me? If you get this right, the rest of the system becomes simple. If you get it wrong, nothing else will fix it. In the next step, we're going to take that clearly defined decision and run it through a structured prompt that forces clarity immediately.
