Showing posts from June, 2024

Outcome vs Output

Success is an ambiguous word, with just as many intangibly squishy synonyms like "delivering value," "having an impact," and "great results." And when it comes to celebrating our team's successes, highlighting the value we bring in our annual reviews, writing an impactful resume, or sharing the results of our work, the ambiguity of these terms do us no favors in helping us determine what we should capture. And so we write about the wrong things. To avoid this pitfall, I always remind myself to focus on Outcome and not Output . Output is the work we produce: The emails we send, meetings we schedule, PowerPoints we build, lines of code we write, or things we fixed. Output isn't bad or good. It's just a means to an end (the Outcome). Outcome is what happens because of your output (and sometimes despite it). You may have led 5 projects, managed 50 people, wrote 500 lines of code, fixed 5,000 bugs - and all of those are meaningless ( yes, even fi


Let's Clear Up The Ambiguity!

Work Experience vs Professional Experience

FAQs for a Software Engineering Hiring Manager

7 Steps to Writing an Amazing Resume

7 Steps to Building your Portfolio MVP