“Heuristics for testing your goals Assess your goals using these guidelines: Does your goal start with a verb (“launch,” “build,” “refactor,” etc.)? Then you probably have an action, so reframe it to describe the outcome you want. Often, this takes the form of translating “X so that Y” into “Y via X” (and consider if you need X in there at all). A helpful trick to figure out the proper framing is to read the goal out, ask yourself why, answer that question, then do that a couple of times until the true goal comes into focus. (See Table 2 for an example.) Do you have “engineering goals” and “business goals,” or something similar? Stop it. Are your goals more than one page, more than three to five objectives, or more than three to five KRs per objective? No one will read them—let alone remember them. When you (or your team) look at your goals, do you wince and think, “What about X? I was really hoping to get to that this quarter”? If not, you probably haven’t focused enough, and your goals are not adding value. Could one team member think a goal is achieved and another one completely disagree? Then your goal isn’t specific enough. (By contrast, if everyone feels it’s mostly successful but the assessments range from 60–80 percent done, who cares?) Can you imagine a scenario where the goal is achieved but you’re still dissatisfied with where you ended up? Then your goal isn’t specific enough, or an aspect is missing. Could you be successful without achieving the goal? Then your goal is overly specific, and you should rethink how to define success.”