About
My decade-plus in healthcare has been anything but linear; recently working as a director level leader leading transformational projects in an academic health centre and occasionally as a fraction VP in the biotech sector.
The work has been varied. Developing new clinical programs designed to shift how care gets delivered, stepping into crisis mode (COVID-19) to support institutional response, building inter-institutional partnerships across jurisdictions, and leading culture shifts and large-scale investments to usher in precision medicine.
Every project no matter how ambitious or technically sound taught me the same hard lesson ... the initial vision or idea is rarely what makes a project/ program succeed or fail. I've been part of teams that took rough concepts and built them into something with meaningful impact. I've also seen brilliant ideas dissolve when teams couldn't figure out how to actually work together, make decisions, or sustain effort through the inevitable chaos of transformation.
Based on my observations the defining factor of success is the culture and operating rhythm of the team NOT the vision or idea that caused its creation. Culture and operating rhythms drive how decisions get made when nobody is watching. It's what happens when conflict surfaces. It determines if people bring their whole selves to the work or hold back. It defines whether the team moves toward clarity or away from it. They drive the thousand small choices made daily that compound into either momentum or inertia.
The other insight that changed how I see this work is that culture and operating rhythm can be shaped by anyone on the team. You don’t need to be in a leadership position to make impact.
Some of my most impactful moments came from people without formal authority who refused to accept dysfunction. They asked the right questions in the moment. They named what was not working when it would have been easier to let it slide. They found ways to move things forward without waiting for permission. They made their team better, and that rippled outwards.
Whether you are designing systems, leading transformation, running a program, or contributing as an individual, the skills that matter are the same: seeing what is broken, thinking clearly about what is possible, and finding ways to help your team operate in a way that matches the complexity of what you are actually trying to build together.
Signalvs is where I'm thinking through these patterns. It’s a space to crystallize observations for my own future reference and to share what I'm learning.
I don’t write about academic theories (though I will cite the occasional paper) nor case studies dressed up as wisdom. Just observations from building in real environments where the stakes matter and the constraints are real.
If you are in the middle of building something ... a team, a program, a transformation and are trying to figure out why the team is stuck, there might be something useful here. My hope is that these ideas help you see your own work differently and give you permission to shape the operating system around you, regardless of your position in the hierarchy.