Communicating Decisively under Constraints

What if you had to achieve the same results with half the resources? Years ago, I ran a workshopping exercise with 90 magazine editors. It was called The 8 Page Magazine. I set the scene: a surprise paper shortage had been announced, and the government had decreed that, for the rest of the year, all magazines must be printed on just 8 pages. The editors had 20 minutes to plan their magazine within this extreme constraint. Their reactions were revealing. Some tried to cram everything in — every feature, every column — just in miniature. The result? A cluttered, unsatisfying mess. But the smartest editors made tough choices. They stripped the magazine down to its essence, giving just three or four key elements the space to breathe. Then I asked them: “Now that you’ve decided what’s really important, what happens if you go back to your normal number of pages?” The impact was transformative. Their magazines became cleaner, more purposeful, and more impactful. They focused resources on what mattered — and cut the clutter. This exercise wasn’t just about magazines. It’s a lesson for any business facing constraints: → What if you could only serve half your customers but twice as well — who would you choose? → What if you could only sell one product — what would it be? → What if you diverted half of your budget into a new area — where would you launch something new? Scarcity forces clarity. Constraints drive creativity. Sometimes, the best way to grow bigger is to think smaller. Is there an 8 Page Magazine moment in your business?

As a commander and senior military leader, communicating tough decisions with my team was never easy for me, but I also understood that it was a necessary and critical skill for effective leadership. Here are six techniques that helped me better communicate difficult decisions with my team: 1️⃣ Prepare: Be confident in your decision and the rationale behind it. Ensure leaders at all levels of the organization also understand the rationale. Anticipate potential questions or concerns from your team. When possible, include members from your team in the decision-making process. 2️⃣ Be Transparent: Be honest and transparent about the situation. Explain the factors that led to the decision and the implications it may have on the team and individuals. Transparency builds trust, even if the decision itself is difficult. 3️⃣ Provide Context & Clarity: Offer as much context and clarity as possible about the decision-making process. Help your team understand why the decision was necessary and how it aligns with the team's goals or larger organizational objectives. 4️⃣ Express Confidence & Support: Even if the decision may not be popular, convey confidence in its necessity and your team's ability to adapt and overcome challenges. We’re in this together. 5️⃣ Encourage Feedback & Questions: Create an environment where team members feel comfortable sharing their thoughts, asking questions, and providing feedback. 6️⃣ Follow Up: Follow up with your team regularly to assess the impact of the decision and address any ongoing issues or concerns. Keep communication channels open to maintain transparency and trust. By following these steps, you can effectively communicate tough decisions with your team while fostering understanding, trust, and resilience. #communication #leadership #FlyingInTheFaceOfFear

When AI meets the Theory of Constraints — the result is next-level clarity. My friend Dan Martell, one of the sharpest minds I know in SaaS and Business sScaling, recently shared how he uses ChatGPT Voice Mode — not just as a productivity tool, but as a thinking partner to decide what the ONE thing is to focus on next. Dan and I share a deep appreciation for the Theory of Constraints (TOC)... In his story, Dan goes for a run, talking to ChatGPT about a tough strategic decision. By the end of the 45-minute run, AI didn’t just give him advice — it cut through the noise and showed him exactly what to do next. What made it powerful wasn’t the AI itself — it was how he used it. He gave it context and constraints — the situation he was in, what he’d tried, and his limitations — and told it to challenge him (using the TOC framework) to find the ONE thing he can and should do next AI without context, constraints, and a focusing framework like TOC generates noise. But with them, it generates signal — the ONE thing we need to succeed. Context can means telling AI your ONE Goal and what hasn’t worked. Constraints mean real-world boundaries, like: “I need something I can apply this week, at no cost, to generate more revenue.” That’s exactly what I suggested to a client who felt overwhelmed and wanted to use ChatGPT: His Q: “I am feeling overwhelmed with all the fires I'm fighting” I gave it his context and my framework — the ONE Thing Focusing Cycle (OTFC) — which guides ChatGPT to think through One Goal, One Constraint, One Problem, One Conflict, One Innovation, and One Experiment at a time. Here’s how ChatGPT helped him apply it 👇 🌀 Applying the ONE Thing Focusing Cycle ONE Goal:  “Free up my time to focus on strategic growth.” ONE Constraint:  “I have limited attention and budget” ONE Problem:  “I’m reacting to what’s urgent instead of what’s important.” ONE Conflict: “Start Focusing only on what’s important to grow, but then urgent issues might slip and create fires. Continue been distracted by urgent tasks to stay reliable, but important goals get delayed.” Each side has pros and cons — growth vs. stability — which is why the problem persists. ONE Innovation: “Block 2 hours each morning for high-leverage work before opening email — protecting time for strategy without neglecting operations.” This resolves the trade-off — keeping pros of both without cons of either. ONE Experiment:  “Try it for one week and measure progress.” By adding context, constraints, and the right framework, AI becomes a thinking partner that sharpens focus and confidence. As Dan said: “Using AI this way — not just for answers, but for thinking better — will make you a ton of money and a ton more impact.” I couldn’t agree more. Because the future of leadership isn’t about knowing more — it’s about focusing better. Question for you: What context, constraints, or frameworks — like the TOC — are you including in your prompts when asking ChatGPT for help?

Since inauguration, nonprofits, governments, and higher ed have been in a state of uncertainty. The most acute effect? Decision paralysis. Contracts are delayed, teams are anxious, and leaders don’t know what’s coming next. Organizations in these sectors, built for slow, consensus-driven decisions, are struggling to respond to constant shifts. The result is churn, stress, ambiguity...AND complying in advance out of fear. We can each help bring clarity and calm to these situations. Whether you’re a CEO, a middle manager, or a program lead, you can model crisis communication by answering (or asking) three simple questions: 1️⃣ What do we know to be true? State clear facts. If you don’t know, ask the room. Example: “This executive order is in effect,” or “We have funding through next year.” 2️⃣ What remains uncertain? Don’t stay silent on unknowns—it breeds fear. Explicitly name the gaps: “We don’t yet know the impact on our programs, but we’re monitoring closely.” 3️⃣ Does this change what we should do right now? Be explicit about the impact on the day-to-day. Should your team continue as usual? Pause? Prepare contingencies? If this question is punted or delayed, everyone will make individual, implicit decisions anyways. So make them intentional. This framework has helped me as an interim CEO, in coaching program leaders, and in navigating crisis moments. And it needs to be repeated every few weeks right now (because uncertainty isn’t going away). We may not have all the answers, but we can choose to communicate in a way that fosters trust instead of chaos. Let’s bring clarity where we can. #Leadership #Communication #DecisionMaking

In my day-to-day activity as a Product Manager, one thing I can’t avoid is trade-off decisions. For every product decision that looks exciting on the surface, something else has to give. Because in product development, you can’t get everything you want at the same time. Tough but true. But then the real question becomes: How do I make these trade-offs while still delivering customer value and achieving business goals? Before making any trade-off decision, I often ask myself: • What will happen if Action A happens? • What won’t happen if Action A happens? • What will happen if Action A doesn’t happen? • What won’t happen if Action A doesn’t happen? A lot of thinking lives in those questions. And if thought well, you will make the “best” decisions. Stategically choosing the most important option right now, given the goal, the constraints, and the long-term direction of the product is my day to day. Some days, that means: • Prioritizing stability and performance over shiny new features • Making a business decision users won’t immediately love • Shipping a smaller scope to move faster • Saying “not now” to good ideas so great ones can take the front row Communicating these decisions can be just as hard as making this decisionespecially when you’re working with different teams who wants something important. Lately, my conversations have sounded like this: “Given our current goal of X and constraint Y, we’re prioritizing A over B, with B planned for Z.” This simple but firm reponse backed with data and lots of this versus that has helped me bring clarity across teams. Clarity doesn’t remove disappointment but it builds trust. And in product management, that trust is everything. #Makingproductdecisions #ProductManagement #TradeOffs #ProductThinking #BuildingProducts #PMLife

One of the world’s largest companies told us "We need all the digital for the CES trade show booths ready in weeks." We said no. This was a huge opportunity, and someone else said yes….AND, they failed to deliver it (it was a mission doomed to failure). The easy path is saying “yes” to every piece of work that pays. The hard path is saying “no” to everything that isn’t going to be successful. The way to “win” is finding a win for both parties. When a client comes with an "impossible" timeline, we don't immediately reject it – sometimes we are even known as people who pull off the impossible. We can do this because we transform these situations into a collaborative problem-solving exercise: "If that date is your constraint, then let's adjust what we deliver and how we work together." This solution-finding approach has become our superpower. We move multiple levers simultaneously — scope, process, team structure, and feedback cycles — until we find a configuration that works. Sometimes, that means delivering 5 pages instead of 20, in time for the event, with a clear path to complete the rest quickly. Sometimes, it means restructuring the team to have fewer people with less hurdles dedicated 100% to the project. The magic happens when we treat clients as partners in solving the problem, not just buyers of services. We empower them with choices rather than ultimatums. This isn't just about managing expectations — it's about creating a partnership where both sides are invested in finding the best possible solution within the constraints.

Minimal resources, tight timelines, high expectations. We've all been there. Here’s how I deliver big projects in tough times as a VP of Engineering: ▪️ Prioritize with Purpose -When you can’t do everything, focus on the right things. Ruthlessly align efforts with goals that deliver the most value. ▪️Foster Creativity Through Constraints - Limitations can force you to think outside the box. Invite your team to find clever, simple solutions that might never have been considered with a big budget. ▪️Communicate Relentlessly - When resources are tight, the margin for error shrinks. Make sure every team member understands the plan, their role, and the "why" behind each decision. ▪️Build Team Resilience- Celebrate wins--big and small. When your team feels appreciated and focused, they’re more likely to rally together and innovate under pressure. One of my most vivid memories as a technical executive was doing exactly this- leading a high-visibility initiative where the budget felt more like a suggestion than a reality. There’s nothing quite like delivering a big project on a shoestring budget. I remember sitting in a room with my team, staring at a list of features and a budget that made us all laugh nervously. But instead of despairing, we got creative. We started by ruthlessly prioritizing: “What’s the one thing that will deliver the most value?” We questioned everything--every line of code, every resource allocation, every timeline--to ensure it was necessary and impactful. The result? A launch that exceeded expectations. We didn’t have everything we wanted, but we focused on delivering what mattered most. Looking back, I wouldn’t trade that experience for anything. It taught me that innovation isn’t about having all the resources--it’s about making the best of what you’ve got. Have you ever had to deliver something when resources were tight? How did you approach it? and what did you learn along the way? Drop your story in the comments--I’d love to hear how you thrived under pressure!

When I first stepped into leadership roles, I was that person who tried to implement EVERY single strategy from EVERY product book I read. 📚 (Anyone else guilty of this?) I realized successful leaders aren't collectors of every best practice. They're thoughtful curators who select what works for their specific context. In the same vein, instead of saying "yes" to every project, I learned to apply what I call the "constraint conversation". When faced with seemingly impossible targets or deadlines, I frame discussions around three constraints: ⌛ Time: What's our actual timeline? 💱 Money: What budget do we have to work with? 👯 Resources: What team capacity and expertise is available? For example, "With our current timeline and budget, we can deliver these three features. If we extend by two weeks, we can add these two more. If we increase resources by 20%, we can bring in additional expertise." This approach transforms what could be tense conversations into collaborative problem solving sessions. It focuses everyone, looking at the same puzzle - and puzzle pieces - together. Through curation and honing in on the techniques that are authentic, a principle I return to is --> people over pixels <-- While technology evolves, focusing on the humans behind the screens remains the constant grounding factor for me. 🌟 Putting It Into Practice 🌟 1. Audit your approach: Which "best practices" are actually serving you and your team? Which are just creating busy work? 2. Reframe impossible requests: Next time you face an unreasonable demand, try the constraint conversation approach. 3. Check with humans: For your current project ask "How does this serve the actual people who will use it and the team putting in the work?" I'd love to hear how you're applying these ideas or others you recommend.

A few months ago, I had the opportunity to put Jim Highsmith 's Agile Triangle to good use to help managers while crafting a proposal with a new client. Here's a breakdown of the approach: The client wanted a lot, but had limited resources (time and money). The traditional approach (fixed scope, time, and cost) wouldn't have worked because it says we deliver given scope within given time and budget. We needed to find a way to meet their needs within the constraints.So here is where the Agile Triangle helped The Agile Triangle has three sides: Value: The most important requirements for the client and project success. Constraints: Time, scope and budget limitations. Quality: Delivering a high-quality product. Here's how we used it: Open Communication: We explained the Agile Triangle to the client, emphasizing our focus on delivering value within their constraints. Prioritizing for Value: We worked with the team to prioritize requirements based on how much they would help the client, not just how complex they were. Quality: We stressed our commitment to delivering a value with high quality, not just features. Negotiation: We used the Agile Triangle for trade-offs and discussed potential adjustments to scope, time, or cost openly. This fostered collaboration and helped us reach a mutually beneficial solution Takeaways for Scrum Masters & Agile Coaches: ✅ Use the Agile Triangle to talk to clients about value within constraints: Explain how Agile focuses on value within constraints and facilitates transparent negotiation. ✅ Prioritize based on value, not complexity: Help your team choose what matters most to the client, fostering collaboration during proposal creation and be prepared to negotiate the trade offs if needed. ✅ Quality: Make it clear that quality is built-in, not an afterthought. #acrt #agiletriangle #agileprojectmanagement

A real conversation between me and a CEO that I worked with in a previous life... Me: "We need to change our benefits broker. We're not getting the service that we deserve, the data that we need, and we're spending too much of our time trying to come up with creative solutions." CEO: “We can make the change, but I've got two rules - I don't want to change our medical carrier, and I'm only going to consider brokers that are headquartered in our home state. Got it?” Me: “Okay. We don't have any issue with the carrier. Our issue is with the broker. You do understand that this will significantly shrink our candidate pool and take the usual suspects out of the equation?” CEO: “Those are the rules.” Me (internally): “Okay… limited pool, tight timeline, big expectations. Let’s go!” So my team rolled up our sleeves, mapped out every qualified in-state broker, vetted capabilities, interviewed teams, and built a short list that actually made sense. A few weeks later, we had our new broker. ✅ Better pricing ✅ Stronger service ✅ Renewed trust in the process And the CEO? CEO: “I didn’t think this was possible.” Me: “That’s kind of my thing.” 😉 💬 Sometimes constraints aren’t roadblocks - they’re creative catalysts. #leadership #HR #benefits #problemsolving #strategy