Latest dealsDeals See all deals→
Lesson 4 of 4 · 11 min

Shape the Output

What you will be able to do

By the end of this lesson, you will be able to ask an AI assistant for a result in a form you can use right away, instead of getting a generic block of text. You will know how to control format, structure, length, and level of detail without making the prompt complicated.

The idea explained plainly

A good prompt does not only say what you want help with. It also says what the answer should look like.

This matters because the same source material can be turned into very different outputs. If you give an assistant project notes and say, “summarize this,” you may get a paragraph. But maybe what you actually need is a three-bullet update for your manager, or a short email to a stakeholder, or a table you can paste into a planning document.

When the form is wrong, even a factually decent answer can still be unhelpful. You then have to spend time reshaping it yourself.

A simple way to shape the output is to add a few instructions such as:

  • Format: bullets, paragraph, email, table, checklist
  • Structure: lead with risk, group by topic, include owners and deadlines
  • Length: one paragraph, five bullets, under 120 words
  • Audience: manager, client, teammate, executive
  • Level of detail: high-level summary, practical next steps, polished wording

You do not need to specify all of these every time. Add the ones that change whether the answer will be useful.

This lesson builds on the earlier ones. You are still asking for one clear output at a time. You are still using only the context that matters. The new step is to tell the assistant what shape the answer should take.

Worked example

We will use the same source material from the earlier lesson so you can see how the output changes even when the facts stay the same.

Source material:

  • Homepage and pricing page designs were approved.
  • Mobile load time improved.
  • The product page remained in Legal review over claims language.
  • Engineering could finish by May 10 if Legal approved by May 7.
  • The launch might move from May 15 to May 22.
  • Maya prefers brief updates that lead with risk.
  • Ignore the possible future blog layout change.

Now imagine three different work situations. The facts are the same, but the output you need is different each time.

Situation 1: Maya wants a quick status update in a message.
Situation 2: A stakeholder needs a polished email.
Situation 3: The team needs a planning view of next steps.

If you asked only this:

Summarize these project notes.

you would probably get a general summary. That is not wrong, but it is not shaped for any of the three situations.

Let’s improve it by asking for one specific output at a time.

Output 1: bullet summary for a manager

Turn these project notes into a brief status update for my manager, Maya. Use 3 bullet points. Lead with the main risk. Keep it concise and practical. Include only facts from the notes. Do not mention the future blog layout idea.

Notes:
Homepage and pricing page designs were approved. Mobile load time improved. The product page remained in Legal review over claims language. Engineering could finish by May 10 if Legal approved by May 7. The launch might move from May 15 to May 22.

A useful answer might look like this:

  • Main risk: the product page is still in Legal review over claims language, which may push launch from May 15 to May 22.
  • Progress: homepage and pricing page designs are approved, and mobile load time has improved.
  • Timing: Engineering can finish by May 10 if Legal approval comes by May 7.

Notice what made this better. The prompt named the audience, format, length, and structure. “Lead with the main risk” matters because Maya prefers that style. “3 bullet points” prevents a long answer. “Include only facts from the notes” helps keep the summary grounded.

Output 2: polished email for a stakeholder

Write a short, polished email to a project stakeholder using these notes. The purpose is to share a clear status update and flag the possible launch shift. Use a professional, calm tone. Keep it to 120 words or less. Do not invent details.

Notes:
Homepage and pricing page designs were approved. Mobile load time improved. The product page remained in Legal review over claims language. Engineering could finish by May 10 if Legal approved by May 7. The launch might move from May 15 to May 22.

A useful answer might look like this:

Subject: Website redesign status update

Hi,

Quick update on the website redesign: the homepage and pricing page designs are approved, and mobile load time has improved. The main open item is the product page, which is still in Legal review due to claims language. If Legal approves by May 7, Engineering can still finish by May 10. If that review takes longer, we may need to move launch from May 15 to May 22.

Best,
[Your Name]

This is based on the same facts, but the form is completely different. The assistant was told to write an email, keep it short, use a calm tone, and highlight the possible launch shift. That is enough to produce something close to usable.

Output 3: table of next steps with owners and deadlines

Create a simple table of next steps from these notes. Use 3 columns: Next step, Owner, Deadline. Include only steps that are supported by the notes. If an owner is not stated, write “Not specified.” If a deadline is conditional, say so clearly.

Notes:
Homepage and pricing page designs were approved. Mobile load time improved. The product page remained in Legal review over claims language. Engineering could finish by May 10 if Legal approved by May 7. The launch might move from May 15 to May 22.

A useful answer might look like this:

Next stepOwnerDeadlineComplete Legal review of product page claims languageLegalBy May 7 to keep current Engineering timingFinish Engineering work on the product pageEngineeringMay 10, if Legal approves by May 7Confirm final launch dateNot specifiedDepends on Legal review outcome; may move from May 15 to May 22

The point here is not that the assistant magically knows everything. In fact, the prompt protects against that by saying what to do when an owner is missing. That is part of shaping the output too. You can tell the assistant how to handle gaps instead of letting it guess.

Here is the main lesson from these three versions: the source material stayed the same, but the output changed because the request changed. Once you know the form you need, you can ask for it directly.

A simple pattern you can reuse is:

Create a [format] for [audience] about [topic]. Keep it [length]. Structure it by [how to organize it]. Include [must-have details]. Exclude [what to leave out]. Use only the information below.

For example:

  • Create a 3-bullet summary for my manager about this project update. Keep it brief. Structure it by leading with risk. Include timing and approved work. Exclude side topics. Use only the information below.

You do not need fancy wording. Clear instructions about shape are enough.

Common mistakes

  • Asking for content but not form. “Summarize this” is often too open. Say whether you want bullets, a paragraph, an email, a checklist, or a table.
  • Forgetting the audience. A manager, client, and teammate may need the same facts presented differently.
  • Leaving length unspecified. If you need something short, say so. Otherwise you may get more detail than you can use.
  • Combining multiple outputs in one prompt. Avoid asking for a summary, an email, and a table all at once. Ask for one output at a time.
  • Letting the assistant guess missing facts. If names, owners, or deadlines are not in the source material, tell it how to handle that. For example, say “write ‘not specified’ if missing.”
  • Over-specifying small things that do not matter. You do not need to control every sentence. Focus on the parts that make the result usable.

Exercise

Do this now with a short workplace task.

Task: You need help turning notes into something you can send to your team.

Notes:

  • The training session is moved from Thursday to Friday.
  • It will still run from 2 to 3 p.m.
  • Sam will send the updated calendar invite.
  • The goal is to avoid a conflict with the finance review meeting.

Your job: Choose one of these outputs and write a prompt for it:

  1. A short team message
  2. A polished email
  3. A simple table with action items

Your prompt should specify:

  • the format
  • the audience
  • the length
  • anything important about structure or detail

If you want a starting frame, use this:

Create a [format] for [audience] about [topic]. Keep it [length]. Include [key facts]. Use a [tone] tone. [Any structure instructions].

Example of a strong answer:

Write a short team message about a training schedule change. Keep it to 4 sentences or less. Include the new day and time, the reason for the change, and that Sam will send the updated calendar invite. Use a clear, helpful tone.

How to check your result

Use this quick checklist:

  • Did I ask for one clear output?
  • Did I name the format?
  • Did I name the audience?
  • Did I set a useful length or level of detail?
  • Did I include the facts that must appear?
  • Did I avoid asking the assistant to guess anything important?

If your prompt passes most of this checklist, it is probably strong enough to get a useful first draft.


So far, the course has built a simple pattern: choose a task AI is good at, ask for one thing well, provide the context that matters, and now shape the result into a form you can actually use. In the next lesson, we will build on this by improving a draft through follow-up instead of trying to get everything perfect in one go.

More courses

All courses →
SEO

Small Site Search Wins

This course shows a small site owner how to improve search visibility without turning the site into a content factory.

5 lessons 1h 3m Self-paced
Lead instructor · Trisha Kapoor View course
Lessons
  1. What Search Can Do
  2. Finding Terms Real People Use
  3. Matching One Page to One Need
  4. Rewriting Pages That Stall
  5. Internal Links That Pull Weight
Remote Work

Home Office, Human Hours

Build a work-from-home setup that supports concentration without taking over the rest of your life.

4 lessons 47 min Self-paced
Lead instructor · Lucas Lewis View course
Lessons
  1. Choose Your Working Ground
  2. Build a Day That Starts Cleanly
  3. Protect Deep Work at Home
  4. Write So People Know What You Mean