Plan what must connect, not just when to start
Six items ask about the user of an output, required features, compatible inputs, dependencies, resource access and operating conditions. The scope is task specification rather than personal time management.
Items 19–24 keep their selected values from 1 to 5. Add all six and divide by six, rounded to one decimal. There are no reversed items. One unscored answer withholds this group alone.
A schedule does not specify the output
Two people may finish on time and still produce pieces that cannot be used together. This group concerns what the output is for, which features are required and which inputs or resources must connect. It deliberately does not ask about distraction control, calendar priorities or estimating personal work time. Frequency of specification is also different from whether the specification was technically correct.
Compute a mean without creating a planning tier
Suppose the six answers are 5, 4, 4, 3, 4 and 3. They sum to 23; 23 divided by six rounds to 3.8. This describes the selected frequencies on this form. It is not a percentage of planning competence, a project-complexity limit or evidence that you can manage a particular occupation’s work.
Check whether the pieces can actually connect
Imagine preparing a display for a community event. A text file, printed backing and available stand all depend on dimensions and mounting conditions. Asking only when each part will arrive misses whether they fit. A small specification can name the reader, essential information, file format and stand size. The example shows a dependency question, not a universal event-planning standard.
Established routines may already carry the specification
In routine work, a template or existing agreement may supply conditions that you do not need to restate each time. In unfamiliar work, more clarification may be necessary. Neither frequency alone establishes efficiency. If you had no relevant occasion to coordinate an output, choose unscored rather than Never. A missing mean remains visible, and the complete means in other themes are retained.
Write a short dependency note
Choose one ordinary output already within your role. Write who will use it, one required feature, one input it depends on and one condition that would stop the pieces from working together. Check the note with the appropriate person if useful. Avoid adding speculative requirements. The exercise is complete when the next decision is clearer, not when the document becomes longer.
Use concrete conditions when discussing development
A useful development conversation can examine whether the intended user and input conditions were known, how a conflict was found and what remained unresolved. It does not need a strong or early-stage label. This original self-report has no norms or established language equivalence and cannot certify project-management competence. For actual evaluation, use the role’s requirements and observed work rather than this mean alone.