Week 6 Remote Collaboration
REMOTE WORK SKILLS TRAINING
MONTH 2 — WORKING PROFESSIONALLY
WEEK 6 — REMOTE COLLABORATION
DAY 26: WORKING WITH TEAMS REMOTELY
Objectives
By the end of this lesson, students should be able to:
Explain what remote collaboration means.
Understand the difference between individual remote work and remote teamwork.
Identify common roles within a remote team.
Communicate effectively with team members.
Understand task ownership and responsibility.
Work with shared tasks and deadlines.
Participate effectively in remote team meetings.
Handle disagreements and team problems professionally.
Software/Tools
Slack, Microsoft Teams, Google Workspace, Microsoft 365, Trello, Asana, Zoom, Google Meet, Google Drive, OneDrive
These tools help remote teams communicate, share files, assign tasks, hold meetings, and track project progress.
1. What Is Remote Collaboration?
Remote collaboration means people working together on the same project or business activities even when they are not physically in the same location.
For example:
A company may have:
A manager in the United States.
A developer in Nigeria.
A designer in Kenya.
A marketing specialist in Ghana.
A data analyst in India.
They can still work as one team using digital tools.
Simple definition:
Remote collaboration = working together through digital tools without needing to be physically together.
2. Individual Remote Work vs Remote Teamwork
Individual remote work
You receive a task and complete most of it yourself.
Example:
A client gives a data-entry worker 500 records to enter.
Remote teamwork
Several people contribute to one project.
Example:
A website project may involve:
Project manager
UI/UX designer
Frontend developer
Backend developer
Content writer
Tester
Everyone has different responsibilities, but they are working toward the same result.
3. Why Remote Collaboration Is Important
Many remote jobs require teamwork.
Even if you work from home, you may still have to:
Attend meetings.
Share files.
Ask colleagues questions.
Give progress updates.
Receive tasks.
Review another person's work.
Meet team deadlines.
Participate in discussions.
Solve problems together.
Being physically alone does not mean working alone.
4. The Remote Team Workflow
A typical remote project can follow this process:
Project → Planning → Task Assignment → Individual Work → Collaboration → Review → Revision → Approval → Delivery
For example:
Website Project
Manager
↓
Creates project requirements
↓
Designer
Creates website design
↓
Frontend Developer
Builds interface
↓
Backend Developer
Builds server/database functionality
↓
Tester
Tests the website
↓
Manager
Reviews and approves
↓
Client
Receives final website
Each person depends on other team members.
5. Common Remote Team Roles
A remote team can have different roles depending on the business.
Project Manager
Coordinates the project, tasks, deadlines and team members.
Team Lead
Provides direction and helps solve technical or operational problems.
Virtual Assistant
Handles administrative and support tasks.
Developer
Builds or maintains software.
Designer
Creates visual materials.
Data Analyst
Analyzes information and produces insights.
Marketing Specialist
Handles marketing activities.
Customer Support Agent
Communicates with customers and resolves issues.
Content Writer
Creates written content.
Quality Assurance Tester
Checks products or software for problems.
6. Understand Your Role
One of the biggest remote teamwork problems is unclear responsibility.
Before starting a task, know:
What am I responsible for?
Who assigned the task?
What is the deadline?
Who depends on my work?
Who reviews my work?
Who should I contact if I have a problem?
Example
A designer finishes a website design.
The frontend developer cannot start properly until the design files are available.
Therefore:
Designer → Developer
The developer depends on the designer.
This is called a dependency.
7. Task Ownership
Task ownership means being responsible for completing a particular task.
If your task is:
“Prepare the monthly sales report.”
You are the owner of that task.
You should:
Understand it.
Track it.
Complete it.
Report progress.
Communicate problems.
Submit it.
Do not assume that someone else will complete your task simply because you're working in a team.
8. Team Responsibility vs Individual Responsibility
A team may be responsible for the entire project.
But each person should still know their individual responsibility.
Example
Project:
Build an e-commerce website.
Team responsibility:
Deliver the complete e-commerce website.
Individual responsibilities:
Designer: Website interface
Frontend Developer: User interface implementation
Backend Developer: Server and database
Content Writer: Product descriptions
Tester: Testing
Everyone contributes to the final result.
9. Communication Channels
Not every message should be sent through the same channel.
Slack/Teams
Good for:
Team discussions
Quick questions
Project updates
Channels
File sharing
Good for:
Formal communication
External clients
Important approvals
Documentation
Zoom/Google Meet
Good for:
Meetings
Discussions
Demonstrations
Problem-solving
Trello/Asana
Good for:
Task assignment
Deadlines
Progress tracking
Project status
10. Choose the Right Communication Channel
Suppose you need to tell your manager:
“I have completed the report.”
A project-management tool or team chat may be appropriate.
But if you need formal approval for a major business decision, email may be more appropriate.
Simple rule:
Use the right tool for the right type of communication.
11. Don't Communicate Everything Everywhere
A common remote-team problem is sending the same message through:
WhatsApp
Slack
Email
Teams
at the same time.
This can create confusion.
For example:
Manager receives the same task update in three different places.
Which one should the team use as the official record?
Agree on the team's communication system.
12. Team Channels
Slack and Teams allow teams to organize communication into channels.
Example:
#general
General company communication.
#marketing
Marketing discussions.
#development
Technical development.
#customer-support
Customer-related issues.
#project-website
Website project communication.
This prevents every conversation from being mixed together.
13. Mentioning Team Members
Tools such as Slack and Teams allow you to mention people.
Example:
@David Could you please confirm whether the API credentials are ready?
This is better than sending a message to the entire team when only David needs to respond.
Use mentions carefully.
Don't unnecessarily mention everyone.
14. Task Handover
Remote workers often need to pass work from one person to another.
A good handover should explain:
What was completed.
What remains.
Where the files are.
What problems exist.
What the next person needs to do.
The deadline.
Example:
Website Handover
Completed: Homepage and contact page.
Files: Google Drive → Website Project → Design.
Remaining: Services page and mobile adjustments.
Issue: Client has not approved the new logo.
Next Step: Continue with the services page while waiting for logo approval.
Deadline: Friday.
This makes it easier for another person to continue the work.
15. Working Across Time Zones
Remote teams may be in different countries.
You might work from Nigeria while your manager works from the United States.
Therefore, don't assume that everyone is working at the same time.
Before scheduling meetings or expecting immediate responses:
Check the person's time zone.
Use calendar tools.
State the time zone.
Respect working hours.
Understand that someone may be offline.
Example:
“The meeting is scheduled for 2 PM WAT / 8 AM EST.”
This reduces confusion.
16. Synchronous vs Asynchronous Collaboration
Synchronous
People communicate at the same time.
Examples:
Zoom meeting
Google Meet
Teams call
Live discussion
Example:
You and your manager join a meeting at 10 AM.
Asynchronous
People communicate at different times.
Examples:
Email
Slack message
Trello comment
Shared Google Doc
The person can respond when they become available.
Example:
You send a project update at 10 PM WAT.
Your manager reads it at 8 AM their local time.
17. Why Asynchronous Work Matters
Remote teams may not work the same hours.
A good remote worker should not expect:
“I sent the message, so you must respond immediately.”
Instead, provide enough information for the other person to understand the issue and respond when available.
Poor:
“Are you there?”
Better:
“Hi David, I'm working on the website deployment. The server is returning an authentication error. Could you please check the deployment credentials when you're available?”
The second message gives context.
18. Don't Send One Word at a Time
Avoid:
Hi
John
Are you there?
I need something.
Please check.
This is inefficient.
Instead:
Hi John, I'm currently working on the website deployment and need confirmation of the hosting credentials. Could you please check them when you're available? Thanks.
One complete message is easier to understand.
19. Team Meetings
Before joining a remote meeting:
Prepare
Check the agenda.
Review relevant documents.
Test your internet.
Test microphone.
Have necessary files ready.
During the meeting
Listen.
Avoid unnecessary interruptions.
Take notes.
Ask relevant questions.
Record assigned tasks.
After the meeting
Confirm:
What was decided?
Who is responsible?
What is the deadline?
What happens next?
20. Meeting Action Items
A meeting should ideally produce clear action items.
Example:
| Action | Owner | Deadline |
|---|---|---|
| Update website content | David | Tuesday |
| Prepare graphics | Sarah | Wednesday |
| Test website | Michael | Thursday |
| Submit final version | Team Lead | Friday |
This prevents:
“I thought you were doing it.”
21. Handling Team Disagreements
Disagreements can happen.
For example:
Developer:
“The feature should be built this way.”
Designer:
“I think another approach is better.”
Don't turn the disagreement into a personal argument.
Focus on:
Project requirements.
Evidence.
User needs.
Technical limitations.
Business objectives.
Professional response:
“I understand your approach. My concern is that this option may affect mobile performance. Could we compare both approaches against the project requirements before deciding?”
22. Don't Blame Team Members
Avoid:
“The designer caused the delay.”
Instead:
“The design approval is still pending, so development of that section cannot continue yet.”
The second statement focuses on the situation rather than attacking someone.
23. Sharing Files Correctly
When sending a file to a team member, provide context.
Poor:
“Here.”
Better:
“I've uploaded the updated sales report to the shared Google Drive folder. The file includes the corrected totals and the new regional sales chart.”
This saves the recipient time.
24. Remote Collaboration Etiquette
Follow these basic rules:
1. Be respectful.
2. Communicate clearly.
3. Respond within reasonable working expectations.
4. Don't disappear when there is an important blocker.
5. Respect time zones.
6. Keep important information documented.
7. Use the correct communication channel.
8. Take ownership of your tasks.
9. Give credit to other team members.
10. Ask for help when genuinely needed.
Real-Life Examples
Example 1 — Website Development Team
A company is building a website.
The:
Designer creates the interface.
Frontend developer builds the pages.
Backend developer creates the server functionality.
Tester checks for errors.
The frontend developer discovers that a design component is missing.
Instead of silently waiting, the developer sends:
“@Sarah, I noticed the mobile design for the checkout page hasn't been included. Could you please provide it so I can complete the responsive implementation?”
The issue is communicated early.
Example 2 — Virtual Assistant Team
Three VAs work remotely for the same company.
VA 1:
Manages email.
VA 2:
Manages appointments.
VA 3:
Organizes documents.
The manager asks for a weekly administrative report.
Each VA updates their section in a shared Google Sheet.
The team leader can then combine the information without asking each person individually.
This is collaboration.
Example 3 — Digital Marketing Team
A marketing team includes:
Content writer
Graphic designer
Social media manager
The content writer prepares the caption.
The designer creates the graphic.
The social media manager schedules the post.
The work must move in sequence:
Content → Design → Review → Scheduling → Publishing
If the writer delays the content, the designer may not be able to begin.
This is a task dependency.
Classwork
Task 1 — Identify Team Roles
A company wants to create an online store.
Identify at least six people/roles who could contribute to the project.
For each role, state their responsibility.
Task 2 — Choose the Communication Tool
Choose the most appropriate tool:
Slack, Teams, Email, Zoom/Meet, Trello/Asana
Formal client approval.
Daily team discussion.
Video project meeting.
Task assignment.
Quick internal question.
Sharing a project update.
Task 3 — Write a Team Handover
Imagine you are a data-entry worker.
You have completed:
700 of 1,000 records.
Cleaned 500 records.
Found 30 duplicate records.
Uploaded the working file to Google Drive.
Write a handover message to another team member who will continue the work.
Assignment 1 — Remote Team Project
Choose one project:
Website development
Social media campaign
Business report
Online store
Company branding
Customer support project
Create a remote team of at least five roles.
For each role, identify:
Job title.
Responsibility.
Tool used.
Dependency.
Deliverable.
Assignment 2 — Remote Collaboration Plan
Create a one-page Remote Team Collaboration Plan.
Include:
Communication
Which tool will the team use?
Meetings
When will meetings happen?
Task Management
Which tool will track tasks?
File Sharing
Where will files be stored?
Progress Updates
How often should team members report?
Time Zones
How will international time differences be handled?
Problems
How should team members report blockers?
Deadlines
How will deadlines be tracked?
Practical Challenge
Scenario: Website Team
You are part of a five-person remote website team.
Team
Project Manager — manages the project.
Designer — creates website designs.
Frontend Developer — builds the interface.
Backend Developer — develops server functionality.
Tester — tests the finished website.
The project deadline is Friday.
On Tuesday:
The designer has completed the homepage design.
The frontend developer has started implementation.
The backend developer is waiting for database requirements.
The tester cannot begin full testing because the website is not yet ready.
The project manager needs a progress update.
Your tasks:
Identify each person's responsibility.
Identify the dependencies.
Identify the blocked task.
Write a team progress update.
Write a message from the backend developer requesting the missing requirements.
Create four project action items.
Assign an owner to each action.
Give each action a deadline.
Identify what should be discussed in the next team meeting.
Key Lesson
Remote teamwork requires visibility, communication and ownership.
Remember:
Know your role → Understand your task → Communicate → Collaborate → Update → Handover → Deliver
A strong remote team member does not simply complete their own task.
They also make sure that the next person has what they need to continue the work.
Next
DAY 27: FILE SHARING AND CLOUD COLLABORATION
You will learn how to:
Store work safely in the cloud.
Share files with clients and team members.
Understand Google Drive and OneDrive.
Manage permissions.
Avoid accidental file deletion or overwriting.
Organize shared folders professionally.
Collaborate on documents in real time.
Control who can view, comment, or edit files.
REMOTE WORK SKILLS TRAINING
MONTH 2 — WORKING PROFESSIONALLY
WEEK 6 — REMOTE COLLABORATION
DAY 26: WORKING WITH TEAMS REMOTELY
Objectives
By the end of this lesson, students should be able to:
Explain what remote collaboration means.
Understand the difference between individual remote work and remote teamwork.
Identify common roles within a remote team.
Communicate effectively with team members.
Understand task ownership and responsibility.
Work with shared tasks and deadlines.
Participate effectively in remote team meetings.
Handle disagreements and team problems professionally.
Software/Tools
Slack, Microsoft Teams, Google Workspace, Microsoft 365, Trello, Asana, Zoom, Google Meet, Google Drive, OneDrive
These tools help remote teams communicate, share files, assign tasks, hold meetings, and track project progress.
1. What Is Remote Collaboration?
Remote collaboration means people working together on the same project or business activities even when they are not physically in the same location.
For example:
A company may have:
A manager in the United States.
A developer in Nigeria.
A designer in Kenya.
A marketing specialist in Ghana.
A data analyst in India.
They can still work as one team using digital tools.
Simple definition:
Remote collaboration = working together through digital tools without needing to be physically together.
2. Individual Remote Work vs Remote Teamwork
Individual remote work
You receive a task and complete most of it yourself.
Example:
A client gives a data-entry worker 500 records to enter.
Remote teamwork
Several people contribute to one project.
Example:
A website project may involve:
Project manager
UI/UX designer
Frontend developer
Backend developer
Content writer
Tester
Everyone has different responsibilities, but they are working toward the same result.
3. Why Remote Collaboration Is Important
Many remote jobs require teamwork.
Even if you work from home, you may still have to:
Attend meetings.
Share files.
Ask colleagues questions.
Give progress updates.
Receive tasks.
Review another person's work.
Meet team deadlines.
Participate in discussions.
Solve problems together.
Being physically alone does not mean working alone.
4. The Remote Team Workflow
A typical remote project can follow this process:
Project → Planning → Task Assignment → Individual Work → Collaboration → Review → Revision → Approval → Delivery
For example:
Website Project
Manager
↓
Creates project requirements
↓
Designer
Creates website design
↓
Frontend Developer
Builds interface
↓
Backend Developer
Builds server/database functionality
↓
Tester
Tests the website
↓
Manager
Reviews and approves
↓
Client
Receives final website
Each person depends on other team members.
5. Common Remote Team Roles
A remote team can have different roles depending on the business.
Project Manager
Coordinates the project, tasks, deadlines and team members.
Team Lead
Provides direction and helps solve technical or operational problems.
Virtual Assistant
Handles administrative and support tasks.
Developer
Builds or maintains software.
Designer
Creates visual materials.
Data Analyst
Analyzes information and produces insights.
Marketing Specialist
Handles marketing activities.
Customer Support Agent
Communicates with customers and resolves issues.
Content Writer
Creates written content.
Quality Assurance Tester
Checks products or software for problems.
6. Understand Your Role
One of the biggest remote teamwork problems is unclear responsibility.
Before starting a task, know:
What am I responsible for?
Who assigned the task?
What is the deadline?
Who depends on my work?
Who reviews my work?
Who should I contact if I have a problem?
Example
A designer finishes a website design.
The frontend developer cannot start properly until the design files are available.
Therefore:
Designer → Developer
The developer depends on the designer.
This is called a dependency.
7. Task Ownership
Task ownership means being responsible for completing a particular task.
If your task is:
“Prepare the monthly sales report.”
You are the owner of that task.
You should:
Understand it.
Track it.
Complete it.
Report progress.
Communicate problems.
Submit it.
Do not assume that someone else will complete your task simply because you're working in a team.
8. Team Responsibility vs Individual Responsibility
A team may be responsible for the entire project.
But each person should still know their individual responsibility.
Example
Project:
Build an e-commerce website.
Team responsibility:
Deliver the complete e-commerce website.
Individual responsibilities:
Designer: Website interface
Frontend Developer: User interface implementation
Backend Developer: Server and database
Content Writer: Product descriptions
Tester: Testing
Everyone contributes to the final result.
9. Communication Channels
Not every message should be sent through the same channel.
Slack/Teams
Good for:
Team discussions
Quick questions
Project updates
Channels
File sharing
Good for:
Formal communication
External clients
Important approvals
Documentation
Zoom/Google Meet
Good for:
Meetings
Discussions
Demonstrations
Problem-solving
Trello/Asana
Good for:
Task assignment
Deadlines
Progress tracking
Project status
10. Choose the Right Communication Channel
Suppose you need to tell your manager:
“I have completed the report.”
A project-management tool or team chat may be appropriate.
But if you need formal approval for a major business decision, email may be more appropriate.
Simple rule:
Use the right tool for the right type of communication.
11. Don't Communicate Everything Everywhere
A common remote-team problem is sending the same message through:
WhatsApp
Slack
Email
Teams
at the same time.
This can create confusion.
For example:
Manager receives the same task update in three different places.
Which one should the team use as the official record?
Agree on the team's communication system.
12. Team Channels
Slack and Teams allow teams to organize communication into channels.
Example:
#general
General company communication.
#marketing
Marketing discussions.
#development
Technical development.
#customer-support
Customer-related issues.
#project-website
Website project communication.
This prevents every conversation from being mixed together.
13. Mentioning Team Members
Tools such as Slack and Teams allow you to mention people.
Example:
@David Could you please confirm whether the API credentials are ready?
This is better than sending a message to the entire team when only David needs to respond.
Use mentions carefully.
Don't unnecessarily mention everyone.
14. Task Handover
Remote workers often need to pass work from one person to another.
A good handover should explain:
What was completed.
What remains.
Where the files are.
What problems exist.
What the next person needs to do.
The deadline.
Example:
Website Handover
Completed: Homepage and contact page.
Files: Google Drive → Website Project → Design.
Remaining: Services page and mobile adjustments.
Issue: Client has not approved the new logo.
Next Step: Continue with the services page while waiting for logo approval.
Deadline: Friday.
This makes it easier for another person to continue the work.
15. Working Across Time Zones
Remote teams may be in different countries.
You might work from Nigeria while your manager works from the United States.
Therefore, don't assume that everyone is working at the same time.
Before scheduling meetings or expecting immediate responses:
Check the person's time zone.
Use calendar tools.
State the time zone.
Respect working hours.
Understand that someone may be offline.
Example:
“The meeting is scheduled for 2 PM WAT / 8 AM EST.”
This reduces confusion.
16. Synchronous vs Asynchronous Collaboration
Synchronous
People communicate at the same time.
Examples:
Zoom meeting
Google Meet
Teams call
Live discussion
Example:
You and your manager join a meeting at 10 AM.
Asynchronous
People communicate at different times.
Examples:
Email
Slack message
Trello comment
Shared Google Doc
The person can respond when they become available.
Example:
You send a project update at 10 PM WAT.
Your manager reads it at 8 AM their local time.
17. Why Asynchronous Work Matters
Remote teams may not work the same hours.
A good remote worker should not expect:
“I sent the message, so you must respond immediately.”
Instead, provide enough information for the other person to understand the issue and respond when available.
Poor:
“Are you there?”
Better:
“Hi David, I'm working on the website deployment. The server is returning an authentication error. Could you please check the deployment credentials when you're available?”
The second message gives context.
18. Don't Send One Word at a Time
Avoid:
Hi
John
Are you there?
I need something.
Please check.
This is inefficient.
Instead:
Hi John, I'm currently working on the website deployment and need confirmation of the hosting credentials. Could you please check them when you're available? Thanks.
One complete message is easier to understand.
19. Team Meetings
Before joining a remote meeting:
Prepare
Check the agenda.
Review relevant documents.
Test your internet.
Test microphone.
Have necessary files ready.
During the meeting
Listen.
Avoid unnecessary interruptions.
Take notes.
Ask relevant questions.
Record assigned tasks.
After the meeting
Confirm:
What was decided?
Who is responsible?
What is the deadline?
What happens next?
20. Meeting Action Items
A meeting should ideally produce clear action items.
Example:
| Action | Owner | Deadline |
|---|---|---|
| Update website content | David | Tuesday |
| Prepare graphics | Sarah | Wednesday |
| Test website | Michael | Thursday |
| Submit final version | Team Lead | Friday |
This prevents:
“I thought you were doing it.”
21. Handling Team Disagreements
Disagreements can happen.
For example:
Developer:
“The feature should be built this way.”
Designer:
“I think another approach is better.”
Don't turn the disagreement into a personal argument.
Focus on:
Project requirements.
Evidence.
User needs.
Technical limitations.
Business objectives.
Professional response:
“I understand your approach. My concern is that this option may affect mobile performance. Could we compare both approaches against the project requirements before deciding?”
22. Don't Blame Team Members
Avoid:
“The designer caused the delay.”
Instead:
“The design approval is still pending, so development of that section cannot continue yet.”
The second statement focuses on the situation rather than attacking someone.
23. Sharing Files Correctly
When sending a file to a team member, provide context.
Poor:
“Here.”
Better:
“I've uploaded the updated sales report to the shared Google Drive folder. The file includes the corrected totals and the new regional sales chart.”
This saves the recipient time.
24. Remote Collaboration Etiquette
Follow these basic rules:
1. Be respectful.
2. Communicate clearly.
3. Respond within reasonable working expectations.
4. Don't disappear when there is an important blocker.
5. Respect time zones.
6. Keep important information documented.
7. Use the correct communication channel.
8. Take ownership of your tasks.
9. Give credit to other team members.
10. Ask for help when genuinely needed.
Real-Life Examples
Example 1 — Website Development Team
A company is building a website.
The:
Designer creates the interface.
Frontend developer builds the pages.
Backend developer creates the server functionality.
Tester checks for errors.
The frontend developer discovers that a design component is missing.
Instead of silently waiting, the developer sends:
“@Sarah, I noticed the mobile design for the checkout page hasn't been included. Could you please provide it so I can complete the responsive implementation?”
The issue is communicated early.
Example 2 — Virtual Assistant Team
Three VAs work remotely for the same company.
VA 1:
Manages email.
VA 2:
Manages appointments.
VA 3:
Organizes documents.
The manager asks for a weekly administrative report.
Each VA updates their section in a shared Google Sheet.
The team leader can then combine the information without asking each person individually.
This is collaboration.
Example 3 — Digital Marketing Team
A marketing team includes:
Content writer
Graphic designer
Social media manager
The content writer prepares the caption.
The designer creates the graphic.
The social media manager schedules the post.
The work must move in sequence:
Content → Design → Review → Scheduling → Publishing
If the writer delays the content, the designer may not be able to begin.
This is a task dependency.
Classwork
Task 1 — Identify Team Roles
A company wants to create an online store.
Identify at least six people/roles who could contribute to the project.
For each role, state their responsibility.
Task 2 — Choose the Communication Tool
Choose the most appropriate tool:
Slack, Teams, Email, Zoom/Meet, Trello/Asana
Formal client approval.
Daily team discussion.
Video project meeting.
Task assignment.
Quick internal question.
Sharing a project update.
Task 3 — Write a Team Handover
Imagine you are a data-entry worker.
You have completed:
700 of 1,000 records.
Cleaned 500 records.
Found 30 duplicate records.
Uploaded the working file to Google Drive.
Write a handover message to another team member who will continue the work.
Assignment 1 — Remote Team Project
Choose one project:
Website development
Social media campaign
Business report
Online store
Company branding
Customer support project
Create a remote team of at least five roles.
For each role, identify:
Job title.
Responsibility.
Tool used.
Dependency.
Deliverable.
Assignment 2 — Remote Collaboration Plan
Create a one-page Remote Team Collaboration Plan.
Include:
Communication
Which tool will the team use?
Meetings
When will meetings happen?
Task Management
Which tool will track tasks?
File Sharing
Where will files be stored?
Progress Updates
How often should team members report?
Time Zones
How will international time differences be handled?
Problems
How should team members report blockers?
Deadlines
How will deadlines be tracked?
Practical Challenge
Scenario: Website Team
You are part of a five-person remote website team.
Team
Project Manager — manages the project.
Designer — creates website designs.
Frontend Developer — builds the interface.
Backend Developer — develops server functionality.
Tester — tests the finished website.
The project deadline is Friday.
On Tuesday:
The designer has completed the homepage design.
The frontend developer has started implementation.
The backend developer is waiting for database requirements.
The tester cannot begin full testing because the website is not yet ready.
The project manager needs a progress update.
Your tasks:
Identify each person's responsibility.
Identify the dependencies.
Identify the blocked task.
Write a team progress update.
Write a message from the backend developer requesting the missing requirements.
Create four project action items.
Assign an owner to each action.
Give each action a deadline.
Identify what should be discussed in the next team meeting.
Key Lesson
Remote teamwork requires visibility, communication and ownership.
Remember:
Know your role → Understand your task → Communicate → Collaborate → Update → Handover → Deliver
A strong remote team member does not simply complete their own task.
They also make sure that the next person has what they need to continue the work.
Next
DAY 27: FILE SHARING AND CLOUD COLLABORATION
You will learn how to:
Store work safely in the cloud.
Share files with clients and team members.
Understand Google Drive and OneDrive.
Manage permissions.
Avoid accidental file deletion or overwriting.
Organize shared folders professionally.
Collaborate on documents in real time.
Control who can view, comment, or edit files.
REMOTE WORK SKILLS TRAINING
MONTH 2 — WORKING PROFESSIONALLY
WEEK 6 — REMOTE COLLABORATION
DAY 27: FILE SHARING AND CLOUD COLLABORATION
Objectives
By the end of this lesson, students should be able to:
Explain cloud storage and cloud collaboration.
Understand how remote teams share files.
Use Google Drive and OneDrive for remote work.
Create professional folder structures.
Share files and folders correctly.
Understand Viewer, Commenter, and Editor permissions.
Collaborate on documents in real time.
Avoid accidental deletion, duplication, and overwriting.
Manage file versions and document changes.
Apply basic cloud-file security practices.
Software/Tools
Google Drive, Google Docs, Google Sheets, Google Slides, Microsoft OneDrive, Microsoft Word, Microsoft Excel, Microsoft PowerPoint
These tools allow remote workers to store, access, edit, share, and collaborate on files from different locations.
1. What Is Cloud Storage?
Cloud storage means storing digital files on internet-connected servers so that authorized users can access those files from different devices and locations.
Instead of keeping a document only on your laptop:
Laptop → File
You can store it in:
Google Drive → File
Then an authorized team member can access it from another computer.
2. Why Cloud Storage Is Important for Remote Work
Imagine a company has five workers.
The manager is in the UK.
The designer is in Nigeria.
The marketer is in Ghana.
The developer is in India.
The data analyst is in Canada.
They cannot depend on passing a flash drive around.
Cloud storage allows everyone to access the required files according to their permissions.
Benefits include:
Remote access.
Easy file sharing.
Team collaboration.
Centralized storage.
Reduced dependence on one computer.
Easier document management.
Real-time collaboration.
3. What Is Cloud Collaboration?
Cloud collaboration means multiple authorized people can work with the same files or documents through an online platform.
For example:
A manager creates a Google Sheet.
The data-entry worker enters information.
The supervisor reviews it.
The manager checks the final result.
Everyone can work from different locations.
4. Local Storage vs Cloud Storage
Local Storage
Files are stored directly on your device.
Examples:
Laptop hard drive.
SSD.
USB flash drive.
External hard drive.
Example:
C:\Users\Raheem\Documents\Sales Report.xlsx
The file exists on that device.
Cloud Storage
Files are stored online.
Examples:
Google Drive
OneDrive
You can access them through your account and internet connection.
5. Cloud Storage Does Not Mean “No Backup Needed”
A common mistake is thinking:
“It's in Google Drive, so nothing can happen to it.”
You should still use good backup practices for important work.
Possible problems include:
Accidental deletion.
Incorrect editing.
Account access problems.
Synchronization problems.
Wrong file replacement.
Permission mistakes.
For critical business files, organizations may use additional backup systems.
6. Google Drive
Google Drive is Google's cloud-storage platform.
It can store:
Documents
Spreadsheets
Presentations
PDFs
Images
Videos
ZIP files
Other file types
Google Drive works closely with:
Google Docs
Google Sheets
Google Slides
Gmail
Google Meet
7. OneDrive
Microsoft OneDrive is Microsoft's cloud-storage platform.
It works closely with:
Word
Excel
PowerPoint
Outlook
Teams
Microsoft 365
A remote worker may use either Google Drive or OneDrive depending on the organization.
8. Professional Folder Organization
A remote worker should not store everything in one folder.
Poor structure:
My Drive
file1
final
final2
new final
report
report new
image
document
important
This becomes difficult to manage.
Better Structure
Company Project
→ 01_Admin
→ 02_Clients
→ 03_Reports
→ 04_Designs
→ 05_Data
→ 06_Final Deliverables
→ 07_Archive
This makes files easier to locate.
9. Use Meaningful File Names
Avoid:
❌ document1.docx
❌ newfile.xlsx
❌ finalfinal2.xlsx
❌ stuff.pdf
Use:
✅ Monthly_Sales_Report_September_2026.xlsx
✅ Company_Profile_Final_2026.pdf
✅ Website_Homepage_Design_V2.fig
A good filename should tell you what the file contains.
10. File Naming Convention
A simple naming structure is:
Project_Name + Document_Type + Date/Version
Example:
ABC_Sales_Report_2026-10-07.xlsx
Another:
ABC_Website_Homepage_V2.pdf
This becomes extremely useful when a project contains hundreds of files.
11. File Versions
Suppose you create a design.
Version 1
Business_Flyer_V1
After changes:
Business_Flyer_V2
After another revision:
Business_Flyer_V3
This helps you identify different stages.
However, when using Google Docs/Sheets or Microsoft 365 collaboration, built-in version history can also help track changes.
12. Google Docs Real-Time Collaboration
Google Docs allows multiple authorized users to work on the same document.
For example:
Writer
Creates the content.
Editor
Corrects grammar.
Manager
Reviews the document.
Everyone can collaborate without repeatedly emailing different versions.
13. Google Sheets Collaboration
Google Sheets is useful for:
Data entry.
Sales tracking.
Customer databases.
Project trackers.
Budgets.
Reports.
Multiple authorized users can work on the same spreadsheet.
Example:
A sales team can update a shared sales tracker while the manager monitors progress.
14. Microsoft Word and Excel Collaboration
Microsoft 365 also supports cloud collaboration through OneDrive and related Microsoft services.
For example:
A team can store:
Monthly_Report.xlsx
in OneDrive.
Authorized team members can work on the file without creating many disconnected copies.
15. File Permissions
One of the most important cloud collaboration skills is understanding permissions.
Common Google Drive permissions include:
Viewer
Can view the file.
Generally cannot directly edit the content.
Commenter
Can view and add comments where supported.
Useful for reviewing work.
Editor
Can make changes to the file.
This is a powerful permission and should be given carefully.
16. Why Permissions Matter
Imagine you are sending a company salary spreadsheet to a colleague.
If you accidentally give:
Anyone with the link — Editor
you may expose sensitive information to people who should not modify the file.
Always consider:
Who needs access?
What do they need to do?
How long do they need access?
Should they edit, comment, or only view?
Principle:
Give people the minimum access they need to do their work.
17. Sharing With Specific People
Instead of making an important document publicly accessible, you can share it with specific email addresses.
For example:
Share with: manager@company.com
Then select:
Viewer / Commenter / Editor
This provides more control.
18. Link Sharing
Cloud services often allow you to share a link.
Example:
“Anyone with the link can view.”
This can be convenient, but you should understand the security implications.
For confidential business files, avoid unnecessary public or broad link sharing.
19. Viewer vs Commenter vs Editor — Example
Suppose your manager asks you to prepare a report.
Manager
Editor
Because they may need to change or update the report.
Client reviewing the report
Commenter
They can provide feedback.
External person who only needs to see the final report
Viewer
They don't need editing access.
20. Real-Time Collaboration
One major advantage of cloud collaboration is that several people can work on a document without sending separate versions through email.
Traditional workflow:
Report_V1 → Email → Report_V2 → Email → Report_V3 → Email
This can become confusing.
Cloud workflow:
Shared Document → Team edits/reviews → Final version
Much simpler.
21. Comments
Comments are useful for discussing specific parts of a document.
For example, a manager can comment:
“Please verify this sales figure.”
The worker can check the data and reply:
“Verified against the source spreadsheet. The figure is correct.”
Once resolved, the comment can be marked as resolved where the platform supports it.
22. Suggestions and Track Changes
Google Docs supports suggestion-based editing.
Microsoft Word provides features such as Track Changes.
These features allow reviewers to propose changes without simply replacing everything.
This is useful for:
Reports.
Contracts.
Articles.
Proposals.
Business documents.
23. Avoid Creating Too Many Copies
Imagine five people download a spreadsheet and each creates a different copy:
Sales_Report_A
Sales_Report_B
Sales_Report_Final
Sales_Report_Final2
Sales_Report_Updated
Nobody knows which is correct.
A shared source of truth is better.
Example:
Master Sales Report
All authorized users work from the controlled version.
24. But Don't Edit a Master File Carelessly
A shared file is not an excuse to make uncontrolled changes.
Before editing an important document:
Confirm what you are expected to change.
Check instructions.
Use comments when appropriate.
Follow the team's workflow.
Avoid deleting important information.
25. Downloading vs Editing Online
Sometimes you need to download a file.
For example:
A client asks for a PDF copy of a report.
You can:
Work on the cloud document.
Review it.
Export/download PDF.
Upload the final PDF.
Send the client the correct version.
Don't accidentally send the editable working file when the client requested a PDF.
26. Cloud File Workflow
A professional workflow can be:
Receive File → Save/Organize → Check Permissions → Work → Review → Rename/Version → Upload → Share → Confirm
This reduces mistakes.
27. File Sharing Message
Don't just send:
“Here's the file.”
Instead:
Hi Sarah, I've uploaded the updated sales report to the Monthly Reports folder in Google Drive. The report includes the corrected totals and regional sales analysis. I've shared it with you as a Viewer for review.
This gives context.
28. What If You Can't Access a File?
Don't repeatedly click the file and then remain silent.
Check:
Are you using the correct account?
Is the link correct?
Do you have permission?
Is the file still available?
Is your internet working?
If access is still unavailable, communicate.
Example:
“I'm unable to access the Sales Reports folder. It appears that my account doesn't currently have permission. Could you please grant access to my work email?”
29. What If You Accidentally Delete Something?
Don't hide it.
First check whether the service provides a recovery option, such as Trash or version history.
Then inform the appropriate person if the incident affects the project.
Professional message:
“I accidentally removed the previous version of the report while reorganizing the folder. I have restored it from the available recovery history and verified that the file is accessible.”
Early communication is better than hiding the mistake.
30. Cloud Security Basics
For remote work:
Do:
Use strong passwords.
Use multi-factor authentication where available.
Check sharing permissions.
Share files only with authorized people.
Lock your device.
Avoid unknown links.
Remove access when no longer required.
Use the correct work account.
Don't:
Share passwords in public chats.
Give everyone Editor access.
Upload confidential files to random websites.
Leave your work account open on shared computers.
Share sensitive documents publicly without authorization.
Real-Life Examples
Example 1 — Virtual Assistant
A VA manages a manager's documents.
The VA creates:
Manager Documents
→ 2026
→ Reports
→ Meetings
→ Finance
→ Clients
The manager can quickly find documents without asking the VA where everything is.
This is professional cloud organization.
Example 2 — Marketing Team
A marketing team has:
Writer
Designer
Social Media Manager
They use Google Drive.
The writer uploads:
October_Content_Calendar.xlsx
The designer accesses it and creates graphics.
The social media manager reviews the approved content and schedules the posts.
Everyone works from the same source.
Example 3 — Software Development Team
A development team stores project documentation in a shared cloud folder.
The project manager can view the documentation.
Developers can edit technical documents.
Clients may receive Viewer access to approved deliverables.
Different permissions protect the team's working files while still allowing collaboration.
Classwork
Task 1 — Create a Folder Structure
Imagine you work for Nobigdeal Digital Services.
Create a professional Google Drive structure containing:
Administration
Clients
Projects
Finance
Marketing
Reports
Templates
Final Deliverables
Archive
Add at least three subfolders under Clients and Projects.
Task 2 — File Naming
Improve these filenames:
new.xlsxreportfinal.docximage2.pngfinalfinal.pdfstuff.zip
Create professional filenames for each.
Task 3 — Permissions
Choose the appropriate permission:
Viewer, Commenter, or Editor
Client reviewing a final report.
Team member updating a spreadsheet.
Manager reviewing a proposal and leaving comments.
External person who only needs to see a final PDF.
Designer who needs to edit a shared presentation.
Assignment 1 — Build a Cloud Workspace
Create a practice Google Drive or OneDrive workspace for a fictional company.
Your workspace must contain:
At least 8 main folders.
At least 3 subfolders.
At least 10 properly named files.
Appropriate file types.
A clear naming convention.
Take note of the structure you created.
Assignment 2 — Cloud Collaboration Exercise
Create a Google Docs or Microsoft Word document titled:
Remote Team Project Plan
Share it with a classmate or another authorized participant.
Set the appropriate permission.
The second person should:
Review the document.
Add at least three comments.
Suggest at least two changes.
Return it for review.
You should:
Review the comments.
Make the required changes.
Respond to the comments.
Resolve completed comments.
Submit the final version.
Practical Challenge
Scenario: Shared Business Project
You are working remotely for a company.
The team has created the following files:
Customer_List.xlsx
Sales_Report.xlsx
Company_Profile.docx
Marketing_Plan.docx
Logo.png
Product_Photos.zip
Monthly_Report.pdf
The manager asks you to organize everything in Google Drive.
Your task:
Create this structure:
Company Project
→ 01_Admin
→ 02_Customers
→ 03_Sales
→ 04_Marketing
→ 05_Branding
→ 06_Reports
→ 07_Final_Deliverables
→ 08_Archive
Then:
Put each file in the appropriate folder.
Rename poorly named files where necessary.
Apply a consistent naming convention.
Decide who should receive Viewer access.
Decide who should receive Editor access.
Create a final-deliverables folder.
Share the appropriate folder with a fictional manager.
Write a professional sharing message.
Explain why you chose each permission level.
Key Lesson
Cloud collaboration is not simply uploading files to the internet.
A professional remote worker must know how to:
Organize → Name → Store → Share → Control Access → Collaborate → Review → Version → Deliver
Remember:
The right person should have the right file with the right level of access.
Good file management can save a remote team hours of unnecessary searching, duplicate work, and confusion.
Next
DAY 28: PROJECT MANAGEMENT TOOLS — TRELLO & ASANA
You will learn how to use Trello and Asana to:
Create projects.
Create tasks.
Assign team members.
Set deadlines.
Track progress.
Manage dependencies.
Use task statuses.
Collaborate with a remote team.
REMOTE WORK SKILLS TRAINING
MONTH 2 — WORKING PROFESSIONALLY
WEEK 6 — REMOTE COLLABORATION
DAY 29: TEAM DOCUMENTATION AND WORKFLOWS
Objectives
By the end of this lesson, students should be able to:
Explain team documentation.
Explain why documentation is important in remote work.
Identify common types of workplace documents.
Create simple Standard Operating Procedures (SOPs).
Document recurring work processes.
Create clear team workflows.
Record decisions, responsibilities, and deadlines.
Create useful handover documentation.
Organize documentation in cloud storage.
Use documentation to reduce confusion and dependency on one person.
Software/Tools
Google Docs — for creating and maintaining team documents.
Microsoft Word — for professional documentation.
Google Drive / OneDrive — for storing and organizing documents.
Trello / Asana — for connecting documentation to tasks and projects.
Notion — for organizing team knowledge, procedures, and internal information.
Slack / Microsoft Teams — for communicating and sharing important documentation.
1. What Is Team Documentation?
Team documentation is the written information a team keeps so members can understand how work should be performed, what has been done, and what needs to happen next.
Instead of relying on someone saying:
“I normally do it this way.”
the process is written down.
Simple example
A company receives new customer registrations every day.
Instead of asking the Virtual Assistant each time what to do, the company creates a document:
SOP — How to Process New Customer Registrations
The document explains the process step by step.
2. Why Is Documentation Important in Remote Work?
Remote teams cannot always walk to another person's desk and ask questions.
Good documentation helps team members:
Understand their responsibilities
Follow the same process
Find information quickly
Continue another person's work
Reduce mistakes
Train new employees
Track decisions
Handle handovers
Maintain consistency
Work asynchronously
Key principle
If important work depends entirely on someone's memory, the process is fragile.
3. What Should Be Documented?
Not everything needs a formal document.
Important information that should normally be documented includes:
Processes
Instructions
Procedures
Project requirements
Task responsibilities
Meeting decisions
Client requirements
Password/access procedures where appropriate and securely handled
File locations
Reporting procedures
Handover information
Project updates
Frequently asked questions
Troubleshooting procedures
4. Common Types of Team Documentation
1. SOP
Standard Operating Procedure
Explains how to perform a recurring task.
Example
SOP — How to Create the Weekly Sales Report
2. Project Brief
Explains what a project is about.
It may contain:
Project objective
Scope
Team
Deadline
Deliverables
Requirements
Important resources
3. Meeting Notes
Records what was discussed during a meeting.
It may include:
Date
Participants
Topics discussed
Decisions
Action items
Responsible persons
Deadlines
4. Handover Document
Explains the current state of work when another person needs to continue it.
5. Checklist
A checklist contains actions that must be completed.
Example
Before submitting a report:
Check spelling
Check calculations
Check dates
Check formatting
Review charts
Save final version
Share with manager
6. Knowledge Base
A collection of information that helps team members understand a company's systems, procedures, products, and common questions.
5. What Is an SOP?
An SOP is a written step-by-step procedure for completing a specific task consistently.
SOP means:
Standard Operating Procedure
Example
SOP: Processing a Customer Order
Open the order system.
Check the customer's information.
Confirm payment status.
Verify the product.
Update the order status.
Send confirmation.
Record the transaction.
Escalate unusual issues.
Anyone properly trained should be able to follow the SOP.
6. Structure of a Good SOP
A simple SOP can contain:
SOP Title
What process does this document explain?
Purpose
Why does the process exist?
Scope
When should the procedure be used?
Responsible Person
Who performs the task?
Required Tools
What software or resources are needed?
Procedure
The step-by-step instructions.
Quality Check
What should be checked before completion?
Escalation
What should happen if something goes wrong?
Last Updated
When was the document last reviewed?
7. Example of an SOP
SOP — Weekly Sales Report
Purpose
To prepare and submit an accurate weekly sales report.
Responsible Person
Data Analyst.
Tools
Excel
Google Drive
Power BI, where applicable
Email
Procedure
Download the week's sales data.
Save the original file.
Check the data for missing values.
Remove duplicate records where appropriate.
Check calculations.
Calculate total sales.
Identify top-performing products.
Create required charts.
Review the report.
Export the final report.
Save it in the correct Drive folder.
Send the report to the manager.
Quality Check
Confirm:
Dates are correct.
Sales figures are accurate.
No required records are missing.
Charts match the data.
File name follows the company's naming convention.
8. What Is a Workflow?
A workflow is the sequence of steps through which work moves from beginning to completion.
Simple workflow
Request → Review → Assign → Work → Review → Approve → Deliver → Archive
A workflow answers:
What happens next?
9. Workflow vs SOP
These concepts are related but different.
Workflow
Shows how work moves between stages or people.
SOP
Explains how to perform a specific process or task.
Example
Workflow:
Customer Order → Payment Check → Order Processing → Delivery → Customer Confirmation
SOP:
How to Check Customer Payment
The workflow shows the overall process.
The SOP explains one part of the process in detail.
10. Creating a Remote Team Workflow
To create a workflow:
Step 1 — Identify the goal
What result should the process produce?
Step 2 — Identify the starting point
What causes the work to begin?
Step 3 — List the steps
Write down everything that must happen.
Step 4 — Identify responsible people
Who performs each step?
Step 5 — Identify dependencies
What must happen before another step can begin?
Step 6 — Identify approval points
Who reviews or approves the work?
Step 7 — Identify possible problems
What can block the process?
Step 8 — Document the workflow
Put the process into a clear document or project management system.
11. Example Workflow — Website Project
A remote website project might follow this workflow:
Client Request
↓
Project Manager Reviews Requirements
↓
Designer Creates Design
↓
Client Approves Design
↓
Developer Builds Website
↓
Content Added
↓
Testing
↓
Client Review
↓
Corrections
↓
Final Approval
↓
Website Launch
↓
Project Documentation
This makes responsibilities and handoffs clearer.
12. What Is a Handover?
A handover happens when responsibility for work moves from one person to another.
This is very common in remote teams.
For example:
A developer is unavailable and another developer needs to continue the project.
The first developer should provide enough information for the second person to continue without starting from zero.
13. What Should a Handover Include?
A professional handover should contain:
Project name
Current status
Completed work
Work remaining
Important files
Current problems
Pending decisions
Important deadlines
Dependencies
Next steps
Contact person, where relevant
Example
Project: Business Website
Status: In Progress
Completed: Homepage and contact page
Remaining: Product page and mobile testing
Blocker: Waiting for product images
Files: Google Drive project folder
Next Step: Build product page after images are received
Deadline: Friday
14. Documentation and the "Single Source of Truth"
A single source of truth means the team knows which location contains the current official version of information.
For example:
Google Drive → Client Projects → ABC Company → Final Reports
The team should know that this is the official location.
Without this, people may have:
Report_Final.docx
Report_Final2.docx
Report_Final_New.docx
Report_Final_Updated.docx
Report_Final_ReallyFinal.docx
This creates confusion.
15. Document Naming
Use clear names.
Instead of:
document1.docx
Use:
ABC_Weekly_Sales_Report_2026-10-07_V1.docx
A useful naming structure is:
Client_Project_Document_Date_Version
Examples
ABC_Website_Project_Brief_V1.docx
Nobigdeal_Student_Report_2026-10-07_V2.xlsx
Client_Social_Media_Calendar_October_2026.xlsx
16. Version Control
Version control means keeping track of changes made to a document or project.
Examples:
V1
V2
V3
Final
Where possible, use built-in version history in:
Google Docs
Google Sheets
Microsoft Word
OneDrive
SharePoint
This is often safer than creating many unnecessary copies.
17. Documenting Meeting Decisions
Remote meetings can become useless if nobody remembers what was agreed.
After an important meeting, record:
Meeting
Topic: Website Project Meeting
Decisions
Homepage design approved.
Product page requires revision.
Launch moved to Friday.
Action Items
Designer: Update product page design.
Developer: Continue homepage development.
Project Manager: Send revised timeline.
Deadline
Friday, 3 PM.
18. Documentation Should Be Simple
A document does not need to be complicated to be useful.
Bad documentation may be:
Too long
Difficult to understand
Outdated
Full of unnecessary information
Poorly organized
Good documentation is:
Clear
Practical
Current
Easy to search
Step-by-step
Relevant to the team
Key principle
Documentation should help someone do the work, not simply prove that documentation exists.
19. Updating Documentation
Documentation can become dangerous when it is outdated.
Suppose a company changes from one CRM to another but the SOP still tells workers to use the old CRM.
Workers may follow the instructions and create problems.
Therefore, documentation should be reviewed when:
Software changes
Processes change
Responsibilities change
Client requirements change
Errors reveal a missing step
New information becomes available
20. Remote Documentation Workflow
A professional documentation workflow can be:
Create → Review → Approve → Store → Share → Use → Update → Archive
Example
A company creates a new customer-service SOP.
VA writes the SOP.
Team leader reviews it.
Manager approves it.
Store it in Google Drive.
Share it with the team.
Team members use it.
Update it when the process changes.
Archive the old version if necessary.
Real-Life Examples
Example 1 — Virtual Assistant
A VA manages a business owner's emails.
The VA creates an SOP:
How to Process Incoming Business Emails
The procedure explains:
Open inbox.
Identify urgent messages.
Categorize emails.
Respond to routine requests.
Forward specific issues to the manager.
Label completed emails.
Record important follow-ups.
Update the task board.
If another VA takes over, they can follow the same procedure.
Example 2 — Software Development Team
A development team is building a Django application.
The documentation contains:
Project overview
Development environment
Database information
Git workflow
Coding workflow
Testing procedure
Deployment process
Known issues
Handover notes
When another developer joins the project, they can understand how the team works without repeatedly asking basic questions.
Example 3 — Digital Marketing Team
A marketing team manages a company's social media accounts.
Their documentation contains:
Content Workflow
Idea → Research → Caption → Design → Review → Approval → Schedule → Publish → Report
The team also documents:
Brand voice
Image dimensions
Posting schedule
Approval process
Hashtag guidelines
Reporting format
This helps different team members work consistently.
Classwork
Classwork 1 — Identify the Documentation
For each situation, identify the most appropriate document:
A new employee needs to learn how to process customer orders.
A team needs to record what was agreed during a meeting.
A developer is leaving and another developer must continue the project.
A company needs to explain the overall stages of a project.
A worker needs to remember all checks before submitting a report.
Choose from:
SOP
Meeting Notes
Handover Document
Workflow
Checklist
Classwork 2 — Create an SOP
Create an SOP titled:
How to Prepare a Weekly Business Report
Include:
Purpose
Responsible person
Tools
At least 10 steps
Quality checks
Escalation procedure
Last updated date
Classwork 3 — Create a Workflow
Create a workflow for:
Receiving and Processing a New Client Request
Start with:
Client Request
and end with:
Completed Work / Client Confirmation
Identify the person responsible for each major stage.
Assignment 1 — Create a Professional SOP
Choose one real remote-work activity such as:
Data entry
Email management
Social media posting
Website maintenance
Customer support
Weekly reporting
Online research
Create a professional SOP containing:
Title
Purpose
Scope
Responsible person
Required tools
Required information
Step-by-step procedure
Quality checklist
Common problems
Escalation procedure
Final completion process
Last updated date
Submit it as a properly formatted Google Doc or Word document.
Assignment 2 — Create a Team Workflow & Handover
Create a workflow for a:
Remote Website Development Project
Your workflow must contain:
Client request
Requirement gathering
Planning
Design
Development
Testing
Client review
Corrections
Approval
Launch
Then create a handover document for a developer who has completed the homepage but must transfer the remaining work to another developer.
Include:
Completed work
Remaining work
Current status
Files
Blockers
Dependencies
Deadlines
Next steps
Practical Challenge
Scenario: Remote Business Operations
You work as a Remote Operations Assistant for a small company.
The company currently has a problem:
Different workers perform the same task differently, and important information is often lost when someone is unavailable.
The manager asks you to create a documentation system.
Your task
Create:
1. Folder Structure
Company Documentation
01_SOPs
02_Workflows
03_Project_Documentation
04_Meeting_Notes
05_Handover
06_Templates
07_Archive
2. Create three SOPs
For example:
Customer Order Processing
Weekly Sales Reporting
Client Email Management
3. Create two workflows
For example:
New Client Onboarding
Website Development
4. Create one meeting-notes document.
5. Create one handover document.
6. Create a documentation index.
Example:
| Document | Location | Responsible Person | Last Updated |
|---|---|---|---|
| Customer Order SOP | SOPs | VA | 7 Oct 2026 |
| Weekly Report SOP | SOPs | Data Analyst | 7 Oct 2026 |
| Website Workflow | Workflows | Project Manager | 7 Oct 2026 |
The goal is to create a system where another team member can find the information and continue the work without asking unnecessary questions.
Key Lesson
Remote collaboration is not only about communication.
It is also about leaving useful information behind.
A professional remote worker should be able to:
Document → Organize → Explain → Share → Handover → Update → Improve
Remember:
If someone else cannot understand or continue your work from your documentation, the documentation is not complete enough.
NEXT
DAY 30: WEEK 6 PRACTICAL ASSESSMENT
REMOTE WORK SKILLS TRAINING
MONTH 2 — WORKING PROFESSIONALLY
WEEK 6 — REMOTE COLLABORATION
DAY 30: WEEK 6 PRACTICAL ASSESSMENT
Assessment Objectives
By the end of this assessment, students should be able to:
Explain remote collaboration.
Work effectively with remote team members.
Select the appropriate communication channel.
Manage shared files and cloud documents.
Use Trello or Asana to manage project tasks.
Create and follow team workflows.
Create basic SOP documentation.
Prepare professional handover information.
Manage responsibilities, deadlines, and dependencies.
Complete a realistic remote team project.
Software/Tools
Trello / Asana — project and task management.
Google Drive / OneDrive — cloud file management.
Google Docs / Microsoft Word — documentation.
Google Sheets / Microsoft Excel — shared data and reporting.
Slack / Microsoft Teams — team communication.
Zoom / Google Meet — remote meetings.
SECTION A — THEORY TEST
Answer all questions.
1. What is remote collaboration?
2. What is the difference between individual remote work and remote team work?
3. What is task ownership?
4. Why is clear task ownership important?
5. Mention four tools that can be used for remote collaboration.
6. What is cloud collaboration?
7. What is a shared document?
8. What is the difference between a Viewer and an Editor?
9. What is a project management tool?
10. What is Trello used for?
11. What is Asana used for?
12. What is a task dependency?
13. What is a blocker?
14. What is team documentation?
15. What does SOP mean?
16. What is the purpose of an SOP?
17. What is a workflow?
18. What is a handover document?
19. What is a single source of truth?
20. Why should remote teams document important decisions and processes?
Marks
20 questions × 1 mark = 20 marks
SECTION B — SCENARIO ASSESSMENT
Scenario 1 — Wrong Communication Channel
Your team leader asks you to send a routine project update.
You send the same update separately through:
Slack
WhatsApp
Email
Teams
The team becomes confused about which message contains the latest information.
Questions
What did you do incorrectly?
What channel would you choose?
How would you prevent duplicate communication in the future?
Scenario 2 — Missing File
You are preparing a client report, but the finance team has not uploaded the latest sales data.
The deadline is tomorrow.
Questions
What should you do?
Should you simply wait?
Write a professional message to the finance team.
How should you record the blocker in Trello or Asana?
Scenario 3 — Shared File Problem
Three team members edit different copies of the same spreadsheet.
At the end of the day, the manager asks:
“Which file is the correct version?”
Questions
What caused the problem?
How can the team prevent this?
What does "single source of truth" mean?
How should the files be organized?
Scenario 4 — Handover
A remote worker is unavailable for several days.
They have completed approximately 70% of a project but did not leave proper notes.
Another team member must continue the work.
Questions
Identify at least eight pieces of information that should have been included in the handover.
Scenario 5 — Team Disagreement
A designer and developer disagree about how a website should be built.
The designer says:
“My design must be followed exactly.”
The developer says:
“The design is difficult to implement and should be changed.”
Questions
How should the team handle the disagreement?
What should they focus on?
Who should make the final decision if the issue cannot be resolved between them?
SECTION C — PRACTICAL TASK 1
Trello/Asana Project Management
Scenario
You have been hired by a small company to coordinate a:
Business Website Development Project
The project team consists of:
Project Manager
Graphic Designer
Web Developer
Content Writer
Client
Create the project in Trello or Asana.
Create at least 15 tasks.
Suggested tasks:
Collect client requirements
Create project brief
Prepare website structure
Collect logo
Collect brand colours
Write homepage content
Design homepage
Design contact page
Review design
Develop homepage
Develop contact page
Add website content
Test website
Fix identified problems
Client approval
Website launch
Your project must include:
Project name
Task names
Task owners
Priorities
Deadlines
Statuses
At least 3 dependencies
At least 2 comments
At least 1 blocker
Marks
15 marks
SECTION D — PRACTICAL TASK 2
Cloud Collaboration
Create the following folder structure in Google Drive or OneDrive:
Business Website Project
01_Admin
02_Client_Requirements
03_Design
04_Content
05_Development
06_Testing
07_Final_Deliverables
08_Meeting_Notes
09_Handover
10_Archive
Create or place sample files inside the folders.
File naming examples
Website_Project_Brief_V1.docxHomepage_Content_V1.docxHomepage_Design_V2.pngWebsite_Test_Report_V1.xlsxFinal_Website_Report_2026-10-07.pdf
Demonstrate:
Correct folder organization.
Proper file names.
Appropriate sharing permissions.
One shared Google Doc or Word document.
Comments or suggestions.
Version control.
Marks
15 marks
SECTION E — PRACTICAL TASK 3
Create an SOP
Create an SOP titled:
SOP — Processing a New Client Website Request
Your SOP must contain:
1. Purpose
Why the process exists.
2. Scope
When the SOP should be used.
3. Responsible Person
Who handles the process.
4. Required Tools
List the required software.
5. Procedure
At least 10 clear steps.
6. Quality Check
At least five checks.
7. Escalation
Explain what should happen when there is a problem.
8. Completion
Explain how the task is officially completed.
Marks
15 marks
SECTION F — PRACTICAL TASK 4
Create a Team Workflow
Create a workflow for:
New Client Website Project
Your workflow should look similar to:
Client Request
↓
Requirement Collection
↓
Project Planning
↓
Task Assignment
↓
Design
↓
Client Review
↓
Development
↓
Testing
↓
Corrections
↓
Final Approval
↓
Launch
↓
Handover
↓
Project Archive
For each stage, identify:
Responsible person
Expected output
Possible blocker
Next stage
Marks
10 marks
SECTION G — PRACTICAL TASK 5
Handover Document
Imagine that you are a web developer who is leaving a project temporarily.
You have completed:
Homepage
About Us page
Navigation menu
Remaining:
Contact page
Mobile responsiveness
Contact form
Final testing
Client review
Create a professional handover document.
Include:
Project name
Current status
Completed work
Remaining work
File location
Known issues
Blockers
Dependencies
Important deadline
Next steps
Marks
10 marks
SECTION H — INTEGRATED REMOTE TEAM PROJECT
Final Practical Simulation
You are now part of a five-person remote team.
Team
Project Manager
Responsible for coordinating the project.
Graphic Designer
Responsible for visual materials.
Content Writer
Responsible for written content.
Web Developer
Responsible for website development.
Remote Assistant
Responsible for documentation, organization, and communication.
Client Request
A small Nigerian business wants a simple website.
The client requests:
Homepage
About Us page
Services page
Contact page
WhatsApp contact button
Company logo
Mobile-friendly design
The client wants the first version ready within 7 days.
Your Team Must Complete
Step 1 — Project Setup
Create a Trello or Asana project.
Step 2 — Task Breakdown
Break the project into at least 20 tasks.
Step 3 — Assign Responsibilities
Assign each task to an appropriate team member.
Step 4 — Set Deadlines
Create realistic deadlines.
Step 5 — Identify Dependencies
Identify at least five dependencies.
Step 6 — Create Cloud Storage
Create an organized Google Drive or OneDrive folder.
Step 7 — Create Documentation
Create:
Project brief
SOP
Workflow
Meeting notes
Handover document
Step 8 — Communication
Create sample:
Team update
Client update
Clarification message
Blocker message
Completion message
Step 9 — Handover
Prepare a handover as though the project is being transferred to another team member.
MARKING GUIDE
| Section | Marks |
|---|---|
| Theory Test | 20 |
| Scenario Assessment | 10 |
| Trello/Asana Project | 15 |
| Cloud Collaboration | 15 |
| SOP | 15 |
| Team Workflow | 10 |
| Handover Document | 10 |
| Integrated Project | 5 |
| TOTAL | 100 |
Pass Mark
60/100
Performance Levels
90–100: Excellent
80–89: Very Good
70–79: Good
60–69: Pass
Below 60: Needs Improvement
WEEKEND ASSIGNMENT 1
Remote Collaboration Portfolio
Create a folder called:
Remote Collaboration Portfolio
Include:
One Trello/Asana project
One cloud folder structure
One SOP
One workflow
One meeting-notes document
One handover document
Five professional team messages
Three project status updates
Two examples of blockers and solutions
One final project report
This portfolio should demonstrate that you can actually work as part of a remote team.
WEEKEND ASSIGNMENT 2
Seven-Day Remote Team Simulation
Create a fictional remote team and simulate a 7-day project.
Every day, record:
Tasks completed
Tasks in progress
Blockers
Team communication
Files created
Project updates
Next day's tasks
At the end of the seven days, prepare a final report showing:
Planned Work → Completed Work → Delayed Work → Problems → Solutions → Final Result
WEEK 6 COMPLETION OUTCOME
After completing Week 6, students should be able to participate in a professional remote team and understand how to:
Communicate → Share Files → Manage Tasks → Collaborate → Document → Track → Handover → Deliver
The student should no longer depend on informal communication alone.
They should be able to use professional digital systems to make the team's work visible, organized, documented, and transferable.
Comments
Post a Comment