How do we change the way we assess performance and still harness the benefits of OKRs?
A few thoughts on why performance management and OKRs are hard and what to do about it 🧵👇:
Problem: If we connect OKRs to financial rewards we risk stifling creativity and innovation due to low-ball key result targets. Teams will set targets they’re confident they’ll hit because it gets them a raise, a bonus or promotion.
Changing performance management criteria is hard. We have decades of historical inertia that reward production.
Another problem: production targets are binary. Your team either shipped "a thing" or they did not.
Binary targets are easy to measure.
And if something is easy to measure it's easy to manage.
Organizations can easily take a look at a team's output and assess if they produced "enough" code/features/products to warrant a reward.
So we find ourselves in a position where financial rewards incentivize mediocre output that doesn't necessarily provide any customer value while also having to rewrite decades-old performance criteria.
There's a 3rd problem: changing performance criteria for long-term employees effectively amounts to moving the goalposts for them after years of working towards the old rewards. The attrition & culture impact this can create is, at best, unpalatable to most HR departments.
So what do we do? Two things (at least):
1. Decouple OKRs from financial rewards
Using money/job titles to drive outcomes ensures your teams won't push too hard or *be* pushed too hard to innovate. Why risk a failed experiment when the safe thing will hit the target?
2. Reframe what being "good" or "successful" at your job means
Traditionallly success measured an individual's contribution to the production of a product. OKRs, a team-based goal setting approach, rewards collaboration, learning and team-wide success, not individual heroism.
Consider setting performance criteria that measures/rewards:
Learning - how many and what learning activities a team does
Evidence-based decision making - what criteria is used for every decision
"Closeness" to the customer - what are teams doing to stay close to the customer
Collaboration - how well are teams collaborating with each other and sharing knowledge
These are just a start. I'm not an HR expert but it's clear that these things have to change if we hope to build agile, responsive, customer-obsessed companies.
How else would you reframe and reward success on a team that works towards positively impacting customer behavior?
I write regularly about #OKR on my blog: jeffgothelf.com/blog and in my monthly newsletter. You should sign up for it here:
I once met a team struggling to get their leaders to hear and incorporate user feedback on the Android app they were building. The team would actively test their ideas, collect their findings and share with leadership.
[🪡🧶] 👇
Their leaders would promptly ignore that feedback because it contradicted their own opinions. They took most of their inspiration from apps they “liked” and features they saw on their kids’ phones (neither the execs nor the kids were target audience for this app).
The only thing the execs did pay attention to was reviews in the app store. They would regularly point to these reviews as the only thing the product team should pay attention to.
While reviews are one channel for feedback, the team had much richer insight from their own work.
Agility is the publicized target condition for nearly every enterprise today. The challenge is defining exactly what that means.
Based on my experience I don’t believe most organizations are actually targeting agility as their goal but rather an implementation of Agile.
🧵👇
The difference is significant. Agile is an output -- a series of steps, processes and methods that dictate how people should work.
Agility is an outcome -- a measurable change in the behavior of our teams, leaders and executives.
Given the broad global adoption of the idea of Agile and the desire to fit in, many organizations seek the path of least resistance to be able to claim that they, too, are agile. What ends up happening is an application of a method
We put a lot of the weight of becoming a customer-centric organization that manages to outcomes and "tests and learns" on the shoulders of our leaders and executives. But it's a two-way street. Our teams also need to change how they work to increase the likelihood of change 1/n
Teams want their stakeholders to trust them to solve problems, allow them to listen to customers and empower them to make tactical day-to-day decisions. In many organizations this is a radical shift for these stakeholders. What do we give them in return for that trust? 2/n
Transparency. Radical transparency is the proactive sharing of information on a regular cadence both up to your leaders and out to your colleagues. Candidly putting on display your work, wins, failures & learnings is key to building the trust that enables agility. 3/n
Corporate innovation labs fail regularly. The way I see it there are 4 reasons for this:
1/ Talent -- intrapreneurship is a tough quality to find in your teams. When it is found, it needs to be recognized and nurtured in ways most big corps treat as theater.
2/ Equity -- innovation comes from creative entrepreneurs. These folks won't give up their best ideas to their employer for the promise of another 2 weeks' worth of pay. How big orgs compensate in-house innovators makes or breaks the "lab."
3/ Exit strategy -- on the off chance that a corp innovation lab finds a big idea, what will they do with it? Without a clear sense of how an idea "exits" the lab most intrapreneurs won't pursue true innovation.
There were some clear themes coming out of the presentations at #productized in Lisbon yesterday about #prodmgmt and #design and #culture. Here is a brief summary of what I heard:
1/ Very little mention of #agile as a problem or a choice. It was just assumed by all speakers that this is the way everyone works.
When we wrote #leanux we wanted to help product design and development teams collaborate more effectively and ultimately build better products for their customers. The overwhelming feedback from readers has been (no surprise) that they want to work this way. However...
What we didn't expect was the amount of teams out there telling us things like "my boss won't let me work this way" or "my company would never let us talk to customers." Hearing this again and again gave us the sense that there was (at least) another conversation to be had. So...
We wrote another book - #senseandrespond . That book took the conversation up a level to leaders and makes the case that to stay competitive in today's business world you have to build continuous learning loops with your customers. I believe many orgs heard this message but...