Kathleen D Wilhoit
Sep 4, 2018 · 1 min read

As a product manager, I have fallen into that trap, especially if the software product is business oriented and requires a lot of functionality. Users need a single form to do many different complex things and it’s an easy place to end up with something that works but is unpleasant or not easy to use.

The problem with dev-ops is a)planning an iteration: what good does it do to have only a portion of the features you need? All that does is give the first users a taste of “inadequate” functionality. 2) planning for your user audience: inadequate business analysis of the user, their level of expertise and their experience of existing software. Hard workflows that can’t adjust for different organizations, inefficient visual workspace that supports complete transactions without detours to sub- functions, or losing work when the user is interrupted.

For the consumer, any feature that isn’t completely self explanatory and intuitive can kill a launch.

I’ve had automatic updates from large companies like Apple, Microsoft and Oracle that took my installations down! Things I had to roll back, or worse, wait until they fixed it. I don’t call that productive.

There’s a balance in using iterative builds to push developers to milestones, but not pushing features to end users until you’re damn sure it will be hailed as an upgrade.

    Kathleen D Wilhoit

    Written by

    CIO by day, painter by night. Sometime writer when I gather my thoughts. Voluntaryist, believer in liberty, crypto, and capitalism.