{"id":21476,"date":"2017-11-01T08:25:33","date_gmt":"2017-11-01T13:25:33","guid":{"rendered":"https:\/\/blog.planview.com\/optimize-customer-success-by-integrating-salesforce-and-targetprocess\/"},"modified":"2017-11-01T08:25:33","modified_gmt":"2017-11-01T13:25:33","slug":"optimize-customer-success-by-integrating-salesforce-and-targetprocess","status":"publish","type":"post","link":"https:\/\/blog.planview.com\/optimize-customer-success-by-integrating-salesforce-and-targetprocess\/","title":{"rendered":"Optimize Customer Success By Integrating Salesforce and Targetprocess"},"content":{"rendered":"
\n
\"Optimize<\/div>\n<\/figure>\n

The<\/span> ‘Requirements Management’ process underpins top-rate enterprise software delivery as it ensures your customers consistently receive value from their software applications. Or in other words, they receive the product\/product features they asked for that will hopefully fulfill their business needs. That’s what software delivery at scale is all about, right?<\/span><\/p>\n

With that in mind, it makes sense that all the teams and tools that oversee the Requirements Management process are working together. For Tasktop (and typically many of our customers), that means that the Sales\/Delivery teams should be collaborating with Product Owners, Business Analysts and Agile Developers, among others, to create a seamless value stream from feature request to feature in production delivering value for the end user.<\/span><\/p>\n

In short, we want our ‘customer-facing’ folk who capture the request and understand what the customer wants to be working with the ‘production-side’ folk to make sure the right product is being built and delivered on time. While this objective seems simple enough, it’s actually rather tricky in reality.<\/span><\/p>\n

Before we integrated <\/span>Salesforce<\/b> and <\/span>Targetprocess<\/b>, these two “sides” within our business were working in silos because both teams work in their own purpose-built tools, and these tools do not naturally speak to each other. Meaning a lot of time is lost to the non-value-adding world of manual communications and administrivia. Even worse, the difficult communication resulted in a lot of misunderstanding and pitted the teams against each other.<\/span><\/p>\n

The Tools<\/b><\/p>\n

Our Sales and Delivery teams primarily work in <\/span>Salesforce<\/b><\/a>, the leading CRM (Customer Relationship Management) solution in the market. Using this tool, we’re able to capture and nurture leads, track accounts and customer requests, identify opportunities and problems, and more. The system serves as the prime link between the business and the customer, with our customer service teams enhancing the quality and speed of communications between the two.<\/span><\/p>\n

Meanwhile, Product Owners and some of our Business Analysts operate in <\/span>Targetprocess<\/b><\/a>, a leading Agile Project Management tool. Here, they can manage the constant and competing barrage of priorities that they deal with on a daily basis; balancing the need to reduce technical debt, drive innovative feature creation, reduce defects, and define customer requests in great detail. This tool enables work to be undertaken using different workflows and methodologies, track requirements and acceptance criteria, visualize the product backlog for Agile work, and develop an efficient process to prioritize the most important work (critical product features etc.).<\/span><\/p>\n

The Disconnect<\/b><\/p>\n

Both <\/span>Salesforce <\/b>and <\/span>Targetprocess<\/b> are two powerful tools that enhance the way both ‘sides’ work. Frustratingly, these teams were unable to spend as much time in their tool of choice as they would like to (or collaborate with colleagues effectively), because they’re trapped in what in what we call “communications chaos.”<\/span><\/p>\n

With no automated flow of information between the two tools, everyone involved was getting overwhelmed by a bombardment of emails and other unreliable forms of communication. No one wants to regularly check or read email threads, or search for attachments, or make endless phone calls, or wait for mind-numbing status meetings, or log into multiple tools just to have an idea of what’s going on.<\/span><\/p>\n

All these means of communicating are tedious and susceptible to human error and, crucially, build animosity between teams. No-one is winning in that scenario – especially the customer! And as with any process, you simply must have end-to-end visibility to control and continuously improve it. And that’s not possible if the tools are not automatically flowing information between each other and the rest of the software value stream. We wanted to tear this wall down and banish the idea of “sides”. We wanted to be one complete team. One whole.<\/span><\/p>\n

Last but not least, you mustn’t forget that your communications will only become more chaotic as your business grows – more teams and more tools aiming to share vital information (including requirements) that are vulnerable to falling down the black hole. With deadlines missed and projects failing, <\/span>addressing this<\/b> communications issue is a determining factor in how successful you will be at scaling your software delivery.<\/b><\/p>\n

The Integration<\/b><\/p>\n

With the objective defined – i.e. allowing key players within the software value stream to work together by integrating their tools of choice, consequently eradicating manual communication, increasing product accuracy and speed of delivery – Tasktop set about connecting <\/span>Salesforce<\/b> and <\/span>Targetprocess<\/b>.<\/span><\/p>\n

We are able to use <\/span>Tasktop Integration Hub<\/span><\/a> to easily connect the two tools (from a technical standpoint) and maintain the integrations in the face of vendor updates, API changes, tool downtime etc. via our testing infrastructure ‘The Integration Factory’. But simply connecting the two tools isn’t the difficult part – that’s child’s play. The tricky bit is<\/span> reengineering the process<\/span><\/a>, which demands a lot of time and energy that most organizations just don’t have. <\/span><\/p>\n

To build a strong, sophisticated integration, you have to understand user workflows and use cases, how people think and work, and provide scope for adaptation and evolution. Fortunately, we’re blessed with a lot of experts at Tasktop who can build and maintain technology that is based on the core needs of practitioners, as well as a deep understanding of human behavior. <\/span><\/p>\n

This user-focus approach is crucial because 80 per cent of the heavy-lifting is manufacturing a process – getting inside people’s heads, obtaining semantic alignment between teams, obtaining an end-to-end understanding of issues, role idiosyncrasies and so forth. And of course, how requests flow across the value stream to ensure the net is tight and non-porous to ensure that nothing is lost to interpretation, misunderstanding or oversight.<\/span><\/p>\n

The Benefits<\/b><\/p>\n

The key benefits that Tasktop has enjoyed so far from integrating Salesforce and Targetprocess include:<\/span><\/p>\n