Type Objective

Decide whether the goal should demand a result, a process, learning, maintenance, or prevention based on how much you actually know.

Your new product has a revenue quota before it has a single confirmed customer problem. The team is being graded on a performance target in a situation where nobody yet knows what works, and everyone can feel the mismatch: pressure without a map. The quota isn't motivating discovery; it's punishing honesty about how little you know.

Type Objective matches the kind of goal to how much you actually know. The types: performance (hit a result), process (follow a routine), learning (find out what works), discovery, maintenance, and prevention. The cue that you need it is a results demand in territory where the mechanism is still unknown, or lingering study-mode in territory you've already mastered. The move question: do we know enough to demand a result, or should the goal first be learning? Run it by naming your biggest uncertainty, then setting the goal at that level; for the product, "discover a repeatable high-value customer problem within eight weeks" replaces the quota. What changes: effort aims at the real bottleneck, and people stop gaming a number they can't honestly hit. The flip side matters too: once a reliable method exists, retire the learning goal and switch to execution, or you'll research forever.