Why we shouldn't use these productivity metrics for project execution

Many of these productivity metrics are output-based and not outcome-based indicators

We should move away from these metrics, which are based on output rather than an outcome.

--

--

--

Tech enthusiast, Project Management. Interested in Complexity science, Economics, Psychology, Philosophy, Human Nature, Behavioral Economics, almost anything.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Object counting with Kerberos Cloud

Native Android in Unity

Learning R | Part 1 | Basics of R & RStudio

Modular Waypoint System

{UPDATE} Bus Simulator 2015 Free - New York Route Hack Free Resources Generator

Distributed Request Tracing

Traces Landing Page

Vim and Git

How is security managed in Kubernetes clusters?

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
Ranjit Damodaran

Ranjit Damodaran

Tech enthusiast, Project Management. Interested in Complexity science, Economics, Psychology, Philosophy, Human Nature, Behavioral Economics, almost anything.

More from Medium

Building Teams Remotely

How to Develop a Software Product in a Faster and Cheaper Way with Fewer Mistakes

The benefit of having Software Developers that think like your customers.

What is this “DevOps” thing, and why should I care about it?

This image comprises the cultures and practices that define DevOps.