There was one person I just wasn't clicking with, and I couldn't say why. So I did something a little embarrassing: I had AI build a communication profile of me, then one of them, then compared the two side by side. What came back wasn't dramatic. It was just true, and I hadn't sat with it before. Includes the exact prompt I use to build a stakeholder profile from meeting transcripts.

I'd made fifteen AI use case videos with no script format, just whatever felt right that day. I transcribed all of them, fed them to NotebookLM, and asked if there was a pattern I couldn't see. There was. Six parts, and I'd been using them the whole time without knowing it.

I built this from an actual presentation to a team that didn't know where to start with AI, then found myself using the same idea to teach my eighty-something relative about cryptocurrency. Four specific habits, nothing about better tools or more time, just moving AI earlier in what you're already doing. Pick one and see what happens.

I used to send my status report after one AI pass and my own read-through. Now five personas argue about it first, the business partner, the executive, the chief of staff, and two more, each built around someone who actually reads the thing. This isn't really about status reports. It's a structure you can point at any output you produce.

AI tools want to answer. That's their default. But one extra line at the end of any prompt forces a pause that changes what comes back — and sometimes surfaces a question you hadn't even thought to ask yourself. Here's what happens in that pause, and why it's often the most useful part of the whole exchange.

Most people use meeting transcripts to capture what was said. That's not the same as understanding who said it — and why. Here's how I started using transcripts as behavioral data, and what changed when I did.

I built a Gem in twenty minutes to handle a framing problem I'd been fighting for months. That part worked. What I didn't expect was what happened when I started giving it stakeholder feedback — and asking it to improve its own instructions.

I sat down to update my resume thinking I knew what I'd accomplished. Months of daily journal entries told me otherwise — not by surfacing things I'd forgotten, but by showing me things I was actively doing that I'd never thought to claim. Turns out the gap between what you do and what you say you do is wider than you think. And it has nothing to do with memory.

I had 387 items of feedback and a process I'd trusted for years. Then AI did the same job — and the uncomfortable part wasn't the time it saved. It was the question I couldn't stop turning over afterward.

My phone was 96% full and I was leaving for vacation in a few days. The reason I couldn't clear it was an external hard drive I'd been avoiding for years — 25 years of photos, buried in backups of backups, scattered across 30-plus folders. I gave myself the weekend and let AI do the heavy lifting. It recovered 2,101 photos I didn't know I had — including the full Morocco trip I thought was only 304 photos. The number that mattered most: zero deletions.

The AI features you're not using are already open on your screen. Slack AI finds what you can't. Zoom AI Companion catches you up when you join a meeting late. Google Drive tells you exactly what changed while you were gone. You don't need new tools - you need to know what your current ones can already do.

I used to check slides the hard way - clicking every object, eyeballing every font, hoping I'd catch what my eyes kept missing. Then I wrote a script to do it for me. My first reaction was: oh shit, that actually worked. What happened after I ran it four more times is the part nobody talks about.

I'm not a developer. I don't know how to write code. I've never taken a programming class. And yet I've built automated tools that saved me hours every week — by doing exactly one thing: describing the problem to an AI and letting it build the solution.

Every meeting generates data about the people in it. Most of it lives nowhere — in your gut, in half-formed impressions. Here's how I started turning meeting transcripts into communication profiles I actually use.

Meeting transcripts are a record of what was said. That's not the same as what was meant. Here's how I started using AI to find the signal I was too busy to catch in the room.

You adapt so quickly in a fast-moving environment that you stop noticing what you've built. The journal doesn't surface things I didn't know. It surfaces things I forgot. There's a difference.

Typing made me wordsmith. Speaking kept me honest. Here's what happened when I stopped typing my thoughts into AI tools and started talking them out instead.

I pasted my messy notes in. Not the polished draft — the real one. I wasn't looking for publishable output. I wanted a second pass on my thinking. Three weeks in, something shifted. AI wasn't editing my status updates anymore. It was pressure-testing my judgment. That's a different thing entirely.

I wasn't avoiding AI because I doubted it. I was avoiding it because I thought it required a project. So I gave myself a constraint: if something would take less than 10 minutes to try, I'd try it. No optimization. No perfect prompt. Just a quick experiment layered into real work. What happened after wasn't what I expected.

I was re-thinking the same framing decisions every week. How direct should the summary be? What counts as a real risk versus noise? None of that was strategic. It was just repeated cognitive setup. I wasn't looking for automation. I was looking for less friction.