AI Productivity Mastery

Have you ever pasted the same task into ChatGPT twice and gotten two totally different answers? If you have, the problem usually isn’t “AI quality.” It’s your prompt. When your prompt doesn’t say who the assistant should be, what situation it should assume, and what limits it must follow, you get answers that miss your real needs.

Think about a simple work task: writing an email to a customer, turning notes into a meeting summary, or planning study practice for a certification. You don’t just want “an answer.” You want the right format, the right tone, and the right level of detail - without extra back-and-forth. This chapter teaches you the prompt basics that create that consistency.

After this chapter, you’ll be able to write prompts that produce clear outputs on the first try more often. You’ll use the ROLE-Context-Constraints Prompt Formula, with copy-and-paste examples you can reuse for daily productivity tasks. You’ll also learn what to watch for when outputs look good but still aren’t usable.

ROLE-Context-Constraints Prompt Formula for Clear Outputs

When you ask ChatGPT for help, you’re really telling it three things: (1) what role to take, (2) what context to use, and (3) what constraints to follow. Most “bad prompt” problems come from missing one of those pieces. For example, you ask for “a summary,” but you don’t say the audience, the length, or what to keep. Or you ask for “a plan,” but you don’t limit the time, format, or assumptions.

Here’s a beginner-friendly way to remember it: you’re building a mini instruction sheet. Your prompt becomes a job description. The assistant can’t reliably guess the missing parts, so you give them directly.

Use this formula like a template. You don’t need fancy wording - just clear sections you can fill in. For this chapter, we’ll use a realistic example: Talia, 24, a junior analyst, who often turns messy notes into clean deliverables for her team.

The ROLE-Context-Constraints Prompt Formula breaks into three parts:

1. Role: Tell ChatGPT who to be

• Write a short role line like: “Act as a senior analyst who formats deliverables for a busy manager.”
• Why it helps: The assistant chooses an appropriate voice, structure, and level of detail.

2. Context: Tell ChatGPT what situation to assume

• Include the task goal, source material (paste notes), audience, and any background facts you already know.
• Why it helps: The assistant stops making up assumptions that don’t match your work.

3. Constraints: Tell ChatGPT what rules to follow

• Add explicit limits: length, format (bullets, table, sections), tone, and what to avoid.
• Why it helps: The assistant produces output you can use immediately, not something you need to rewrite from scratch.

A quick comprehension check: after you write a prompt, ask yourself, “If I had to show this to a coworker, could they answer the same question without asking me anything?” If yes, your prompt likely has enough context and constraints.

Putting Roles, Context, and Constraints into Practice (with Examples)

Let’s build a prompt the way Talia would for a daily productivity task. Her job often involves turning notes into something her manager can scan quickly. She wants a summary that fits a specific format: short, structured, and action-focused.

First, she decides on the role. She doesn’t want “a generic helper.” She wants a deliverable-style summary.

Second, she adds context. She includes the notes she already has, the audience (her manager), and what the manager will use it for (a decision meeting).

Third, she adds constraints. She limits length, requires a specific section order, and asks for decisions and risks to be clearly separated.

Here are two concrete prompt examples you can copy. Notice how each one includes all three parts.

Example A: Turn notes into a manager-ready update

• Role: Act as a junior analyst who writes manager-ready updates.
• Context: I’m sending this to my manager before a 15-minute decision meeting. Notes: [paste notes here]. The goal: highlight what changed, what we recommend, and what we still need.
• Constraints: Output must be 180-220 words. Use exactly these sections in this order: “What changed”, “Recommendation”, “Open questions”, “Risks”. Use short sentences. Do not add new facts not found in my notes.

Expected outcome: A tight summary with the exact section headers Talia’s manager expects, without random extra commentary.

Example B: Draft a customer email with a specific tone

• Role: Act as a customer support specialist who writes clear, calm emails.
• Context: Customer message: [paste message]. Our goal: acknowledge the issue, explain next steps, and set a realistic timeline. Audience: the customer, not internal staff.
• Constraints: Write 120-160 words. Tone: friendly and direct. Include one question at the end to confirm the next step. Do not blame the customer....