Define the problem, output, responsibilities and acceptance criteria in a compact project brief that keeps a small team aligned.
Many small projects lose time because people start with different pictures of success. A one-page brief gives the team a shared reference before tasks are divided. It does not need complex terminology; it needs decisions that make the next action and the final result clear.
Describe the problem and the deliverable
Separate the issue from the proposed solution. In a hypothetical student project, the issue might be confusing induction information; the deliverable might be a tested two-page guide. State the audience and what is outside scope. A guide project should not quietly become a complete redesign of every student service.
Make completion observable
Define acceptance criteria such as required sections, source accuracy, readability and the person who will review the draft. Give each milestone an owner and a date. Identify dependencies, including information or permission needed before work can proceed. This makes a delay easier to diagnose than a general statement that the project is behind.
Control changes without blocking learning
Keep a brief decision log when the scope changes: what changed, why and what it does to the schedule. Review the final output against the original criteria, noting approved adjustments. A clear brief is a working agreement that can evolve transparently while protecting the team's limited time.
Worked example: accept a two-page induction guide
Imagine a team preparing a practice guide to submitting an assignment. Acceptance criteria could require ordered steps, accepted file formats, a way to recognise successful submission and a source for each instruction. Ask a peer to test it using a mock scenario without real student data. Record where a spoken explanation is still needed. Check those findings against the criteria before adding features; helping the reader complete the task matters more than extra pages or decoration.
Manage a blocked dependency explicitly
If one instruction depends on information from another person, assign an owner and follow-up date, then identify work that can continue independently. Do not fill the gap with a guess that later looks authoritative. Keep open questions visible and distinguish the working draft from the version ready for review. When someone proposes an additional task, discuss its effect on time, scope or responsibility so the team does not accumulate work that nobody agreed to own.
Further reading
Image: original editorial artwork prepared for the Asas library; it illustrates the topic and does not depict an actual event or student.
