Readiness is not Application with Mike Simmons

Are you AI ready, or are you applying AI to do better work?  It's a simple question, it may be hard to answer. What happens when the "what changed" question comes up?
In this session I'll share how we apply the Catalyst Learn.Think.Act. & Mindset.SkillSet.Toolset. Frameworks to move from AI Readiness to Application, and Results. I'll share what we have built, why we have iterated, and how we have fired ourselves from specific work in the business.

Results by design are better than wishful thinking.

‍

Session Transcript: Readiness Is Not Application

Event: Human-Led AI for Instructional Designers‍

Speaker: Mike Simmons

‍Host: Luis Malbas

Luis Malbas: Alright. Here we go. The event has started, and this session is live. Welcome! Let me take a look and see if people are coming in. Helen has entered the room. Kathleen is here. Welcome. How are you this morning? Here comes everybody—Amanda, Karen. Welcome, everybody.

In the chat area, if you can, please just type in where you're logging in from. Kathleen is saying that she's still caffeinating. I hear you. I just took my last big gulp of coffee. Nicole, welcome. And Kathleen is coming in from California. Yes, everybody, please, as you log in, type where you're coming in from. I'd love to see that and get the chat area working.

Looks like we've got everybody. Oh, Mike, you're in Orlando right now? Are you doing a conference or anything?

Mike Simmons: I am. No, we just came out here for a quick trip before heading to Dallas. Andrew's got a swim meet in Dallas, so we did this to kind of chill out for a little bit and then head to Dallas.

Luis Malbas: Nice. Alright, welcome, everybody. This is Human-Led AI for Instructional Designers, and I'm just going to do a little bit of housekeeping to let you know what's going on. We are in Airmeet, a platform I've loved and used for years. In between sessions, there is a chat area with tables. I'm probably going to be going in there every once in a while. If you have any questions about TLDC, membership, or anything that the community does, I'm happy to answer them. You can go in there and host a table as well; they act as little AMA areas to just chat.

A little bit about this particular event: I think that AI has basically disrupted L&D in so many different ways. I am sort of still unsteady on my feet on exactly how I'm managing TLDC on a regular basis, trying to figure out what is relevant anymore in L&D, how the audience is changing, and how things are evolving. As somebody who has always been eternally curious, AI has disrupted my process for curiosity. All of a sudden, I can get instant answers about so many different things rather than doing the research and making the connections I used to have to make. I almost just don't have to do that anymore because I can ask AI to complete these tasks.

So, I'm still figuring out how to get on my feet about producing these virtual events and finding content that is relevant in November 2026. In a way, this particular conference is something that I'm selfishly wanting to do because I want to know how we can use AI as a copilot in instructional design versus being controlled by it.

I'm really excited to have Mike Simmons here to help with that because Mike has always been a leader in this space and has spoken many times for TLDC. Let me tell you a little bit about him. Mike is a go-to-market strategist and leader with over 30 years of experience driving revenue and sales effectiveness. Through his company, Catalyst Sale, Mike has helped more than 100 organizations—from early-stage startups to $250 million enterprises—replace confusion with clarity and execution. He's here today to share his practical approach to strategy and actionable next steps.

Mike is going to be using a device called a reMarkable Paper Pro. I suggest you maximize the screen on this one so you can see how he's using this technology and see the whiteboarding. If you mouse over the screen, you should see a tool in the upper right-hand corner that will maximize your view. Helen says she has a reMarkable 2 and loves it. I'd never even heard of the device, so now I'm super curious. I love sessions like this where I get to geek out a little bit.

Go ahead, Mike, take over. I'm going to maximize my screen and mute my microphone.

Mike Simmons: Perfect. Thank you, everybody. Keep the chat going. If there are any questions on anything that comes up, please let me know. I'm going to do this format differently than I've ever done before, so we'll deal with technology as it comes.

My goal is that throughout this process—and this is any time I'm speaking with a group—we take in information. Sometimes it's information we already know, especially with me, because I tend to focus on fundamentals. These are things we learned in kindergarten, on the playground, or playing sports, and how they apply over and over again in life.

We take in something new, maybe we learn it for a second, third, or fourth time. Then we think and reflect on how it applies to what we already know. Here's the whiteboard going: We learn. (And you'll see my handwriting peaked in second grade.) We think. We reflect on how it applies to something we already know. This is the reflection piece. We ask questions. The reflection piece is super important because when you connect the new thing to what you already know, you connect those synapses. Then you start to feel more comfortable taking action. We act.

And then this becomes a loop: We learn. We think. We act. We repeat. Over time, what we should start to see is that our inputs—from an action perspective—start to create the output that we're looking for. If it doesn't, then we figure out how to adjust. This concept is my approach to adult learning theory, and it applies directly to how we can leverage this emerging tech that's in front of us.

To provide a little background, I left a thousand-person organization to join a small startup called CBT Systems right about the time they changed their name to SmartForce. This is where I first got into emerging enablement technology—new technology that enables humans to do human things better. That drives me: helping humans do what they want to do, better and faster.

Luis shared a story about how AI is changing how he interacts with content. Now he can ask a question in a chatbot and get feedback that helps him understand something or put together a process. The very first prompt I put into OpenAI's ChatGPT back in October 2022 was, "How do I train my dog how to sit?" It wasn't because I needed to know how to train my dog; I wanted to see what the tool would return. How close would it be to the actual conditioning and training process? I was shocked, and it put me on the path that most of us have been on for this four-year period.

We learn, we reflect on how it applies to what we already know, and then we take action. When thinking about the human aspect of AI, consider: What is it that you want to convey to others? What do you want to learn? What do they want to learn? Then, how do you prompt the tool to think about it differently? Finally, what do we actually do with the output? How do we evaluate if the thing is returning what we expect?

These machines are not intelligent. As much as they feel magical, they're just doing a lot of stuff in repetition, fast. I am technical, but I'm not a software engineer. Yet, I've used these tools to create software applications today that I couldn't have done nine months ago, specifically around website development. I use this reMarkable Paper Pro to interact with the bots I've got working as part of my team. I provide feedback on website design—which I was doing on the plane to Orlando—and get the bots to do the work so the website is updated. The off-site page, the whiteboarding page, the main page at CatalystSale.com—those have all been redesigned without me putting my hands on a keyboard. I couldn't have done this three months ago, let alone four years ago.

So, we learn, we think, we bridge the gap with action, and we reflect on what we just did. I want everybody to keep that loop in mind. The second part that is really important here is Mindset, Skill set, and Tool set.

Mindset for me is an acronym: A, B, C, D. Attitude, Belief, Clarity of Definition. Clarity of definition is so important. When we talk about leadership, my mindset definition is: Leaders build leaders. Leadership starts with self. Leadership is how we move forward.

Next is Skill set. In order to lead, there are five core skills: Problem-solving, decision-making, goal-setting and execution, design, and communication. Today, we're going to talk about the design and decision-making aspects.

Finally, Tool set. It is always in this order: Mindset, Skill set, Tool set. It's super easy for us to go out and buy a piece of technology. But a fool with a tool is still a fool. How do we create leverage with the tool? We create leverage with skills. Skills applied using a tool will help you create leverage. As Archimedes said, if you give me a lever long enough, I can move the world. We just have to know how long the lever needs to be and where to place the fulcrum.

Tools are going to change incredibly quickly. You will not be able to keep up with that, and it's a fool's errand to think you can. What you can do, where you have agency, is build the skills so that you can create leverage with the tools.

If we have those stable building blocks, we can literally build and do anything. A few months ago, a smart light switch in my house went out. I found out the app for my Wemo switches had been end-of-lifed by Belkin. Instead of replacing all the switches, I thought, "I know the MAC addresses. Can't I build an application to do this?" I prototyped it with Grok on my phone, and the following day used Claude to code the application. Within 24 hours, I had a working application on my phone that turns our switches on and off. I've never built applications, but I built that quickly.

As instructional designers leveraging technology to enable human performance, you can create environments that work perfectly for your users in their operating spaces.

Let's get into how we actually do this using decision-making. Fit is one of those things you cannot manufacture. Many people try to squint and make it work. I want you to think about how you create fit and where you want to focus your attention when serving your customers. From a "jobs to be done" perspective, what is the objective we need to achieve when building or deploying something? Does it need to be mobile? Does it need to work without an internet connection? You map out four to five binary requirements (Yes/No statements) to create lines of clarity. Decisions are about cutting things off. We sever.

Luis Malbas: Hey, Mike. Can you do an example that is more specific to instructional design?

Mike Simmons: Yp. Give me a scenario where someone might be looking to build and deploy some kind of content inside an operating environment.

Luis Malbas: Let's see... Sophia in the chat has a good one: Onboarding a franchise restaurant.

Mike Simmons:Awesome. Sophia, do we want to look at this through the context of finding the right owners, creating content to support the owner doing the work, or helping the owners find employees?

(Checking chat)

Okay, creating content that supports the owners so they can retain the brand's reputation. Perfect. I've never owned a franchise, but conceptually, we can work through this.

First, they need to put the brand out to the market to attract customers and employees, so I would put "Brand" at the top. Next, the owners are going to be super busy. They need to hit the ground running; they are there to operate a business, not go through extensive training. So it needs to be "Simple" and digested in "Small" increments. Finally, it needs to be accessible in their operating environment, so "Mobile."

So we have: Brand, Simple, Small, Mobile. You map these up and prioritize them to determine what needs to be true to deliver that in this environment. You're defining the list and prioritizing it so you can go back and ask, "Is the work we're doing actually aligned with this?" You are applying decision-making to break a complex scenario down into smaller parts. In instructional design, you might think of this as a rubric you use to measure against.

Let's move into one more tool to simplify this. How many people are familiar with the Eisenhower Matrix? Urgent vs. Not Urgent, Important vs. Not Important. I have one I've created specifically around how we optimize our work. On the X-axis, it's "Sucks the life out of you" on the left, versus "Builds you up (creates energy)" on the right. For me, meetings where we don't take action suck the life out of me. On the Y-axis, it's "Low Impact" versus "High Impact" on others.

When you think about the daily tasks you do as an instructional designer, which ones suck the life out of you? Some people love research, some love building, some love iterating. The exercise is to figure out which tasks build you up and are high-impact.

Your goal is to move as much work as possible to the top right (High Impact / Builds you up). For the work that is high-impact but sucks the life out of you, find a partner. Today, one of the most amazing partners is an AI tool—a bot, an agent, or automation software. Write down what you do throughout the week, give it a plus or minus for energy, and rate its impact. Eliminate the things that are low impact and suck the life out of you.

Luis Malbas:I'm curious, Mike, if anybody in the chat can list some of the "remove energy" tasks that people are universally feeling right now? Tasks that AI could take over?

Mike Simmons:(Reading chat) Pulling information from SME brains. Tedious manual adjustments of timeline edits. Having to do constant iterations based on feedback from people who have no context. Travel, lead generation follow-up, holiday gift giving. Brutal! These are exactly the kinds of things.

This gets us into design. Decision-making is about cutting things off ("Do, yes, or do not. There is no try."). Design thinking is about designing backward and executing forward. Begin with the end in mind. If you know what Z is (the desired state) and you know where A is (the current state), you can bridge the gap.

When you're working with an SME, it's hard because SMEs skip steps. But as an instructional designer, you are plotting out the exact stepping stones to get that franchise owner from new operator to thriving operator. You work backward from success and test forward. When you break these workflows down into small, simple steps, you can figure out exactly where to outsource a specific step to an AI agent, bot, or software.

A big mistake I see today is people thinking they have to do everything inside a chat LLM. Sometimes it makes more sense to build a specific piece of software or automation with distinct guardrails to do that repetitive work for you. There is a difference between rules (binary yes/no), guidelines (areas for creativity), and guardrails (boundaries we don't cross). When you have rules, guidelines, and guardrails, you get the systems to learn much faster.

(Mike's connection briefly drops)

Am I back?

Luis Malbas:Yeah, you're back. You dropped out for just a couple of seconds.

Mike Simmons:Here's an exercise I'd like everybody to do. Take out a piece of paper and write: "It sucks that _________." Fill in the blank to identify a problem. Then write: "It would be awesome if I could _________."

Those two statements will help you gain perspective around problems you want to solve and things you want to innovate on. Apply the design thinking and decision-making components we just shared, and you will do things in the right order: Mindset, Skill set, Tool set. Create the definitions, build the skills, apply the tools.

I hope this was useful. Thanks, everybody, for dealing with the technical stuff. I am happy to answer any questions.

Luis Malbas:Sophia had a question about something you showed earlier regarding firing clients.

Mike Simmons:Yes, sometimes it just isn't the right fit. Some people want to be perceived as wanting to change but won't actually do the work. The faster I eliminate customers or specific work that isn't a fit, the more time I have to focus on the things I'm meant to do.

For example, I like being creative, but I don't like paying attention to detail when it comes to typos. It sucks the life out of me. It would be awesome if I could solve for it. So now, I have one of my bots—the CMO bot—proofread content before it gets pushed live on the website. I fired myself from that specific work.

Luis Malbas:Mike, I have to ask you something relevant to both of us. A couple of years ago, O'Reilly Media went all-in on AI first for everything. Every employee had full access to Claude, ChatGPT, Gemini, etc. We were instructed to use AI in every process. On my team, I focused on using AI to optimize the tools we already had. But a partner on the team, who loved coding, started building competing products with AI that I knew would eventually replace what we were using.

Thinking about your Mindset, Skill set, Tool set idea—especially since I got laid off from O'Reilly in September—it feels like people are just going to be infinitely building tools. Doesn't the skill set have to be how well you can navigate and become proficient at all these tools people are building?

Mike Simmons:Just because you can, doesn't mean you should. Yes, I could build a new CRM locally on my Mac. I could use up all my tokens prototyping. But that doesn't mean I'm prepared to build the right thing.

This goes back to the core skills: What are we trying to achieve? What is the journey we're trying to create? What do we want to eliminate? If you build those foundational skills—problem-solving, decision-making, goal-setting, design, and communication—you will build the right thing. It is so easy to build now, but you could build a bunch of stuff for nobody that never gets used, like a treadmill that just holds laundry.

You have to make a buy versus build decision based on security risk, operational risk, and user experience. But at the same time, if you aren't building and testing, how are you going to learn what these tools do? Get out there and build.

Since everyone can build now, the real question becomes: How do we be more human in the way we interact with people? How do we help people solve problems using our domain expertise? The two biggest challenges organizations face right now are an aging workforce and hiring people. Those are challenges that people with instructional design and enablement backgrounds are perfectly positioned to solve.

Luis Malbas:It's a lot to think about, and I'm still trying to find my way. In fact, my next event is probably going to be about change management, because as content development is commoditized, those are the pathways that will be helpful to everyone.

We've gone a bit over time, so we better wrap it up. Mike, thanks so much. Enjoy Orlando. Thanks everyone for being here. Our next session is at 10:00 AM Pacific time. The speaker couldn't attend live, so we're going to try broadcasting her pre-recorded session. Feel free to drop in! Thanks again, Mike.

Mike Simmons:Thanks, everybody. Bye for now.

‍

Key takeaways

Similar videos