What to Do When You Can't Get Excited About Your Product
Product management requires sustained engagement with the product, its users, and its strategic direction over time. The PM who has lost genuine enthusiasm for their product — who is managing features rather than pursuing a product mission — typically produces worse work than one who is genuinely invested in what they’re building.
But loss of enthusiasm isn’t always a signal that something is wrong. Sometimes it’s a temporary trough that precedes re-engagement; sometimes it’s a symptom of a specific fixable organizational problem; and sometimes it’s genuine information that the role or the product isn’t the right fit.
Diagnosing the Source of Disengagement
Before deciding what to do about lost enthusiasm, diagnose where it’s coming from:
Product-specific disengagement: The product itself doesn’t feel meaningful to you — it doesn’t solve a problem you find compelling, serve users you find interesting, or create value you find worth building. This is the most serious form of disengagement and the hardest to sustain through.
Strategic disengagement: The product could be compelling, but the current strategic direction doesn’t reflect what you believe the product should be doing. The strategy feels misguided, and working toward it creates the specific frustration of building toward a direction you don’t believe in.
Organizational disengagement: The product and its strategic direction are compelling, but the organizational environment makes pursuing them difficult — political dynamics, inadequate support, poor team culture, or management that overrides product judgment consistently.
Situational disengagement: A temporary frustration from a difficult period — a launch that didn’t go well, a priority battle that was lost, a run of disappointing user research — that will likely resolve with time.
Finding the Path Back to Engagement
For strategic and organizational disengagement, the path back typically involves addressing the underlying cause: having the frank conversation about strategic direction, advocating for the changes that would restore organizational conditions for good work, or accepting that this organization or strategic direction isn’t the right one.
For product-specific disengagement, the harder question is whether the product can be connected to a mission the PM finds meaningful, or whether the fit is genuinely poor.
For situational disengagement, time and the recovery from specific setbacks is typically sufficient.
Key Takeaways
Loss of enthusiasm for your product is worth diagnosing specifically — the source (product, strategy, organization, or situation) determines the appropriate response. Product-specific disengagement is the most serious form; organizational and strategic disengagement may be resolvable through the right conversations and interventions; situational disengagement typically resolves with time and recovery from specific setbacks. The honest diagnosis is the starting point for finding the path back to genuine engagement — or for recognizing when a change is genuinely needed.
When the Path Back Isn’t Available
Some loss of product enthusiasm reflects genuine product-specific disengagement that can’t be reconnected to a mission the PM finds meaningful. When this is the honest diagnosis — when extended reflection confirms that the product doesn’t solve a problem the PM finds compelling — the most honest response is accepting that the current role isn’t the right fit and pursuing a transition, rather than attempting to manufacture enthusiasm for work that genuinely doesn’t engage.
Key Takeaways
Loss of enthusiasm for your product requires diagnosis by source. Product-specific disengagement is most serious; organizational and strategic disengagement may be resolvable; situational disengagement typically resolves with time. The honest diagnosis is the starting point for finding the path back to genuine engagement — or for recognizing when a change is genuinely needed. The IT roadmap’s most transformative function is the organizational conversation it initiates — the discussions between IT leadership and business stakeholders about what the technology foundation needs to look like and why, which typically doesn’t happen without the roadmap providing the structure that makes the conversation productive.