DGB 4: Creative Collaboration with Media and Software Tools

← Digital Literacy – Year 4

Digital collaboration is more than several people editing the same file. Productive teamwork requires a clear goal, suitable tools, roles, version control, feedback rules and shared responsibility. Students practise these principles through media and software projects.

Curriculum reference

Area	Classification
Competence area	Production
Perspectives	T, G, I
Focus	Goal-oriented and creative collaboration using digital media and software
Competence	Plan collaborative digital projects, choose suitable tools, manage roles and versions, and use feedback to improve a shared product.

Learning objectives

Students can:

explain collaboration as a planned process;
choose tools that fit a task rather than simply using familiar software;
co-edit documents and media responsibly;
use comments, suggestions and feedback constructively;
organise ideas with shared whiteboards or planning tools;
assign tasks and monitor progress;
manage versions and sharing permissions;
combine individual contributions into a coherent product;
coordinate audio, video or design work;
resolve conflicts and document decisions;
evaluate both the group process and the final product.

Learning content

Collaboration as a process

Start with purpose, audience, output, roles and deadlines. Tool choice should follow these requirements rather than determine the project.

Shared writing and editing

Collaborative documents allow simultaneous work, comments and revision history. Clear sections and responsibilities reduce accidental overwriting and duplicated effort.

Collaborative design

Design platforms can combine layouts, images and text. A shared style guide helps ensure that different contributions still form one coherent product.

Developing and visualising ideas

Digital whiteboards and concept maps support brainstorming, clustering and prioritisation. The goal is not to collect endless ideas but to decide what moves the project forward.

Task management

Kanban boards, checklists or simple tables can show who is responsible, what is in progress and what is blocked. Transparency supports fair workload distribution.

Versions, permissions and responsibility

Version history allows teams to trace changes. Sharing rights should follow the principle of least necessary access: viewers do not need editing rights, and public links should not be used by default.

Audio, video and multimedia collaboration

Complex media projects benefit from scripts, shot lists, naming conventions and clear handover points between recording, editing and publication.

Feedback as a design tool

Specific feedback explains what works, what is unclear and what concrete change would help. Teams should record decisions so that feedback leads to improvement rather than repeated debate.

Classroom activities

Shared poster project

Create a poster with assigned content, design and quality-control roles.

Expected outcome: A coherent shared poster.

Collaborative writing workshop

Write and revise one document using comments and change history.

Expected outcome: A final text plus revision trail.

Whiteboard for ideas and roles

Collect ideas, cluster them and convert selected ideas into assigned tasks.

Expected outcome: A planning board.

Team audio project

Create a short audio product with script, recording, editing and review roles.

Expected outcome: A finished audio clip.

Video with clear responsibilities

Plan scenes, record material and edit using agreed file names and handovers.

Expected outcome: A short team video.

Kanban media project

Use a simple board to track tasks and blocked work.

Expected outcome: A completed project board.

Justify design decisions

Record major choices about layout, media and audience.

Expected outcome: A design decision log.

Combine individual contributions

Merge separately produced sections into one consistent product.

Expected outcome: A unified final product.

Feedback rounds

Apply comment rules that are specific, respectful and actionable.

Expected outcome: A peer-review record.

Choose the tool deliberately

Compare two possible tools against collaboration needs, privacy and accessibility.

Expected outcome: A justified tool choice.

Creative task with constraints

Produce a creative solution under fixed format, time and accessibility requirements.

Expected outcome: A constraint-driven product.

Project reflection

Evaluate communication, workload, quality and one change for next time.

Expected outcome: A team improvement plan.

Self-check

I can plan collaboration before opening a tool.
I can choose tools based on task requirements.
I can manage roles, versions and permissions.
I give feedback that leads to concrete improvement.
I can combine separate contributions into one coherent product.
I can reflect on both process and result.