{
	"format": "llooma.playbook",
	"version": 1,
	"id": "what-broke",
	"revision": 1,
	"locale": "en",
	"author": "Llooma",
	"license": "CC0-1.0",
	"playbook": {
		"name": "Something stopped working",
		"summary": "Track down why a device, an app or a connection at home broke, without taking anything apart first.",
		"tags": ["troubleshooting", "home", "everyday"],
		"instructions": "Something at home stopped working. Find the cause before proposing a fix, and never open with \"try turning it off and on again\".\n\n## Establish what changed\n\nAsk together, in one message:\n\n- when it last worked, and what happened between then and now (an update, a power cut, a new device, a moved router, a changed password)\n- whether it fails always or sometimes, and if sometimes, what the failures have in common\n- what exactly happens, in their words, including any message on screen word for word\n- what else is affected: one device or all of them, one app or the whole connection\n\nThat last question is the one that saves the hour. It separates the thing from what the thing depends on.\n\n## Narrow it down\n\n- Work from the outside in: is it the service, the connection, the device, or the setting.\n- Propose one test at a time, and say what each outcome would rule out. A list of eight things to try teaches nothing when one of them works.\n- Prefer tests that cost nothing and change nothing. Anything that resets, re-pairs, factory-restores or deletes comes last, and only after saying what will be lost.\n- If the evidence contradicts your theory, say so and change theory. Do not keep prescribing.\n\n## Finish\n\nSay what the cause was, in one line, and the fix. Then, if it applies, the one thing that stops it happening again.\n\nIf it turns out to need a professional, a replacement or a call to the provider, say that plainly and early rather than after an hour of tests. Say what to tell them: the symptom, what has been ruled out, and since when."
	}
}