Team resistance is information, not insubordination

Resistance triggers founder frustration — 'They're stuck in the past.' Often resistance is rational: unclear career impact, bad past tool rollouts, data ethics concerns, extra work during 'efficiency' projects. Labeling resistance insubordination wastes information.

Categorize resistance signals. Capability fear ('I can't learn this'), workload fear ('This adds tasks'), quality fear ('Clients will notice'), ethics fear ('We're cutting corners'), identity fear ('My expertise won't matter'). Each category needs different leadership response.

Respond with specifics, not slogans. Capability fear gets training and paired champions. Workload fear gets time reclaimed metrics and temporary load relief. Quality fear gets QC checklists and client feedback loops. Ethics fear gets governance transparency.

Involve resistors in design where possible — the skeptic who helps shape a pilot often becomes its best auditor. Forced adoption without input breeds quiet sabotage: minimal compliance, maximal cynicism.

Track sentiment over time through brief pulse surveys — three questions, monthly. Resistance dropping correlates with adaptation sticking. Persistent resistance localized to one team signals manager or workflow mismatch, not universal AI rejection.