Innovation at the Edge: AI, ERP, and the Art of the Calculated Bet
In this episode of Practical Product Management, hosts Leah Farmer and Marilyn McDonald sit down with Evan J. Schwartz, Chief Innovation Officer at AMCS Group, to explore what innovation really looks like inside a large, mature SaaS organization.
Evan explains how his role works as a separate innovation track — taking high-risk bets on AI and emerging technology, running lean matrixed teams, and handing proven concepts back to the product organization once they've reached critical mass. The conversation covers how to structure innovation without creating resentment among product and engineering teams, the difference between technical innovation and product innovation, and why the most important question is simply: is there a there there?
The second half digs into ERP transformations — one of the most reliably painful experiences in enterprise technology. Evan draws on his book and years of implementation experience to explain why transformations fail, why weak upfront requirements are the root cause of most project death marches, and why "do nothing" should always be a viable outcome of a systems review. Marilyn and Leah push back, debate, and ultimately arrive at the same place: map your as-is, define your to-be, and know your why before you touch anything.
Key Takeaways
1. Innovation needs a separate track — and a clear handoff. At a certain company size, core product teams can't run high-risk bets alongside mature product delivery. A dedicated innovation function proves ideas out fast and hands them back once the questions are answered — with tight oversight and shared standards throughout.
2. Fail fast, fail cheap, and know when to stop. The job of an innovation team is to answer questions, not build finished products. "Not a good bet" is a valuable outcome. The goal is to find that out as quickly and cheaply as possible and redirect the budget.
3. ERP transformations fail because companies skip the foundations. The technology is rarely the problem. Weak goals, no baseline metrics, and undocumented processes are where implementations go sideways. Map your current state and define three ROI-backed reasons for the change before you sign anything.
4. "We have to upgrade" is not a vision. A compelling, shared picture of the future state is what carries teams through the friction of a rollout. Without it, every paper cut becomes a project-stopper.