← Back to all experiences
Full syllabus · B03 · Think & plan · Basic

Review edition · Complete text lesson. Platform screenshots are being prepared.

Lab / Work smarter

Suppose you could…

Turn a goal into practical next steps

Build a dependency-aware action plan without inventing commitments.

◷ 15 minutes✳ First-timerLearn by doing
BY THE END, YOU CAN…

Build a dependency-aware action plan without inventing commitments.

Time is a practice estimate. Pause or return whenever you need.
01 / IMAGINE

A useful little possibility.

Your goal is a usable work artifact, not a perfect-looking AI answer. Build a dependency-aware action plan without inventing commitments.

02 / TRY

Let’s make a start.

Use a fresh conversation in an AI tool you are permitted to use. Copy the fictional sample below, then paste the starter prompt with it. No file upload, web search or paid integration is required.

1. Circle the fixed review date and the unresolved approval.
2. Run the prompt.
3. Check that drafting, review and revisions happen in a plausible order.
4. Ask for the single next action that would unblock the most work.

Your sample material

Fictional training material. No real customer information needed.

Today is Monday. Goal: prepare a pilot welcome pack for review on Friday, not public release. Required: one-page guide, feedback form and review copy. Nia can draft for two hours Tuesday. Omar can review for 30 minutes Thursday. The brand template is not yet approved; approval owner is unknown. Printing is not required.
Download sample .txt ↓
YOUR STARTER PROMPT
Using only these facts, create a table of deliverable, next action, dependency, confirmed owner, timing and unresolved question. Label suggested assignments and estimates as proposals. Work backwards from the Friday review. Do not turn available time into a commitment without saying it is proposed.

Keep personal and confidential information out of external AI tools. Start with the sample material.

03 / CREATE

Turn a first try into your thing.

Compare the result with the checklist before opening the worked example. Identify one specific weakness and ask for a targeted revision, referring to the original sample. If all checks pass, tighten the wording without changing the facts. Save the reviewed result in your own document; do not send or publish it as part of this exercise.

04 / UNDERSTAND

Pause for the “aha.”

A plan is a set of dependencies and decisions, not a decorative list of dates. AI-generated scheduling can look authoritative even when it rests on invented availability.

CHECK YOUR RESULT

Useful beats convincing.

Check these against your actual output. Your answers stay on this device; this is self-review, not automated grading.

Finished your first try? Reveal a worked example ↓

First resolve who can approve the brand template and when. Proposed: Nia drafts the guide and feedback form Tuesday within her stated availability; her ownership still needs confirmation. Proposed: Omar reviews Thursday, then an unassigned person prepares the Friday review copy after feedback. Do not mark printing or public launch as tasks. If template approval is delayed, propose a plain-text review copy and explicitly ask whether that is acceptable. Friday is a review milestone, not a launch promise.

Download worked example ↓
NOW MAKE IT YOURS

A new case. Your own approach.

Apply the review principles to these new facts, not the previous sample’s specific numbers or answers.

Plan a survey draft for Wednesday using these facts: questions need legal review; reviewer and review timing unknown; Lee has one hour Monday; mailing is out of scope. Identify the dependency that prevents a guaranteed Wednesday sign-off.

05 / SHARE & REMIX

One possibility leads to another.

Repeat on a small, permitted task of your own. Record what you changed and which check caught a problem. Keep using fictional inputs if workplace material is not approved for your chosen tool.

Your reusable workflow card ↓
Task: Turn a goal into practical next steps
Audience: [who will use this]
Approved source material: [paste]
Required output: Build a dependency-aware action plan without inventing commitments.
Constraints and unknowns: [list]
Review before use:
- Friday is a review milestone, not a public launch.
- Approval dependency is visible.
- Available people are not treated as confirmed assignees.
- Review precedes final revisions.
- There is a specific unblocking next action.
Download workflow .txt ↓

You tried something. That counts.

Keep a note of what you made or what surprised you. It stays in this browser.