PM Behavioral: A Strength You Have Outgrown and Would Rather Stop Doing

In a product manager interview at WorkBoard, the interviewer asks you to name one thing you are genuinely good at but would rather stop doing. Explain what it is, why you want to step away from it even though you are strong at it, and what that choice says about the work you want to focus on next. ```hint Check it against the role Before you settle on an example, ask whether that activity is a central part of the product manager job you are interviewing for, and how naming it will sound to the person who would be your manager. ``` ### Clarifying Questions - Should the example come from product management work, or can it come from an earlier role such as engineering, consulting, design or customer support? - Does "stop doing" mean declining the work entirely, or wanting it to become a small part of your week that you still cover when the team needs it? - Is it acceptable to name a task inside this role's normal scope, such as writing detailed specs or running sprint rituals, or should the answer stay outside the role's core duties? ### What a Strong Answer Covers - A genuine strength backed by a specific example and its result, not a weakness in disguise. - A reason for stepping back that points toward growth or higher-leverage work rather than boredom or dislike. - How the work stays covered: handed off, taught, automated, or still done when the team needs it. - A choice that is peripheral to this product manager role, tied to what you want to do more of here. ### Follow-up Questions - If this role needed you to keep doing that work for a while after you join, how would you handle it? - When you last stepped back from this work, who took it over, and how did you make sure quality held up? - What would you do with the time you free up, and what are you already doing to build that skill?