Customer Success

Adoption Hacks

Adoption hacks are little tips and tricks you can use to stimulate adoption of technology. Actions that can include any number of activities, all designed to get users learning about, understanding and using features of a technology to get new value from it.

Activities can be anything from communication, learning components, social proof (showing how others are getting value) all the way to mandating something. All is fair when it comes to adoption hacks :)

I’ll start documenting what I am doing and what I learn about from others in the way of adoption hacks in posts like these.

At the moment, at Microsoft, I am focusing heavily on Microsoft Teams adoption. Teams is is seen as a platform play because it is the front end to a lot of other tools in the Office 365 technology stack as well as those outside through various integrations.

Teams is extensible and customisable so that you can reach users in their chats, channels, notifications and personal workspaces. A single app can provide one or more capabilities.

They enable users to make decisions and take action faster. They reduce context switching on important tasks. They create opportunities for collaboration around external content. They make for the perfect adoption hacking tools in other words 😁

Teams apps come from different publishers. 1st party apps are developed by Microsoft for Office 365 or Office workloads as mentioned and enable better together scenarios. 2nd party apps are those not built by Microsoft and are popular work applications enabled in a central location (the store you can access in Teams). Custom apps are built by your organisation to meet specif business needs. Just some examples below:

  • Bots help users get tasks done in conversations. I’m using https://zoom.ai/ a lot at the moment in Team channels and in direct conversation with the Bot and its great for things like setting reminders to follow up on actions that stem from conversations.
  • Tabs surface rich content within Teams. For example, O365 activity usage reports from PowerBI that can be discussed and actioned right from within Teams
  • Connectors allow you to post rich updates from activity in other applications into your Team feeds.
  • Actionable messaging adds rich interaction to your connector cards so you can act on new information you receive from ☝
  • Compose extensions allow you to query and share rich cards in conversations.

Conversational AI and the new dynamics of computer assisted collaboration and automation to aid adoption

One key learning we’ve had at Microsoft is that Bots, custom line of business applications that integrate business processes, and ‘ready to use’ applications integrated into Teams = stickiness and relevance that keeps users coming back every day and drive company-wide adoption.

One very specific example of this I am making use of with my customers to support end users is combining Teams and the Microsoft Bot framework to create Q&A Bots. Users can query the Bot and get answers to questions on Teams as well as other applications. In my case I am focusing on other O365 related applications but it could be used for any.

Here is documentation on some Bot service templates which can be used to get started building Bots and includes one on to build a Q&A Bot.

Dentsu Aegis Network have done a great job with this and you can read this article to find out more: Dentsu Aegis Network (DAN) builds Teams chatbot to drive internal adoption of new technologies.

This is such a great example of using new technology to support adoption of technology which I am hugely motivated by. I’ll be sharing more as I learn in this super interesting space.

Customer Success

State of Customer Success 2018

I attended Pulse Europe (the 4th) on the 8-9th November, an event run by Gainsight, a Customer Success (CS) technology vendor. They run the larger, main event in the US and I had the pleasure of attending last year where I captured the State of Customer Success 2017. So this is a timely update with a local, regional flavour.

Below are some general observations, main takeaways and then I captured notes from the sessions I attended (including my spin on things).

Chatting to the GM of the European office of Gainsight, Dan Steinman, I concluded that not only were Gainsight in the CS technology business but also in education. He agreed.

By that we didn’t mean the services part of Gainsight where they do offer education in support of their technology (see Gainsight University). I mean the education of an industry, a nascent one that needs it. It’s in their interest of course, to grow the category and also the industry within which it operates, mostly Enterprise Software [as a Service]. 

We also discussed how other industries could benefit from learning about the CS business, like car manufactures which I have written about before: The connected car vision is missing a few connections

I digress, the point is Gainsight take a leading role in informal education and for helping grow and share learning between individuals, companies, for the category and beyond. In this respect they are very successful and the event achieved that aim too.

Main take aways:

1. Tighter integration between product and CS, the move to self service and broader alignment

This was a theme driven not just by Gainsight on the back of their acquisition of Aptrinsic (more here). I’ve been seeing this more and more and driving it in my work and it is definitely a growing trend.

It encompasses two elements:
(1) greater collaboration between product and CS teams on high touch interactions with and insights from customers and,
(2) the built in onboarding, help and product adoption features in products that drive end user self service.

This trend is possibly the most evident but there is also the need, oft talked about, of greater alignment within customer service oriented teams and with sales and marketing teams.

2. Lack of innovation

I found at this event and on the whole that there are no real innovations being driven or presented other than in company products themselves (point above). I am writing an eBook / trend report about this and in the work I do mentoring startups and it is a main pillar I stress.

I think in an industry or category often struggling to find its way (see next point) we will have to do more to innovate and increase the impact of customer success activities. There is so much scope since the customer is at the forefront of everything and technology is changing so much and so fast. But innovation needs to come to business models, processes and people too.

3. Hype Cycle

The chart below was presented by Nick Mehta, CEO of Gainsight in one of his keynotes. Billed as a maturity chart, you could also easily see this as a hype cycle. I’ve been through the early curve twice in companies and seen it happen in others. I’ve also seen it happen with many technologies which the cycle most often refers to. I got an impression that as an industry we are in a trough of disillusionment.

Perhaps I’ve been in CS too long and lack the starry eyed optimism of a newbie but I’m saying this from the perspective of what I hear. I hear too much justification, disagreement on the function and its impact, arguments on who owns the customer, fights with other disciplines like customer experience, etc.

It just feels like the conversations are typically of the kind you find in the trough of disillusionment. It’s also a period characterised by lack of innovation as mentioned. That’s not  a bad thing. If I’m right, I’m looking forward to the slope of enlightenment for the industry as a whole because on this, I’m a true believer 🦄 🚀

Day 1 – 8 November ’18

Keynote – CS trends

This is a list that Nick Mehta, CEO of Gainsight ran through:

  1. CS drives sales. Prospects talk to customers and advocacy is key. So if you ensure customers are successful, they will act as willing reference points and that will help close deals. I totally agree with this and think it’s an undervalued KPI (from the vendor point of view).
  2. Company-wide priority. Top down involvement, endorsement and integration into operations is critical for CS success. Having been  a part of two reorganisations because this was not done right from the start, I absolutely concur. Where CS fits is still being debated though and the dust has yet to settle on that. More on this later.
  3. Career success. CS is one of the twenty most promising jobs of 2018. Growth in Chief Customer Officer’s was talked about and the fact they are primed to be the next CEO’s with some early examples quoted.
  4. Prescriptive. There’s a greater drive to commonality, standardisation and bench-marking. The periodic table by Gainsight below is an attempt to define this. With this lacking in many of the organisations I’ve worked in and with, it’s going to be a challenge to define for an industry but I agree it’s critically needed.
  5. CS movement. The growing attendance at Pulse conferences and book sales was pointed to as evidence of a growing CS movement. A little self serving perhaps but I can definitely feel an uptick in tempo over the years. The jobs market is also an obvious indicator and aside from CS being a most promising job, the number of openings I’m seeing is rising almost exponentially.
Periodic Table of Customer Success Elements – by Gainsight

CS in EU

  • Pockets of activity mentioned like London, Berlin, etc. For me they echo the startup centres in EU where often the bigger, better SaaS companies reside and thus CS naturally follows.
  • EU is learning and following fast and a couple of stand out companies were quoted as evidence of that – see next point (in brackets is what they are excelling in):
  • Slido (Voice of Customer); Intelliflo (ROI); ReviewPro (tech touch + human, e.g. 3 mails following sign up – if no open, human contacts); Signavio (customer health); Attraqt (exec alignment/sponsorship – internal); Response Tap (success planning); Workfront (risk management); Gainsight (stakeholder alignment – external).

CS and Product

This was presented by Travis Kaufman, VP Product Growth, Aptrinsic on the back of Gainsight’s acquisition of Aptrinsic. Ultimately its a reflection of the strategic direction Gainsight believes they need to take to grow the market and no doubt themselves. There are some compelling arguements.

  • Sales and Marketing have done it (quotes about Salesforce’s acquisition and integration of several marketing platforms into their offering), now CS and product need to. Hardly compelling evidence but some other drivers were mentioned which do make sense.
  • Driven by
    — Data. Drive new opportunities based on usage data.
    — Scale onboarding by extending the journey into the app.
    — Influence product roadmap based on data not opinions
  • Product is way to scale CS engagement for high volume, low touch accounts. I’ve written about this multiple times here and here.
  • Feature / user feedback built into the product and covering onboarding as well as ongoing use will expand.
  • Sales and marketing consolidation will be followed in the CS / product world is the firm prediction – I’m rooting for this outcome.

Accenture analysis

A talk on why CS is the new growth mantra which is based on the main C-Suite challenge around delivering profitable growth. 500 executives were surveyed for the insights amongst 10 brands: Microsoft Azure/O365, Tableau, Symantec, Adobe, Salesforce, SAP, Cisco, Workday, Dell-EMC, Marketo.

  • A customer’s level of trust in a brand is the single most important 
    factor in a renewal decision (55% said so). Trust is the #1 influencer and counts no matter how long a customer has been buying a product or service. 
  • First impressions count – deployment (installation, activation and setup) is the most important CS activity. It is 2 times more significant in determining whether a customer will renew. A bit of confusion on their part here. As pointed out in various other presentations over the two days, I would separate out CS management from deployment activities and for me its much more about how you launch to end users: Launch like a boss – bringing consumer startup practice to your enterprise technology platform.
  • Longer term customers value access to self service tools and the ease of renewal – 73% think its important and it can have a 20% influence on renewal decisions. I love this since it validates a lot of my thinking: Role of Self Service in Customer Success.

Must win moments for a CS team

By the author of The Three Value Conversations: How to Create, Elevate, and Capture Customer Value at Every Stage of the Long-Lead Sale. This presentation was about a messaging approach for customer renewals, price increases and upsells. It was part based on a quote referenced by Nick Mehta (see screenshot) that renewals are really resells. It also emphasised the need to tell a better story. Great example of Malcom Gladwell’s Tipping Point book success – he wasn’t the originator of the theory, Morton Grodzins was. But Gladwell popularised the theory through better story telling. Other points:

  • Selling (acquisition) stories need to be different to staying (retention) stories because the latter reinforces preference stability as opposed to disrupting change / status quo bias.
  • At point of renewal, there is no sense selling on new features/functions which many sales people do, but rather on reinforcement.
  • Some really good scientific and evidence based reasoning (neuro science, behavioural economics, social psychology and decision science) on why good storytelling works. Totally get this having done several sessions on storytelling before – key CS skill I would say.
  • Focused around the customer retention path post sales (why stay), but also answering questions around why the customer should pay more and evolve (expand)
Customer Deciding Journey

Success Planning

ResponseTap and Micro Focus went through some of their common approaches.

  • No common view of desired customer outcomes between sales, deployment, onboarding, etc.
  • Single source of truth needed – one document
  • 3 time lines created for a plan (short, medium, long)
  • Everyone agrees on common outcomes before plan is approved – sales, CS, support, etc,
  • Benefits/Learning:
    — Having a common customer journey between departments
    — Tracking NPS at different stages is useful and should cover various journey phases: sales, onboarding, then service/support and CSM
    — CS should review internally feeding progress back to the organisation
    — Improved cross team collaboration and decision making
    — Better renewal rates after implementing

Self Service

This applies mostly to the support function and was presented by someone from Insided.

  • Most customers don’t want to contact companies for support (72%, Forrester) so important to address well from a self service point of view.
  • Free trials and freemium customers also need support
  • Automation is not the answer for everything. 7 out of 10 interactions with chat bots fail.
  • Including community responses in help centre search responses is good practice – Google quoted as example.
  • Peer to peer answers are viewed as more trustworthy. Best is for the company to focus on company and FAQ material and the community, the long tail of other queries. Coincidentally I just came across another research based post that bears this out: Why Online Communities Are The New B2B Superpower
    — From the post: online communities are the third most common digital engagement channel for post-purchase customer feedback or support (after email and website).
  • Support or help in product is best and voice queries are rising (digital assistants).

Scaling user onboarding but keeping a personal touch

Again this was presented by Travis Kaufman, VP Product Growth, Aptrinsic. I agree with this approach from a scale, tech touch point of view. The only problem I see with it is the potential over emphasis on features. This can be a distraction from the all important emphasis on business outcomes which should never be forgotten.

  • Most of the user experience happens within the product and so it’s a good reason to focus on this which I totally agree with.
  • Onboard users to aha moments – key features you want to emphasise.
  • Onboard to new features as they release
  • Re-engage users to complete critical tasks
  • Product teams need to know what feature adoption rates are and also what the qualitative feedback behind that use is. Work with CSM’s to leverage this and drive or accentuate further use. 
  • Derive personas for specific use cases. Ask in qualitative surveys or deduce from the use of a feature and who you intended it for.

The quest to be LAER efficient

From the President and CEO of TSIA (Technology Services Industry Association) J.B. Wood, a great overview of the industry as a whole. Also touching on the broader opportunity with XaaS (Everything as a Service). The TSIA is an association that works with the top 400 tech companies to understand what they are doing and what impact that has.

  • LAER: Land Adopt Expand Renew. Where XaaS meets profitability – see operating framework in slide below.
  • 5 key markers on the path to LAIR effectiveness which is comprised of 4 stages – see this also in slides below
  • Monetisation of CS falls in the effective phase. Allows for investment in better CS activities
  • Point made that Cost of Sales and Marketing (COSM) is too high in cloud companies because customer acquisition costs (CAC), customer expansion costs (CEC) and customer retention costs (CRC) are based on activities being driven by traditional sales and marketing teams.
  • If the CS org were to manage activities covering the latter two it would drive down COSM. Fair point and this lead to a lot of discussion around the CS org owning renewals, upsells and expansions – the standard discussion that always comes up and was covered in other talks/discussions. On this topic I feel like the verdict is still out even after years of discussion. See also Nick Mehta’s point on this from his keynote on Day 2.

CEO’s view of CS

A panel discussion between CEO’s of Futrli, Precursive and TaskRay facilitated by the CCO of Box, Jon Herstein. All had robust CS functions so naturally the input was mostly positive.

  • What can you do to make CS successful? Spend time with the team. Understand the problems customers and CS org experiences. Get quantitative/qualitative feedback on ideal CS function then build it. Get people to think like customers – spend time there.
  • How to avoid silo’d CS function and ensure cross company accountability? Success hacks across functions. Have hypothesis that will achieve CS outcome then try prove. Non traditional customer facing roles spending time with customers, e.g. engineers. Love the hacking idea – I’ve written about this before: Success Hacking
  • Where will you invest? Automation of tasks so CS can focus on value work. Love it – say no more.
  • Any questions from VC’s around CS? A resounding YES around what is being done and how. They want insights into CS like scope of effort, ration of CS individual to customers, on what, etc.

Day 2 – 9 November ’18

Keynote, Nick Mehta, CEO Gainsight

Rumination on the raison d’etre of the CS org and where and how in the organisation it works best based on Gainsight experience. All makes total sense and as it should be for now.

  • Started on the debate over CS being a role or strategy. If not solved there’s a danger we lose the initiative. It should and can be both.
  • The CS charter: CS (Customer Success) = CX (Customer Experience) + CO (Customer Outcomes). CS > CSM (Customer Success Manager), in other words, Customer Success encompasses CSM’s and many other areas besides.
  • Lessons from Gainsight:
    CS and Renewals separated at Gainsight. Different skills and tasks and difficult to do both well.
    CS and Account Management also separated. Expansion happens off the back of adoption, outcomes and different audience relationships that CS build.
    CS and Services. Handover opportunities and knowledge for skilled teams from CS to Services to implement deep work and methodology (project management).
    CS and Marketing. Building the right outcomes and thus advocates happens in CS, formal references and stories developed further by marketing.
    CS and Support. Strategic, exec stakeholder and impact work is for CS. Technical skills, process and speedy results should be covered by Support.
    CS and Product. They have so much common ground: adoption breadth and depth; customer feedback, etc. Too often they have different ways to measure and silo’d thinking. Again example of sales and marketing and need to combine CS and Product which Gainsight are doing.
    Exec team and CS. CS provides insights to customers, execs can amplify, drive resources, decisions and problem solving, etc.

Sirius Decisions: B2B alignment and impact on business performance

Sirius Decision are a research and advisory company focused on demand generation and performance measurement. They presented findings from various bits of research.

  • B2B Revenue Engine expectations have been increasing, challenging organisations to drive stronger alignment across customer success, sales, marketing and product teams.
  • The historical view of alignment predominantly around the buyer is no longer sufficient to drive growth and profitability rates ahead of the market and the competition.
  • Customer engagement is one of the six critical areas of alignment that B2B revenue leaders must focus on.
  • Achieving and maintaining alignment within customer engagement initiatives requires a roadmap to realise the business impact it can deliver to the organisation.
  • Engagement scoring (for all the various customer interactions) highly sought after by CMO’s

Customer Success at Cisco

Alistair Wildman, Head of customer experience EMEA was interviewed on stage. This is what he shared after being there and in his position for 6 months.

  • They call it customer experience which includes CS. Covers other functions: support, service, etc. So it’s the whole post sales experience.
  • Hardware has been wrapped up into services subscriptions model
  • 80% of post sales efforts happen through partners – they are key in strategy. Not like Microsoft apparently although not true. Good analogy of a pit stop, one tyre is changed by Cisco, the other three by partners.
  • They have account based CS which is a direct engagement model and technical CS which will work with partners on customer challenges.
  • Data is key. They are still in the process of building dashboards to understand usage which they think will take 2-3 years.
  • Lessons from Salesforce (where Alistair worked previously): Hire for skill not for count. Senior people that know how to do the job. Develop skills through customer engagement simulations with product for training.

Data science at Gainsight

I attended this session thinking I was going to get insights into the cutting edge practices adopted by Gainsight but it was more like a basic intro to data science. Here are my brief notes before I left the session.

  • We are heading into the age of predictability which is where we want to be – anticipating trends, heading off negative ones, leveraging positive ones. 
  • Tasks to consider are: identify the nature of your data sources; quantify and get a score for your data outputs, understand and plot maturity stages, move up the scale.
  • Prescriptive analytics understands causes for outcomes and prescribes solutions upfront. Needs AB testing of playbooks. This is the kind of deep level insight I was hoping for but we merely skimmed the surface.

How do VCs see CS

Joyce Liu (Dawn Capital), Paul Morrisey (Battery Ventures) and Stephen Millard (Notion Capital) were interviewed by Igor Beckerman (CFO Gainsight).

  • Usage and adoption is a clear priority early on. Value comes later. Customer advocates seen as important and so too Customer Advisory Board’s (CAB).
  • Metrics in the boardroom. Predictability and causality key. What are targets likely to be and why are they what they are.
  • How much to spend on CS. Depends on whether the company has big end customer’s vs small end customer’s. Onboarding should be a big investment. Where early value is seen with correlation on outcomes, investment goes up. CS can be a cost centre in the early days but profitability is important later.
  • CS leaders. Some of the best were waiters in the past – they all have a love for service. For larger companies, those that can have quality conversations across a broad range (multi functional). Systems thinkers and those that can take multiple perspectives (customer, industry, vendor)
  • CCO to CEO. If former responsible for 90% of long term profit that stands to reason it will happen.
  • Decision factors for investment. Talking to customers to get their views on the company. Tools and processes in place are also a key decision factor.

Bonus

Brain Cox came and spoke on astronomy and the result was 🤯 Some excellent perspective after two days of intense CS overloading.

Customer Success

Role of Self Service in Customer Success

Customer success teams were put in place in technology SaaS and subscription companies to ensure that customers are successful in their use of the technology they invested in. They have become a core part of ensuring the customer derives long-term value and ultimately stays with the vendor (in other words renews the subscription).

But has the vendor and customer become too reliant on them?

I am a customer success manager. Far be it for me to be talking myself out of a job. But actually that is the point. If I could get to it (that point) I would have done my job I think.

Especially with technology products you would think that the technology itself would play a major role in helping users use it and get value out of it. And with the advent of AI, machine learning and automation, even more so.

Enterprise technology is quite a different beast though. The complexity of organisations means that technology use and adoption is not straightforward. It’s dependent on many environmental factors. Like culture, organisational complexity and maturity, etc.

Factors that technology is not good at dealing with but humans are. These have to be factored in, so to speak, in terms of how you ensure use and value creation of a technology in an organisational context. So I don’t see human effort going away anytime soon.

Still, lets look at how technology can and should help to alleviate burdensome tasks best left to machines.

In my mind, a lot of the help technology provides is ultimately geared towards the user being able to self help or serve. And its not just about the end user but also those responsible for end user adoption – the people customer success managers typically work with. I’ll call them adoption managers for sake of clarity. They are typically the ones served by Customer Success Managers most directly but as you will see in the next section, I certainly am driven to make them as self sufficient as possible too.

Technology’s role

By this I mean two things:

  1. What role the technology itself provides with things like built in help and support from onboarding guides to a help manual that can be contextualised with key features as well as be generally available to users.
  2. What role any other technology provides to support the end users and adoption managers. For example, as part of recent hackathon efforts at Microsoft where I currently work, the team and I all won first at a local UK level and then at a global level, for a solution intended to support customer success managers and adoption managers. We called the solution Journey because that is what adoption typically is. Here are a couple of slides from our pitch deck which hopefully explain:

The origins of the idea and also current manual efforts are documented in this post I shared on LinkedIn: Co-owning success with Office 365 customers

Validation has come from winning the hackathon awards (at the global level we won in a field of over 24 000 competitors and 5 000 entries). We also received solid validation from customers we are working with on the current manual efforts mentioned and all new customers we introduce it to.

So it seems there is appetite for this gap in the market. You can watch a very short demo of what we pitched and won with and answer 3 short questions in a follow up survey here if you like – it would help with further validation.

AI and Automation

According to a study on Customer Service trends:

The future of customer service is about giving customers more control and better access to operations, so they can build their own experiences in real time. To do this, in addition to investing and moving customer service to cloud-based operations, they focus in on how to work better with automation.

I am totally in agreement with this as I wrote in this post: The Future of Customer Success is Not Human. Even though the context of the study above covers customer service trends which is very different to customer success, it is still broadly applicable. The domain is the same.

I think these activities are going to continue to expand in use and value, especially to alleviate customer success manager efforts where they are overloaded and too much is expected of them and where bureaucracy has crept in.

Technology can help reduce bureaucracy

In the post where I wrote that the future of customer success is not human, I quoted a study on bureaucracy. It has customer service, in which again I would suggest customer success falls, at the top of the rankings of roles and fields where bureaucracy has crept in (list of rankings pasted again here). Being a practitioner I would concur with that and the point I made then and again now is that technology can help avoid this.

Of course a large portion of the problem stems from overzealous management ptractices which is not something technology can help with. But by and learge I see it as a valuable counterbalance.

What needs for human intervention will never go away?

Assuming that technology can take up a lot of slack and reduce bureaucracy, what does this leave the customer success manager and those responsible for adoption to do?

Well it will be to focus on those intractable problems that I mentioned earlier technology will not be able to help us with and will become increasingly needed. Thorny problems and challenges that can be overcome to improve the customer experience. Those that require and will take imagination, creativity and innovation and will focus on the challenging art of managing people.

I have two separate posts on these topics that elaborate on that if interested.

Customer Success

The Future of Customer Success is Not Human

It’s a pretty provocative statement, I know. To be clear, I’m not suggesting humans won’t be involved any longer or that there won’t be a need for them.

If anything, humans will be liberated to carry out the high-touch, heavy lifting work we are uniquely qualified to do and should be focusing on instead, like complex and creative problem solving, relationship building, strategy setting, and more.

The work that is repetitive can be automated and managed by AI, bots, etc. Things like onboarding new users, growth hacking (tracking use and suggesting amplifying or mitigating actions) and general product optimization, will be able to be programmed and managed by these advances.

This is particularly relevant when faced with the increasing burden that a growing rate of bureaucracy places on individuals in organizations, especially those like CSMs, who are most directly involved in creating customer value.

Based on this HBR study (see chart), you can see that customer-facing roles have the highest rates of increase in bureaucracy. Mitigating the increase in bureaucracy for these roles by implementing tools with automation and AI capabilities could be an ideal solution.

To provide some context, this research will be a part of my new eBook – I’m exploring this angle in a chapter (see point 8).

My heading is not so alarmist when you consider the claims that robots and AI are going to be the drivers of productivity in just about anything in the near future. Lawyers, doctors, pharmacists, and programmers are all going to be affected. In my opinion, Customer Success as an infant profession is not going to be immune either and it’s the way it should be.

To reiterate, I’m not saying humans won’t have a role. I’m saying they can and will, but it will be a smaller one and much more focused. I’m not sure to what degree – maybe the 80 / 20 rule will apply? If that is the case, there is still the potential that humans can play a disproportionately large role in daily CS operations.

The human’s role notwithstanding, in this post and indeed, in the chapter, I want to explore how AI and automation are already starting to play a role and how that will be enlarged over time. Another factor to keep in mind is the function of the product itself.

The product’s role in customer success

To explain my last point briefly, I am referring to the role an excellent product plays, one with superb usability, that delivers critical business benefits, etc. No amount of AI or automation is going to solve the issues that emerge when a product is convoluted to use, and creates mountains of arduous and unnecessary work for users. Metaphorically, it’s like pushing a proverbial boulder up a hill and this is made worse when there is no clear business benefit.

To take it one-step further, people have even anticipated “anti-active usage” products. From this excellent article, The Next Generation of SaaS Won’t Optimize for User Engagement:

“With anti-active usage products, you don’t necessarily need to use the product to get something done because the product (1) understands the problem, (2) works out a solution and (3) outputs a result. Anti-active usage products don’t need human interactions at any level of their value-chain.”

I mentor startups, and several of the ones I have worked with are already moving into this space. TIQ probably best illustrates this premise – their software facilitates time tracking by connecting to the tools you use to get your work done. TIQ automatically creates an overview of the time you have spent on separate documents, emails, meetings, and other activities, and all you do is confirm (tick off) what gets logged. The objective is to spend less time on the function AND using the tool, reducing the need for manual inputs entirely.

Current state of activities

My interest in this whole area was piqued when I listened to Derek Roberts, the Director of Services, Strategy, and Operations at HubSpot, speak at Pulse 2017 (the annual Customer Success conference) earlier this year. I documented my learnings from the event, including a summary of his talk, here: State of Customer Success – Learnings from Pulse 2017. (Here are his slides and audio, if you’d like to see more details).

I then, coincidentally, bumped into the folks at Strikedeck, who are in the Customer Success space as well, and are doing an excellent job in this area. I arranged for a few conversations, and a demo of their tool, so I could find out more.

There are two things Strikedeck focuses on, amongst many others, that I wanted to explore in detail, that are relevant to this whole area.

Integrations, Data, and Dashboards

Strikedeck seamlessly integrates with at least 50 connectors already, and is architected to easily be able to build out more, as long as the other systems have open APIs, web hooks, etc.

They integrate with marketing automation, CRM, event trackers, call centers, billing systems, and many other data applications so you can reach out to customers at just the right moment and see all their information in one place. Connecting to Salesforce, Marketo, Zendesk, Google Analytics and more is entirely self-service, and done in a few clicks. Each integration can be completed in less than 20 minutes.

This is fundamental to be able to start some of the necessary automation work, and because you need access to the data on product usage to be able to act on it.

It is all presented in easy to view and modify dashboards – screenshot below:

CustomerHealth.png

In my mind, the three steps I outlined in the sub header are the critical setup to follow sequentially and have available as features to carry out the necessary work.

In the demo, I also noticed that customer experience can be tracked in terms of progress across predetermined paths. It can be taken from other systems (renewal data from CRM), but can also be included manually from input into the tool upfront.

This last area above fits nicely into the role I see Customer Success Managers playing in determining the optimal customer experience that I cover in my eBook. After all, to properly affect optimal customer experiences, you need to be able to map them and track progress on the path.

Detailed segmentation is also possible in Strikedeck, with relevant slicing and dicing of views. This then leads naturally into the next important area in which automations are activated and set up.

Workflow, Tasks, and Playbooks

An automation workflow allows you to activate email campaigns, survey series, slack & text messages, schedule meetings and calls, activate in-app notifications for your customers, create tasks for your Customer Success teams, update customer data objects in any of the target sources (CRM, Help Desk etc.) based on the trigger criteria set (support ticket, product usage, stakeholder role change, billing information, and more). This functionality can be customized to display the triggers that are critical in your business use cases. Some screenshots below:

MacBook - workflow recipes 2NoMac.png

WorkflowRecipes.png

Playbooks are another area that support CSMs in how they automate their activities. Playbooks are essentially an execution script of tasks, notifications, and escalations with relative dates and dependencies. Playbooks ensure consistency and standardization of best practices across the organization.

The best way to think of a playbook is to see it as a set of automated workflow actions that are launched as soon as the first trigger is activated. You can specify if the workflow is a task or action, set priorities, determine dependencies, and create timelines for completion.

Playbooks can be used in situations like:

  • Dissatisfied Customer – Triggered by a low NPS or support ticket
  • Product Usage Drop
  • Account Renewal
  • New Customer Onboarding

playbooks2

AI, Bots, and Beyond

I asked Strikedeck about these areas of functionality in their product, and they have some really exciting features coming up:

Coach: A Bot that lives inside the product and is a coach to the users of the product, helping them get more ROI from the product. Based on how a user is utilizing the product, the Strikedeck ‘Coach’ will automatically suggest what the user can do to improve usage. This can be activated through a ‘Coach Me’ button inside the product. The ‘Coach’ is rule-based initially, and over time learns to give better suggestions.

Zen: A Bot (initially on Slack and Gmail) that provides information on a customer. Anyone in the organization can ask a question, like – what’s the revenue for Customer A? or When’s the renewal due for Customer B? or Which customer could be a good reference advocate for telecom industry? – and the bot will search the database for the correct answer so CSMs don’t have to do the research themselves.

I can see a combination of trends coming together to facilitate how a user will get value from a product and how this will allow Customer Success Managers to expedite help for the user.

What do you think – future or fantasy?