We turn down roughly two engagements for every one we take.
People hear that and assume arrogance. The opposite is true. Saying no is the most useful thing we do for the clients we keep, and the math behind it applies to your business too.
The backlog trap
Filling a backlog is easy. Ideas are cheap. Your team generates twenty good ones in a single meeting, and every one of them sounds worth doing.
So you do a little of everything. The backlog grows. The team stays busy. And the number you care about barely moves, because effort spread across twenty projects is effort no single project ever gets enough of.
Busy is not the same as progress. A full calendar feels like work. A moved metric is work.
Every yes is a no somewhere else
Here is the part the backlog hides.
Your team has a fixed amount of attention. Every project you say yes to spends some of it. So a yes to a low-value project is a silent no to a high-value one, because the hours went somewhere and cannot go twice.
The cost of a bad yes is invisible. You never see the better project you did not do. You only see the busy team and the flat results, and you assume you need more people or more budget. Usually you need fewer priorities.
The triage is the work
Most people treat prioritizing as the thing you do before the real work starts. We treat prioritizing as the real work.
Figuring out which two or three things will move the number is harder than executing twenty. Execution is mechanical. Triage takes judgment, honesty, and the willingness to kill ideas you like. The studios and teams who win are the ones who do that hard thinking first and protect their attention for what matters.
A simple version you run yourself:
- List every project on the table. All of them, no filter.
- For each, estimate the realistic upside and the effort to get there.
- Find the two or three with the best ratio of return to effort.
- Start those. Schedule a few for later. Kill the rest out loud, so they stop quietly draining attention.
The hard part is the last step. Killing a good idea feels like a loss. Keeping twenty good ideas alive at once is the real loss.
A worked example
Picture ten projects, all sensible.
A new landing page. A paid channel test. A loyalty program. A blog. A rebrand. A referral system. Three feature builds. A partnership.
Run the math. The landing page touches every visitor and converts at half its potential, so fixing it returns fast and large. The paid test has a clear hypothesis and a cap, so the downside is bounded. The other eight are real, but each one returns less per hour, or depends on something not done yet.
You start two. You schedule the paid test results to decide the next move. You tell the team the other eight wait. The business moves faster, because the attention went deep on the things that pay instead of thin across everything.
Why we say no out loud
When a project does not fit, we say so at the start.
Often the work a founder wants is not the work the business needs. They came for a rebrand. The real problem is a checkout leaking revenue. Taking the rebrand would be billable and wrong. So we say no to the rebrand and point at the leak, even when the no costs us the easy invoice.
We would rather be honest at the start than billable at the end. That is the same discipline we apply to your roadmap. Fewer, better decisions, made on purpose, protected from the backlog.
The takeaway
A long list run badly loses to a short list run well. Every time.
If your team is busy and your numbers are flat, the answer is not more projects. The answer is the courage to pick the two or three that matter and say no to the rest. At MZD, that triage is the first thing we do, because the decisions you skip are the ones costing you the most.
