The Do-Not list is the most-praised, least-implemented artifact in strategic planning. Everyone nods. Almost nobody ships one that survives the quarter.
Why most Do-Not lists die
Three failure modes account for almost every collapse:
- It's a vibe, not a register. "We're not going to chase enterprise this quarter" is a feeling. "We are not building SOC 2 controls, hiring enterprise AEs, or accepting RFPs over $250K through September 30" is a register.
- It has no owner. A Do list has owners. A Do-Not list rarely does. The fix is symmetric: every entry on the Do-Not list has the name of the person empowered to say no on behalf of the company.
- It isn't visible at the point of decision. A Do-Not list filed in a planning doc is invisible at the moment someone in a Slack thread says "let's just take that one call."
The format that survives
A working Do-Not list has five columns: what, why, until when, who can say no, what would change this. That last column matters most. A Do-Not list without a re-entry condition turns into dogma, and dogma loses to a good-sounding opportunity every time.
Example row:
- What: We are not pursuing healthcare verticals.
- Why: Sales cycle and compliance cost don't fit our current bandwidth.
- Until when: End of Q3.
- Who can say no: VP Sales.
- What would change this: Inbound from three named accounts, or HIPAA roadmap funded.
Where it lives
In the same system as the Do list. Not in a separate doc. If your strategic priorities live in one tool and your "explicitly not doing" lives in another, the second one will quietly disappear by week four — because nothing in the workflow references it at the moment of choice.
The Vindaris take
A strategy that only describes what you're doing is half a strategy. The other half is the list of things you are deliberately not funding this quarter, with names and dates. Without both, "focus" is a sentiment, not an operating decision.