steadystate · Tools
Five dimensions, twenty statements, scored zero to three. The output is a profile of your next drop, not a grade. Nothing is stored; your answers live in the URL.
The next drop is where product and delivery meet. Most of what goes wrong with it was decided before anyone wrote a line of it.
Score the drop you are about to commit a team to: a season, a DLC, a feature, an update. Each statement is scored against four anchors describing what that score looks like in practice, because without them everyone gives themselves a two. Answer from what happened on the last drop rather than from what is supposed to happen. The result names the two weakest dimensions and what usually sits underneath them.
Score the drop as the team behaved on the last one under pressure, not as the plan says this one will go. If a practice exists but was dropped the last time a date slipped, it scores a one. The anchors are written so that the flattering answer and the true answer are different sentences. If you find yourself reading past an anchor to reach a higher number, that is the finding.
0 of 20
What is missing
Goes to Alexander directly. No form, no sequence, no obligation.
The link holds your scores and nothing else. Have the producer and the lead score it separately; where they disagree is usually the finding.