Here’s the homepage draft. Let’s keep feedback in this thread before Friday’s review.
Homepage draft.pdf240 KBThreadsOne message.
One message.
The whole discussion.
Discuss the details in replies to a message. Keep the original message, files, and replies together while other conversations continue in the channel.
launchOctober launch
Playing one sample message and reply.
Enter to send · Shift + Enter for a new line
Product tour with sample contentRead the shared draft and its two replies together. Try writing a sample message; the reply is scripted.
One question. All its replies.
Continue a detailed discussion in a thread attached to its message. The original question, shared file, and replies stay together so someone joining later can read how the team reached its answer.
Channel and direct-message threads
Open replies to the relevant message in a channel or direct message. Start a separate message and thread for a different question.
Replies anchored to the parent message
Read the original message and its replies in the thread panel. The starting point remains in view as other messages appear in the channel.
Files and reactions inside replies
Attach a file to a reply or add a reaction. Keep feedback on a document under the message where it was shared.
Option to also post a reply to the channel
Use the option to also send a reply to the channel when the wider team needs the outcome. The rest of the discussion can stay in the thread.
Give the outcome an owner.
The thread settles how the guide should be updated. Create a task for Maya and choose a due date. Follow its status in a list or board while the reasoning remains in the original conversation.
First-week preparation#welcome
Open a task, then change its owner or status.
Changes in this example are not saved to your workspace.
Explore List and Board, then select a task to see its owner and due date.
Work through one question.
The replies discuss including the mobile layout in Friday’s review. Read the question, draft, and response together in one place.
Open a thread
Move detailed discussion under the relevant message.
Keep replies together
Keep the reason visible while replies, files, and reactions accumulate.
Share back when needed
Post the outcome back to the main channel when the wider team needs it.
The question and reasoning remain alongside the conclusion, while new conversations can continue in the main channel.
Make room for the details.
Feedback on a design
Discuss changes to a shared screenshot in its thread. Post the relevant reply to the channel when the team needs the conclusion.
Following up on a question
Collect findings beneath the original customer question. A colleague taking over can read the explanation, file, and earlier replies together.
A thread and a task serve different purposes.
A thread holds the discussion around a message. Create a task when work needs an owner, status, and due date. Writing a reply does not automatically create a task or calendar event.
Frequently asked questions.
A few details about using this feature and what it covers.
Keep the discussion with its question.
Open a thread from a channel message. Add the feedback there and share the outcome with the team when it is ready.