3 ms·
I've found that teams (and individuals) function best when tasks are either scope-delimited or time-delimited. Not both, and not neither. If the task is concr
by nostrademons 11y ago
I've found that teams (and individuals) function best when tasks are either scope-delimited or time-delimited. Not both, and not neither. If the task is concrete enough that the desired outcome is crystal-clear and there's not much risk in completing it, then just say "It's done when it's done" and let someone work at it. If the task has fuzzy success criteria - "Make this UI better", for example, or "speed this up as much as you can", or "explore new approaches for this module" - put a deadline on it. It's possible to spin your wheels forever if you don't have a clear destination and clear timeframe.
- holografix 11y agoThis. So obvious and so right.