{"id":4888,"date":"2021-01-28T10:00:00","date_gmt":"2021-01-28T11:00:00","guid":{"rendered":"https:\/\/sonusbenefits.com\/if-you-care-about-roi-follow-this-strategy\/"},"modified":"2021-02-12T15:43:38","modified_gmt":"2021-02-12T15:43:38","slug":"if-you-care-about-roi-follow-this-strategy","status":"publish","type":"post","link":"https:\/\/sonusbenefits.com\/if-you-care-about-roi-follow-this-strategy\/","title":{"rendered":"If You Care About ROI, Follow This Strategy"},"content":{"rendered":"

When you measure progress within your organization, you don’t do it by checking off each individual activity done by your team. You do it by looking at how well you’re accomplishing your overall company goals. So why do we often approach projects from the opposite direction?<\/p>\n

A common mistake that leads to loss of ROI and efficiency stems from our human need to get swept up in the details. Now, there’s nothing wrong with getting all the details right, but details shouldn’t be first in the pecking order of priorities.<\/p>\n

For progress to happen, you need to measure your activities. But without goals and a strategy, you can’t measure anything accurately. If you don’t have a solid plan of alignment, you won’t prioritize what actions and details need the most attention.<\/p>\n

The flaw in quick solutions<\/h3>\n

As we’ve all learned in the last year, crises happen, and they can happen overnight. Organizational pivots can be spurred by internal and external events within your market, industry, or location. With varying levels of success, businesses responded to shifts caused by the pandemic by implementing new technology, changing processes, and rearranging priorities.<\/p>\n

Even outside the pandemic, it’s incredibly easy for organizations to implement “solutions” to their problems, creating more friction. For instance, many organizations struggle with data duplication because they use different systems to track their prospecting and sales, marketing, and client management. The result is a chaotic mass of unusable data that provides extremely limited information to those who need it.<\/p>\n

Here’s how to ensure your organization avoids this type of costly mistake by changing your approach to problem-solving.<\/p>\n

Stepping back<\/h3>\n

Before you decide to implement a solution for a problem, start by following these steps.<\/p>\n

1. Identify your core goal<\/h3>\n

Your goal should be in the context of the result<\/em> you’re looking for, not the solution. For instance, “We need a system to help us manage our prospecting” is an example of a solution statement. A goal<\/em> statement looks more like, “We want to make more informed decisions around how we manage our prospecting and have a smoother handoff between prospecting\/sales and client management.” Starting with the goal statement stops you from identifying possible solutions before you’re ready and keeps the door open to make connections between this goal and other related goals.<\/p>\n

2. Review department alignment<\/h3>\n

If you want to save time and resources, spend time reviewing how this goal might affect other departments; specifically, determine if it aligns with issues cropping up in those departments. In the case of data duplication, if an organization approaches marketing, sales, and client management as separate tasks, they miss what it’s all about: the entire customer experience.<\/p>\n

Suppose they approached this issue with a broader lens. In that case, they could implement a tool to combine each of these activities under one system, resulting in no data duplication and a smoother transition between the customer journey stages.<\/p>\n

3. Identify your KPIs<\/h3>\n

If you’re interested in measuring how well a solution is working (which you should be for several reasons, ROI aside), then identify core KPIs you can use to track a tool’s success. Keep them measurable, attainable, and specific.<\/p>\n

To continue with the example used above, KPIs for this type of solution might involve:<\/p>\n