Practice Task

Practice: Write execution plans for three client requests

For three rough client requests, write concrete execution plans, deliverables, risks, and questions.

Practice typeRealistic client scenario · no cash reward
SubmissionsOpen practice; every contributor can submit their own version
Review outcomePass: +35 Trust Points. Revision or not passed: no points until fixed.
Current statusOpen
Practice boundaryRead the exercise here; submit and revise in the task room

The brief is not the submission area

This page gives the customer scenario, source material, deliverables, review criteria, and suggested format. Formal practice submissions, files, revision notes, and review outcomes belong in the task room so each attempt is auditable.

Exercise brief

Use this page to understand the scenario, assumptions, source material, deliverables, and pass/fail criteria before working.

Task room

Submit the completed result, upload supporting files, send clarification messages, and resubmit a new version if revision is requested.

Reusable practice

There is no participant quota. Multiple contributors can submit, and each version is reviewed against the same criteria.

Review record

Outcomes are pass, revision needed, or not passed. Only a passing version earns Trust Points or case-review eligibility.

Client Scenario

What problem are you solving?

A client sends three small needs at once. You are not posting tasks for the platform; you are showing whether you can turn rough requests into executable work plans.

System Context

Use these assumptions

No client software is fixed. Request A may be a research document, B may be a spreadsheet workflow or script, and C may be a form-notification diagnosis. Do not pretend you already have access to client systems.

Source Material

Base your work only on this material

A: Can someone find out which AI customer-service tools our peers use?
B: We spend too much time finding abnormal orders in a spreadsheet every week.
C: Our old web form often fails to send notifications.
Deliverables

What to submit

  • One execution plan each for A, B, and C
  • Steps for each plan
  • Expected delivery format
  • Risks and boundaries
  • At least three confirmation questions for each request
Review Criteria

What makes a result pass review

  • All three requests need concrete steps
  • Do not merely rewrite the titles
  • Do not make finding real demand the deliverable
  • Mark assumptions clearly
  • Make the next client input obvious
Submission Format

Recommended format

  • Separate A, B, and C
  • Use headings: steps, deliverable, risks, confirmation questions