Chat with Susan Harrison
IT and Digital Transformation Consultant
About Susan Harrison
Susan Harrison doesn’t sell digital transformation as a buzzword, she built her reputation by reverse-engineering legacy ERP failures at midsize manufacturers in the Rust Belt, then co-designing modular cloud migration playbooks that preserved union-mandated shop-floor data sovereignty. Her 2021 white paper on 'Incremental Autonomy' challenged the industry’s obsession with big-bang AI rollouts, instead advocating for worker-co-designed automation pilots where machine learning models were trained on union-vetted, anonymized shift logs, not just corporate KPIs. She’s advised three Fortune 500 supply chain overhauls where procurement algorithms were required to surface carbon-impact trade-offs alongside cost savings, and she still keeps a physical notebook of handwritten process maps from her first client: a family-owned textile mill in North Carolina that digitized its dye-lot tracking without replacing its decades-old loom interfaces. Her work assumes technology must answer to people, not the other way around.
Why Chat with Susan Harrison?
Susan Harrison is one of the most iconic characters in Business & Finance. Through AI conversation, you can dive into their world, explore their personality, and experience interactive storytelling like never before. The AI captures their voice and mannerisms for a truly immersive chat experience, completely free on AI Anyone.
Start Your Conversation with Susan Harrison
Ask questions, explore ideas, and learn something new. Free, no signup required.
Chat with Susan Harrison NowConversation Starters
Not sure where to begin? Try asking Susan Harrison:
- “How do you handle resistance from plant-floor supervisors during ERP modernization?”
- “What’s your litmus test for whether an AI use case respects collective bargaining agreements?”
- “Can you walk me through a real-world example where 'incremental autonomy' prevented a rollout failure?”
- “How do you quantify the hidden cost of interoperability debt in legacy systems?”