“Updated the onboarding checklist” reports a completed task but hides the choice behind it. Which delay did you target? Which control did you keep? What alternative did you reject? A short decision note makes those judgments reviewable without turning the update into a claim that the whole process has already improved.
The video argues that useful judgment can disappear inside a finished task. One practical response is to write a short decision note alongside the update. Its purpose is to expose reasoning for review. It is not a script for guaranteeing a promotion, nor a way to relabel every routine action as strategy.
Begin with a decision someone can examine
The U.S. Office of Personnel Management’s program and project competency definitions connect strategic thinking with objectives, priorities, a longer-term perspective and anticipated threats or opportunities. Its problem-solving definition includes assessing relevant information and evaluating alternatives.
That is a useful reference point, with a limit: a federal competency framework does not prove how a particular manager will judge your work. Use it to sharpen the evidence you present, rather than to claim your employer must recognize a particular label.
Take a fictional example. A team wants new starters ready to work sooner. You are asked to revise the onboarding checklist. The decision worth describing is which cause of delay to address, while protecting the checks that still matter.
Keep the observation smaller than the conclusion
Suppose your review of ten recent onboarding records finds six cases waiting for manager approval. This is invented data for the example. It is enough to identify a possible bottleneck in those ten records. It does not establish that approvals explain all delays across the organization.
A careful opening might be:
In the ten cases reviewed, six waited at the manager-approval step. I propose testing an earlier review slot before removing any control.
This is more informative than “streamlined onboarding.” It gives the reader an observation, its scope and a proposed response. It also leaves room for a manager to identify missing context, such as a necessary check that occurs during the apparent wait.
Do not quietly convert the intended benefit into a result. “The change should reduce waiting” and “the change reduced waiting” require different evidence. If the change has not been tested, keep the future tense.
Show two credible alternatives
A choice becomes easier to review when the alternative is visible. In the example, one option is to remove an approval step. Another is to keep the approval but schedule it earlier. A third is to leave the process alone until better evidence is available.
Describe the relevant difference rather than making the rejected option absurd. Removing a step might reduce waiting but needs an assessment of the control it provides. Moving the review earlier may preserve that control but require manager availability. Further investigation costs time while improving confidence in the diagnosis.
You do not need a long list of every idea discussed. Pick the alternatives that clarify the actual constraint. If you lacked authority to remove an approval, state that. A decision note should make responsibility easier to understand, not imply power you did not have.
Put the tradeoff next to the recommendation
Here is a compact note for the fictional case:
| Part | Example wording |
|---|---|
| Objective | Reduce waiting before new starters receive access |
| Observation | Six of ten reviewed cases waited for manager approval |
| Proposal | Test an earlier manager-review slot |
| Alternative | Removing approval requires a separate control assessment |
| Tradeoff | Managers must reserve time earlier in the process |
| Uncertainty | The ten cases may not represent future starters |
| Next decision | The process owner decides whether to authorize the test |
Notice what the note does not claim. It offers no invented percentage improvement, no assurance that risk is unchanged and no claim that the proposal is approved. Those gaps are part of an honest account.
A useful note can be challenged. If the manager says the approval delay is only a symptom of missing documentation, the conversation has found something valuable. The goal is a better decision, not a presentation so confident that nobody questions it.
Choose a review trigger before declaring success
For a proposed test, record what would make you reconsider. In this example, the process owner might ask to review the next group of cases and check whether earlier scheduling actually changed waiting, while confirming that required checks still occurred.
Do not invent an acceptable failure rate or control standard for someone else’s organization. Ask the responsible owner which conditions are required. Your contribution is to identify the question and preserve the evidence needed to answer it.
Keep a distinction between the action and its consequence. The calendar slot might have been created successfully while the delay remained. That result would be useful evidence against the initial diagnosis. Recording it is more credible than counting completion as proof of impact.
Use the note in an ordinary update
Lead with the decision needed or the most relevant finding. Then offer the reasoning and the underlying detail. For example: “I need the process owner’s approval for an earlier review-slot test; the ten-case review suggests waiting at that step.”
If no decision is needed, say what you learned and what you are watching. An update can be short without stripping away its limits. Keep routine completion information available, but let the reader see why it matters.
Finally, discuss expectations with your manager. Ask which kinds of decisions your role should own and what evidence they need to assess them. Clearer writing can reveal your judgment; recognition also depends on responsibilities, opportunity and the organization around you. A decision note gives that conversation something specific to work with.
