2 Comments on “Metrics for Technical Account Managers (TAMs)

  1. Great topic! There are a couple of things I like to measure TAMs on – one is the support backlog. I would expect a TAM to be pushing (cross-functionally if necessary) for resolution of their customer’s issues and keeping a high level of visibility on them. If a TAM is newly appointed to an account, I would expect the backlog to trend down. If they have been on the account for a while, I would expect the backlog to stay below an agreed on threshold.

    Another metric is project success. If a TAM is at all involved in product installation, upgrade, patch, etc., I would track the success rate of those projects. A TAM should be the customer’s advocate internally to make sure a patch was thoroughly tested against the reported bug before installing, for example, and that the people executing the steps are trained, and that project timelines are vetted (don’t tell the customer it will require 30 minutes of downtime to upgrade and then it takes 2 hours). Sadly, I’ve seen these types of projects fail for many reasons that should have been caught internally before the product ever went to the customer, and the TAM is a good backstop to reduce this type of failure by asking the right questions and holding internal teams accountable for their answers. I think this is best as a team metric to drive the proper rigorous internal processes into place (which can take a while), but it can be used as an individual metric if one individual’s performance deviates from the team norm significantly.

    • Love your ideas, Jennifer. I can see how the TAMs can team up with the support managers to keep backlog in check.