The "Sure, Why Not?" Filter I Use Before Saying Yes to Anything
I used to be the person who said yes to every request that came across my desk, then spent three nights rewriting things because I had overcommitted. The problem wasn't effort. It was that I never had a filter for whether something was actually worth doing. Then I started treating "sure, why not?" as a genuine decision framework instead of a reflexive agreement. That shift changed how I plan projects, allocate time, and eventually what I put on my calendar. The core idea is straightforward. When someone asks you to do something, or when an opportunity appears, you run it through three questions in order: sure, why not, how. "Sure" means do I actually want to do this? Not whether I could, not whether it would look good — whether I want to. "Why not" removes the imaginary obstacles you've been telling yourself about. "How" forces you to get specific about execution before you commit. Most people skip straight from "I should probably say yes" to vague optimism without the middle steps, which is why they end up stretched thin. Here's the thing nobody talks about: this isn't really a productivity method. It's a conversation tool, and that's why it works better than most frameworks I've seen. You don't use it alone in your head. You use it when someone pitches you something, when your boss assigns a task, when a client sends a rough brief. The moment you start asking "how" out loud, the conversation changes. People either realize they don't actually have a plan, or they come back with more detail. Both outcomes help you.
I ran into a real edge case with this a while back. A department head came to me and said we needed to "quickly onboard a new team onto our reporting system." Sure, I thought, why not, how. I asked for the deadline, the number of people, the existing training materials, and the scope of access they'd need. What came back was roughly 40 people across three time zones, a custom dashboard configuration that had never been documented, and a two-week timeline. I had initially agreed to something I was imagining as a half-day onboarding session. The "how" exposed that completely. I pushed back, proposed a phased rollout over six weeks with documentation first, and we ended up saving everyone from what would have been a terrible two weeks. The framework didn't just protect my schedule. It protected the other team from getting a half-finished product shoved at them. There are a few advanced nuances that trip people up. First, "why not" doesn't mean ignoring real constraints. If you literally have no budget, no headcount, and the technology doesn't exist yet, those aren't imaginary obstacles. The question is whether the obstacles are fixable within a reasonable timeframe or whether they're structural blockers. Second, you need to separate the ask from the relationship. Saying "I need to understand the how before I can commit" is not the same as being difficult. I've heard that distinction fail repeatedly in places where saying no is culturally penalized. In those environments, you reframe it as "help me understand the scope so I can give you an accurate timeline" rather than "I need answers first." Same outcome, different framing. One counter-intuitive insight: this method actually slows you down at first. For the first few weeks, you'll feel like you're taking longer to respond to requests. People might even find it annoying because you're not giving them the quick yes they expected. That friction is normal and temporary. Once the pattern is established, you spend less time saying yes to things you later resent. The net effect is faster turnaround on the work that actually matters.
Here's where it breaks down. If you work in a high-velocity environment where decisions genuinely need to happen in minutes, this framework is too slow. Emergency response, certain types of trading floors, crisis management during outages — situations where deliberation costs more than a wrong decision. In those contexts, you default to action and revise after. The "sure, why not, how" approach is designed for knowledge work where the cost of committing to the wrong thing outweighs the cost of spending ten extra minutes clarifying scope. Another limitation: this doesn't help if you don't actually have the authority to push back. If your organization treats any delayed response as insubordination, you're working against the system, not the mindset. I've seen this happen at companies with deeply hierarchical cultures where speed of agreement is valued over accuracy of agreement. In those places, I recommend using a modified version — you say yes immediately but document the "how" part in writing right after, which creates a paper trail and gives you leverage to renegotiate scope later when the real requirements surface. The practical way to start: pick one interaction this week where you'd normally say yes automatically. It could be a meeting invitation, a task assignment, or a casual request from a colleague. When it comes in, run it through the three questions before responding. Write down what "sure" means to you personally — is this aligned with your current priorities? Then "why not" — what are the actual barriers, not the imaginary ones? Then "how" — what does success look like, what resources do you need, what's the realistic timeline? Send back a response that reflects that thinking. It will feel awkward. It will also probably change how people treat your time going forward.
Get the Full Details
I track this loosely by keeping a simple log of opportunities I received and how I responded. After about a month, you start seeing patterns. You'll notice which types of requests consistently fall apart under the "how" question. You'll notice which colleagues respond well to the clarification process versus which ones get defensive. That data is more useful than any calendar optimization tool because it's specific to your actual work environment, not a generic theory about time management. One more thing that surprises people: this framework scales poorly into groups. It works well one-on-one because the conversation is contained. The moment you bring it into a meeting with five people who all have different agendas, "how" becomes a negotiation instead of a clarification. I've found that in group settings, the most effective move is to ask the person making the request to walk through the "how" themselves first, publicly, before you commit. It shifts the burden of specificity onto the originator of the ask, which is where it belongs in most cases. If you want to try this, there's nothing to download. The only tool you need is the habit of pausing for thirty seconds before agreeing to anything non-trivial and mentally running through those three questions. Thirty seconds. That's it. Most of the damage in professional life comes from agreements made in the space between someone asking and you saying yes without thinking. Closing that gap is what changes things.
