I've built automation into the core of Fulfill.com's operations, and here's what I've learned: your automation champion needs to be a translator, not just a technician. The best champions I've seen can speak both languages - they understand the technical possibilities but obsess over business outcomes. At Fulfill.com, we've automated document processing across thousands of warehouse integrations, from purchase orders to shipping labels to inventory reports. The person who led this wasn't our most senior engineer. She was a mid-level operations manager who spent two years manually processing these documents and knew exactly where the pain points were. That's the profile you want - someone who feels the pain daily and has the credibility to rally others around the solution. For recruiting internally, I've found success by framing it as career acceleration, not extra work. When we identified our automation champion, I made it clear this was a 6-12 month rotation that would position her for leadership. We backfilled 50% of her operational duties and carved out 10-15 hours weekly for automation work. The key is making it official - not a side project, but a recognized role with clear objectives and executive sponsorship. The technical versus business question is a false choice. Your champion needs enough technical literacy to evaluate tools and understand what's possible, but they don't need to code. What matters more is process thinking - can they map workflows, identify bottlenecks, and quantify impact? At Fulfill.com, our automation champion spent 60% of her time on stakeholder management and change management, 30% on process design, and only 10% on technical implementation. That ratio surprised me initially, but it's proven right. Time commitment varies by phase. In discovery and planning, expect 15-20 hours weekly. During implementation, it might spike to 25-30 hours for 4-6 weeks. Post-launch, 8-10 hours monthly for optimization and expansion. We learned to batch automation projects quarterly rather than running them continuously - it prevents burnout and allows the champion to maintain some operational connection. The biggest mistake I see is choosing someone too senior or too junior. Too senior and they can't dedicate the time. Too junior and they lack the organizational influence to drive adoption. Look for someone 3-5 years into their career with strong relationships across departments.
What I look for in an automation champion is someone who's naturally curious about why a process takes as long as it does. Not the loudest voice, not the most technical person, just someone who sees patterns and asks the annoying but useful questions. You recruit them internally by giving them permission to fix one pain point they already complain about. That way it doesn't feel like extra work, it feels like removing friction from their day. Whether the champion is technical or business-focused matters less than people think. The best ones sit in the middle. They understand the workflow well enough to spot edge cases and can work with technical teams without translating everything three times. Time-wise, a realistic commitment is 2 to 4 hours a week once you're past the first sprint. Enough to steer, not enough to derail their day job. If it requires more than that, the process isn't ready for automation yet.
What I've found is that the best way to recruit someone internally without overwhelming them is to shift the workload, not stack it. The mistake most teams make is asking a high performer to 'help' with automation on top of their current job. Instead, I start by freeing up 10 to 20 percent of their time by removing low-value tasks or redistributing routine work. Then I frame the role as an opportunity to fix the headaches they already face. When people see that automation will eliminate the very tasks that drain them, they lean in. It becomes growth, not extra work, and that's when you get real buy-in from the inside.