I met her for coffee expecting a conversation about podcasting. I left thinking about systems.

She runs an agency and a content brand, and the agency is a mess right now. Corrective actions. Firings. People walking out. She told me all of it across the table, and she looked exactly how you'd expect someone to look when they're managing chaos by hand, every single day. Frazzled is the right word.

At some point I asked what her podcast was really about. The concept. Who it's for, what it does for that person. She talked for a while. I still couldn't have told you at the end.

When a business has no processes, you can see it on the person running it. She was reactive in real time, mid-conversation. A phone buzz pulled her eyes down. An answer that should have been quick took a long lap around the room before it landed. The podcast idea, which she's been sitting on long enough to be pitching it to strangers at coffee meetings, hadn't hardened into anything you could actually hand someone.

That's what the absence of systems costs. You stay in response mode. Every decision gets made fresh, from scratch, with whatever mental bandwidth is left over after the fires. There's no stored thinking to draw from because nothing ever got written down and made reusable.

She made a comment that stuck with me: she said she'd love to have Mel Robbins on the show someday. I kept a straight face. But my actual reaction was that the gap between "I want a famous guest" and "I can't explain what my show is" is exactly the gap that systems close. They do the thinking once so you don't have to do it again under pressure. They let you move fast on the things that matter because the low-leverage work already has a track.

She invited me to a networking event on Saturday and I'm going. She's interesting and the connection is worth having. But I'll think about her for a while, because watching someone that smart run that hard and still feel that far behind is a useful thing to see. The problem is the absence of systems to hold the effort.