Write Better Fin Guidance: Start with the Outcome in Mind. | Community
Skip to main content

A lot of us naturally default to vague guidance like,

"Make sure Fin understands our product types."

But Fin thrives on clarity. A stronger version might be:

"If a customer asks about the 'search' feature, first ask which product they’re using. Then give product-specific instructions."

See the difference? That second version gives Fin clear steps and a condition under which to act. It's specific, it's actionable, and it’s something Fin can consistently follow.

When you're writing guidance, ask yourself: what should Fin say first? What should happen next? That simple shift in thinking can make your guidance 10x more effective.

How do you typically plan out what Fin should do in different scenarios?

Be the first to reply!

Reply