FLOW: How to Actually Get Great Work Out of AI
By Tatiana Dominguez
Most people prompt AI like they're shouting at a drive-through window. They drop a generic line, get a generic response, blame the AI and move on.
FLOW is the opposite. It's a four-step sequence: Frame the goal, Load the inputs, Organize your playbook, and Work the iteration. Watch the video, then keep the two-page handout next to your keyboard.
F: Frame the goal
Set your intention. Define the outcome, the audience and what success looks like, so the AI knows the destination. This is where most prompts collapse: the goal feels obvious to you, and the AI doesn't have your context. If you don't say where you're going, you get something that wanders.
Answer three questions before you type:
- What outcome am I creating? Not the topic, the actual thing. "A 200-word post."
- Who is it for? Be specific. "A mid-market CEO scrolling between meetings," not "leadership."
- What does done well look like? The honest version. "They forward it to their team" beats "engaging copy."
Thin: "Help me write a sales email."
Strong: "I'm writing a sales email to a warm lead who attended my workshop last month but hasn't booked a follow-up call. The goal is a 30-minute discovery call next week. Done well means they reply and pick a time. It should sound like me, not like a sales template."
L: Load the inputs
The output is only as good as what you feed it. Don't expect the AI to guess your brand voice, your industry, your past decisions or your constraints. Tell it. Worth loading every time:
- Context. The backstory: who's involved, what's been tried, what's at stake.
- Examples. Show, don't tell. Paste a "yes, like this" and a "definitely not like this."
- Constraints. Word counts, tone guardrails, format, things to avoid.
- Tone and voice. Casual, direct, warm? If you have brand voice docs, paste them in.
- References. Past versions and source material the AI should pull from.
The prompt gets longer. The output gets sharper. That's the trade.
O: Organize your playbook
Your first great prompt is a win. Rewriting the same prompt from scratch the tenth time is a tax. The longer you use AI, the more leverage you get from past wins.
- Save the prompt, not just the output. The prompt is the asset.
- Tag it by use case: sales email, blog post, client recap, data analysis. You'll find the right one in ten seconds.
- Version it. Save improvements as new versions. The older one may suit a different job.
- Add a two-line note: "Use for warm leads only. Too familiar for cold outreach."
- Keep it where you'll actually open it: Notion, a Google Doc, a folder of text files, a custom GPT.
Treat prompt writing as a skill that compounds. Every great prompt you save is a tool you can reuse forever, and share with your team.
W: Work the iteration
AI is a collaborator, not a vending machine. The first response is a draft, not a deliverable. Five moves that reliably make it better:
- "Make it sharper." Cuts filler and tightens the language.
- "What did you leave out?" Surfaces what it dropped to be efficient.
- "Push back on this." It finds the weak spot in its own answer.
- "Try it three different ways." Variety beats commitment while you're still deciding.
- "What would [someone] do differently?" Add a persona, a constraint or a perspective.
The mistake to avoid: accepting the first answer because it's good enough. Good enough is the enemy of great. Push one more time. Iteration isn't a sign the prompt failed. Iteration is the work.
Putting it together
The job: a quarterly update to clients about how the agency is using AI internally.
- Frame. A 400-word email to existing clients, mid-market CEOs. Done well: they feel we're ahead of the curve, not chasing trends, and nobody unsubscribes.
- Load. The three internal tools we rolled out this quarter, as bullet points. Voice: confident, specific, no jargon. Constraint: name no tools, focus on outcomes. Reference: last quarter's update, for tone.
- Organize. Saved as "quarterly client update v2," tagged "client comms, recurring," with the note: "Worked. Clients replied. Reuse next quarter with new updates."
- Work. The first draft sounded too proud. Pushed back: "More grounded. Less 'we're crushing it,' more 'here's what we learned.'" The second draft landed. Total time: about 15 minutes.
Four principles
- Framing is the lever. Spend more time on F than on the rest combined.
- Loading isn't optional. "The AI should know that" is a myth. Tell it.
- Your playbook is a moat. Fifty saved prompts make you faster, sharper and more consistent than starting from scratch every time.
- Iteration is the work. First drafts are starting lines, not finish lines.
When to use FLOW
- Always for high-stakes work: client deliverables, strategic decisions, anything with your name on it.
- Optional for quick questions, brainstorms and throwaway drafts. Sometimes a one-liner is fine.
- Especially when you're stuck. Three tries and still not happy? You probably skipped F or L. Go back.
Keep going
The handout puts all four steps on two pages, with examples written for school and district teams.
FLOW works best once you know which problem you're solving. If you're not there yet, start with It Would Be Easier If.