If your note-taking system feels like work, you won't use it. I finally found a tool I actually enjoy using and feel confident I can find anything again.

I use AI, but cautiously, while being as intentional as I can about where I bring AI into my life—because ignoring something speeding out of the train station generally makes the problem worse later.

A fictional detective reminded me how to build great teams: given direction, clear expectations, and encouragement, people could flourish. It's not about finding the best people—it's about creating the conditions where good people become great.

Learning to swim as an adult taught me something unexpected about the future of corporate training. After struggling through fear, frustration, and countless failed attempts, I realized what no AI could have given me, and what many organizations are missing in their approach to employee development.

And does it even matter?

Short answer: Yes and yes.

Long answer: It's complicated.

Tips for setting the scene, or writing the brief, before diving in to solve a problem with AI.

Microsoft Teams is one of those apps that people use all the time, but it doesn't get a lot of love. Is all the hate warranted? In this article, I explore that it's all in how you use it.

Ever notice how AI is sold to companies versus how it's received by the people actually expected to use it? There's a fundamental disconnect here that I want to explore.

Writing without AI feels slow and inefficient.

But, writing with AI doesn't always give us the results we want—it can be bland, bloated, and overly enthusiastic.

The question I explore in this article is how do you find the AI sweet spot for writing?

Despite the Microsoft AI promises, we still struggle with generic outputs, confused Copilot responses, and the constant need to double-check everything the algorithms spit out. This post explores the issues and suggests a few fixes.