AfieldIn this article
Plan around a question the team needs to answer. In this example, buyers want to know whether they can bring existing company records into a trial. The week should produce a usable answer and the files behind it.
The week’s assignment
Demo plan: a fictional product supports a defined CSV import. The actual field rules must come from the product team. The dates below are ordering cues; a task starts when its required material is ready.
| Order / owner | Task | Required input | Deliverable and completion check |
|---|---|---|---|
| 1 · Sam, product | Confirm the import rules and run a small sample. | Test environment and supported field definitions. | Input file, observed result and one rejected-row example with its correction. |
| 2 · Priya, writer | Write the preparation tutorial. | Sam’s files and results. | Complete draft that explains who cleans the data and how to fix the sample error. |
| 3 · Sam, product | Repeat the tutorial. | Priya’s draft and sample files. | Recorded corrections; sample works using only the published instructions. |
| 4 · Avery, marketing | Update the product page’s migration section. | Reviewed tutorial and confirmed service scope. | Accurate summary and working link on the public page. |
| 5 · Morgan, sales | Use the answer in a relevant buyer conversation. | Published tutorial. | The question answered, any remaining objection and the exact page sent. |
While Sam tests, Morgan can collect the original buyer wording and Avery can locate the product passage to change. Priya can prepare the article structure, but a structure alone does not complete the tutorial.
Update a blocked task without restarting the plan
Suppose the valid sample works, but Tuesday’s result lacks the rejected-row response. Keep the successful sample and assign the missing piece:
Task: Import preparation tutorial
State: Draft can proceed; error-handling section blocked
Available: Supported fields, valid sample and successful import result
Missing: Actual rejected-row response and correction for the duplicate identifier case
Owner of missing input: Sam
Writer can do now: Explain preparation and supported happy path
Publication decision: Hold the promised error-fixing section until the observed result is supplied
Resume from: Existing draft; do not generate a replacement weekly planIf the exception remains unresolved, either narrow the article’s promise to a useful supported procedure or wait. Keep the unresolved case visible so the title does not promise a complete import guide.
Review the resulting work on Friday
- Can someone complete the sample import using the tutorial and supplied files?
- Does the product page explain the supported scope and cleanup responsibility?
- Does the public link open the reviewed version?
- What did the buyer still need to know: source-system export, cleanup effort or an unsupported format?
Use the remaining question to select the next task. In Afield, keep the working conversation and saved result associated with the task so a teammate can resume the research or draft. A completion checkbox is useful for planning; the files, page or message are what the next task needs.