Organise coordination for a remote project

Describe deliverables before selecting tools

A remote project can generate many conversations while leaving people uncertain about what they should produce. Describe the expected deliverables and what will make each one ready for its intended use. A “customer file” might mean a summary, a collection of documents or a proposal awaiting review; agree which meaning applies. Assign an owner who brings the questions together for each deliverable. Tools can then support this organisation, but they cannot replace a shared understanding of the expected result or a clear allocation of responsibilities among participants.

Create a reference space for the project

Choose a shared workspace that holds the brief, working documents, decisions and open actions. Messages can announce a change, but the reference should remain easy to find after the conversation has moved on. Explain where to place a document and where to request approval. When a Moroccan team works with partners using another language, identify the documents that need adaptation. Keep project references consistent so exchanges remain connected to the same deliverables. A colleague should not have to guess whether differently named attachments describe the same piece of work.

Make dependencies and obstacles visible

For each open action, record what is needed to move forward: a response, a document, access or a confirmed choice. A status such as “in progress” does not explain why the work remains incomplete. For example, a presentation may depend on an approved visual; its owner needs to know who prepares that visual and how availability will be communicated. Frame the obstacle as a concrete question for the appropriate person. Avoid copying the same problem into several conversations where nobody recognises responsibility for resolving it.

Separate information, discussion and decisions

An information update requires a different response from a request to approve a choice. Make the purpose of your message clear. For a decision, explain the options, their observed consequences and who can make the choice. Use shared meeting time for issues that need an actual exchange. Descriptive updates can go into the project workspace for colleagues to read when they resume work. Once a decision is made, record the choice and its reason in the file instead of requiring an absent colleague to replay the whole conversation to understand it.

Prepare for a colleague to resume the work

Before completing a stage, leave a short note explaining what was produced, what remains open and where to find the usable version. Consider whether someone who missed the conversations could continue from that note. When a handover is unclear, improve the shared reference rather than sending repeated reminders in the messaging tool. Felexia Conseils can help establish coordination and management routines. Start with an actual project and adjust the approach based on the difficulties participants encounter, keeping the routine understandable for people who join the work later.

Continue reading

• Business management advisory
• Contact Felexia Conseils