Output, Results, and Things That Are Difficult to Measure

This is a brainstorm rather than a well thought out (or thought out at-all) blog post. I briefly considered a tweet stream, but wanted to give my few followers a break.

I’ve been thinking a bit recently about what it means to be productive on a software team – or how that productivity is viewed, tracked, or measured. I’m not going to dive into performance reviews, as those have a lot more moving parts and dynamics – but just the general view of how we view result – or output from any individual, and any organization.

Traditionally, “output” is a bullet point list of things-you-did. This is output – or production. It’s certainly measurable, and if someone has no output or results, there’s likely an issue. But there’s another kind of output that doesn’t get talked about enough. What about the person who makes other people better? The person who coaches, mentors, and finds ways to make people around them productive?

Jessica Kerr, calls this attribute ‘generativity’

I like the term, and have begun using it recently…which is probably why I’ve been thinking more about this over the past few days.

Some points to consider (and potentially discuss):

  • Output is linear. I can produce 0 things, and I can produce n things. More things == more production. (Note that all produced things are not equal).
  • Generativity can be positive or negative. I can help the team achieve more than the sum of their parts, or I can be an asshole and hold everyone back.
  • You can be both Generative and Productive. While you can be Productive without being generative, I don’t know that it’s a good thing to be Generative and not Productive. More on this below the bullets.
  • Generativity requires leadership – this means that generative people tend to be more experienced (and that less experienced people may focus entirely on output).
  • For those who care about measuring, Productivity is much easier to measure than Generativity.

I don’t know of a system that’s done a decent job figuring out how to measure the non-tangible output (Generativity) of team members. I’ve seen highly generative (IMO) people viewed poorly because their output was difficult to measure (which is why I included the third bullet above), but I think generative people are critical for success in most teams. Of course, the best generative people I know also produce some measurable results as well, so perhaps that combination is necessary.

Similar Posts

  • The truth about meetings

    I’ve been talking about meetings recently at work (I’m still giddy that have far fewer meetings to attend these days). I’ve had discussions about meetings for at least a decade, and they’re all about the same.People grumble about ineffective meetings, while others grumble about too many meetings. Some grumble about who should be in the…

  • Who owns quality?

    I think I’m finally caught up and recovered from my brief North American tour last week. While it was fun to present at two conferences plus a customer talk in four days, I missed out on a the second day of both conferences, as well as the opportunity to meet nearly as many people as…

  • Specialists and Bottlenecks

    A few episodes ago on AB Testing, we talked about the Theory of Constraints and related topics. A lot of us frequently see “QA” or “Test” as a bottleneck, even on Agile teams – where several changes may be waiting for signoff from the designated quality or testing specialist before being deployed or marked as…

  • |

    Five for Friday – January 12, 2018

    I’m finally reading Pat Lencioni’s latest book on Ideal Teams. I’m a huge fan of Pat Lencioni’s business novels, and enjoying this one just as much as the others. You’ve probably already seen this article on testing microservices. I shared it with my team this week, and think it’s a good read. All About Lean…

  • Career++

    Chris Mcmahon once (I think after reading this post) described me and my test role at MS as being like a “tenured professor” – that I have the freedom to choose what I do and choose how I go about it (as long as I show value). I enjoy this role, and think I’ve been…

5 Comments

  1. If you don’t know what to measure how do you know what behaviors to promote? They’re the same, right?

    Related topic: I think that Fredrick Winslow Taylor tried to measure the wrong things. That explains how he was badly received.

    Another related topic: I think Edwards Deming had success with continuous feedback about how the system was behaving instead of minutia (and even called out things like performance reviews as a sin).

    I don’t have the answers you want but I thought shaking the cage a little and tossing in related ideas might inspire you to where you’d like to go.

    Also, unrelated: “negative generativity” sounds like stopping the line in lean manufacturing. I don’t think it’s so bad in that context.

    1. I think you can promote behaviors without measuring. I.e. I can praise your work (thus promoting it) without measuring (or counting) how many times you do praiseworthy work.

      1. Peter Drucker said “what’s measured improves” and I think he’d argue that you’re measuring in that scenario even if you’re not keeping track of the results. It can be measurement even if you don’t put a number on it and I assume you determine what’s praiseworthy somehow rather than just praising everything, right?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.