Every technology organization will tell you they are high-performing. Here is how I actually find out.
When I step into a new organization there are five signals I look for before I look at anything else. Not the architecture diagrams. Not the project portfolio. Not the metrics deck.
These five things first.
Signal 1: How People Talk About The Last Failure.
I find the most recent significant production incident and ask three people independently what happened. I am not listening for the answer. I am listening for whether people describe a system that failed or a person who failed. Organizations that assign blame have stopped learning. Organizations that diagnose systems are still improving. You cannot see culture clearly once you arrive with an agenda.
Signal 2: Whether Anyone Can Hand Me A Clean Application Inventory.
Not a list. A clean inventory — with owners, business criticality, and age. Most cannot. What I find instead is a number nobody agrees on and dependencies nobody has fully mapped. The size of the portfolio is not the problem. The absence of ownership is. I have never walked into a technology organization with too few applications. The portfolio tells you how many decisions got deferred and for how long.
Signal 3: Where Technology Sits When Business Decisions Get Made.
Not in the org chart. In the room. Are technology leaders present when business strategy is discussed — or do they receive requirements after the decision has been made? The answer tells you whether technology is a strategic function or a service center. The remediation path for each is completely different. Knowing which one you are walking into before you accept a role is not optional.
Signal 4: What The Engineers Are Worried About That Leadership Is Not Saying.
I do skip-level conversations in the first 30 days — not to gather intelligence, but to calibrate the gap between what the organization officially believes and what the people closest to the work actually know. That gap is always present. The size of it tells you how much organizational hearing loss has accumulated. In every significant platform failure I have experienced, someone below the leadership layer knew before leadership did. The signal existed. The path for it to travel did not.
Signal 5: How Long It Takes To Deploy A Change.
Not in theory. In practice. From approved to production. The answer compresses years of architectural decisions, risk culture, and organizational trust into a single number. A high-performing team with a broken deployment pipeline is constrained. A low-performing team with a fast pipeline is dangerous. The number alone does not tell you everything — but it tells you where to look next.
Ninety days is enough time to know what you are actually working with.
Most organizations do not need a new strategy in the first 90 days. They need an honest assessment of the one they are already executing.
What is the signal you look for first?