# Slack for agile coaches on Mac: a 2026 setup for stand-ups, sprints and retros

> Set up Slack on Mac for agile coaching: channels per ceremony, threads, Canvas retro boards, Workflow Builder check-ins and Lazur help in the app.

URL: https://www.lazur.app/for/agile-coaches/slack
Updated: 2026-11-08

Slack for agile coaches on Mac works best with one channel per ceremony, threads for the discussion, and a few Canvas and Workflow Builder pieces for the repeated work. This guide covers the channel layout, the menu paths in the current Mac app, and the places where Lazur helps while you work.

## Quick answer

- Give each ceremony its own channel, such as #daily-standups and #retrospective-feedback.
- Keep stand-up and retro talk in threads so the main channel stays readable.
- Build the daily check-in with Workflow Builder at Agents & tools > Workflows > New > Build Workflow.
- Copy action items into a List, which holds up to 1,000 items on Pro, and set an owner on every row.
- Lazur points at the right control, guides you one click at a time, and drafts or dictates text. It does not click for you.

## What agile coaches do in Slack every week

Most agile coaches use Slack for the same few jobs. You run stand-ups, sprint planning, sprint reviews, retrospectives, backlog work and release planning. Slack's agile guide lists those same ceremonies as the work it supports. Each one needs a place to post, a place to talk and a place to keep notes.

The trouble is that these jobs collide. Stand-up notes end up under a review thread. Retro ideas get lost in a direct message. Action items never get written down where you can find them again. Slack's agile guide names the same pain points: fragmented communication, context switching and the admin of tracking action items.

![Agile coach working on a Mac laptop during a stand-up call with a team, for Slack for agile coaches on Mac](https://images.lazur.app/content-images/role-app/agile-coaches-slack/slack-for-agile-coaches-on-mac-1-ff1f2c.jpg)

## Set up one channel per ceremony

Give each ceremony its own channel. Slack's agile guide recommends separate channels for projects, sprints, features and ceremonies, with names like #daily-standups and #retrospective-feedback. Keep names short and plain. Your team should be able to find any channel with ⌘K in a moment.

| Channel | What it holds | Who posts | When to archive |
| --- | --- | --- | --- |
| #daily-standups | Check-in threads, one per day | Each team member | Keep open for the life of the team |
| #sprint-goal | The sprint goal and progress notes | Product owner and coach | Archive at sprint end |
| #sprint-review | Demo notes and stakeholder feedback | Team and stakeholders | Archive after the review |
| #retrospective-feedback | Retro ideas and the action list | Whole team | Archive once action items close |
| #backlog-grooming | Questions on upcoming stories | Product owner and developers | Keep open |
| #release-planning | Milestones and release notes | Release lead | Archive after release |

_A starter channel layout for one team. Adjust the names to match your team's words._

Start with a few channels. Add a new one only when a ceremony keeps spilling into another channel. Archive a channel when its ceremony ends, and ask the team first. Someone may still read it every day.

## Use threads to keep stand-ups readable

A thread is a reply chain under one message. Post the daily check-in as a top-level message at the same time each morning. Ask people to answer inside its thread. The channel then shows one line per day, not a long scroll of replies.

Threads also cut noise in retros. Start a thread on each idea and let the discussion happen there. Post the final action item back in the main channel so everyone sees it. Slack's agile guide makes the same point about threads and channel noise.

To reply, hover over a message and choose the reply option. For a new line inside a reply, press ⇧ Return. For a full walkthrough, read [how to reply in a thread in Slack](https://www.lazur.app/how-to/reply-in-a-thread-in-slack).

## Run daily check-ins with Workflow Builder

Workflow Builder can prompt the team for daily updates at a set time. Slack's agile guide recommends it for that job. It can also collect retro feedback through forms posted to a channel or canvas. Here is the route in Slack's current desktop help.

1. Click Agents & tools in the sidebar.
2. Go to Workflows > New > Build Workflow.
3. Pick the trigger On a schedule. Other triggers include from a link, from a webhook, when a message is posted and when a list item is updated.
4. Add a step that posts a message to #daily-standups. Ask what the person finished, what they will start next and what blocks them.
5. Test the workflow in a private channel before you turn it on for the team.

Anyone on a paid plan, except Frontline Members, can build workflows by default. Owners or admins can restrict that. If the sidebar item is missing, look under the Tools tab and choose More. Older guides describe a Tools menu under the workspace name. Those guides predate the change.

Review the schedule each sprint. A check-in that keeps firing while people are out sick or on holiday asks for updates nobody can give. Turn it off for those weeks, then turn it back on when the team returns.

## Build a retro board in Canvas

Slack recommends a Canvas retro board with three columns. Use the headings What went well, What could be improved and Action items. Create the canvas in your retro channel, paste the three headings and let the team add their points under each one.

Close the board after each retro. An old board turns into a pile of notes that nobody reads. Copy the action items into a List, where each item gets an owner and a due date.

![Agile team looking at a sprint board, the planning work that Slack for agile coaches on Mac helps organize](https://images.lazur.app/content-images/role-app/agile-coaches-slack/slack-for-agile-coaches-on-mac-2-68e22d.jpg)

## Track action items in Slack Lists

Lists work like a small table. The default fields are Completion, Name, Assignee and Due date. On desktop, open Files > Lists > See all to browse templates. Put one action item on each row, and fill in Assignee on every row before the retro ends.

Lists have a size limit. Pro and Business+ lists hold up to 1,000 items and subtasks. Enterprise Grid holds up to 5,000. When a list hits its limit, the oldest items archive automatically. Start a new list each release so old work does not disappear quietly.

- **41%** of desk worker time goes to low-value, repetitive work, Slack research finds ([source](https://slack.com/blog/news/new-slack-research-shows-accelerating-ai-use-at-work))
- **10,281** full-time desk workers surveyed in six countries for that research, fielded January 2024 ([source](https://slack.com/blog/news/new-slack-research-shows-accelerating-ai-use-at-work))
- **1,000** items per Pro list before the oldest items archive automatically ([source](https://slack.com/intl/en-gb/help/articles/27452748828179-Use-lists-in-Slack))
- **90 days** of message history on Slack's Free plan ([source](https://slack.com/pricing))

## Use Slack AI recaps without trusting them blindly

Slack AI can write channel recaps, thread summaries and huddle summaries. It can also produce stand-up and sprint summaries from a plain prompt. Slack's agile guide describes those features. They save time when you come back from a day off.

Check every recap against the thread it summarizes. A summary can miss a quiet objection or a decision made in a huddle. Ask the summary to list open questions, then answer those questions in the thread yourself.

## A sample sprint rhythm in Slack

Here is one way a sprint can run in Slack. The rows below are a pattern, not a rule. Adjust them to your team's calendar and the ceremonies you actually run.

| When | Where | What happens |
| --- | --- | --- |
| Sprint planning day | #sprint-goal | Team agrees the goal and posts it at the top of the channel |
| Every morning | #daily-standups | Check-in thread, replies only, blockers get a name and a next step |
| Midweek | #backlog-grooming | Questions on stories, answers in threads |
| Review day | #sprint-review | Demo notes and stakeholder feedback collected in one thread |
| Retro day | #retrospective-feedback | Canvas board first, then action items copied to a List |

_A sample sprint rhythm for one team._

Notice the pattern. Each ceremony has one home, and each home has one job. When a question shows up in the wrong place, move it to the right channel and say so in one line.

## Use huddles for live ceremonies

Some ceremonies need a live call, and Slack huddles cover that. Start a huddle from the channel, then share your screen to walk through a backlog or a sprint board. Slack AI can summarize the huddle afterward, and you can post that summary back to the channel. For steps, read [how to share your screen in a Slack huddle](https://www.lazur.app/how-to/share-your-screen-in-a-huddle-in-slack).

A call that works for one part of the team can fail for another. Keep the thread open for people who cannot join live. Ask them to reply with their three check-in answers before the call starts.

![Team at a retrospective meeting with notes on a table, the setting for a Slack retro board on Mac](https://images.lazur.app/content-images/role-app/agile-coaches-slack/slack-for-agile-coaches-on-mac-3-f190f3.jpg)

## Search and jump between channels fast

Press ⌘K to jump to any channel or person. Type a few letters, then press Return. To find an old blocker or a retro idea, use search and add the channel name to narrow the results.

Pin the channels you open most. For the exact steps, see [jump to a conversation in Slack](https://www.lazur.app/how-to/jump-to-a-conversation-in-slack) and [search messages in Slack](https://www.lazur.app/how-to/search-messages-in-slack).

## Cut notification overload

Notification overload comes up often in vendor blogs and reviews. Those sources are qualitative, and no primary study measured it for agile coaches. You can still fix it with three moves.

- Pause notifications when you need focus. Use the profile menu, and see [pause notifications in Slack](https://www.lazur.app/how-to/pause-notifications-in-slack).
- Mute channels you read on a schedule, such as the sprint review channel between reviews. See [mute a channel in Slack](https://www.lazur.app/how-to/mute-a-channel-in-slack).
- If alerts stop arriving at all, check the settings before you blame the app. See [fix Slack notifications on Mac](https://www.lazur.app/how-to/fix-missing-notifications-in-slack).

Set your status when you are heads down, so teammates know to wait for your reply. Write a clear message, such as Focus until noon. See [set your status in Slack](https://www.lazur.app/how-to/set-your-status-in-slack).

## Mistakes agile coaches make in Slack

- Running retros in direct messages. The team cannot see each other's ideas, so the board stays empty.
- Posting a new stand-up message each day with no thread. The channel becomes a log that nobody scans.
- Leaving action items inside a thread. Nobody owns them, and they drop out by the next sprint.
- Trusting a summary without reading the thread it came from.
- Keeping retro notes only in Slack. Free plan history covers 90 days, so copy important notes out before they age out.
- Splitting follow-ups between Slack and Apple Reminders with no rule. Pick one home for each type of follow-up.

## Check your plan before you promise a setup

Several parts of this setup depend on your plan. Slack's pricing page says Free plan message history is 90 days, and Pro is unlimited. It lists up to 10 apps on Free and unlimited app integrations on Pro. It does not clearly say whether Canvas, Lists or Workflow Builder come with Free.

Slack's templates page says templates come with all paid plans. It names one project management template and no agile-specific ones. Some third-party guides say the full gallery appears on Free. Trust Slack's own page, and check the pricing page before you promise a setup to your team.

## How Lazur fits your Slack day

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ to ask about anything on screen. Lazur answers out loud. When you ask where something is, it draws a circle and a label around it. When you ask how to do something, it guides you one click at a time and waits for each click.

Lazur does not click buttons, edit files or operate other apps for you. It is not a plugin or add-in for Slack. You make every click and every send.

Hold fn to dictate. Clean, formatted text lands at your cursor in any app, which helps with long retro notes. Read the text back before you post it.

## Good questions to ask Lazur from inside Slack

- Where is the Agents & tools item? Lazur points to it on screen.
- Walk me through a daily check-in workflow, one click at a time.
- Draft three retro prompts for the Canvas board.
- Explain what a thread summary covers before I trust it.
- Look up the Workflow Builder help article and summarize it while I keep working.

## Where the numbers in this guide come from

No study measured how agile coaches spend time in Slack, and this guide does not claim one. The 41% figure covers desk workers in general, based on Slack's own research of 10,281 full-time workers. It is not a coach number.

Slack's agile guide also cites 3.4 hours a week saved by support workers who use automated processes. That figure is vendor-reported, and it describes support work. Treat it as a hint, not a benchmark for your team.

On versions, Slack's Mac release notes list 4.53.280 from Nov 3, 2026 as the newest build this guide could confirm. The same page lists a later build dated after today, so it is left out. Check the About Slack entry on your Mac to see what you run. The Mac menu layout was not confirmed in Slack's own Mac help, so menu names may differ a little on your build.

## Next steps for this week

1. Create the channels from the table above, or use your team's own names.
2. Build one stand-up check-in with Workflow Builder. Test it in a private channel first.
3. Build the three-column retro canvas and use it at your next retro.
4. Start one List for action items. Fill in Assignee and Due date on every row.
5. Ask Lazur to walk you through any step you cannot find. It waits for each click.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Lazur, draft a daily check-in with three questions I can post in the stand-up channel.”: Lazur drafts the check-in and types it where your cursor is. You read it and post it yourself. (Drafts it)
- “Lazur, where is the Agents & tools item in the sidebar?”: Lazur draws a circle and a label around the sidebar item so you can find it fast.
- “Walk me through building a workflow for a daily check-in.”: Lazur guides you one click at a time through Workflows > New > Build Workflow, waiting for each click.
- “Draft three headings for a retro canvas.”: Lazur writes the three headings and a one-line prompt. You paste them into the canvas yourself.
- “Hold fn and dictate my retro notes into this thread.”: Your spoken notes land at the cursor as clean text. Read them before you send.
- “Put the action items in Apple Reminders for Friday.”: Lazur adds the items to Apple Reminders. Your Slack reminders stay separate.
- “Explain what a Slack AI thread summary will include.”: Lazur answers out loud what a thread summary covers, and what to check against the thread.
- “Find the Slack help article on Workflow Builder and summarize it.”: Lazur runs the search in its own Chrome tabs and returns a summary and a report.

## FAQ

### Does Slack have an agile template for Mac?

Slack's templates page names one project management template and lists no agile-specific templates. Slack says templates come with all paid plans. You can build your own channels and a three-column retro canvas with the steps above.

### Can I run a daily stand-up in Slack without a bot?

Yes. Post one check-in message each morning and ask people to reply in its thread. Workflow Builder can post the prompt on a schedule if you want it automatic. Pick whichever fits your team.

### Where is Workflow Builder on a Mac?

In the current desktop help, start from the Agents & tools sidebar item, then go to Workflows > New > Build Workflow. If you do not see the item, check the Tools tab and choose More. Older guides describe a Tools menu under the workspace name.

### Will my retro notes disappear on the Free plan?

Slack's pricing page lists Free plan message history as 90 days. It lists Pro message history as unlimited. Copy important retro notes into a List or a document before they age out.

### Does Lazur set up Slack for me?

No. Lazur points at controls, guides you one click at a time and drafts text you can use. It does not click buttons or operate Slack for you. You make every change and every send.

### Why did old items leave my Slack List?

Pro and Business+ lists hold up to 1,000 items and subtasks. When a list reaches that limit, Slack archives the oldest items automatically. Start a new list each release so you do not lose track of older work.

### Which Slack for Mac version should I expect?

Slack's Mac release notes list 4.53.280 from Nov 3, 2026 as the newest build this guide could confirm. A later build dated after today appears on the same page, so check About Slack on your Mac to see what you run.

## Sources

1. [Slack for Mac - Release Notes](https://slack.com/release-notes/mac), Slack, checked 2026-11-08
2. [Agile Planning: Optimize Your Team's Workflow with Proven Agile Techniques](https://slack.com/blog/collaboration/agile-planning-build-better-workflows-with-this-proven-system), Slack, checked 2026-11-08
3. [New Slack research shows accelerating AI use and quantifies the 'work of work'](https://slack.com/blog/news/new-slack-research-shows-accelerating-ai-use-at-work), Slack, checked 2026-11-08
4. [Slack Pricing](https://slack.com/pricing), Slack, checked 2026-11-08
5. [Slack templates for project management and business](https://slack.com/features/templates), Slack, checked 2026-11-08
6. [Build a workflow: Create a workflow in Slack](https://slack.com/help/articles/17542172840595-Build-a-workflow--Create-a-workflow-in-Slack), Slack Help Center, checked 2026-11-08
7. [Use lists in Slack](https://slack.com/intl/en-gb/help/articles/27452748828179-Use-lists-in-Slack), Slack Help Center, checked 2026-11-08