search icon

Development for and with the end-users

In a first of 6 posts about our pillars of JOINT INNOVATION, I talked about how we want to lower and eliminate the barriers of collaboration with our customers in order to get as much feedback as possible. In this second post I want to shed some light on how that collaboration trickles down into our development cycle. If there is one place where JOINT INNOVATION should shine, it is here of course.

Feature requests

In that first blogpost we mentioned the Make-A-Wish Button for feature requests from within the application. But that’s not the only place where feature requests are raised. Feature requests can come from an in-app chat session, from a follow-up sales call or from the onboarding training we provide to our customers. No matter where the question is raised, we centralise the information in our roadmap tool (AHA) and we include from who and how we got the request. This because we also want to be able to follow up after a feature makes it into production with the people that have requested it.

Release cycle pace

The following complaint rises at almost every user conference in our industry: “we have been asking for this functionality for 3 years now, and this is not what we asked for“. Somehow, in our industry, the software suppliers have settled for the speed of functionality delivery to be even slower than the speed of sales 😉 In this modern day and age this is unacceptable. Therefore TrendMiner, and most new players that enter the market, will be characterised by an AGILE development culture. At TrendMiner we bring a new release every two to three months and every release is a well balanced equation of new functionality and product enhancements.

The problem description

At TrendMiner we acknowledge that we do not own the truth. This is the base of why JOINT INNOVATION exists. Therefore we keep close contact with customers throughout the whole development cycle, and listen to our end users.
Development
As you can see in the development cycle graphic here we don’t even start writing our code before we had a good understanding about the problem statement behind specific feature requests. This is the only way we can bring features faster to the customer in the way they need them to solve their business problems.

Prototyping

Another reason of that problem description phase with the customers is lean management. This means that we want to eliminate waste at every aspect of our activities. This avoids development work that has to be thrown away. The second way we do that is by creating prototypes. These are early development features. They are quick-and-dirty mock-ups of what was discussed in the problem description.

The biggest problem with prototyping in software is that the customer has to go through the IT department yet again for new resources. In the spirit of lowering the barrier of collaboration, we at TrendMiner have solved this by making prototypes possible on the same setup without impacting the production environment. This approach is quite unique for Enterprise Software applications. This way we can have some dedicated end-users who can try out the new prototype functionality while all others can keep working like before. One extra major advantage here is that we can test these prototypes on the same data without copying it.

Lab Features

Before we release new functionalities to the customers, every release has a short BETA phase where a subset of customers get their download a couple of weeks before the general availability (GA). This will most likely be asked to those customers who have requested for one or more of the features in that build. However, sometimes, we get feature requests of which we feel every customer should be testing the prototype. For those requests we have now the lab-feature status. This is a –slightly better developed– prototype mock-up that will be delivered in a GA build where every customer can decide to activate them.

Customer centricity

I hope that by now you have noticed that the customer centric approach of TrendMiner is not just a buzzword, it’s the core of our company culture and runs through everything we do. Is there even more we could do? LET US KNOW!

Share

Keep me informed

More from Hans De Leenheer