TJ Walker shows managers how to handle two common workplace dilemmas: Aaron negotiates a rushed deadline that would overload his team, and Nina finally confronts a chronically late employee. Both use a structured framework to generate options, pressure-test outcomes, and find solutions that balance business needs with team health.
Chapters
Ultimize. A team leader named Aaron gets pulled into a meeting with his boss. The boss says, we need this client presentation moved up by 2 weeks. Aaron knows immediately what that means. His team's already stretched. 2 people are behind on deliverables, and moving the deadline up will almost guarantee late nights and weekend work. But in the moment, he nods. Okay, we'll make it work. Meeting ends. Now the real decision starts. Aaron sits down and thinks, should I push back or just get it done? That's the wrong question, so he reframes it. What outcome am I trying to protect over the next 2 weeks? Now the option becomes clear. Option 1, say nothing and push the team harder. Option 2, push back directly and risk friction. with his boss. Option 3, propose a modified timeline or scope. Now he runs the structured prompt. I'm a team leader with a boss who just moved a deadline up by 2 weeks. My team is already at capacity. Give me 3 ways to respond strategically, the risk of each approach, the likely impact on my team performance, and my relationship with my boss. Now the situation becomes visible. Say nothing— short-term compliance, long-term burnout and resentment. Push back aggressively— protects the team but risks damaging trust with the boss. Propose an alternative— hey, it could show leadership, balances delivery and team health. Now Aaron adds pressure testing. What is the most likely way staying silent fails? Well, the answer: the team misses the deadline anyway, quality drops, and Aaron looks like he mismanaged the situation. Now the decision is clearer. Doing nothing is the worst option. So instead of reacting emotionally, he responds strategically. He schedules a quick follow-up. Here's what we can realistically deliver in the time frame, and here's what I would need to change to make it work. Same situation, completely different outcome. Now let's look at a different scenario. A manager named Nina has a direct report who keeps missing deadlines. Not by a lot, just enough to be a problem. Nina avoids addressing it directly. She drops hints, adds reminders, hopes it improves. It doesn't. Now the issue is bigger, more frustrating, more personal. So she runs the system. She defines the decision. Do I address this directly now, escalate it, or continue managing around it? Then she runs the prompt. What are the risks of addressing performance issues too early Versus too late. Now she sees it clearly. Too early can feel harsh. Too late creates patterns that are hard to fix. Then she pressure tests things. What is the most likely outcome if I continue avoiding this conversation? The answer: the behavior continues. Other team members notice, and overall performance drops. Now the decision becomes obvious. She schedules a direct conversation, addresses the issue clearly, sets expectations. Problem handled early instead of becoming a long-term issue. This is what navigating people in power actually looks like. Not avoiding tension, not reacting emotionally, but seeing the real trade-offs and acting with clarity. Because most workplace problems are not technical. They're decision problems involving people. And when you structure your thinking, you stop guessing how to handle them and you start leading.
