The highest-impact work often comes from improving systems, not just executing within them. None of my most meaningful improvements started as assigned work.
One thing I've been reflecting on recently is how often inefficiencies become "normal" over time.
A process that takes hours. A tool that doesn't scale. A workflow with built-in bottlenecks. We adapt to them. We work around them. Eventually, we stop noticing them.
But every so often, it's worth stepping back and asking: is there a better way this could work?
Also shared on LinkedIn.
In the past few years, that question led to a few meaningful improvements:
Cutting a 6–10 hour disk copy process down to under an hour. What started as noticing that the existing process was painfully slow turned into a systematic approach to imaging and provisioning that the team now uses as a standard.
Replacing a shared spreadsheet with a database-backed approach. The spreadsheet had a waitlist. People were waiting to update it. That's not a spreadsheet problem — that's a design problem. Recognizing the pattern led to a better solution.
Prototyping a more scalable testing approach using a dev codebase. The existing coverage wasn't keeping pace with system complexity. Instead of just adding more tests to the existing structure, I looked at the architecture and found a better place to start.
What stood out in each case: none of these started as assigned work.
They started as small observations.
Most engineering work is execution — taking a defined problem and building a defined solution. That work matters. It keeps systems running.
But the highest-impact work is usually found one level up: identifying which problems are worth solving, and why the current approach isn't solving them well enough.
That requires permission to notice things. To say "this seems inefficient" without immediately being redirected to the current sprint. To treat observations as the beginning of a conversation, not a complaint.
I've found that engineers who consistently do high-impact work share something in common: they're genuinely curious about the systems they work in, not just the tasks they're assigned.
They ask:
The answers to those questions often point to work that's more valuable than anything on the backlog.
The highest-impact work often comes from improving systems, not just executing within them.
Start with the observation. See where it leads.