I coach with stories.
Not because stories are nicer than slides. Because a slide is easy to nod at, and a story is hard to forget when you sit back down at your own computer.
Most of the people I work with are already on a machine all day. CEOs, COOs, CFOs, CIOs, directors. You know you need AI. You are not going to chase every new AI. You are not going to build the tools yourself. You are going to sit next to Claude, or Gemini, or whatever tool you already have, and you need a way to think about what you hand it.
That is the job.
What this is
I call it story-based coaching.
We name the idea in plain language. I ground it in a story you already understand (a costume on a table, a stack of rocks, a student you would let sign the return). Then we use it the same hour, on the thing that is actually stuck.
I was a teacher before I wrote software. I still do not walk in with a 40-slide curriculum. Every session starts the same way. What have you worked on since we last talked?
If the answer is "I spent an hour arguing with the output," we do not add another tool. We change the move.
What this is not
It is not a chatbot class.
It is not a dump of prompts you will not open again.
It is not me pretending you should become an engineer.
Consultants leave a deck. Workshops leave a folder. Coaching is the same person, the same context, week after week, until the new habit is just how you work.
How a leader should use AI
You cowork with it. You do not vanish into it.
You keep the decisions that have your name on them. You let the model draft, cluster, summarize, and make the ugly first version. You read what it made. You decide what is good enough to send, and what has to go to someone technical.
That last part is most of the value. Knowing when to stay in the chair, and when to hand the work to someone who builds the software, is a leadership skill. It is not a prompt.
I can build the repeating work too. When a team needs a closed workspace (real tasks, real security, a place to try this without leaking the company), I set that up as a separate piece of work. I do not teach the build in a blog post. I will tell you whether you need one.
Who this is for
You run a mid-market firm, or a function inside a larger one. Your board or your clients are asking about AI. You have tried a tool. It was fine. Nobody quite trusts it.
You want to think clearly, not collect software.
Who this is not for
Teams that only want a class, or a folder of prompts, and no time from leadership.
If you want to become the engineer, there are better places to learn that than me.
Stories I teach from
These are short. Each one is one lesson. Read them in any order.
If you want to talk
Start with a conversation. If we are not the fit, you will still leave with something you can use on Monday.
jake.k@jwal.ai · Book a Discovery Call →
Contact me for pricing. Five seats is the coaching floor.