Bridging Tech and Business Metrics

How to work backwards to tie technology value to outcomes

In Maine, a place in the far northeast regions of the United States, people are often heard saying the following when giving directions:

“You can’t get there from here”

If you spend time in Maine, getting from point A to point B can be daunting. GPS has helped in today’s world. If you have ever traveled through remote regions of the world however, you know that the roads are not always as straightforward as shown on the app.

“Begin with the End in Mind”
-Stephen R. Covey

Starting from the end is not so uncommon. This principle is the second habit of Stephen Covey’s The 7 Habits of Highly Effective People. One of Amazon’s fundamental approaches to serving customer needs and developing product is to “Work Backwards”. Even in my math classes, the idea of working backwards was a common approach to solving problems.

Image for post
Image for post
  • Level 2 (“L2”) — Metrics derived as a direct implication of the use of the technology, such as cycle time from story point to deploy or MTTR rates over time
  • Level 3 (“L3”) — Metrics tying technology to business goals, such as time to market for new feature or customer satiscation for new feature or product
  • L2 metrics cover reduction in Jira tickets, code commit rates for newly onboarded developers, and higher rates of code sharing
  • L3 metrics range from lower defect rates, customer ratings on feature or app, increased product availability
Image for post
Image for post

Episode #10 — Building an operations sensibility in developers with Christine Yen of

Podcast episode with Christine Yen of

Thoughts on developers, digital transformation, enterprise agility, community building & software engineering culture. Author 👉

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store