Discover
AI Change Desk
AI Change Desk
Author: Michael Hanna-Butros Meyering
Subscribed: 0Played: 0Subscribe
Share
© MHBM 2026
Description
AI Change Desk is a source-backed AI change management and AI governance podcast for leaders, managers, and operators. Hosted by Michael Hanna-Butros Meyering, each episode turns a current AI capability, policy, privacy, security, or workflow shift into a practical operating decision: context, impact, and action.
52 Episodes
Reverse
Hey! I'd love to hear your thoughts, send me a voice note.Does Blank Mean Nobody Used It?
Episode 54 of AI Change Desk with Michael Hanna-Butros Meyering.
A blue binder, a sticky front door and a training invitation that nearly goes to the wrong person. In a fictional rollout, Ruth wants to help people use Copilot. Before she sends her note, can someone else explain why each person belongs on the list?
Context
Separate GitHub and Microsoft examples distinguish missing editor detail from observed activity, unavailable fields from measured zeroes, and feature totals from a count of people. A reporting window is not automatically the right audience rule for a reminder.
Impact
Move one invented person's last qualifying use from twenty-nine days ago to thirty-one days ago. With the other conditions held fixed, the eligibility decision changes. But meeting an inactivity criterion does not mean the person has never tried the tool, or that anyone should send a message.
Action
Give two colleagues twenty minutes, four fictional paper cards and a pencil. Record the intended action, product and population, qualifying event, period and end date, handling of missing fields, and decision owner. Ask each reader to justify an inclusion, an exclusion and a case where they must stop for missing information. Review the invitation's first sentence as carefully as its audience.
The people, reports and activity dates are fictional. No employee exports or messages are used. The exercise does not test or certify provider software. GitHub and Microsoft examples are separate products, not joined records or evidence of an actual mistaken notification.
Correction: EP053 Source Update
Conductor has withdrawn the wind-down notice discussed in EP053. Its updated notes cross out the November 13 and 20 dates, and its new update says development is resuming. Those dates in the earlier recording are historical, not current deadlines. Check Conductor's current guidance for service and data-retention details.
Official Sources
GitHub: telemetry and version fields
GitHub: usage-metrics definitions
GitHub: feature engagement update
Microsoft: reporting and outreach criteria
Conductor: amended notice
Conductor: development update
Disclosure
I use AI to help research, produce, and narrate this show.
I check the claims, flag the risks, and decide what goes on air.
My work in privacy shapes the questions I ask, but I don't discuss nonpublic work here.
I speak for myself, not the State of Oregon or any other organization.
This is practical guidance, not legal advice.
Hey! I'd love to hear your thoughts, send me a voice note.Who Owns the Automation After It Changes?
Episode 53 of AI Change Desk with Michael Hanna-Butros Meyering.
Correction: Source update - November 16, 2026. Conductor has withdrawn its previously announced wind-down. Its updated 0.93.0 notes cross out the November 13 read-only and November 20 shutdown dates, and its 0.94.2 update says Conductor is not shutting down and development is resuming. The dates mentioned in EP053 are historical, not current deadlines. Consult Conductor's current guidance for service, export and data-retention details. The original recording is unchanged.
Sources: updated announcement, revised 0.93.0 notice, 0.94.2: Conductor is back.
On Friday, a dispatcher gets a reopened repair back onto the crew list. On Monday she's off. Will the next dispatcher get the corrected list, or just the same mistake at a different address?
A follow-up can fix one report without changing tomorrow's instructions. Michael looks at how shared GitHub Copilot automations survive a handoff, why a Google Cloud skill name doesn't tell you which revision ran, and how teams preserve ownership when a tool's plans change.
Try It This Week
Give a colleague the saved rule and three fictional tickets: one open, one reopened, one closed. Before they build the list, have the dispatcher write down which repairs should appear. Compare answers. Record who can change the rule, who accepts the result and when they'll check a fresh list.
The dispatch story is fictional. The exercise needs no production access and does not test or certify a vendor's software.
Sources
GitHub: shared Copilot Automations
VS Code: run and review a cloud automation
Google Cloud: Agent Registry release notes
Google Cloud: skills and revisions
Conductor: announcement and updated plans
Disclosure
I use AI to help research, produce, and narrate this show.
I check the claims, flag the risks, and decide what goes on air.
My work in privacy shapes the questions I ask, but I don't discuss nonpublic work here.
I speak for myself, not the State of Oregon or any other organization.
This is practical guidance, not legal advice.
Hey! I'd love to hear your thoughts, send me a voice note.Who Set the Permission Mode?
Episode 52 of AI Change Desk with Michael Hanna-Butros Meyering.
A request to correct a library's opening hours sounds simple. But who may approve
the assistant's next action: the person, a fixed rule, or another model?
GitHub's assisted-permissions announcement and connected cloud workflow provide
the lead for this week's distinction: a task request, an approval decision, and
an enforced boundary are three different things. NIST's proposed agent-identity
principles and Google's preview policy documentation add two supporting perspectives.
In This Episode
Why approving a task is not blanket approval for its intermediate actions.
The unresolved difference between two GitHub descriptions of managed ask rules.
Why reasoning about a useful action and controlling access are separate concerns.
Why a recorded policy verdict does not by itself demonstrate prevention.
A 45-minute, paper-only exercise to prepare a bounded trial proposal.
The community library, staff and exercise records are fictional. No library
system or vendor permission behavior was tested. The GitHub documentation
difference is unresolved, not a demonstrated bypass. NIST's tenets are proposed
principles, not a binding rule or judgment about a vendor. Google's feature is
in preview. The exercise is not deployment permission or a safety certification.
Sources
Public primary-source claims were rechecked November 2, 2026. The GitHub pages
belong to one source family; NIST and Google do not independently verify GitHub's
runtime behavior. The Google guide's October 30 update is not a launch date.
GitHub: assisted permissions generally available, October 26
GitHub: connected Copilot cloud experience, October 28
GitHub: assisted-permissions guide
GitHub: enterprise managed settings
NIST: proposed agent-identity design tenets, October 27
Google Cloud: configure semantic governance policies
Disclosure
Quick disclosure before we start.
AI-assisted tools were used in parts of the research and production workflow.
Final editorial judgment, risk posture, and release approval stayed human-led.
This is operational guidance, not legal advice.
These are my opinions and are not representative of any organization.
One additional disclosure as the Desk evolves.
My current role includes privacy work,
so you will hear me pay closer attention
to purpose, access, retention, deletion, and accountability.
I will not discuss nonpublic work here.
These are my personal views,
and they do not represent the State of Oregon
or any other organization.
Hey! I'd love to hear your thoughts, send me a voice note.What Changes After the Conference?
Episode 51 of AI Change Desk with Michael Hanna-Butros Meyering.
After attending Gartner IT Symposium/Xpo in Orlando, Michael connects three themes from his session notes: attention to the person receiving a service, time and coaching to develop judgment, and an honest account of AI value and risk.
A hospitality story, a leadership conversation and Gartner's published research lead to one practical question: did the work become better for someone, or did the organization simply produce more of it?
In This Episode
Why a technically correct answer can still leave someone unable to finish a task.
Why permission to experiment is not the same as time and support to learn.
How to distinguish faster responses from a better overall service experience.
A proposed 45-minute, paper-first exercise for improving one service interaction.
The access-support scenario is fictional. The exercise is editorial guidance, not a validated assessment, compliance certification or permission to deploy a production change. Conference observations are not a survey of attendees or peers. Gartner's reported survey result is attributed self-report, not an independent audit.
Sources
The symposium took place October 19-22, 2026. Public source claims were rechecked October 26. Multiple Gartner pages belong to the same source family; they are not independent corroboration. Guidara's TED account is an earlier telling of his story, not a new event.
Gartner: Orlando symposium dates
Gartner: Will Guidara keynote
Gartner: Serena Williams keynote
Gartner: AI value and risk
Gartner: CIO survey and methodology
Gartner: technology trends for 2027
TED: Will Guidara, September 2022
Watch EP051 on YouTube
Read: Bring Back One Better Service
Disclosure
Quick disclosure before we start.
AI-assisted tools were used in parts of the research and production workflow.
Final editorial judgment, risk posture, and release approval stayed human-led.
This is operational guidance, not legal advice.
These are my opinions and are not representative of any organization.
One additional disclosure as the Desk evolves.
My current role includes privacy work,
so you will hear me pay closer attention
to purpose, access, retention, deletion, and accountability.
I will not discuss nonpublic work here.
These are my personal views,
and they do not represent the State of Oregon
or any other organization.
Hey! I'd love to hear your thoughts, send me a voice note.Did the Test Touch Production?
AI Change Desk | Episode 50 | October 19, 2026 | 19:27
Your AI demo works. Then a technician calls about the repair request it created. There is no repair: it was a test ticket. For your team, this was a demonstration. For somebody else, it became their morning.
That opening is fictional. The operating question is not: when a test reaches a real working system, who owns the effects on the receiving side?
Michael marks episode fifty with a brief thank-you, then examines the difference between stopping an agent, restoring a setting, removing access, and confirming that the affected workflow is actually resolved.
Context, Impact, Action
Context: separately attributed OpenAI and Anthropic evaluation reports, with Google Cloud guidance on oversight and permissions. These provider accounts do not independently corroborate each other or establish receiving-side recovery.
Impact: a failed request can still change server state; restoring a setting does not necessarily revoke access. Invented test data can still enter a real queue.
Action: run a 45-minute paper-only destination rehearsal. Track what was attempted, what arrived, what changed, what access remains, and who owns the final disposition. Do not test an outside organization without authorization.
Sources
OpenAI: Accessing and changing internal systems during dashboard research - October 15 report about June 17 evaluations.
Anthropic: Investigating unintended model actions - October 9 report, corrected October 12. The practice-form example is a separate case.
Google Cloud Agentic AI Responsible Use Guidelines - marked modified October 12. Deployment guidance, not a new law or proof of control effectiveness.
Sources checked October 19, 2026. Receiving-side recovery is not independently verified in this episode.
Disclosure
AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led.
This is operational guidance, not legal advice. These are my opinions and are not representative of any organization.
My current role includes privacy work, so you will hear me pay closer attention to purpose, access, retention, deletion, and accountability. I will not discuss nonpublic work here. These are my personal views, and they do not represent the State of Oregon or any other organization.








