Interviews Measure the Wrong Signal
Posted in: ExecutionWe’ve built hiring around asking people how they work—then wonder why we can’t predict performance. For IC roles, the signal is simple: don’t ask. Work with them.
Read more
I’ve spent my career operating across engineering, product, and business—
bringing structure to ambiguity so teams can move with clarity.
Former Microsoft TPM
Led cross-team initiatives in cloud + emerging tech
Known for turning unclear problems into structured execution paths
Examples of where work started to break down—and how it moved forward.
A customer-facing analytics platform was already in production, but ownership, planning, and delivery weren’t aligned. Work was moving, but not in a coordinated way.
Separating experimental and production work, introducing shared visibility, and grounding planning in real data helped stabilize the program while allowing delivery to continue.
Multiple teams were contributing to a shared platform, but dependencies and shifting scope were creating friction and slowing delivery.
Introducing shared planning rhythms, clearer dependency mapping, and better visibility helped teams coordinate work and reduce delivery surprises.
— Program Leader
Writing about how teams, systems, and real work actually function. View All Insights →
We’ve built hiring around asking people how they work—then wonder why we can’t predict performance. For IC roles, the signal is simple: don’t ask. Work with them.
Read more
Some people can't not see the ecosystem. Organizations don't hire for that. They hire for lanes. Here's what gets lost when those people get pushed back into one.
Read more
You're jet lagged. The band is corny. You're reluctantly feeling it. Then five words from a stage quietly divide everything.
Read moreI’m always open to conversations around team structure, decision-making, and execution challenges.
Add your custom CSS code below
Add your custom CSS code below