How can I tell whether I am improving at a skill without a formal test?

Turn “better” into a few things you can point to in the update itself. For example, you might look for whether a reader can identify the current status, the next action, and any decision or help needed without having to ask you to clarify. You could also notice whether the update stays focused on the project rather than including background that does not affect what happens next.

Pick no more than a handful of criteria at first. Make them observable, not personality judgments: “names the next action and owner” is easier to check than “sounds more confident.” Keep a copy of a representative update from now, along with the task context. That gives you a starting sample, not a verdict on your ability.

Compare examples that are reasonably similar, and write down the differences that could affect the comparison. A short update about a routine task is not a fair direct match for a complicated update involving several dependencies. If you cannot find close matches, compare each sample against the same criteria rather than claiming the tasks were equivalent.

Here is a simple hypothetical example. Suppose your first update says: “We made progress on the draft. There are a few items left, and I’ll share more soon.” Your criteria might show that it does not state what remains, who will act, or when the next update is due. A later example might say: “Draft is complete; I’m checking the figures today. I’ll send the reviewed version to [team or person] by [date]. The open question is [decision needed] from [owner].” That later version makes actions and an open question easier to find. It is evidence of improvement on those criteria if the task and conditions are comparable; it does not establish that every part of your writing skill improved.

Keep the ordinary and awkward examples too, not just your best work. Choose a regular review point—such as after every few relevant updates—and record each sample or a short note about it. For each one, mark the criteria as “shown,” “partly shown,” or “not shown,” and add one sentence about the task, time pressure, or feedback you had. Those labels are your own tracking tool, not a validated score.

Then look for a pattern: Are the key details appearing more consistently? Do you need fewer reminders to include them? Can you use the approach on a different kind of update? A setback can point to a condition that makes the skill harder to use, rather than cancelling earlier progress. If you have feedback from a reader, record the specific comment separately from your own assessment. One person’s reaction can be useful context, but it is not a formal measurement.

Copy this for each sample and fill it in with brief, concrete notes:

Skill: Writing concise project updates Sample date or sequence: [date or sample number] Task and audience: [what the update covered; intended reader] Conditions: [routine or complex task; time available; relevant support] Criteria:

1. Status is easy to identify: [shown / partly / not shown; evidence]
2. Next action and owner are clear: [shown / partly / not shown; evidence]
3. Decision, risk, or help needed is stated when relevant: [shown / partly / not shown; evidence]
4. Extra detail is limited to what the reader needs: [shown / partly / not shown; evidence]

What changed from the previous comparable sample? [specific difference] What remains difficult? [specific example] Next practice step: [one small change to try]

Review several entries together. If the tasks differ a lot, say so in your conclusion. You can reasonably write, “I’m stating next actions more consistently in routine updates,” rather than “I’ve mastered concise communication.” The sheet can help you organize observations, but it cannot prove a broad skill level or rule out other explanations for a change.