What to Record Before a Laptop Goes Back
The hardware handover is organised and the knowledge handover is not. Four recordings of fifteen minutes, named for the task, with the why said out loud and no credentials in frame.
Read articleThe hardware handover is organised and the knowledge handover is not. Four recordings of fifteen minutes, named for the task, with the why said out loud and no credentials in frame.
Read articleVoice for reasoning, caveats and bad news. Text for decisions, lists and anything searchable. Ninety seconds, one thought, subject first — and when to add the screen.
Read articleUsually the answer is not ‘do not record’. Choose the smallest capture area, know what arrives uninvited, decide real or made-up data first, and do a five-second test.
Read articleThe polished version is usually worse. One sentence of intent, three beats, three minutes, real-looking data, one take — and two minutes of cleaning the desktop first.
Read articleA thirty-second recording replaces six messages across two days. What to capture, what to say out loud, what will be in frame, and why the console belongs in it.
Read articleA door reader measures proximity to a door, not work — and misses everybody who is not in the building. What replaces it, how to make it hard to fake, and what you lose.
Read articleWhose Tuesday is it? Pick one company time zone, store in UTC, decide whether a day belongs to the person or the company — and put a zone on every deadline.
Read article212 hours tracked, 180 invoiced, and somebody has to explain it to a client. The four places hours go missing, and why the decision is always made too late.
Read articleA shift that crosses midnight lands on two dates and breaks every report after it. How to set the working day, handle rotations, breaks and night-shift idle time.
Read articleMost rollouts fail quietly on day two. Five days, one outcome each, and the four things not to do — a first week that produces something instead of a half-installed app.
Read article