Steven McPhee shares how the real goal of a Copilot Catalyst program is building strategic adaptability. AI toolsets will inevitably change over the coming years, but organizations who know how to learn and adapt will be able to take advantage of opportunities.

Rather than start with AI tools and how they can provide value, Steven McPhee recommends identifying business challenges with an “AI blindfold” on and then seeing how AI can be of help.

Steven McPhee provides a frame for thinking about AI investments: fertilizer, making the organization stronger without immediate impact, and staple crops, showing clear returns. He recommends a portfolio with both types of AI initiatives for long-term impact.

Despite the name, Steven McPhee describes how our Copilot Catalyst program isn't really about Copilot. Rather, it's about giving leaders a shared bootcamp experience with a common framework and hands-on practice with enterprise AI.

AI adoption expert Steven McPhee discusses how direct reports follow what leaders model, so one skeptical VP can meaningfully slow down AI adoption. That's why we learned to cross-pollinate teams, share real stories, and work across departments.

Steven McPhee shares the sobering insight that three good experiences create an advocate, while three bad experiences will create a vocal skeptic who stalls momentum across entire departments. That's why we engineer deliberate quick wins in AI adoption.

Steven McPhee shares the insight that AI moves too fast for feature-based training to stay relevant, but fluency compounds forever. That's why we stopped teaching "click here, prompt this" and started teaching exploration, error recovery, and peer learning.

Steven McPhee shares practical takeaways from rolling out Microsoft 365 Copilot. This includes learning to start with a short, high-energy sprint, then pivoting to measured reinforcement.

Steven McPhee shares how enthusiasm cascades down from leaders’ own experimentation in Copilot adoption. Instead of a handful of high performers lobbying for a broader rollout, executives lead the charge and tell the story that keeps the investments flowing.

Steven McPhee summarizes eight lessons learned from rolling out Microsoft 365 Copilot to a pilot group of twenty leaders. These aren’t theory or best practices. Just what actually worked.

This month marks four years since starting FlexPoint Consulting. In honor of the milestone, our team shared a series of “4 things...” thoughts throughout the month of July.

Pedro Cortez reflects what we can learn from his son’s (temporary!) set-backs in Ninja competitions, including tenacity, preparing thoroughly, and resisting reacting in panic when things go wrong.

In honor of March Madness, Liz Pryor reflects on this season of coaching middle-school basketball. Her team navigated considerable adversity, and she saw a lot of improvement on (and off!) the court.

What is one of the most important elements of a discovery session? Keen insights? Not quite. A bingo on the consulting jargon card? Nope. Kim Ehrman argues that it is silence, so we can give space for everyone to think and truly learn from the discussion.

Kim Ehrman describes four key elements of FlexPoint discovery sessions, semi-structured conversations where we know the topic of interest but we truly don’t know what we’ll find out along the way.

Kim Ehrman shares details from a car running into her house and draws lessons learned for consultants and clients based on the experience.

Kim Ehrman and Michael Daehne share questions to ask in connecting the dots between four key digital topics and their people implications. We can increase the effectiveness of technology efforts by designing them around their impact on people.

Kim Ehrman and Michael Daehne share reframed -- and sometimes counterintuitive -- perspectives on critical business topics like integration, work-life balance, and career advancement.

Building on learnings from a recent Inflect podcast, Kim Ehrman shares how to define desired metrics vividly enough to collaborate with Analytics and IT teams to create or gain access to them.

Michael Daehne argues that teaching -- rather than explaining -- big technology concepts drives more long-term success. He shares five tactics to teach ideas, including being clear on why the topic matters, identifying learning objectives, and more.