Case study
Siemens: an AI agent platform for the US workforce
Built and launched Spark AI, a 120+ agent platform for 1,000+ Siemens US employees across every major function, took adoption from 3% to 65% in 10 weeks, and presented a 3/6/12-month AI roadmap to US leadership.
Confidentiality. Details are under NDA; this describes my role and approach, not proprietary specifics.
Context
In summer 2026 I worked at Siemens as an AI Product Strategist in the XPS Program, focused on the Siemens US organization. The assignment was enterprise AI adoption: getting AI into the daily work of employees across every major function, not only engineering.
The problem
At the start of the summer, few people across the US organization used AI in their daily work. The work was to give employees in each function, at each level of seniority, AI tools built for their own jobs, get them to actually use those tools, and leave leadership with a plan for the next 12 months.
My role
My manager originated the idea for the platform. I built and launched it, drove adoption across the organization, and wrote and presented the roadmap for what should come next.
What I built / did
- Built and launched Spark AI, a custom AI platform for Siemens US made up of 120+ custom agents and 50+ custom skills, built for specific job functions and seniority levels rather than as one general assistant.
- Deployed it across 1,000+ employees spanning all major job functions.
- Designed and presented a 3/6/12-month AI transformation roadmap to Siemens US leadership. It was sequenced by each function's readiness, mapped the dependencies between steps, and tied role-specific success metrics to measurable workflow efficiency outcomes.
Results
- Active adoption rose from a 3% baseline to 65% in 10 weeks, with 650+ employees actively using it by the end of the summer.
How I worked
I wrote a product spec first and built against checklists with acceptance criteria. At the end of the summer I demoed the platform live to the team and walked through what worked and what did not.
What I'd do differently
More QA before each release, and a steadier cadence of smaller releases instead of large drops.