- Home
- Services
- Product Development & Open Innovation
- We ship a lot and the product isn’t moving
Feature factory
We ship a lot and the product isn’t moving
A team that ships constantly while the product stands still is what’s known as a feature factory, a symptom whose causes straddle product and code. After release, how the feature is used goes unobserved, so priorities are set by the latest request. Things get built without being checked, and every extra feature makes the next one more expensive, until little time is left to understand what works.
Book a callDoes this sound familiar?
- The backlog fills faster than we can empty it, and nobody remembers why half the items are there.
- We release often, yet product metrics stay flat from one quarter to the next.
- Priorities shift with the latest big customer or whoever last asked for something in a meeting.
- After release, nobody checks whether users use the new feature, or how.
- Every feature costs more than the last, and the team spends more and more time maintaining what exists.
How do you end up shipping a lot while the product doesn’t grow?
It all starts after release, when usage goes unobserved, and it feeds back into the backlog as priorities set by opinion. From there things get built without being checked, and the code grows heavy with features few people use.
Things get built before they are checked
Ideas enter the backlog as tasks to carry out, with no agreement on what evidence would show whether they work. Before any code is written, we bring together people who know the market and people who will build the product, to decide what to check first and what minimal architecture is needed to do it.
The latest request sets the priorities
Without shared criteria the backlog is ordered by the people who push hardest. The team executes without the context to say ‘not now’, and initiatives already started are left half done when the next one arrives.
Production usage stays out of the priorities
A released feature is considered finished, and nobody watches in production whether users use it and how. Without that feedback the next priorities are again set by opinion, and the cycle starts over.
Every feature costs more than the last
The code fills up with features few people use, and each adds cases to handle. Changing an old feature means touching parts nobody wants to break, and the team spends more and more time maintaining what exists.
What changes when you build what is needed
Every initiative starts from what you want to check, reaches production in small steps and is judged by how users use it. The backlog gets lighter, because much of what isn’t needed is discovered before it has been built.
People who set the product direction choose with usage data in front of them, and the team brings to the discussion what it has seen in production. The code stays easy enough to change to follow that data, even when the direction changes.
How does a feature come about at your company?
We follow a feature from the person who asks for it to the person who uses it, and tell you frankly whether the knot is in the priorities or in the code.
Message sent
Thanks for reaching out. Our team will get back to you within 24 hours with a tailored proposal