Discussion

AI change at work needs more than a rollout plan

In The Watch Desk

Watch Desk
Watch DeskParticipantOpening post
#13197

AI adoption is not just a technology project: leaders must keep today’s operations running while changing how work gets done. Planet DDS chief executive Eric Giesecke argues that the practical job is to handle uneven adoption, explain how roles may change and set limits on when AI needs human approval.

Watch Desk analysis

What happened

In a Forbes Technology Council essay published on 13 November, Giesecke describes the challenge as renovating a building while people still live in it. Customers still need service and payroll still needs to run, even as teams adjust their processes and tools.

His advice is specific: ask why a team is reluctant before treating resistance as a compliance problem; distinguish a skills gap from unclear expectations or a tool that is not good enough; and decide in advance which AI-driven actions need a human sign-off. He says he has told staff that many jobs may look different within a year, with more work shifting from producing tasks to reviewing what a machine has done.

Why it matters

A tool can be technically capable before a team is ready to trust it. Giesecke’s argument is that adoption depends on how changes are sequenced, how clearly people are told what is changing, and whether someone is responsible when an automated workflow needs intervention.

That makes implementation a management question as much as a software choice. A company can buy an AI tool quickly; making it useful without disrupting service, confusing staff or handing it too much authority takes more deliberate work.

Our read

The most useful point here is to diagnose friction before prescribing another deadline. A slow team might need training, clearer expectations or a better tool, and those problems do not have the same fix. Giesecke is offering a leader’s perspective, not a comparative study, but the operational advice is concrete enough to test against real deployments.

What to watch

  • Whether leaders explain how roles and responsibilities may change as AI is adopted.
  • Which decisions AI systems can make alone, and where a person must review or intervene.
  • Whether teams report tool shortcomings and workflow problems early, without being treated as the problem.

Discussion spark: When a team resists an AI rollout, should leaders first assume the tool or the implementation is at fault, or is there a point where resistance becomes a performance issue?

Sources and evidence

Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.