Continue with Steam Start with the full official notes and the date of the update. Identify the changes that affect your hero, items, upgrade path or common opponents, then ask what job each changed part used to do. Test one specific hypothesis before changing your entire build. If the changes do not affect the reason you chose that build, keeping the familiar setup while you gather evidence is a reasonable decision.
A patch note confirms that a change was announced; it does not by itself prove which build is strongest. Separate the written change, your prediction about its effect and what you actually observe in practice or matches.
Check the full update and date
Open the site’s Patch Notes and check the update date and full official source. Individual hero and item pages may also include Recent Patch Changes when relevant data is available; these summaries are a starting point, so follow the complete notes for surrounding changes and later corrections. Check whether the guide or build you are using predates the update, and whether another update has happened since the example or advice was published.
Read beyond your hero’s name. A changed item, component, shared mechanic or frequent opponent can affect the plan even when your hero is not mentioned. Conversely, a change elsewhere may not alter the purpose of your current setup. Record that no change is needed for that job and why; recheck if later evidence changes the situation. Separate the notes from an early tier list or a player’s interpretation.
Trace the change through your build
Write down the current job of each important part: reach an ability upgrade, survive a threat, create an opening, deal 
damage or support an ally. Then check the change against the whole path.
| What changed? | Check against your plan | Decision to consider |
|---|---|---|
| Ability or upgrade | Base effect,  scaling, cooldown and requirements |
Keep or revise the skill priority for its actual job. |
| Item or component | Effect, cost, prerequisites and timing | Compare a feasible alternative, including the full path. |
| Interaction or matchup | Whether the sequence reaches the target and survives a response | Test the changed step and a fallback. |
| General rule or teammate | Whether the next job or team dependency changed | Adapt to the situation, not just a tier label. |
Check components and budget
If an item changes, check its components and any upgrade that depends on it. If a required component or upgrade is unavailable, stop: reconstruct a feasible path and budget before testing it. A cheaper or stronger final item is not automatically a better purchase if its path delays a tool you need sooner. If an ability changes, check both the base ability and the upgrade you actually use; an upgrade-only change does not necessarily affect an earlier part of the match. Treat suspected interactions as questions until you can verify them.
Historical example: turn one confirmed change into a test
In Valve’s September 16, 2026 Minor Update, 
Haze’s 
Fixation headshot 
stack count was increased from +2 to +3. This is a historical illustration, not a claim that these are the latest notes or that the same numbers remain current. Read later notes before using it to make a present-day choice.
A historical example, not a current recommendation
Suppose an older Haze build was chosen partly to take advantage of reliable 
weapon damage. The confirmed note gives you a specific question: when I can land headshots in a realistic engagement, does this change make my existing damage plan easier to execute, or is another part of my setup still the limiting factor? The note does not answer that question, establish an optimal item order or prove that every headshot-focused build improved.
First compare the old guide’s date with the update, then read the ability and relevant item descriptions available to you. Check whether the recommended purchases still fit your budget and whether their components or upgrade requirements changed. If your actual problem is surviving an approach or reaching the target, a change to a stack count may not resolve it; preserve or adjust the defensive part based on that job. The Haze guide offers hero context, but its recommendations should also be checked against later notes.
Evidence ledger: Record the confirmed change and source, your prediction about the build, and the result you actually observed as three separate notes. If you have not tested a claim, leave the observation unknown.
Test one hypothesis before changing the plan
Choose one observation you can make. For example: “With the same hero and intended situation, can I use the changed ability sequence reliably before I need to disengage?” Keep other relevant conditions as similar as practical—hero, ability upgrade, item setup, target and situation—and record what you changed. A controlled practice setting, if available to you, can help check the basic sequence; it does not reproduce every enemy response or team fight.
Do not interpret a few attempts as proof of a universal advantage. Note whether the sequence works, what resources it consumes, and what happens when a step misses or an opponent interrupts. If a purchase order is the question, compare when each path becomes affordable and what useful capability you give up before that point. Do not assume a changed cost also changes an item you have not checked.
Move from practice to a real decision
Then apply the hypothesis in matches. In an available replay or recording, inspect one relevant decision: could you reach the target, did you have the upgraded ability and item, and was the alternative actually available? Record the trigger, your action and the observed result; a single outcome does not establish cause. The replay-review guide explains how to separate information available at the time from what appeared later. Keep the old choice if it still meets the job, switch if the observed trade-off consistently matters to your play, or keep testing if evidence is unclear.
Read post-patch statistics cautiously
After a new update, match samples can be small and player behavior can change as people experiment. On the site’s Heroes and Item Tier List, compare the same available patch and rank context; rank represents a match-level average, not each player’s exact rank. Check hero match counts on the Heroes table. Item tier cards do not display match counts, and an item detail page need not use the same filtered slice. Missing data or a fallback should not be interpreted as a measured zero.
Rates are associations, not isolated effects of an item. An item purchased in successful games may have been chosen by players already ahead. A short-lived post-patch rise in win rate is a prompt to investigate, not proof that the item caused the change. The statistics guide covers sample size, scope and selection bias in more detail.
Should I change my build because a new tier list ranks it lower?
Not automatically. Check whether the ranking uses the same patch and relevant match context, and whether there are enough observations to interpret it. If the changed ability or item still performs the job you need, keep testing the familiar plan; change it when a specific, observed trade-off justifies the switch.
A short decision record for the next update
- Confirmed: Write the patch date, source and the exact relevant hero, item or general change. Check later notes for corrections.
- Affected job: Identify which part of your existing plan depends on it, including components, budget and ability upgrades.
- Hypothesis: State one expected difference and a feasible alternative, including its cost or risk.
- Test: Compare the relevant sequence or purchase path under similar conditions, then inspect a real match decision if a recording is available.
- Decision: Keep, adjust or defer. Record why and revisit after more evidence or another update.
An early impression can be useful as a question. Label it as an impression until the notes and your observations support a more specific conclusion.