daBongo LMS AI Training Courses

Grok as Your Thinking Partner – Core Workflows

Lesson 2: Requesting Structured Output and Effective Iteration

Log in and enroll to track lesson completion.

Lesson Objectives

By the end of this lesson, students should be able to:

  • Specify output format such as tables, numbered steps, checklists, or comparison matrices
  • Run effective "improve this" iterations with clear targets
  • Ask for multiple options and a clear comparison of trade-offs
  • Know when to stop iterating and move to human review

Lesson Content

Unstructured paragraphs are hard to edit and hard to trust. Structured output forces Grok to organize its thinking and makes your job as the human reviewer much easier.

Useful structures include:

  • Numbered step-by-step plans
  • Tables for comparisons
  • Checklists with checkboxes
  • Risk / benefit matrices
  • "Assumptions / Recommendations / Open Questions" format

Iteration works best when you are specific about what to improve. Instead of "make it better," say "make the second section more concise and add one concrete example." Each iteration should have a clear target.

Power users often ask for two or three different approaches in one response, then request a short comparison of trade-offs. This gives them real options instead of hoping the first answer is perfect.

Practical Example

Weak prompt

Write a script for my video.

Improved prompt

Create two different 90-second video script outlines for a YouTube Short about the psychology of survival mode. Format: Numbered steps with estimated seconds for each section. For each outline, include: Hook (first 8 seconds), main teaching point, and a single practical takeaway. After both outlines, add a short comparison: which one would feel more energetic and which one would feel more compassionate.

Lesser-Known Tip

When you receive a long response, reply with: "Highlight the three most important sentences in this answer and explain why each matters for my goal." This quickly surfaces whether Grok actually understood your priorities.

Safety Notes

Even well-structured output can contain confident-sounding errors. Structure makes review easier, but it does not remove the need for human verification on factual claims or important decisions.

Practice Task

Take the outline or draft you created in Lesson 1 (or any current document). Ask Grok to convert it into a comparison table of two alternative approaches, then request a short "trade-offs" section at the bottom.

Completion Check

You should be able to request a specific structure and then run one targeted improvement iteration that clearly moves the output closer to usable.

Scroll to Top