Episode 16: Solve Someone Else’s Problem

Episode 16 Learning Lab

Solve Someone Else’s Problem

Your AI skills become more useful when they help someone else with a real problem. Use this interactive Lab to identify a text-heavy bottleneck for a colleague, scope a focused 20-minute collaboration, and capture a practical external reference for your evidence ledger.

Before you choose your pathway

Understand why external validation matters before you help a peer.

Self-recorded time savings can only take you so far. External validation helps show that your AI-supported workflow improved a real task for someone else.

What this lesson is about

This Lab focuses on moving capability out of isolated chat windows and into the wider team. You will learn how to find useful text-heavy bottlenecks around you, keep the collaboration contained, and capture proof that the work helped.

The goal is to move from private tool use to visible capability, where your AI practice helps other people reduce friction in real work.

By the end of this Lab you will be able to

  • Identify text-heavy roadblocks that are suitable for AI-supported drafting, summarising or structuring.
  • Guide a peer through a short workspace consult while keeping ownership of the work with them.
  • Set clear human checking boundaries so the final work remains accurate, locally relevant and owned by the right person.
Key concepts from this episode

The four principles of safe workflow scaling.

The self-assessment ceiling

Your own notes are useful, but a peer reference is stronger when you need to show that your workflow helped someone else.

The keyboard stewardship rule

Your colleague should stay at the keyboard while you guide the structure, so the session builds capability rather than dependency.

Discrete bottleneck isolation

A useful consult does not try to redesign everything. It targets one clear text bottleneck that can be improved within a short session.

The verification boundary

The person responsible for the final deliverable must manually check the output before it is used.

Choose your working depth

Choose the amount of evidence that fits your week.

These pathways guide your focus. You can log one useful task, capture a short written reference, or build a stronger case study from a more complex workflow.

Listen

Start with the episode.

Listen for the difference between doing someone else’s work for them and guiding a short, structured consult that creates useful proof of capability.

Watch

Watch the scoping consult sequence.

Use the video to see how a small, contained consult can isolate an admin bottleneck, set boundaries and keep the work owned by the right person.

Read

Set the boundaries before you help.

Review the four-part sequence before you help someone else: isolate one text-heavy roadblock, keep the session contained, work on their screen, and build in clear checks.

Isolate text-heavy tasks. Look for document synthesis, weekly progress tracking, meeting notes, consultation summaries or other text-heavy tasks that drain time and attention.
Keep the work on their screen. Keep your colleague’s hands on the keyboard during the session. Avoid moving their work into your own private tool account or profile.
Verify the original source. When source material is involved, ask the model for clear references, then manually check them against the original material before anything is used.
Important constraint: compare normal periods. Make sure your before-and-after comparison is fair. Avoid using weeks distorted by public holidays, leave gaps or unusual workload spikes unless you clearly explain them.
Apply

Log your peer consult details.

Capture the practical details from your peer consult. These responses feed directly into your final reference asset.

Required

Identify the role of the person responsible for the task or deliverable.

Required

Describe the specific text-heavy drafting, summarising or analysis roadblock causing friction.

Required

State the hours or minutes this usually takes without AI support.

Required

Describe the prompt pattern, structure or workflow you helped build on their screen.

Standard / Ambitious

List the checks that must happen before the output is used.

Standard / Ambitious

Record the time saved, quality improvement or other clear change, including checking time.

Ambitious

Note any changes needed to make the material fit local New Zealand or Australian context, terminology or rules.

Copyable peer consult prompt

Act as a practical workflow coach specialising in AI-supported text work. Review the task notes below, which describe a text-heavy roadblock currently experienced by a colleague.Use this information to create a short performance reference block that meets these criteria: 1. Compare the manual baseline with the AI-supported workflow, including any checking time. 2. Cover three areas: the original task bottleneck, the prompt or workflow intervention, and the human checking steps used. 3. Write the final output as three concise sentences suitable for an internal portfolio, using New Zealand and Australian English spelling.

Reflect

Manage expectations and safety.

Consider the boundaries of the consult. The aim is to show responsible AI-supported help, not careless acceleration.

Standard / Ambitious

Confirm how you ensured your colleague retained ownership of the deliverable during the consult.

Required

How will your contact validate this record so it can be used as external evidence?

Create

Create your peer workflow reference asset.

Complete the required fields, then use the live preview as your first takeaway document.

Required

Summarise what this peer consult proves about your practical AI-supported value.

Standard / Ambitious

Paste the statement confirmed by your colleague, including the time or quality improvement.

Peer Workflow Reference and Testimonial

Generated from your Episode 16 Learning Lab responses.

Saved
' + ''; }fields.forEach(function (field) { field.addEventListener('input', function () { saveField(field); renderAsset(); updateProgress(); showToast('Saved'); });field.addEventListener('change', function () { saveField(field); renderAsset(); updateProgress(); }); });pathwayInputs.forEach(function (input) { input.addEventListener('change', function () { setPathway(input.value, true); }); });pathwayButtons.forEach(function (button) { button.addEventListener('click', function () { setPathway(button.getAttribute('data-pathway-choice'), true); }); });const copyPromptButton = lab.querySelector('#z2ai-copy-prompt'); const promptText = lab.querySelector('#z2ai-prompt-text');if (copyPromptButton && promptText) { copyPromptButton.addEventListener('click', function () { copyText(promptText.textContent.trim(), 'Prompt copied', 'Copy failed', showToast); }); }const copyAssetButton = lab.querySelector('#z2ai-copy-asset');if (copyAssetButton) { copyAssetButton.addEventListener('click', function () { copyText(getAssetText(), 'Asset copied', 'Copy failed', showToast); }); }const printAssetButton = lab.querySelector('#z2ai-print-asset');if (printAssetButton) { printAssetButton.addEventListener('click', function (event) { event.preventDefault();renderAsset();const printWindow = window.open('', '_blank', 'width=900,height=1100');if (!printWindow) { showToast('Print window blocked'); return; }printWindow.document.open(); printWindow.document.write(buildPrintHtml()); printWindow.document.close(); printWindow.focus();window.setTimeout(function () { printWindow.print(); }, 350); }); }const clearLabButton = lab.querySelector('#z2ai-clear-lab');if (clearLabButton) { clearLabButton.addEventListener('click', function () { const confirmed = window.confirm('Clear the saved responses for this Learning Lab in this browser?'); if (!confirmed) return;window.localStorage.removeItem(storageKey);fields.forEach(function (field) { field.value = ''; });setPathway('minimum', false); renderAsset(); updateProgress(); showToast('Responses cleared'); }); }restoreState(); }labs.forEach(initLab); })();