Who is this article for?

Mazlan users working with agents and assistants.

Mazlan is required.

When you work with Mazlan, the quality of your results depends on the quality of your prompt. A good prompt is like giving clear instructions and the more specific and detailed you are, the better Mazlan understands what you need.

Mazlan responds to what you ask. If you ask vaguely, you'll get a general answer. If you ask specifically, you'll get a tailored answer. Think of it as a conversation: the more context you provide, the better Mazlan can help you.

The five elements of a good prompt

1. Be Clear About What You Want

Start by stating exactly what you need. Don't assume Mazlan will guess.

Weak: "Can you help with this risk?"

Strong: "I need to create a risk register entry for a data breach vulnerability in our customer database."

2. Provide Context and Background

Give Mazlan information about your situation. This helps it tailor the response to your specific needs.

Weak: "What should I do about compliance?"

Strong: "Our organization is in the financial services sector. We're currently preparing for a GDPR audit and need to identify compliance gaps in our data handling processes."

3. Be Specific About Your Requirements

Tell Mazlan what format, structure, or outcome you need.

Weak: "Create an incident report."

Strong: "Create an incident report for a warehouse chemical spill that includes: what happened, who was affected, immediate containment actions taken, and next steps for investigation."

4. Include Relevant Details

Share any information that affects the answer—your industry, regulations, team size, existing systems, or constraints.

Example: "I'm creating a training document for our 4-person remote content team. Two team members are neurodiverse (one with processing delays, one with autism). The document should use short paragraphs, clear headings, and avoid jargon."

5. Explain the Purpose (When It Helps)

If knowing why you need something helps Mazlan respond better, share that too.

Example: "I need this risk assessment for our board presentation next week, so it needs to be executive-level—high-level summary with key metrics, not detailed analysis."

The prompt formula

Here's a simple structure you can follow:

1. What you need: Specific output or task
2. Context: Relevant background information
3. Requirements: Format, structure, or specifics
4. Any constraints: Deadlines, audience, tone, technical limits

Example: from weak to strong

Weak Prompt: "Can you create a risk management policy?"

Strong Prompt: "Create a risk management policy for a small software development team (6 people, remote). The policy should cover: how we identify risks in development, how we log them, who decides if they're critical, and escalation procedures. We use Jira for tracking. Keep it clear and not too long—this needs to be practical for the team to actually use, not a compliance document that sits on a shelf."

What to do if results aren't what you expected

If Mazlan's first response doesn't quite fit your needs, don't give up. Try these adjustments:

Add more detail: "I mentioned software development—I specifically mean security risks in code. Add a section on how we handle discovered vulnerabilities."

Rephrase: Sometimes a different angle works better. Instead of "What's the best way?" try "Here's our current process. How should we improve it?"

Give an example: "Here's what a good risk entry looks like for us: [example]. Can you create three more like this?"

Clarify the outcome: "I need this in plain language that a non-technical team member can understand. Can you rewrite it without technical jargon?"

Remember: Always Review the output from Mazlan.

Before you accept or use Mazlan's output, always review it. Check for:

• Accuracy: Does it match what you asked for?
• Completeness: Are all the parts you needed included?
• Relevance: Does it fit your specific situation?
• Tone and clarity: Does it sound right for your audience?

Your review is a critical part of the process. Mazlan supports your work. It doesn't replace your judgment.

Quick tips

• Be specific, not vague: "Create a risk register for manufacturing defects in our injection molding process" beats "Create a risk register."
• Provide examples when possible: If you show Mazlan an example of what you want, it can match that style or structure.
• Explain your constraints: Deadlines, audience level, format restrictions—all help Mazlan respond better.
• Iterate: Your second or third prompt often produces better results than your first. That's normal.
• Use your expertise: You know your organization, your team, and your needs. Mazlan provides tools and suggestions, but you make the final call.

Remember, a good prompt shows Mazlan that you've thought through what you need. It doesn't need to be perfect—just thoughtful and specific. The more effort you put into asking clearly, the more useful the answer will be.