Earn Context Before You Ship: A Framework for New-Hire Impact

The instinct to prove yourself immediately in a new role can backfire when action outpaces understanding. Drawing on his move from Monzo to Engine by Starling, the author reframes ‘bias toward action’ as a strength only when it’s grounded in context—swinging a sledgehammer before reading the blueprints risks knocking out a load-bearing wall. The core argument: decisiveness and speed aren’t the same as rushing, and premature changes to systems or processes you don’t yet understand are just noise.

The piece lays out three phases. First, a deliberate collection period—mapping stakeholders, running discovery-focused 1:1s, and applying Chesterton’s Fence by investigating why a legacy process exists before criticizing or removing it. Second, a synthesis phase that connects recurring pain points surfaced independently by different people and sorts them into low-risk quick wins versus systemic, long-term problems. Third, strategic acceleration: shipping a small, visible win that makes someone else’s job easier to build political capital, circulating a one-pager hypothesis before any major project, and gradually shifting the working ratio from mostly listening to mostly doing.

The takeaway is a calibration discipline rather than a case for moving slowly. By front-loading context, a new hire ensures that when they do act, they’re pushing on something that genuinely needs it—advice that maps directly onto engineers inheriting unfamiliar codebases, on-call rotations, and legacy infrastructure, where ‘why was this built this way’ is often the most valuable question to answer first.