No – The hardest yes in leadership often starts with a no 🦉 Because no today means strength tomorrow.
- Carey-Jo Hoffman
- Sep 19
- 2 min read

One of the most interesting challenges of leadership is living at the fine edge between opportunity and focus.
This week I found myself writing letters of gratitude—thank you, no—to international companies, trade organizations, and accelerators who see global potential in PrimeHealth. Their excitement is energizing—and it’s tempting to say yes to everything. But sometimes the wiser choice is no.
At the same time, we’re deeply engaged with Fraser Health Authority and the BC Nurses’ Union—two of the most respected institutions in British Columbia. Their partnership has been paramount in our product development. They’ve been more than early adopters—they’ve been articulate participants and thoughtful contributors, helping us build something real, proven, and practical. That’s a yes worth protecting.
And there are plenty of potential partners in the funnel who fit within the well-considered criteria PrimeHealth has created right now. That’s our scope. And as always, Rob is designing a highly configurable, modular product—one that will expand well beyond our current focus with ease, at the right time.
So the dialogue becomes: chase the wide horizon, or deepen the ground under our feet? The truth is, both matter. But timing matters even more. Saying no now allows us to say yes later. Nope to distraction, yes to density. Because density builds intensity, and what we make strong here can later scale outward with confidence.
I’m learning that leadership isn’t always about the next best thing—it’s often about the current right thing. Saying no isn’t easy, but it keeps us in conversation with what’s essential now, so we can say yes to more—later.
A special thank you to Kerry Brock , whose guidance helps us stay between the lines with clarity and courage.
How do you navigate this tension in your own work? When have you chosen depth over breadth—or said no in order to say a bigger yes later on?



Comments