The 9 Slack Statuses Manager OTG Has Used This Month

Manager OTG's Slack status changed eleven times this month. More, if you count the week he was in Austin. The status is a communication mechanism — it is meant to tell his team where he is and whether he can be reached. That is what he thinks it does.

Here is what it does.

1. 🚀 Heads down today

Duration: forty-seven minutes.

His green dot stayed on the entire time. He replied to Priya's 9:17 AM Slack in three minutes. He did not reply to Greg's question about the data pipeline — a question that had been sitting in the thread since Tuesday, about whether to proceed or hold for the quarterly review. The question did not go away on its own. Greg answered it himself on Wednesday morning, documented the decision in a Notion page, and tagged Priya. The page has not been read by Manager OTG. Priya read it within the hour. Dana read it the following week and sent Greg a one-line Slack that said "this is right."

Greg does not have "Heads down" on his Slack status. He does not have a Slack status.

2. ✈️ In transit

Duration: nine hours, Denver to New York via layover.

Fourteen Slacks sent. Six of these were question marks appended to forwarded threads — including one forward of a thread he himself started in October. One message was to Priya asking whether the deck for Thursday's all-hands was "close to done." It was done. It had been done since Monday. He sent this at 6:44 AM from Gate D7.

The layover was in Charlotte. He was in the Admirals Club. His status said "In transit." This was technically correct.

3. 🤔 Thinking through some things

Duration: twenty-six minutes (11:22 PM – 11:48 PM, a Sunday).

He had read a Substack newsletter called "The New Architecture of Distributed Work." He forwarded it to Priya at 11:24 PM with the note: "interesting here — maybe something for the team?" She saw it at 7:51 AM Monday and did not respond. He was asleep by 11:31 PM. His green dot stayed on because he uses a mouse jiggler. Everyone knows.

4. 🎯 Focus Time: Q3 planning

Duration: ninety minutes, a Tuesday.

He made a Notion document called "Q3 — Some Initial Thoughts (WIP)." He added one bullet point: Continued emphasis on cross-functional alignment. He started a second bullet and deleted it. He left the document in a folder called "Strategy 2026 (Active)" — a folder that no one else has opened, in a workspace section no one else has found, in a Notion sidebar that gets longer every quarter and narrower every month.

Priya also had ninety minutes of Focus Time on Tuesday. She built the Q3 roadmap. These are different things.

5. 📍 On-site: customer visit

Duration: two days.

Accurate. He was in Austin, Texas. The customer has been with Lumenwave for three years and will remain so regardless of the visit. Greg wrote the pre-call brief. Manager OTG read the title of the brief. During the visit, the customer asked a technical question. Manager OTG said "let me get our team on that" and sent Sarah a Slack on the flight home that read "quick q for you when you surface." Sarah replied the next morning with a three-paragraph answer. He forwarded it to the customer with the words "team looked into this — see below."

Greg was not mentioned in the forwarded email. Greg is not mentioned in most things.

6. 🔋 Low battery — slow to respond

Duration: four hours, a Thursday.

He responded to Marcus's question about the product roadmap in three minutes (2:17 PM). He did not respond to Sarah's deployment question — which had a hard EOD deadline, which she had sent at 10:41 AM, which she re-sent at 1:58 PM with "just making sure this is visible." Sarah pinged Priya at 3:30 PM. Priya made the call. The deployment shipped on time.

His battery had been at 83% since noon. He charges at his desk.

7. 📆 In back-to-backs

Duration: marked as three hours. Actual meetings: one.

The first meeting, a vendor sync, was canceled at 9:48 AM — eleven minutes before it started. No new meeting was booked in its place. The third block was a calendar hold labeled "INTERNAL SYNC — do not schedule over," with no attendees and no description. It is olive green. Nobody knows what olive green means. He sent an email explaining the calendar color system in January. Olive green was not in it.

He was on LinkedIn for thirty-eight of the ninety free minutes. He posted something about giving your team room to run. It has 34 likes. Four are from direct reports. They felt they had to.

8. 👋 Stepping away for a sec

Duration: one hour and forty-one minutes.

He did not say where. He came back.

9. 🧠 Strategy Mode

Set at 7:14 AM, a Monday. Expired sometime before the 10 AM standup.

This was a new status. He had not used it before. It was not clear whether it signaled unavailability or was meant as ambient communication about the kind of thinking he was doing. Dana saw it from her desk at 7:16 AM and sent Kyle a message: "have you seen his status." Kyle replied: "🙏." Dana did not respond to Kyle.

By 9:30 AM, he had sent nine Slacks. One was a "Thoughts?" forward. Two were meeting requests. One was to Kyle, who had also set his status to Strategy Mode at 7:19 AM.

The strategy was not documented anywhere. There is a Notion document called "Q3 — Some Initial Thoughts (WIP)."

It has one bullet point.