How To Measure the Value of Internal Tools

Chang Liu2 Aug 2023

Problem

Square's Seller Experience org runs internal tools: a communications platform, a customer data platform (CDP) and the Amplitude data platform, which data scientists use to build dashboards. Building, maintaining and using them costs time and money, yet they have no direct link to sales or revenue, so their return is hard to show. Often the usage data they need was never logged, because nobody planned for measurement at design time. Without metrics, owners cannot tell whether a tool is adopted, what to improve or where users struggle.

Example from the article: the CDP merges data from many sources into one hub for internal users. The post names a data infrastructure tool like the CDP as a product that product metrics apply to.

Solution in brief

Sort internal tools into groups by the metrics they need, and track two kinds of metrics for each. Product metrics describe how users adopt and use the tool. Operational metrics describe how well the team behind the tool performs. Plan the logging early so the metrics can be computed.

Questions this case answers
  • How to define a standard yet flexible metric set for products whose value cannot be tied directly to revenue
  • How to design usage logging and user-to-team mapping so adoption can be measured after launch
  • How to measure whether an internal tool is adopted and worth its build and maintenance cost when it has no direct revenue link
  • How to choose a standard set of metrics for different kinds of internal tools without forcing one metric on all of them

Tools and methods

  • Product metrics — adoption, engagement, satisfaction and business impact, viewed from the user's side
  • Operational metrics — internal impact, service level and reliability, viewed from the tool provider's side
  • Usage logging and user-to-team table — the data layer that makes the metrics computable per team
Continue reading — it's free

Google or a one-time email code. No password.