What to do with downtime at the office (without looking checked out)

Downtime happens. Early in a job, it can feel scary because you don’t want anyone to think you’re lazy — especially if you’re still building credibility.

The framing that helps:

Downtime is not a guilt moment. It’s a reputation moment.

Your manager can’t read your workload. They can only see your signals.

The situation most people handle poorly

You’ve got a 30–60 minute gap. Not enough to start something big. Too much to just stare at your inbox.

This is where people accidentally send the wrong signal — not because they’re lazy, but because they don’t have a playbook. Downtime is when you either look checked out, or you quietly build credibility.

The “you look like a pro” list

High-signal activities that don’t require permission:

• read industry news relevant to your team
• clean up your notes and turn them into a one-pager
• organize your workspace and docs so you can find things fast
• prepare for upcoming meetings (agenda + questions)
• fix a small recurring friction point (template, checklist, automation)
• take a short walk or reset — yes, this counts

A good test: would I be comfortable if my manager walked by right now?

The “reads as checked out” list

Even if you could do these, avoid them in visible contexts — office, open Zoom, shared spaces:

• endless social media scrolling
• online shopping
• watching shows
• gaming
• loud personal calls at your desk

People don’t know your workload. They only see your behavior.

The downtime decision tree

When you have 15–60 minutes free, run this.

1. Are you blocked on something? Write the question you need answered. Include context plus your attempted solution. Ask the smallest possible version.

“I’m blocked on ___. I tried ___. I think the right next step is A, but I’m not sure. Can you confirm A vs. B?”

2. Is there a meeting coming up? Skim the doc. Write one or two questions. Decide what “a good outcome” is. Meeting prep is invisible until it isn’t. People can tell when you’re unprepared.

3. Can you create a reusable asset?

• a checklist (what you do every time)
• a template (status update, meeting recap, briefing doc)
• a quick FAQ (acronyms, “who owns what,” common links)
• a short SOP (how to do X here)

One asset per week makes you dramatically more useful.

4. Can you learn one tool that removes future pain? Pick something directly tied to your job — spreadsheets, Jira, Salesforce, Looker, Notion. Not “random learning.” Removing future friction.

5. If you’re regularly idle: ask for more work. Once.

“I have a bit of capacity this week. Is there a small task I can pick up to help the team?”

Two rules: ask once, not every hour. Offer something specific: “I can document X.” / “I can QA Y.”

Don’t become a volunteer doormat

Being helpful is good. Becoming the person who absorbs everyone’s leftovers is not. Three guardrails:

1. Ask permission before taking someone else’s work.
2. Timebox: “I can spend 30 minutes on this today.”
3. Close the loop: send a recap when you’re done.

How to communicate capacity

If you’re blocked or genuinely light, don’t sit there hoping someone notices:

“Quick update: I’m waiting on ___ to proceed with ___. While I wait, I can either (A) document ___ or (B) help QA ___. Which would be more useful?”

That message does three things at once: proves you’re not idle by default, gives your manager easy options, and prevents the “why didn’t you tell me?” conversation later.

—

The first-year version of me thought looking busy was the same as being valuable. It isn’t. The seniors who watched me hardest weren’t tracking whether I was idle — they were tracking whether the things that came out of my downtime were useful when I had more of it. The reusable assets you build during your slow weeks are what get you trusted with bigger work in your busy ones.

For the simplest reusable asset that works in almost any role, use the Status update template.