We Go With AI Podcast

“What’s for dinner?” sounds like one question. Then come the others. How much time do I have? What’s in the refrigerator? What will everyone eat? Do I need another bag of rice, or is there enough in the cupboard?In this week’s podcast, I walk through using ChatGPT to work through those decisions. You can try the same conversation in Claude or another AI tool you use. Start with three dinners. That’s enough to practice without sorting out an entire week.Here’s the process, with prompts you can copy as you go.Start with your householdBefore asking for recipes, explain what a useful plan needs to account for. I like having AI ask me one question at a time. I can answer what’s in front of me and add details as I think of them.Copy this:Help me plan three dinners. Ask me one question at a time about my household, food preferences, dietary requirements, cooking time, budget, leftovers, ingredients I already have, and how I want to cook—for example, a slow cooker, Instant Pot, sheet pan, or stovetop. Wait until you have enough information before suggesting meals.You might remember halfway through that Tuesday is especially busy or that you want leftovers for lunch. Add that information when it occurs to you.Keep personal details as general as you like. “Someone in my household avoids dairy” gives it a practical requirement without sharing a name or medical history.Approve the menu before the recipesOnce it has enough context, give yourself a small decision to make:Suggest three dinners with a short description of each. Wait for my approval before writing the recipes.Would you actually cook and eat these meals? Do they fit your evenings? Do they use the ingredients you want to use?If something doesn’t work, explain why:Replace the second dinner with something that takes less than 30 minutes total.Or:Two of these meals are very similar. Give me a different option for the third night.For a slow-cooker meal, be clear about whether your limit is hands-on preparation time or total cooking time. Those are different requests.You don’t have to accept a meal because the plan looks polished. This is your dinner.Ask for recipes and check the detailsWhen the menu works, move on:Write the recipes for the number of servings we discussed. Include ingredient quantities, preparation steps, and estimated preparation and cooking times.Read through them before moving to the grocery list. Check the servings, the ingredients, and the time involved. A quick dinner that needs extensive chopping and an hour in the oven may need another pass.Corrections can be simple:This recipe serves six, but I asked for two. Adjust the ingredient quantities.Remember, these meals need to be dairy-free. Please revise the sauce.That review is part of making the plan useful. It also helps you notice which instructions you want to make clearer next time.Build one grocery listNow bring the recipes together:Create one grocery list organized by store section. Combine quantities for ingredients used in multiple recipes. Separate ingredients I already have from things I need to buy. Ask me to confirm pantry staples; don’t assume I have them.Before confirming what you have, open the cupboard. Check the oil, spices, and how much rice is actually left in the bag.Here’s something I do: I upload pantry photos, then use the microphone in the chat to talk through what I see in the refrigerator. Milk, broccoli, mushrooms, bell peppers, jalapeños, lemons—whatever is there. I also mention what needs to be used soon.You can try:I have broccoli, bell peppers, and mushrooms I need to use within two days. Prioritize those in the plan. Ask me about quantities if you need more detail.Check anything the AI identifies from a photo before relying on it. A photo can help start the inventory; you still need to confirm what’s there and how much you have.When the list is ready, pick an ingredient and trace it through the recipes. If chicken appears in two dinners, is there enough on the list for both? Did the fresh herbs make it onto the list? Is something you already own still listed under “buy”?You can ask AI to cross-check its work, too. Review the result yourself, and check product labels for ingredients that need to meet your household’s dietary requirements.Give next week a starting pointBefore you finish, ask:Summarize my ongoing food preferences and meal-planning rules. Separate those from details that apply only to this week.That distinction helps. A food you dislike might stay the same. The vegetables in your refrigerator, your schedule, and the number of people coming for dinner can change.I call my conversation Weekly Meal Planner so I can find it again. Next time, I can open it and say:Let’s plan three more dinners. Here’s what’s different this week.Then I update the schedule and ingredients, review the preferences it’s using, and correct anything it misses.Try three dinnersYou can build on this later with lunches, freezer meals, or pantry tracking. For your first attempt, three dinners is enough.Start here:Help me plan three dinners. Ask me one question at a time.Work through the menu, recipes, and grocery list. Then ask yourself: What did I need to explain or correct to make this useful?Maybe it needed more detail about your schedule. Maybe the meals were too complicated. Maybe you realized leftovers matter more than you’d mentioned.Bring that learning into the next conversation.If you try it, tell me in the comments: What did AI get right, and what did you need to change?Go first. Learn out loud. Bring others with you.

A very full photo library became an experiment in designing a system I could actually maintain.

In this episode: why finding and using saved material mattered more than freeing storage; the weekly habit I pushed back on; monthly learning-resource capture and quarterly personal-photo review; what our Pinterest test revealed; and which automation still needs testing.

Try it: ask AI to help design a low-maintenance system around your real review habits. Start with one small, non-sensitive collection. Check whether you can retrieve an item later, and keep decisions about moving or deleting content in your hands.

Read the companion article and copy the prompt at We Go With AI: https://wegowithai.substack.com

Go first. Learn out loud. Bring others with you.

Welcome to We Go With AI!

We’re going first—and bringing others with us.

I’m excited to officially launch the We Go With AI Podcast!

Over the past 25+ years, I’ve worked through some incredible shifts in technology. From the early days of the internet, email, and instant messaging to enterprise software, digital transformation, and now artificial intelligence, I’ve seen firsthand how technology changes the way we work.

But one thing has remained consistent through all of those changes.

Technology alone doesn’t create transformation. People do.

That’s really why I’m starting this podcast.

I’ve spent much of my career helping organizations implement technology, navigate change, and build the skills and confidence needed to work differently. More recently, my work with generative AI has reinforced something I believe deeply: the biggest opportunities aren’t just about what AI can do. They’re about what people can learn to do with it.

And we’re all still learning.

What you can expect

Through this podcast, I’ll share real experiences, practical ideas, lessons learned, and conversations with people who are navigating AI transformation in their own organizations and careers.

We’ll explore questions like:

* How do we move beyond AI experimentation to meaningful adoption?

* What does it really take to help people build confidence using AI?

* How can leaders create environments where learning and experimentation are encouraged?

* What can we learn from the successes, mistakes, and experiences of others?

Some episodes will feature conversations with leaders, practitioners, and people doing interesting things with AI. Others will be opportunities for me to share what I’m learning along the way.

You won’t find a lot of hype or promises that AI will magically solve everything.

What you will find is curiosity, practical learning, and a willingness to figure things out together.

Why “We Go With AI”?

Because I believe we need more people willing to go first.

Not because they have all the answers, but because they’re willing to try something, learn from the experience, and bring others along.

You don’t have to be an AI expert to participate in this transformation.

You just have to be willing to begin.

Your Go First moment

Here’s my invitation to you this week:

Think of one thing you’ve been curious about trying with AI but haven’t gotten around to yet.

Give yourself 15 minutes to experiment.

Then share what you learned with someone else.

It doesn’t have to be perfect. In fact, it’s probably more valuable if it isn’t.

That’s how we start building confidence, one experience and one conversation at a time.

Let’s keep the conversation going

If this resonates with you, I’d love for you to subscribe to We Go With AI, listen to the podcast, and share it with someone who might benefit from the conversation.

You can also explore the We Go With AI newsletter, where I share practical ideas, tools, and reflections on AI adoption, leadership, and learning.

I’m looking forward to the conversations ahead and to learning alongside you.

Go first. Learn out loud. Bring others with you.

— Kristi

Creator & Host, We Go With AI