360REV Newsletter
Daily Briefing
When the assistant starts building the tool
Good morning. The clearest thread running through Friday's productivity releases is that the assistant is no longer just answering questions beside your work. It is starting to build the surfaces you work in, and in some cases to run tasks on your behalf, which changes what you are actually buying when you buy software.
That shift is worth slowing down for. A tool that answers is easy to evaluate: you ask, you read, you decide. A tool that acts is harder, because now you are trusting it with the doing and not only the thinking. Before adopting anything in this category, it helps to have already decided where you draw the line between work an assistant may complete alone and work it may only draft — a line we have written about in decisions automation should never make and in what AI should and should not do in your business. 360REV takes the same view internally: automation drafts, and a person retains the decisions that carry consequences.
What we're tracking
- Microsoft reframes Copilot around doing, not just answering Microsoft announced a new version of Copilot organised into three named surfaces: Home, Code and Autopilot [1]. The naming itself is the signal. "Home" and "Code" describe places you go; "Autopilot" describes work that continues without you steering every step. Microsoft frames the change as a reimagining of the product "to enable work as it evolves" [1], which is a broad promise, and a business should read it as an intent rather than a finished specification.
- GitHub lets you build the workflow by describing it GitHub published a guide to building custom workflows with canvases in the GitHub Copilot app. The idea is that you describe the interface you need in plain English and the agent builds a live surface you can both use and update [2]. GitHub's own framing is that you "spend less time adapting to tools and more time getting work done" [2].
- A small calendar change that removes real friction Not every useful release is an AI release. Google added the ability to view up to three time zones in Google Calendar on the web, configured as a primary, secondary and tertiary zone [3]. Google describes the goal as "making it easier to schedule and coordinate meetings across global teams by expanding time zone support" [3].
- Why a performance change is a buying signal GitHub also wrote about improving site performance, explaining how it "fully migrated github.com away from CSS-in-JS" [4]. On its face this is an engineering story about how a page is built. For a buyer, it is more interesting as a signal.
- What to take from the day The assistant is moving into the work, not just beside it. That is the pattern under Friday's news, from Microsoft's autopilot surface to GitHub's generated canvases. It brings speed and flexibility, and it raises the stakes on the boring questions — what it may touch, what it records, and what you keep if you leave. Ask those first. The capability will impress you on the demo; the answers to those questions are what you live with afterwards.
From the blog
What good customer follow-up looks like
How to decide when to follow up, how often, and where the line sits between staying useful and becoming a nuisance.
When a spreadsheet stops being enough
Spreadsheets fail in predictable ways once several people depend on them. Here are the specific signs that a shared system is overdue, and what each one is really telling you.
How to choose software you will still use in a year
How to judge a tool by the work you actually repeat every week, instead of by the length of its feature list — and the questions to ask before you commit for a year.
Sources
Share this issue
Facebook · X · Reddit · LinkedIn · WhatsApp · Email · Bluesky
Every briefing is on the site the morning it is written, with the announcement behind each item. All briefings