A Practical Method to Balance “Keep the Lights On” vs “Build Something Big”

Balancing “Keep the Lights On” vs “Build Something Big”

Every product team lives in tension: you must keep quality high and build new value. Most teams pick one by accident. They either drown in maintenance or chase shiny initiatives while the foundation cracks.

A better approach is to treat the roadmap like a portfolio with explicit categories.

Step 1: Name the categories (four lenses)

Use the four lenses as your portfolio buckets:

• Customer: fix the workflow pain people feel today.
• Business: improve levers like activation, retention, expansion.
• Strategy: invest in how you win (platform capabilities, differentiation).
• Vision: build the future product narrative in concrete steps.

Step 2: Set non-negotiable allocations

Pick a simple quarterly allocation that fits your reality. For example:

• 35% Customer
• 25% Business
• 20% Strategy
• 20% Vision

The exact percentages don’t matter. The explicitness does. This prevents “urgent” work from silently taking 90%.

Step 3: Translate allocations into objectives

Instead of allocating effort to projects, allocate effort to objectives.

• Customer objective: “Reduce time-to-answer for core reporting workflows by 30%.”
• Strategy objective: “Standardize the data reliability layer to reduce churn risk.”
• Vision objective: “Ship the first workflow automation loop (insight → action).”
• Business objective: “Increase activation by improving onboarding to first value.”

Step 4: Enforce a sequencing rule

Big bets can’t compete with hygiene tasks in one list. Compare like with like.

• Rank initiatives within each objective.
• Only trade between objectives at leadership level, explicitly.

Takeaways

• Your roadmap is a portfolio; manage it like one.
• Use allocations to stop “urgent” work from crowding out “important” work.
• Objectives create clarity; a single ranked backlog creates conflict.

---