Stop starting every AI conversation from zero

The 15 minutes before you ask your question

You open a new chat. You explain who you coach, the group sizes, the time you get with them, what you don't have. You paste the thing you're working on. Four hundred words later, you finally ask your question.

The answer's good. Worth doing.

Then Thursday comes. New question. New chat. And you type all of it again.

Most coaches quit AI right about here. Not because it didn't work, but because it cost fifteen minutes of setup every time it did. Anything that expensive to start doesn't survive a season.

That's not a prompting problem. It's a systems problem, and there's a built-in fix most coaches walk right past.

What a Project actually is

Every major AI tool now has Projects. Most coaches treat them like a folder, a place to file old chats so they can find them later.

That's the miss. A folder stores conversations. A Project feeds them.

A Project has two things a folder doesn't: custom instructions that apply to every chat inside it, and files that every chat can see. Start a new conversation in a Project and it opens already knowing your setting, your rules, and your reference material. You don't set the table. You just eat.

A folder remembers where you put things. A workspace remembers why you're there.

Inside the Lab: build one, and plug in last week's work

Don't build eight Projects tonight. Build one, around something you already do every week. Start with Continuing Education, the graveyard of podcasts and saved articles you meant to do something with.

Three moves.

• Drop in your Program Card. Last week's one paragraph on who you coach, your environment, your constraints, your philosophy. Upload it as a file. That single move is the whole point. You wrote it once so you'd never retype it again, and now every chat in the Project reads it automatically.
• Set the standing instructions. The custom instructions box is where the leverage is. You're telling every future chat how to hand information back, before you ask anything:
• Feed it as you go. Transcripts, papers, notes. The Project gets sharper the more you use it.

"When I bring you research, a podcast, or clinic notes: tell me what applies to my setting and what doesn't. Separate what the evidence supports from what the speaker is speculating about. Show me the simplest version I could test. Tell me plainly what I shouldn't copy without thinking first."

One Program Card, one set of instructions, one afternoon.

What it looks like in the real world

You listen to a podcast on deceleration training on the drive home. You want it, but you don't know what to do with it yet.

Old way: blank chat, re-explain your athletes and your setup, paste the transcript, hope you framed it well enough to get something usable.

New way: open the Project, drop the transcript, type one line.

"Run this."

The Project already knows, from your Program Card, that you've got 105 football athletes in four lift groups, 60 minutes, three coaches, no force plates. It already knows to separate evidence from opinion, find the simplest testable version, and flag what not to copy.

So you get back the two drills that fit your groups, the protocol that assumes tech you'll never own, and the one thing worth testing Tuesday. You're not describing your program anymore. The Project already has it.

Where the coach stays in charge

Persistent context is only useful while it's still true.

The card you built in the off-season describes a team that no longer exists once the season starts. Leave it stale and the Project confidently answers questions about a program you're not running, which is worse than starting from zero, because it looks right. Re-upload it when the season turns or the roster does.

The Project doesn't make decisions. It sorts information, drafts options, and gets you ready to think. You still decide whether the info impacts Tuesday's session, or whether that group's too beat up to add anything at all.

AI assists. The coach decides.

The Coach's Scouting Report

• Signal. A Project isn't a folder for old chats. It feeds every new chat your context and your rules automatically.
• Noise. Building ten Projects you'll never open. Letting the context inside them go stale.
• Next Rep. Build one Project for the task you repeat every week. Upload your Program Card, write your standing instructions, and start your next conversation inside it instead of from scratch.

See you next Sunday.