Slack for product managers on Mac in 2026: setup, shortcuts and Lazur help

What product managers do in Slack every day

Slack has no product manager mode. Most product managers use it for five jobs. Each job has its own failure, so each one needs a small fix.

• Engineering threads: scope, bugs and trade-offs, often in busy channels.
• Customer feedback: forwarded requests, call notes and quotes from sales.
• Status updates: short notes for leads, partners and executives.
• Decisions: what was chosen, who agreed and why it was chosen.
• Launch tracking: owners, due dates and what is still open.

Feedback gets buried in busy channels. Decisions disappear into long threads. Status updates go out late because nobody can find the facts. Small settings and a few habits fix most of this. You do not need a new tool.

Slack has not published data on product managers as a group. The steps on this page come from Slack's own project template and feature pages, plus common complaints in public reviews. Where a number is a review count and not a measurement, this page says so.

Set notifications before anything else

Notifications draw more complaints than any other part of Slack in the reviews we checked. G2 counts 1,137 review mentions of notification issues, the highest count on its Slack pros and cons list. Those are review mentions, not a survey. Reviewers keep returning to the same problem: too many pings and too little signal.

Mute the channels you only skim

Mute a channel when you read it once or twice a week. Keep mentions and direct messages on. Mentions are the signal that a person needs you right now. Read muted channels at set times, such as the start of your day. The step-by-step version is in our guide on muting a channel in Slack on Mac.

1. Review the channels you joined last month. Mute every channel you read less than once a week.
2. Keep mentions and direct messages on, so urgent items still reach you.
3. Pause alerts for one focus block a day. The profile menu steps are in how to pause notifications in Slack on Mac.
4. Check your Mac too. Alerts can stop at the operating system level, so read the callout below.
5. If alerts still fail after that, follow the fix guide for missing notifications.

Find past decisions without scrolling

Search is where product managers lose time. Slack Engineering says that on average 20% of a knowledge worker's day goes to finding the information needed to do work. That figure comes from a 2017 post that cites McKinsey. Treat it as a rough guide, not a fresh measurement.

Search works best when you search for the decision, not the topic. A decision usually uses words like decided, final, go with or cut. Pair one of those words with the feature name. Then jump to the channel with ⌘K and search inside it. For the steps, see how to search messages in Slack on Mac and how to search inside a conversation.

Worked example: find a decision from last quarter

Say you need to know why an export feature was cut from the March release. Press ⌘K and type the channel name. Then search for the feature name alone. If you get too many hits, add a decision word such as cut or final.

When a hit points to a thread, open it and read the last few replies first. The final call often sits near the end. Copy that line into the project canvas with the date and the name of the person who made the call. Messages are what the 90-day rule limits, so a line in a canvas keeps the decision in front of the team.

Know how far back Slack search reaches

History limits decide what you can find later. On the Free plan, messages are searchable for 90 days. Upgrading to a paid plan gives access to the previous 12 months. A decision from last spring may be out of search reach on Free.

These limits change how you record decisions. A decision that matters should live in a list row or a canvas, not only in a thread. Old threads are the first thing to go missing. Copy the final decision into the project canvas on the day it is made. That way the record survives the 90-day window on Free.

Use the project template for each launch

Slack's Project starter kit template creates a project channel for you. It sets up an overview canvas with a description, goals, team and key resources. It also adds an embedded task tracker and two workflows. Use it when a launch needs one place for context and tasks.

• An overview canvas with the description, goals, team and key resources.
• A task tracker list that starts with three placeholder tasks, each with Task and Description fields.
• A status change alert workflow that posts to the channel when tasks change.
• A new-member welcome workflow. Both workflows can be edited from the Workflows tab.

Replace the three placeholder tasks on day one. By default, all channel members can add, update and remove items in the tracker. That suits a small launch team. It gets messy when guests or new joiners start editing rows. Decide who owns the tracker before you invite anyone else.

Track owners and due dates in Lists

Slack Lists lets you create, track and manage projects without leaving Slack. You can keep track of deliverables, assign owners and watch due dates. Slack says workflows work inside lists, and a list can sit inside a canvas. The canvas holds the plan. The list holds the rows.

Slack's Lists FAQ says Lists is included in all paid plans. Lists can be shared with external partners, customers and clients. Slack's Lists page does not describe list views, custom fields or edit permissions. Test those in the app before you promise a workflow to a team.

Keyboard shortcuts worth learning on Mac

Slack's keyboard article lists a short set of shortcuts. Start with two. ⌘K jumps to a channel or person by name. ⌘/ opens the full shortcut list, so you can check what your version supports. Open that list once a month, because the app changes and the list is the reference.

• ⌘K: jump to a channel or person by name.
• ⌘/: open Slack's list of keyboard shortcuts.
• Hold ⌥ ⌘: ask Lazur about anything on screen. Lazur answers out loud.
• Hold fn: dictate clean text at the cursor in any app.

Slack's article lists no shortcut for workspace search, Lists, Canvas or huddles. Third-party guides disagree about a search shortcut. Test any shortcut you read somewhere else with ⌘/ before you rely on it. A few shortcuts you use daily beat a long list you forget.

Where Lazur fits in a Slack day

Lazur is a voice assistant for the Mac. It lives in the notch. Hold ⌥ ⌘ and ask. Lazur sees your screen, points at things, answers out loud and helps you get the work done in any app. It is not a plugin or add-in for Slack or any other app.

Lazur does not click buttons or operate Slack for you. It guides you one click at a time and waits for each click. It points at things when you ask where they are. It can draft text, but you read it and post it. Lazur only sees what is on your screen while you hold the shortcut.

Ask Lazur to point, explain or guide you

Use point when you cannot find something. Ask where the task list is, and Lazur draws a circle and a label around it. Use explain when you need to understand a thread. Use guide when you know the goal but not the clicks. Lazur answers out loud, so you can keep your eyes on the thread.

Pick the request that matches the moment. If you ask how to do a thing, you get steps. If you ask where a thing is, you get a label. If you ask what a thread means, you get an answer. Lazur sees what you see, so describe the goal in plain words.

Draft status updates and dictate replies

Status updates are one of the most repeated writing tasks for product managers. Hold ⌥ ⌘ and ask Lazur to draft a short update from the thread on your screen. Read it before you post. Lazur only knows what is on screen, so add the facts it cannot see.

For a reply you already have in your head, hold fn and speak. Dictation types clean, formatted text at the cursor. Use snippets for lines you repeat, a personal dictionary for product names, and clipboard slots for links you reuse.

Mistakes product managers make in Slack

• Leaving default alerts on. The Siit review says default settings generate more alerts than most people can process.
• Keeping decisions only in threads. Copy the final call into the canvas or a list row.
• Tracking tasks in chat. A task in a message has no owner or due date. A list row has both.
• Searching by topic. Search for the decision word plus the feature name instead.
• Forgetting the Free plan window. Messages older than 90 days may be out of search reach.
• Sharing a list with outside people before testing edit rights. Test with one guest first.

Most of these mistakes cost a few minutes a day. They add up over a quarter. Fix the alerts first, because noisy alerts make every other problem harder to see.

Edge cases for large workspaces and guests

Large workspaces can feel slower. The Siit review says search in very large workspaces is slower than the marketing suggests. It also reports heavy desktop memory use and slow channel switching. The review gives no measurements, so treat it as a warning, not a benchmark. If search lags, search inside the channel first.

Guests need more thought. Check which channel holds the list before you invite a partner or client. Public and private channels behave differently. The steps are in how to create a channel in Slack on Mac. Pick the channel type first, then add people.

Which Slack version this page covers

Slack's Mac release notes list build 4.53.280, dated 3 November 2026, as the newest build dated on or before 7 November 2026. The three latest Mac release notes list no changes to menus, navigation, Lists, Canvas or Workflows. A later build appears with a date after today, so this page does not rely on it. Recheck the release notes if a step looks different on your Mac.

A one-week Slack setup for product managers

1. Day 1: set notifications for each channel. Mute the channels you read less than weekly.
2. Day 2: pause alerts for one focus block. Use the pause guide for the steps.
3. Day 3: open or create the project channel. Add the overview canvas and the task list.
4. Day 4: replace the three placeholder tasks with real owners and due dates.
5. Day 5: check the status alert workflow posts to the right channel. Post one test update.
6. Day 6: copy the decisions from the last month into the canvas or a list row.
7. Day 7: hold ⌥ ⌘ and ask Lazur to explain the thread you are reading. Note what it gets right.

The setup is quick. The habit takes longer. Read the decisions channel every morning, and keep the rest for set times. Review your alerts once a month, because channels change as the launch moves.

Next steps

If you want the wider picture, read Lazur for product managers. Ready to try it on your Mac? See download Lazur. Pricing details are on the pricing page.

Start with one change today. Mute one noisy channel and set one decision habit. Add the rest across the week, and keep a short note of what breaks.