-
Alone or Lonely?
When we’re making software, it’s easy to have our hearts and minds focused on The Next Thing, the new hardware that will support it, the rate of adoption. But it’s worth remembering that you may have devoted customers who are not going to install your new things right away. They’re worth listening to.
-
Customization Complications
On the surface, letting people have all the customizations anyone has ever asked for seems like a great way to get alignment with what they want. They’ll just use the things they need! And maybe they want something they haven’t thought to ask for. But that’s just the first thought, because the more options a…
-
Consent of the Upgraded
Software users, especially in the enterprise, are a captive audience, until they aren’t. How do we respect their experience and their capacity to consent?
-
Progressive Delivery requires alignment
The goal you’re aligning to needs to be broad enough that everyone can see their place in it, and narrow enough that they can tell what isn’t part of the goal. When you get something that well-defined, you can hold up every action and choice to it and tell whether it will help or hinder…
-
Fogged Glass
That assumption of configurability is a core part of Progressive Delivery – we don’t all need to have the same experience, even if we’re using the same software. Using feature flags and sticky settings, everyone gets their preferred interaction style.
-
Never finished: A manifesto on Progressive Delivery
What do we mean when we say “Progressive Delivery”? It’s a way to get curious about the whole lifecycle of your product, including after it leaves your control.
Progressive Delivery 