High-Level Product Usage Tips

1. Use Threads by Default

Threads give Hana cleaner context and make follow-ups far more reliable.

• Keep one thread per topic.
• Continue the same thread for ongoing work.
• Start a new thread if goals or participants change significantly.

Read more

2. Be Explicit About Scope and Time

Weak prompt:

@Hana what are updates in daily_standup?

Strong prompt:

@Hana summarize updates in daily_standup from today 9am-5pm grouped by owner

3. Mention People Directly

Use @mentions for people when asking people-specific questions or creating actions. This prevents ambiguity when names are similar.

4. Ask for One Outcome Per Prompt

Split multi-goal requests into separate prompts.

Good sequence:

1. Summarize decisions.
2. Extract action items.
3. Draft follow-up message.

5. Use Structured Output Requests

Specify output format up front:

• table
• bullet summary
• action items with owner + due date
• risks and mitigations

6. Add Memory Sources Early

Hana becomes materially better when grounded in your team context.

Recommended starter memories:

• SOP or runbook docs.
• Team policies.
• Project briefs.
• Org glossary and naming conventions.

Manage memory at Hana Dashboard.

7. Break Up Very Long Inputs

If a message exceeds practical chat limits, send it as multiple messages in the same thread. Hana can still reason over the sequence.

8. Verify High-Stakes Outputs

For legal, financial, compliance, or production-critical decisions, verify key facts before execution.

9. Language Guidance

Hana supports multilingual prompts, but if results are inconsistent, retry in simpler wording and define expected output format explicitly.