The Art of the Ask: Mastering Prompt Engineering for Better AI Results

Mar 10, 2025

Alvin Omozokpia

When I first stumbled upon Google Voice’s early voicemail transcriptions, I felt as if technology had learned to speak my language. At that moment I realized something profound: how we phrase our questions shapes the answers we receive. Years later, I saw the same truth play out in real time with ChatGPT, and it changed the way I approach every AI interaction.

Finding My Voice in AI Conversations

I recall the day my Applied Product Management Professors, Nan Jia and Gordon Ho, invited me to lead a session on prompt engineering and building products with AI in my final semester at the USC Marshall School of Business. Standing before my classmates, I guided them through building a simple Tic‑Tac‑Toe game one prompt at a time. Watching their “aha” moments taught me that effective prompts are less about clever hacks and more about clear intentions. From that point on, every time I sat down to work with an AI agent, I treated it like a colleague who needed context, structure, and respect.

What I’ve Learned Along the Way:


Context is King (and Queen, and the Whole Court)

When I start a prompt, I gather everything the AI might need: screenshots of my current wireframes, snippets of code, even a short note about why I’m asking. It’s like prepping for a meeting: the more background I share, the more tailored the AI’s suggestions become.

Be Precise, Not Pedantic


I once asked for a user‑flow outline and ended up with a dense, two‑page report. Since then, I’ve learned to specify format and length: “Give me a three-step flow in bullet form” or “Show me JSON with keys: step, description, next action.” That guidance keeps the output lean and immediately usable.

Guide the AI’s Thought Process (Give it Room to “Think”)


For complex tasks, I prompt the model to walk me through its reasoning. A simple “Explain how you arrived at that recommendation” often uncovers hidden assumptions and reveals opportunities I hadn’t considered. It’s as if I’m peeking under the hood of the AI’s logic engine.

Own the Outcome (No Emotional Baggage)

When a generated design or code snippet isn’t quite right, I resist blaming the AI. Instead, I ask myself which piece of context or example I missed. Each revision of my prompt sharpens my own understanding and results in a cleaner, more accurate response.

Rolling Back and Experimenting


There was a time I tried to patch a flawed UI mockup layer after layer, and it became a tangled mess. Now I rely on my tool’s rollback feature, revert to the last solid state, and reissue a focused prompt. This simple habit has saved me hours of frustration and freed up mental space for creative exploration.

A Little Politeness Goes a Long Way (Maybe?)

Okay, this one’s partly tongue-in-cheek, but I genuinely believe in interacting respectfully. I know AI can’t feel gratitude, but adding a quick “please” or “thank you” shifts my mindset. It turns the session into a collaborative rhythm rather than a transaction. That small gesture reminds me that I’m in control of the conversation and responsible for steering it toward the most valuable insights.

Looking Ahead

Prompt engineering is an evolving craft. Every project teaches me something new, whether it’s the importance of naming conventions in code, the power of real‑world examples for clearly illustrating a feature, or the subtle art of asking “What’s a blind spot I’m missing?” As I continue this journey, I’m excited to share these lessons and help others discover how to unlock AI’s full potential.

©2025 Alvin Omozokpia. All rights reserved.

©2025 Alvin Omozokpia. All rights reserved.

©2025 Alvin Omozokpia. All rights reserved.