output vs presence work

Over time, I’ve come to realize that roles in tech generally fall into two broad categories: output-based work and presence-based work. Though some roles can be a high mix of both.

They require different skill sets, different types of energy, and offer different kinds of fulfillment. Neither is better than the other but it’s important to understand the difference so you can choose a role that aligns with how you work best in your stage of your career.

Output based work

This is the “build it and ship it” zone.

Think shipping features, writing white papers, sales enablement slide decks, or creating polished excel or notion documents. Your work is based on your deliverables.

Output-based work runs on uninterrupted focus. If your calendar’s packed with meetings, your ability to deliver real results might suffer due to too much context switching. Figure out ways to protect your calendar so you can produce the expected output such as blocking off deep work hours daily or designating a “Focus Wednesday”.

Presence based work

Now, presence work is still work. It’s about showing and connecting internally and externally.

Think speaking at conferences, running customer trainings, hoping on calls with users, constant cross-functional work, or hosting livestreams/webinars.

Presence-based work runs on energy, not just time. To stay sharp and sustainable, treat recovery like part of the job. Build in buffer blocks after high-energy events, protect no-call hours during heavy collaboration weeks, and plan PTO proactively.