Strongly Held Beliefs
These are a few strongly held beliefs that guide how I work.
Organizations are information-sharing architectures
An organization is fundamentally an information-sharing architecture, and its culture is the protocol by which information moves: what can be said, who is believed, what gets amplified, and how quickly the group corrects itself.
Many problems that appear to be failures of talent or execution are actually failures of consistency. Smart, well-intentioned people can each act rationally and still produce an irrational outcome when they are working from different versions of reality.
This is why transparency alone is insufficient. An organization needs mechanisms that turn fragmented observations into a shared, trusted understanding of reality. The strongest organizations are not those where everyone agrees; they are those where disagreement is grounded in the same evidence and the collective model updates quickly.
How an organization communicates does not merely support its culture and its work; it creates both.
Find pain, not flaws
A request is evidence of a problem, not a build specification. Look for the underlying pain, the recurring pattern, and the outcome people are actually trying to reach.
Build to learn, then cut to clarify
A prototype tests an idea; it is not a commitment to the final system. Software often expands while you learn, then contracts as you remove what no longer earns its place.
Spend complexity where it matters
Pragmatism is not choosing the least sophisticated tool. It is resisting the urge to rebuild what already works, and writing custom logic only where it creates real leverage.
A manager’s job is to reduce chaos
Good management creates clarity: what matters, what can wait, who owns what, and how the team makes decisions. The goal is to make it easier for people to do good work.
Follow the signal
Cut through requests, requirements, and noise to find the recurring pain. Focus on the work where solving it creates the most leverage.