Saying "No" to Get to a Better "Yes"

Years ago a German colleague of mine said something that stuck with me: the English are masters at saying "no" and making it sound like "yes."  While it was a lighthearted observation, the point is a powerful one. Saying "no" for the right reasons can be a crucial step toward a much better "yes."

This "better yes" might mean lower costs, more efficiency or a more robust product. We’ve compiled our top five reasons to say "no" and what we say "yes" to instead.

1. Say "No" to Solutions, "Yes" to Problems  

It's a familiar scene: an issue is found and a solution is immediately proposed.  For example, a user error is corrupting data so the solution is to add a pop-up warning.

While this may seem like a quick fix, it often just masks the real problem and can even create new ones.  We would instead say "yes" to understanding the core issue first. Why is the data being corrupted?  Can the process be improved to not rely on a user action?  By asking these questions you can define a solution that actually fixes the problem making your product stronger.

2. Say "No" to Flaky Code, "Yes" to Fixing It

No one likes flaky code. It increases risk and makes testing a nightmare.  Teams often feel pressure to deliver new features but ignoring flaky code is just storing up trouble for the future.

We say "yes" to acknowledging the issue and making a plan to fix it. The severity and frequency of the problem should determine the priority.  While it might mean a slightly delayed delivery of new features, building a robust and reliable codebase will pay off for years to come.

3. Say "No" to Continuing a Bad Decision, "Yes" to Pivoting

Sometimes a decision that was great at the time is no longer the right one, whether due to new technology or market changes.  It can be hard to walk away from a lot of time and money already spent but this is a classic case of sunk cost fallacy.

The best approach is to say "yes" to focusing on future value.  Acknowledge the costs you've incurred then provide a new path that builds on what's already been done. This shift will ensure the final product is fit for purpose and will ultimately save time and money.

4. Say "No" to Change for Change's Sake, "Yes" to Strategic Priorities  

Change is great when it's for the right reason, such as fixing an outdated system or meeting new security requirements.  But making a change just because you can is expensive, time-consuming and can introduce more risk.

Instead of saying "yes" to every proposed change, we recommend saying "yes" to a thorough review.  Evaluate all proposed changes based on the value they'll bring, the risk involved and the estimated return on investment.  This will help you prioritise changes that will have the highest impact for your users and your business.

5. Say "No" to Ineffective Meetings, "Yes" to Productivity

We all know the feeling of dreading a meeting. Too many people, no agenda, and no clear actions - it’s a waste of time and money.

Our advice is to say "yes" to better meetings.  The most productive meetings are smaller and have a focused invite list with the right people to make decisions.  They have a clear agenda and they always end with notes and defined actions, ensuring things actually move forward.

Ready to move from "no" to a better "yes"? Let's chat. Contact Next Phase Consultancy to start a conversation about your business goals.