Feature flags are not a strategy

Kamikun Johnson — Wed, 21 Oct 2026 11:41:07 +0000

Feature flags are not a strategy.

They're a deployment crutch - one that turns every release into a high-stakes experiment. The problem isn't the flags themselves. It's the teams that treat them as a substitute for clarity.

A flagged feature without a clear hypothesis, a defined success metric, or a rollback plan is just a delayed launch. It's not innovation; it's procrastination in engineering terms.

The real strategy begins when the product team answers: Why are we shipping this behind a flag? Is it to validate demand? To mitigate risk? Or simply to avoid the accountability of a public launch?

When flags become the default, the product strategy disappears. Teams stop debating what to build and start debating how to hide it. That's not agility. That's avoidance.

The paradox? The most successful flagged features are those with a clear exit strategy. The ones that ship, learn, and then vanish - leaving no trace of the uncertainty they were meant to mask.

What's the one feature your team has shipped behind a flag that you wish had been launched publicly from day one?

DeliveryManagement #ProductManagement #Scrum

By Kamikun Johnson — revival audits for Web3 protocols.

Why 'we'll fix it later' kills roadmaps

Kamikun Johnson — Tue, 20 Oct 2026 14:03:07 +0000

The 2022 bear market killed more PM processes than bad managers.

Not the crash itself. The cascading deferrals.

Roadmaps become graveyards of "we'll fix it later" commitments. Every deferred decision isn't just a delay - it's a compounding liability. Technical debt piles up. Scope shifts without owners. Priorities shift without consequences. What starts as a minor adjustment becomes a structural flaw, then a crisis, then a legacy of distrust.

The problem isn't the decisions themselves. It's the illusion of control. Teams assume they'll revisit the deferred items later, but "later" never arrives. Why? Because the cost of revisiting isn't just time - it's context. The team changes. The market changes. The original rationale for the deferral evaporates.

Worse, deferred decisions create a feedback loop. Each new priority displaces the old, but the old never gets resolved. The roadmap becomes a Rube Goldberg machine of dependencies, where every fix requires unwinding a dozen prior choices. Leadership assumes the team will "figure it out," but teams don't fix what they never own.

The real cost? Not the technical debt, but the priority debt. The unspoken truth that no one is accountable for the deferred items. That's when roadmaps stop being strategic and become a series of excuses.

What's the most common deferred decision you've seen turn into a crisis?

PM #Leadership #ProjectManagement

By Kamikun Johnson — I do revival audits for Web3 protocols.

DEV Community: Kamikun Johnson

Feature flags are not a strategy

DeliveryManagement #ProductManagement #Scrum

Why 'we'll fix it later' kills roadmaps

PM #Leadership #ProjectManagement