At the center of many college campuses, there’s a grassy rectangle known as the Quad. Sidewalks and paths crisscross this space for commuting, picnicking, protesting, performance, etc. Look carefully and you may notice long stretches of worn grass around the Quad. That’s where students actually walk. That’s where the sidewalks and paths should have been.
The Quad is a decent analogy for usage metrics. Customers in B2B SaaS may not necessarily vocalize feedback. They’re busy. They aren’t UX designers. They can live with some clunkiness. Like students at the Quad, though, they use certain sidewalks and not others. They follow paths through the software that you never intended.
B2B software companies use tools to measure the paths taken and not taken. But what do usage metrics really tell you about your users and product?
CONTEXT FIRST
When evaluating customer health—the probability that subscribers value a platform and will stick with it—nothing is more objective than usage. In my experience, the customer who says they “love” the product but doesn’t spend time in it is just being polite.
That said, the meaning of usage depends on the intent of a product. Social media companies try to maximize time spent on their platforms because that equates to more ad impressions and therefore more revenue. Apps like Wordle, for example, release one puzzle, game, or task per day, so consistent, daily completion is more important than session length.
Usage varies in B2B software, too. My team at Filevine values high usage because we provide the space where legal work happens. Conversely, an automated product recommendation engine for e-commerce sites might notwant to see heavy administrative usage, except once or twice a quarter when someone reviews the data and adjusts settings. The more telling usage metrics could be the rate at which users click and ultimately buy recommended products.
Context provides assumptions about how a product should be used. When usage metrics deviate from those assumptions, the users are probably signaling something important.
USAGE BLIND SPOTS
Recently, I was looking at metrics from a Filevine user who completed 6,500 actions in one day. Keeping context in mind, that means a) our platform is a big part of their day and b) completing work means taking numerous actions in Filevine. Good, right? Well, not until we consider several blind spots:
1. A person may use your product daily yet churn suddenly. Unhappy customers might use your software because they have no better alternative. They may gripe about your platform and cannot wait to cancel their subscription. Despite their high usage, your platform could be the bane of their existence. One thing you can do is cross-check usage against Net Promoter Score or customer satisfaction surveys so you can better detect these disgruntled users and intervene in time.
2. A customer has high usage metrics because they are inefficient in your platform. What if someone clicks 500 times in a single feature that’s meant for a relatively quick and non-repetitive action? I would think something is buggy, confusing, or frustrating. That’s a signal to investigate whatever is spinning that user in fruitless loops.
3. The time spent in a feature is disproportionate to the value it provides. For example, I don’t think any small business owner wants to spend six hours weekly on their accounting platform generating and sending bills. So how long should 10 invoices take? If a user spends two or three times the average amount of time on that task, determine why. Is it a product problem, a training problem, or a quirk in their billing model that creates friction?
4. Power users ignore a feature you’d expect them to use. Judges often ask lawyers to deliver or do something within 30 days (how helpful…), so one widget in Filevine lets someone enter 30 days from today and find out what date that is. We notice that several happy customers use an outside widget for confirming dates, unaware that we have a well-liked solution. That could mean that we’re failing to educate customers or perhaps burying the widget somewhere they don’t expect to find it.
These blind spots illustrate that usage data—whether it’s the clicks in a platform or the flattened grass on the Quad—can only tell so much of the story. And while that fragment of the story probably doesn’t contain a solution, it can help point to a discussion that is worth having with customers.
DON’T JUST STARE—TALK
At first, it may feel odd to tell your customers what you saw them do in the product and wonder why they did it. But that’s where the real learning can happen.
The customers who follow the official sidewalks meet your expectations given the context. It’s the customers wandering off the path (or dancing a little funky on their own) who have something to teach you. Maybe they’re even hoping you notice them.
The burden is on you, the vendor, to discover what usage patterns really mean in the mini universes you create. The point is, don’t just stare. Don’t wait for customers to tell you what’s wrong with your product or churn. Search for their unspoken frustrations in the data and either fix the problem or ask for a conversation.
Ryan Anderson is the founder & CEO of Filevine, a project management, collaboration, and legal case management tool for lawyers.