Here's an anti-pattern to watch for: Hiring a process, tool, framework, or label to do too many jobs. An example. A team starts using OKRs. You ask them "why have you decided to use OKRs?" They explain. Well, the OKRs will help us set goals. Oh, and they will help us track our progress! Accountability, right? And alignment of course, and keeping score. Objective grading is part of it. And autonomy when a team sets good ones.
TBM 15/52: Stop Hiring Things to Do Too Many…
Here's an anti-pattern to watch for: Hiring a process, tool, framework, or label to do too many jobs. An example. A team starts using OKRs. You ask them "why have you decided to use OKRs?" They explain. Well, the OKRs will help us set goals. Oh, and they will help us track our progress! Accountability, right? And alignment of course, and keeping score. Objective grading is part of it. And autonomy when a team sets good ones.
Create your profile
Only paying subscribers can comment on this post
Check your email
For your security, we need to re-authenticate you.
Click the link we sent to , or click here to log in.