How do I introduce our first AI project without our 30-person team assuming it is a plan to cut jobs?
Introduce a named workflow improvement, not a vague company-wide AI transformation. Explain which low-value task you want to reduce, who will help design the change, and what employees should be able to do with the time recovered.
Starting with employee productivity is a practical approach because recurring administrative work consumes paid capacity. That does not justify making promises about staffing that leadership cannot keep. Be direct about the project's purpose and honest about any broader organizational decisions.
Before building, ask the employees doing the work where time disappears and which exceptions demand judgment. Choose an internal champion who understands those details and has colleagues' trust. Their role is to help shape a useful workflow, not police everyone else's AI usage.
Make the first project's boundaries visible:
- Name the task being assisted or automated.
- Explain which decisions remain with people.
- State how employee feedback will affect the pilot.
- Describe what success means beyond simply using AI.
- Identify the valuable work that recovered capacity should support.
Measure the workflow's manual effort and cycle time, including time spent reviewing AI output. Avoid turning the pilot into an individual employee ranking exercise. Otherwise, people have a reason to conceal errors or exaggerate savings.
Give leaders concrete implementation responsibilities too. Adoption should not become extra work delegated downward while leadership remains uninvolved. The strongest reassurance is a small, useful improvement that employees helped validate, accompanied by clear ownership and honest communication.
Category: First AI Project