Slack for operations managers on Mac: a practical setup for 2026 with Lazur

Most operations managers use Slack for the same few jobs. They chase status, they route requests, they track open work, and they answer the same questions again. Slack has a feature for each job. Most of them already sit in your workspace. The trick is to use the right one for each job, instead of posting everything into one busy channel.

Set up the Mac app before you build anything

Start with the Mac desktop app, not a browser tab. Slack's keyboard shortcut page says ⌘J, the jump to the latest unread message, works only in the desktop app. Slack's Mac release notes list 4.53.280, dated Nov 3, 2026, as a security update. That is the newest build I could confirm with a date before today, so keep your app at or above it.

Next, sort out your notifications. An operations manager with every channel set to notify gets very little real work done. Open your preferences from the profile menu and decide which channels should ping you. Mute the chatter channels. The guides on pausing notifications and fixing missing notifications walk through the steps.

Then give each kind of work a home. Create one channel for requests and one for the daily standup, for example. Public channels let the whole team see the work. Private channels limit who can read it. The guide on creating a channel in Slack covers both steps.

Use Workflow Builder for standups and status updates

Workflow Builder handles the questions you ask every day or every week. Slack's blog lists five templates. They include a status update form, an editable request approval workflow for expenses or travel, a daily break reminder, a daily standup reminder posted to a channel, and a feedback form triggered by an emoji reaction. For operations, the standup reminder and the status form do most of the work.

Finding them is simple once you know the spot. Slack's blog says a channel's custom workflows sit in the channel's shortcuts menu. Look for the lightning bolt at the bottom left of the message box. Click it, and the workflows for that channel appear.

1. Open the channel your team reads every morning, such as #ops.
2. Click the lightning bolt at the bottom left of the message box.
3. Pick the daily standup reminder template, or start a workflow from scratch.
4. Set the time and the channel, then test it with one teammate first.
5. Read the first week of replies before you change the questions.

Slack's help article says Full Members can create workflows by default. Members and guests can use them. If a guest fills in a form, make sure the form lives in a channel that guest can reach, and test it from their side before the first send.

Track requests and open work with Lists

Lists are Slack's tracker. Slack Help describes three common uses: managing a project, triaging requests, and planning team priorities. For an operations manager, triage is usually the use that replaces the shared spreadsheet nobody updates. Messages can be sorted into a list for review, so requests are less likely to get lost in threads.

Know the limits before you rely on a list. Lists hold up to 1,000 items and subtasks on Pro and Business+. Enterprise Grid allows up to 5,000. At the limit, the oldest items are archived automatically. Close finished items on a schedule, so the list keeps the open work and nothing you still need gets archived.

Access is tight by default. Slack Help says lists are visible only to people or channels they are shared with. General access defaults to Only invited people can access. Share the list with the channel that owns the work, not the whole workspace.

• Name it after the work, such as Vendor requests or Facilities tickets.
• Add a field for the owner and another for the due date.
• Share it with the channel that owns the work.
• Triage new items every morning, before your first meeting.
• Set a reminder on any item that goes past due.

Frontline Members can't create lists. If floor staff need to add requests, send them a form or a workflow instead. Then triage the answers into a list yourself.

Cut search time with Mac keyboard shortcuts

Search eats more time than most managers expect. ⌘G starts a search. ⌘F finds text inside the conversation you have open. ⌘⇧A opens All unreads. ⌘J jumps to the most recent unread, in the desktop app only. ⌥⇧↑ and ⌥⇧↓ move between unread channels or direct messages.

Slack's keyboard shortcut page does not list a Mac shortcut for switching conversations. Its only switcher shortcut is Ctrl+K on Windows and Linux. On a Mac, use ⌘G to find a channel or person, then open the result.

• ⌘G: start a search across Slack.
• ⌘F: search inside the open conversation.
• ⌘⇧A: open All unreads.
• ⌘J: jump to the latest unread, desktop app only.
• ⌥⇧↑ or ⌥⇧↓: move between unread channels or direct messages.
• A on a focused message saves or unsaves it. M creates a reminder.

For the full steps, read the guides on jumping to a conversation and searching messages. Use the list above as a cheat sheet. Tape it near your monitor if your desk has room.

Manage unread messages without losing track

Unreads pile up fast after a day of meetings. Open All unreads with ⌘⇧A, and work from the top. Mark a message as unread when it needs a decision later, so it stays on your list. The guide on marking a message as unread shows the steps.

Mark all as read is a blunt tool. It clears every channel, including the ones you never checked. Use it after you have read the channels that matter, not before. The guide on marking all messages as read explains the Unreads view.

Threads keep side talk out of the channel. Reply in a thread, so the channel stays readable for the rest of the team. Check the Threads view in the afternoon for replies you missed. The Threads view guide covers the steps.

Plan around Free and paid plan limits

Slack Free keeps message history saved and searchable for 90 days. It also allows up to 10 apps. Pro, Business+ and Enterprise+ list unlimited message history and unlimited app integrations. If you need last quarter's vendor thread, check whether it falls inside that 90 day window.

Prices are on Slack's pricing page. Pro is $8.75 per user per month billed monthly, or $7.25 billed annually. Business+ is $18 monthly or $15 annually. Enterprise+ is $45 per user per month billed annually, with contact sales. Check their pricing page before you budget, since plans change.

Mistakes operations managers make in Slack

• Posting daily status into the main channel. Use a form or a standup workflow, so answers stay in one place.
• Setting every channel to notify. The urgent messages get lost in the noise.
• Tracking requests in direct messages. Nobody else sees the status, and the work gets lost.
• Letting a list grow to the limit. At 1,000 items, the oldest items are archived.
• Assuming the Free plan includes workflows. Check the plan first.
• Clearing unreads without reading them. Mark all as read hides what you never checked.

What the research says about search time and interruptions

Estimates for search time vary a lot. Evy reviews five studies, and their figures run from about 5 to 15 hours a week. McKinsey's 2012 estimate puts search at 19% of the week. Atlassian's 2025 figure is 25%. Evy says all five figures are self-reported. It also says three of the five creators sell search or work-hub software.

Slack's own blog cites its Workforce Index from June 2024. It says desk workers spend a third of their time on low-value tasks, such as searching for information and sorting paperwork. That figure comes from Slack, so treat it as a claim worth checking, not a measurement.

Interruptions have a cost too. A summary of a 2008 CHI paper says people worked faster after an interruption, with more errors and more stress. It gives 23 minutes as the average time to resume a task. I did not open the paper itself, and that figure is disputed. Use it as a reason to batch your Slack checks, not as a number to quote.

Where Lazur fits in your Slack day

Lazur is a voice assistant for the Mac. Hold Option and Command, then ask about anything on screen. It answers out loud. In Slack, you might ask where the workflows live, or how to set a reminder. Lazur draws a circle and a label around the right control.

When you ask how to do something, Lazur guides you one click at a time. It waits for each click. It does not click for you. You stay in control of every send and every change to a channel or a list.

Dictation also fits this job. Hold fn to dictate a status note straight into the message box, in any app. Read the text before you send it. Dictated names and numbers need a quick check.

Lazur is not a plugin or add-in for Slack or any other app. It sees your screen only while you hold the shortcut. Plans and the trial are on pricing.

A week of Slack habits for an operations manager

1. Monday: check that the standup workflow posts at the right time.
2. Each morning: open All unreads with ⌘⇧A, then triage the request list.
3. Midday: search with ⌘G for anything you were promised.
4. Afternoon: check the Threads view for replies you missed.
5. Friday: close finished list items and read the week's form answers.

Keep the habit small. Short, scheduled checks beat a constant feed. Batch them, and leave notifications on only for the few channels that need speed. Your team will notice the difference in how fast you answer, even if they never see your settings.

Edge cases to plan for

Guests and outside vendors need extra care. Lists are visible only to people or channels they are shared with. Before you share a list with an outside vendor, check exactly who it is shared with. Then send them the one list they need.

Workflows need a plan that supports them. Check the plan on every workspace your team uses, including side workspaces for vendor work. A workflow that works in one workspace can be missing in another.