{"id":21028,"date":"2019-08-01T08:35:26","date_gmt":"2019-08-01T13:35:26","guid":{"rendered":"https:\/\/blog.planview.com\/how-tasktop-dramatically-improved-its-flow-velocity-in-one-day\/"},"modified":"2019-08-01T08:35:26","modified_gmt":"2019-08-01T13:35:26","slug":"how-tasktop-dramatically-improved-its-flow-velocity-in-one-day","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/how-tasktop-dramatically-improved-its-flow-velocity-in-one-day\/","title":{"rendered":"How Tasktop dramatically improved its Flow Velocity in one day"},"content":{"rendered":"
\n
\"How<\/div>\n<\/figure>\n

In the latest release of <\/span>Tasktop Integration Hub (19.3)<\/span><\/a>, the Product Development team tried out an experiment to deliver even more business value out of our flagship product. <\/span>In my last blog<\/span><\/a>, I described how Tasktop has made few cultural and process-oriented changes to be more customer-obsessed and ship features faster. Galvanized by the new energy that was instilled across the team, we decided to try something a bit different.<\/span><\/p>\n

For a very long time, the team only focused on features that provided l<\/span>arge amounts of quantifiable business value to our customers, such as <\/span>time-tracking integration, Test Management integration suite and Twinless update (disaster recovery). This does not necessarily mean that it was the wrong approach; only that it made sense to do so at the time. As Tasktop grew, our customers demanded more and this resulted in a backlog containing a long list of aesthetic features and improvement suggestions by customer-facing folks, as well as the external users of the product.<\/span><\/p>\n

What do aesthetic features from the perspective of a product design mean? Aesthetics is the manner of the experience with the product that brings meaning and joy to users. These aesthetic features might not have a direct impact on the sales or retention numbers but definitely contribute to a higher Net Promoter Score for end users. <\/span><\/p>\n

With an ever-growing pile of requests in the backlog, Product and Engineering teams (who sit under one umbrella Product Development team) needed to modify their execution strategy. We asked ourselves, “Is there any way to ship as many features as possible in the coming days?”<\/span><\/p>\n

And we said to ourselves, “Let’s try; if we don’t succeed at least we know that something doesn’t work for us.” With this in mind, we all decided to get together and work on this list of minor aesthetic\/general requests that would greatly improve the customer experience with the product. We called this experiment “Quick Wins”.<\/span><\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n