← All questions
Product sensestretch
How would you improve Slack for a company of 20,000 people?
How to approach it
Scale changes the problem. Ask who the user is here: individual employees drowning in channels, or admins worried about security and cost.
How a strong answer opens
“At 20,000 people, the problem changes. Is the user the employee drowning in channels, or the admin worried about security and cost?”
Outline of a strong answer
Try answering out loud for a few minutes before you open this.
- Clarify user and goal: employee productivity or admin control
- Pick employees and describe information overload at that scale
- Pain points: too many channels, missing key announcements, finding answers
- Ideas: priority inbox, verified announcement channels, better search
- Trade-offs: control for admins versus flexibility for teams
- Measure time to find information and message volume per active user
Where this question usually goes wrong
Treating it like a small-team workspace and ignoring information overload, compliance needs and the admins who decide on enterprise contracts.
Learn the method
Prioritize and defend the trade-offs in Module 1, Product sense and design.
The full kit has worked answers in full, start to finish, for every round type. $129 once.