Skip to main content
I’m starting to think that “creating an AI prompt” is the fastest way of transferring knowledge as a product leader. When I use the ✏️ edit button and do 5-10 iterations on a prompt to get the result I want… AI is squeezing me to extract my “taste” in ways traditional docs or feedback never could. (And in 1/10th the time) When PMs iterate on prompts with AI (whether for a PRD, marketing email, API docs, or knowledge base docs) what they’re actually doing is:
  • Capturing our feedback in rapid cycles
  • Articulating domain knowledge that was previously tacit
  • Codifying our taste and judgment standards
Each time I add a clause and sharpen what I want, the AI has essentially squeezed out of me the practical knowledge and subtleties I didn’t even realize I possessed. It’s no longer 2023 and prompt engineering is not about “magical spells.” It’s just about iterating until you like the result. (That’s value that others don’t have to spend time creating on their own!)

​
For product leaders, this creates a powerful scaling mechanism:

1️⃣ Your prompts are capturing your product judgment in ways that can be shared and scaled 2️⃣ The act of iteration itself makes you more conscious of your own expertise 3️⃣ You can package your taste and standards outside of 1:1 coaching I’m now realizing that I’ve been using this approach to scale myself without even fully understanding what I was doing. The prompts I’ve created are a strange new kind of documentation. ➡️ Turns out that arguing with an AI about “what I actually meant” 🤬 has become one of my most effective professional development tools.
If you want to go deeper on implementation and adoption, I offer live courses and workshops.