Product design question

How do you improve Slack?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests basic product sense for a mature B2B collaboration tool, picking a specific workplace friction point over generic feature suggestions.

Clarify scope: default to the core messaging and channel experience for existing team users, not the App Directory or enterprise admin tools.
Segment users: heavy daily users managing many channels, and lighter users who only check a few specific channels.
Pick one pain point: important decisions or action items made in a fast-moving channel conversation get buried and lost as the channel scrolls on.
Propose a lightweight decision or action-item tag applicable to any message, surfaced in a dedicated per-channel summary view.
Address the trade-off: this must be low-friction to apply, one click, or users won't bother, given Slack's fast, informal communication culture.
Define success: reduction in can-someone-remind-me follow-up messages, and adoption rate of the tagging feature in active channels.

Picks a specific, common workplace pain point, lost decisions in fast-scrolling channels, rather than generic feature requests.
Proposes a lightweight, low-friction mechanism fitting Slack's fast, informal culture, rather than a heavyweight documentation requirement.
Addresses adoption friction explicitly, recognizing a feature that's not effortless to use won't get adopted in Slack's culture.
Defines success with a specific behavioral proxy, reduced clarifying follow-ups, tied directly to the pain point.

Proposing heavyweight solutions like mandatory meeting notes that conflict with Slack's fast, informal use pattern.
No adoption-friction consideration, proposing a feature too effortful for users to bother using consistently.

How would you prevent this tagging feature from being underused or forgotten?
How would this integrate with Slack's existing thread and pinned-message features?