Practical IT advice. With the day job in mind.
Practical IT guidance for people responsible for making technology work.
Practical notes, independent views and the occasional complaint about a problem that should have been fixed years ago.
46 briefings
Practical IT guidance for people responsible for making technology work.
A completed backup job is only part of the evidence.
A polished demo is a poor substitute for a useful result.
How to document, review and retire a workaround before it becomes an unsupported dependency.
Some methods resist phishing better than others.
Make the exit test part of the SaaS trial.
Agree who makes the decisions, who operates the service and what happens when its owner is unavailable.
Use a handover test to find the missing instructions.
Turn an informal request into a clear next step without hiding the impact of the work.
Tell us about the recurring problem that deserves a closer look.
A change record earns its keep during the rollback, not at the approval meeting.
The same request arriving forty times is telling you something about the service, not about the users.
On-device tools, AI-assisted network investigation and new releases for teams building with AI. Four developments worth examining in the context of your own work.
Before moving saved passwords, agree who can access the export and how you will close the migration.
Use a Windows battery report alongside the person’s working day before choosing the next action.
Run a short response exercise with finance and IT before someone has to find the right number under pressure.
CodeMender’s preview update, new agent connections for cloud security, and Anthropic’s embedded-evaluation announcement: the practical implications for IT teams.
A short Teams rehearsal can establish what participants can use and how decisions will be recorded.
Prepare the working files for a site visit before relying on a folder visible in File Explorer.
A Windows clipboard rehearsal can reveal a gap in your support instructions without using real customer data.
Put business records and device ownership ahead of the reset button when preparing a Mac to leave the organisation.
Use Mozilla’s September redesign as a prompt to check the browser instructions your colleagues actually follow.
Review public business information with its owner, keeping useful customer content and removing detail that no longer has a purpose.
Use Google’s October interoperability update to plan a focused room test before changing the instructions beside the screen.
A Claude release, a Google Cloud data toolkit and a workplace-prompt transition, with practical checks for the teams responsible for them.
Give a business form an agreed home and test the response workflow before its creator moves on.
Check the intended reader’s access before calling a Google Drive project folder ready.
Investigate the interrupted task before changing Chrome performance settings across the business.
Add a practical human review before sending the next business presentation.
Haiku 5.5, local GitHub Copilot and Google’s Gemini agent: what UK IT teams can evaluate, and what still needs checking.
Check the sent-message trail in a shared mailbox before the next handover.
Make the support contact clear before accepting a Quick Assist session on a work PC.
Use Google’s October announcement to write a practical acceptance test before committing to a Microsoft 365 migration.
Make a deliberate release copy of a Word document, with a review of the material that should leave your organisation.
For teams already using Time Machine, a small restore exercise can make the support procedure more useful.
Use the return to GMT to check that a business schedule still matches the time its owner expects.
Give colleagues a clear route to help without asking them to prove that a message is malicious first.
Copilot Studio’s Frontier rollout, a changed Google skills timetable and Anthropic’s evaluator access: practical implications for UK IT teams.
Before automating disk cleanup, review the affected files with the person who uses the device.
A focused permission check for Mac support teams, without granting access to every app just to get a call working.
Turn a vague request for Teams access into a specific collaboration decision.
Plan a useful discussion with named follow-up work, rather than a meeting that ends with everyone agreeing it was interesting.
Review existing entries deliberately when adding validation to a working Excel workbook.
Claude integration upgrades, Gemini connection management and shared stewardship for agent tools: practical checks for UK IT teams.
Agree a predictable print destination and confirm it in the actual application before sending work.
Separate a Google Drive cleanup request from a decision about who should retain access.