Career & Leadership › Career Growth
Impact
Outcomes that matter to the business, not just output.
Also known as: engineering impact, making an impact, output vs outcome, business impact, engineering outcomes
Impact is the change you cause that matters to users, the team or the business. It’s different from output, which is how much you produce (lines of code, tickets closed, hours worked). You can have lots of output and little impact, or modest output with great impact.
| Output (activity) | Impact (outcome) |
|---|---|
| “I closed 30 tickets” | “Checkout failures dropped from 2% to 0.3%” |
| “I wrote a new service” | “Customers get their reports in seconds instead of hours” |
| “I answered many questions” | “New hires reach their first PR in 3 days instead of 2 weeks” |
| “I refactored the module” | “Releases in that area no longer break, and changes there take half as long” |
Impact is about results that others can see and care about.
How to increase it
- Pick the right problems. The biggest lever isn’t working harder, but working on things that matter. Understand what the team and company are trying to achieve (product thinking).
- Ask “so what?” Why does this task matter, and who benefits?
- Solve root causes, not symptoms (root cause analysis).
- Finish and ship. Half-done work has no impact. Follow it all the way to users and check the result (ownership).
- Multiply others. Reviews, mentoring, docs, tooling and removing blockers raise a whole team’s output. This “glue work” counts, though it’s easy to overlook (glue work).
- Reduce toil and risk: automating a painful process or preventing an outage is impact.
- Measure. Define what success looks like before you start, and check afterwards.
- Say no to low-value work (saying no, prioritization).
Making it visible
Good work that nobody knows about doesn’t help your career or the team’s priorities. Record what you did, why it mattered and the result, with numbers where you can (brag document). Share outcomes in updates and reviews (status updates). This isn’t bragging. It’s helping others understand value, and it’s what promotion and performance discussions look at (performance review, promotion).
Impact grows with level
At junior level, impact is reliable delivery of well-scoped tasks. At mid-level, it’s owning features end to end. At senior and beyond, it’s shaping direction, improving how teams work and making others more effective (scope of work).
Don’t confuse impact with visibility or heroics. Quiet prevention often beats dramatic rescue.