Curriculum
Course: Collaboration and Team Role Development
Login
Text lesson

Contribution is behaviour in a task, not a permanent box

Ask what the work needs before assigning a role

People contribute differently across tasks and conditions. Someone may generate ideas in a familiar topic and become a careful checker in another. A contribution-frequency profile can prompt reflection on these patterns; it does not establish a fixed identity, technical competence or the ideal staffing formula for a team. Begin with the project’s output and the work required, then examine evidence of contribution and support needs.

Fictional case: a Polokwane student/community team is planning a career-information event. The fastest speaker volunteers to lead everything. A quieter member notices that the venue information is out of date. If the group treats speaking frequency as leadership ability, it may overlook a contribution essential to the event. Instead ask who can verify information, coordinate the venue, prepare materials and review access, and what time each person actually has.

Describe a contribution with evidence

Write a short account of one time you helped a group: the task, what you did and the effect you observed. Separate the observation from your interpretation. “I checked three provider links and found one expired page” is evidence; “I am the team’s only quality person” is an overclaim. Add a situation where the same tendency could be unhelpful, such as continuing to polish materials after the deadline for a usable version.

Map three work needs in the fictional event. For each, identify an observable contribution, a current evidence source and support required. Use “unknown” where nobody has tried the task. A person can develop a contribution through practice; do not use an assessment label to deny them the chance or excuse an essential task indefinitely.

Self-review your map for task relevance, workload and changeability. It should help the group decide what needs doing and how to support it, not rank personalities. Save your contribution evidence note and a question to discuss with the team. If working alone, write a fictional conversation showing how another member could correct your view.