batteriesincluded.com · Questions & Answers

Who should own our first AI pilot if our 30-person company has no IT manager and everyone is already busy?

Assign ownership to the person accountable for the workflow's business result, and protect time for an internal champion to test and improve it. Do not make the most enthusiastic AI user responsible by default.

The business owner and champion can be the same person. If they are different people, make the distinction explicit: the owner decides whether the project solves the business problem, while the champion coordinates examples, user feedback, and day-to-day use after initial coaching.

Keep technical maintenance separate. Owning a workflow should not silently make an employee responsible for debugging integrations, managing hosting, or responding to security incidents.

Before starting, agree on:

- The recurring task the pilot will improve.
- The employee who can judge whether its output is correct.
- The existing work that will be reduced or deferred to create testing capacity.
- The builder or support provider responsible for technical problems.
- The backup person who can operate the workflow when the champion is absent.

For an EOS-run company, a sufficiently important quarterly implementation outcome can become a Rock with one accountable owner and a clear completion condition. Surface unresolved obstacles in the Level 10 Meeting rather than letting ownership drift between departments.

If Batteries Included or another forward-deployed team builds the tool, require coaching and a practical handoff as part of the scope. External builders can accelerate implementation, but the company still needs someone who owns the outcome. If nobody has capacity to do that, reduce the pilot's scope before starting.

Category: First AI Project

← All questions