Choose a workplace app you rely on as a PM (Jira, Slack, Drive) and propose improvements

Quick Overview

A product improvement exercise where you choose a workplace tool that product managers use daily, such as Jira, Slack or Google Drive, and propose how to make it better. It tests user segmentation, pain-point prioritization, solution trade-offs and success metrics.

Choose a workplace app you rely on as a PM (Jira, Slack, Drive) and propose improvements

Company: Houzz

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Product managers live in a handful of tools every day: a team chat app such as Slack, an issue tracker such as Jira, shared file storage such as Google Drive, and others. Pick one product you use regularly, either one you love or one that frustrates you, and explain how you would improve it. ```hint Anchor on one recurring moment Rather than listing every annoyance, pick one type of user and one moment in their week where the tool lets them down. A specific moment makes the pain points easier to rank and the improvement easier to measure. ``` ### Clarifying Questions - Should I approach this as a PM at the company that makes the tool, so the improvement must also serve its business, or purely as a user improving my own workflow? - Must the improvement target product managers, or may I pick another group of the tool's users (engineers, designers, executives) if the larger opportunity is there? - Is any tool fair game, or should I stay with the kinds you named: team chat, issue tracking and file storage? - Are you looking for one well-developed improvement or a broader roadmap for the tool? ### What a Strong Answer Covers - A justified choice of tool and a goal for the improvement tied to the maker's business (adoption, retention, more paid seats), not only personal preference. - A chosen user segment and a walk through their workflow that surfaces concrete, ranked pain points. - Several solution options compared on impact, effort and confidence, with one recommended first release. - Success metrics and guardrails, including the effect on the tool's other users, and how the change would be tested. - Risks and trade-offs specific to the chosen tool, such as data trust, permissions or added complexity. ### Follow-up Questions - Your improvement helps PMs but depends on engineers keeping the tool up to date. How do you make it work for them too? - How would you show that the change makes paying teams more likely to renew, rather than just adding usage among PMs? - A competitor ships a similar feature first. What would you change in your plan?

Overview: A product improvement exercise where you choose a workplace tool that product managers use daily, such as Jira, Slack or Google Drive, and propose how to make it better. It tests user segmentation, pain-point prioritization, solution trade-offs and success metrics.

Houzz logo
Houzz
Oct 21, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Product managers live in a handful of tools every day: a team chat app such as Slack, an issue tracker such as Jira, shared file storage such as Google Drive, and others. Pick one product you use regularly, either one you love or one that frustrates you, and explain how you would improve it.

Clarifying Questions Guidance

  • Should I approach this as a PM at the company that makes the tool, so the improvement must also serve its business, or purely as a user improving my own workflow?
  • Must the improvement target product managers, or may I pick another group of the tool's users (engineers, designers, executives) if the larger opportunity is there?
  • Is any tool fair game, or should I stay with the kinds you named: team chat, issue tracking and file storage?
  • Are you looking for one well-developed improvement or a broader roadmap for the tool?

What a Strong Answer Covers Guidance

  • A justified choice of tool and a goal for the improvement tied to the maker's business (adoption, retention, more paid seats), not only personal preference.
  • A chosen user segment and a walk through their workflow that surfaces concrete, ranked pain points.
  • Several solution options compared on impact, effort and confidence, with one recommended first release.
  • Success metrics and guardrails, including the effect on the tool's other users, and how the change would be tested.
  • Risks and trade-offs specific to the chosen tool, such as data trust, permissions or added complexity.

Follow-up Questions Guidance

  • Your improvement helps PMs but depends on engineers keeping the tool up to date. How do you make it work for them too?
  • How would you show that the change makes paying teams more likely to renew, rather than just adding usage among PMs?
  • A competitor ships a similar feature first. What would you change in your plan?