Writing The Right Prompt - Lessons from a Ski Jacket

Once a year, I head to Colorado to cautiously ski down the easy part of the mountain. My gear of choice has been a big fluffy yellow jacket. Upon greeting the family for the holidays, my sister’s welcome was slightly colder than the wind chill:

“You look like the Michelin Man with jaundice.”

Ok then. New jacket it is.

Gemini Prompt:

You are a ski fashion designer. What should I buy to look like I belong on the mountain?

Armed with a list of brands, I went to the store and met a 33 year sales veteran who calls himself Red:

“I’m looking for this [Insert Expensive Brand] jacket.”

“Why?” said Red.

“Ummm, I want something fashionable?”

Red said: “You don't really want fashion. You want comfort.”

Fifteen minutes later, I had a goose down parka that cost 38% less than I thought. How had I screwed up? Simple: The Prompt. I had over-indexed on "fashion" and neglected the "local expertise" constraint.

From the Slopes to the Runway

This brings us to our Scheduling conundrum of the day.

I recently sat down with Maestrow to analyze a carrier revamping its network in Q1 2026. The goal? Shedding unprofitable routes. My initial prompts focused heavily on frequency reductions. The results were great - graphics, analysis, and intelligence on where the carrier was pulling back.

But I made the "Yellow Jacket" mistake again. I was looking at the cuts, but I hadn’t asked the most important question: “What is happening to the planes?”

When I adjusted the prompts to look for insight into next steps - the "dry" data became a much different tale. The real story was a Fortress Hub expansion. The carrier wasn't just shrinking; they were reallocating to out-schedule on primary routes.

I almost missed this!

Your Intellectual Partner

Using an AI platform like Maestrow is a constant exercise in discovery. Our CIO, Chris, and I often "get into it" (sometimes in a collegial manner) regarding “Teaching the User” vs. “The User Experience.”

Chris argues that the system should be intuitive—and it is. Maestrow gets smarter daily by digesting our documentation libraries and existing prompt histories. However, I have to (grudgingly) admit that Chris is right: Prompt Context is everything. If you ask for a "fashionable" schedule, you’ll get one that looks good on a slide deck.

But if you treat the system as your intellectual partner and ask about the effects of asset reallocation, you get the "Red" version: the truth that saves you 38% and reveals the competitor's next move.

So, what have we learned?

1. Always ask what happens to the planes when the route is cut.
2. The right prompt turns "dry" data into actionable strategy.
3. My doctor has officially confirmed I do not have jaundice.