The fix note: what was wrong, what you did, how you know it worked

A closed ticket carries three lines: the cause, the fix, and the verification. Not 'resolved', not 'fixed it', but the fault named, the change named, and the test that proved it, so the next person who sees the same thing has the answer in twenty seconds.

Hone is a place to practise a career, one idea a day. This is one of its lessons, written out in full and free to read without an account.

What it is for

Six weeks on, the same user, the same fault, and the last ticket says 'sorted'. Whoever wrote that has left. The new technician starts from nothing, takes forty minutes, and finds the same stuck spooler. Three lines would have made it a two-minute ticket. The note is written for a person you will never meet.

How to think about it

Write it as three labelled lines. Cause: what was actually wrong, in one sentence. Fix: the one change that fixed it, by name, with anything you tried that did not. Verified: the real task the user did in front of you that proved it. Then ask the user to confirm before you close, and link the knowledge article if there is one.

Worked example

Cause: print spooler service had stopped after a job from a damaged PDF

The fault, named. Not 'printer problem'.

Fix: cancelled the stuck job (no effect); restarted the print spooler service (fixed)

The change that worked, and the one that did not, both named.

Verified: user printed a two-page document from their own application; pages came out

The user's real task, done in front of you. Not a test page from the printer's menu.

User confirmed by reply at 11:14; closed; linked to article KB-0231

Confirmed, closed, and pointed at the article, so nobody rewrites it next month.

Your turn

Write the label of the third line of a fix note.

Cause: … Fix: … : …

The trap

Writing 'user confirmed working' as the verification. It says the user said so. It does not say what they did, so nobody can repeat the check or tell whether it was a real test.

Practise the fix note on HoneA question on it now, a coding challenge where there is one, and it is remembered for review. Free, no email needed.