At most one email a week. Unfollow anytime with one click.
Transcript
The full narration of this video. The current sentence is highlighted while the video plays; click any sentence to jump there.
Show transcript
Introduction
Hi, and welcome back to the Prompt Basics session. We can already build prompts, give examples, and revise. Now we focus on the shape of the result. In this episode we ask Claude to present answers as tables, lists, steps, and layered summaries, then move them neatly into a spreadsheet and WhatsApp.
Step 1: Why the shape of the result matters
Imagine Dewi asks for a comparison of three suppliers, and Claude answers with three long paragraphs. The content is correct, but Dewi has to read it again and again to compare. This is where the shape of the result matters. The first benefit: it's easy to read. With a table or bullet points, readers get the point in a few seconds. Second, it's easy to check. Neatly arranged numbers and facts are quicker to verify. Third, it's ready to use. Just copy the result into a report, email, or chat. Fourth, it's easy to move into other apps, such as a spreadsheet or presentation slides. Claude often uses tidy formatting on its own already. But when you state the shape clearly, the result fits your needs much better.
Step 2: Asking for the right table
Let's practice. Dewi pastes three A4 paper quotes, then asks for a table with five columns she names one by one: supplier, price per ream, minimum order, delivery time, and return guarantee. She also asks for the rows sorted from cheapest, plus a one-sentence recommendation. The result is a table the director can read in ten seconds. Look at the recommendation. Abadi Co. is the cheapest, but Claude suggests Sinar Paper Ltd. because delivery is fast and returns are accepted. Dewi still checks the numbers in the table against the original quotes. Imagine if Dewi had only written compare these three quotes. Claude might have picked its own columns, such as the supplier's office address, which doesn't matter for Dewi's decision. From that example, there are five things worth stating when you ask for a table. First, the column names, in order. Columns you choose yourself are usually more useful than the ones Claude picks. Second, the units, such as rupiah per ream or working days. Consistent units make the comparison fair. Third, the row order: cheapest first, newest first, or alphabetical. Fourth, the number of rows. For lots of data, ask for just the top five so the table doesn't get too long. Fifth, a conclusion below the table, such as a one-sentence recommendation or a total row. You don't have to state all of them every time. But the more important the table, the more complete your request, just like the prompt structure principle we've already learned.
Step 3: Lists, steps, and checklists
Besides tables, there are three shapes you'll use often. First, a bullet list, for a set of things in no particular order, such as product strengths or content ideas. Second, numbered steps, for a procedure that must be followed in order, such as the SOP for opening the shop. Third, a checklist, for checks you tick off one by one, such as checking orders before the courier leaves. State the shape explicitly in your prompt. The words numbered steps and checklist produce different shapes, even when the content is similar. The next example comes from Sunset Coffee. Laras has messy notes on how to open the shop. She asks for an SOP for Dimas with clear rules: numbered steps, short instructions, one action per step, seven steps max. Claude arranges six steps in order, from turning on the machine to putting up the Open sign. Each step is a single action, so a new employee can follow it easily. Laras wants a final check. She asks for a short checklist to go through before the sign goes up. Claude adds four checklist items. Now Laras has an SOP and a checklist she can print and pin near the cashier. Notice the difference: the SOP is numbered because the order of actions matters, while the checklist isn't numbered because it can be checked in any order. An SOP like this is also easy to update. If there's a new step tomorrow, such as checking the fridge temperature, just ask Claude to insert it in the right place.
Step 4: Layered summaries
The next shape is very useful for reports: the layered summary. Start with the task: summarize certain material for a certain reader. Both become variables. Then the three-layer format. Layer one is a single key sentence, twenty-five words max. Layer two is three main points. Layer three is the details in a table. Finally, the limits: a tone that suits the reader, and a rule against adding information that isn't in the material. This sentence stops Claude from making things up. Busy readers only need layer one. Those who want details can keep reading down to the table. Save this as Go-To Prompt number four. Mr. Hendra tries the template right away. He asks for a summary of this month's grade notes for the parents of Class 5A, with three layers and a warm tone. Claude builds it in the right panel. Layer one is a single key sentence, layer two is three points, and layer three is a table of topics with average scores. Also notice Claude's message on the left. It deliberately leaves out student names because the report covers the whole class. Even so, it's best to anonymize grade notes before pasting them. Parents who only have time to skim still get the message from the first sentence. Mr. Hendra just checks the averages against his grade book before sending it.
Step 5: Moving results into other apps
Now for moving results. Dewi copies the supplier comparison table with the copy button, then pastes it into a spreadsheet. The Abadi Co. row lands in the right columns. The Sinar Paper Ltd. row is neat too, complete with the minimum order and delivery time. The Jaya Store row is in place as well. Now Dewi can add a total cost column or make a chart from this data. If the paste doesn't split into columns, ask Claude to resend it in CSV format, which is text separated by commas that any spreadsheet app can open. For WhatsApp, the result is different. Laras asks for the menu as plain text for her customer group. Claude gives short lines, one piece of information per line, and asterisks around the title. In real WhatsApp, text between asterisks shows up in bold. The message looks neat when it's sent, and a customer orders right away. Compare that with pasting a table: the table lines would turn into a mess of symbols. The final key in this episode: always say where the result will be used. For a spreadsheet, ask for a table or CSV. For WhatsApp, ask for plain text with short lines and no tables, because WhatsApp can't display tables. For a document or report, ask for headings, subheadings, and bullet points. For presentation slides, ask for five points max per slide, with short sentences. For printing, ask for it to fit on one page, with no emoji. Just add one sentence like: I'll paste this into WhatsApp. Claude will adjust the format on its own.
Done!
We've learned to ask for tables with the right columns, choose between lists, steps, or checklists, build layered summaries, and move results neatly into a spreadsheet or WhatsApp. In the next episode, the final one in the Prompt Basics session, we look at the most common prompt mistakes and how to fix them, while polishing your five go-to prompts. See you there!
Practice exercises
Try these on your own after watching to lock in what you learned.
Ask Claude to compare two real quotes in a table with columns you choose
Turn one of your work procedures into numbered steps and a checklist
Save the layered summary template as Go-To Prompt number 4
Ask the class material
Type a question or keyword; we find the part of this episode that explains it and jump the video there.
My notes
Notes are saved with the current video time and are only visible to you.
Questions & answers
Stuck on a step? Ask here; the instructor and other learners can answer.
No questions yet.
Your instructor
Cerdas Inovasi Digital Team
Software developers, BIM & 3D engineers, and AI practitioners
53 video classes1,282 episodes
We build software, BIM models, games and AI automations for clients every day, and turn that hands-on work into step-by-step classes: every step is shown on screen and comes with a PDF guide you can keep.
