6.1Concrete cases
The essentials in 30 seconds
- Two end-to-end projects: a digital workstation audit and a hybrid customer workshop.
- A stable method: frame, arrange, prepare, animate, trace, check.
- The deliverable counts more than the tool: a clear box, a useful meeting and dated actions.
Nassim’s thread — two end-to-end missions
Nassim coordinates the projects of a digital services SME in Algiers. He receives two missions: overhaul his digital workstation and prepare a hybrid customer workshop. Each mission replays the same process: frame the need, organize the space, prepare the exchanges, then check the traces.
Each case follows Context, Steps, Result: replay it on your own environment.
Why concrete cases?
Knowing how to click is not enough: mastery of Teams and Outlook is measured by the ability to carry out a complete mission, with contacts, deadlines and shared files.
The two cases below involve levels 0 to 5: professional account, mail, calendar, Teams, channels, meetings, files, notifications and best practices.
Case 1 — Overhaul the digital workstation of an SME
Context: Nassim arrives in an SME of 45 people. Files are scattered among attachments, USB drives and several personal accounts. Meetings get lost in conversations and everyone has their own organization. Management requires a common, simple and tenable working environment.
Déroulé :
- List actual uses: mail, calendar, meetings, conversations, files and mobile access. Identify the three main irritants with two colleagues from different departments.
- Check that everyone is using their professional account and not a personal account. Take stock of installed applications: desktop, web and mobile.
- Create a Teams team by major project or department, with a general channel and channels by subject. Avoid near-empty teams and catch-all channels.
- Define a simple rule: email for external and formal, chat for quick, channel for what must remain visible to the team, meeting to decide.
- Clean out the inbox: archive old messages, create four folders maximum, set up two sorting rules and a common signature.
- Configure the calendar: working hours, time zone, meetings without unwanted notifications and concentration slots. Test the planning assistant with two colleagues.
- Create a “Customer Workshop” channel with a Files tab, a Notes tab, and a pinned message that explains where to drop what.
- Set file naming rules: date, project, version. Show a successful example and a counter-example to make the rule concrete.
- Configure notifications: priorities, silent hours on mobile, summary of monitored channels. Mute alerts from channels that do not require immediate action.
- Take stock at D+7: three questions, three adjustments. Measure the number of files found without asking a colleague and the number of meetings canceled due to lack of preparation.
Result: A Teams team per project, a controlled email box, a readable calendar, shared naming rules and controlled notifications. Nassim can lead the rest without becoming the bottleneck.
Case 2 — Organize an end-to-end hybrid customer workshop
Context: The SME must lead a framing workshop with a client in Oran: three people on site and four remotely. You must send the invitation, prepare the documents, lead the meeting, share the decisions and relaunch the actions. The client works with Outlook and Teams.
Déroulé :
- Clarify the expected result: decisions to be made, participants, duration and documents to prepare. Write the calendar in three points maximum.
- Create the Teams meeting from Outlook, invite participants and add the meeting link. Check time zones and suggest a slot with the scheduling assistant.
- Prepare a shared file in the project channel: calendar, support, list of participants and decision table. Send the link rather than the attachments.
- Test the hardware: microphone, camera, screen sharing and connection. Provide a telephone plan B and a substitute moderator to monitor the chat.
- Open the meeting five minutes before, welcome participants remotely and check that everyone sees the material. Remember the rules: one question at a time, chat for links.
- Animate with shared media. Record decisions in the pipeline as they happen, not after the meeting. Use the mentions to designate someone responsible for action.
- At the end, rephrase the decisions, those responsible and the dates. Ask for explicit validation out loud and in chat.
- Publish a short report in the channel: decisions, actions, next deadline. Pin the message and create a task or reminder for each action.
- Send a summary email to the client with the report link and next steps. Avoid duplicating attachment files.
- On D+2, check that each action has a person responsible and a date. On D+7, take a 10-minute update and close the completed actions.
Result: A workshop prepared, animated and outlined: clear invitation, shared file, visible decisions, dated actions and accessible report. The customer knows where to find the information and Nassim does not have to send back five versions of support.
Script ready to say — frame the review (30 s)
“I start by observing your actual uses, not by adding tools. Then I propose a simple organization: one team per project, channels per subject, four folders in the box and naming rules. We measure the gains on D+7.”
To be used at the start of a mission to avoid over-organization.
Script ready to say — frame the client workshop (25 s)
“We prepare the calendar, the shared file and the decisions to be made. During the workshop, I write down the decisions in the channel. At the end, everyone leaves with a manager and a date.”
Show that the meeting produces a deliverable, not just an exchange.
Copy-paste template — workshop scoping sheet
OBJECTIVE: _______________
PARTICIPANTS: _______________
DURATION: _______________
DECISIONS EXPECTED: 1) ____ 2) ____ 3) ____
DOCUMENTS: _______________
MINUTES OWNER: _______________
FOLLOW-UP DATE: _______________Copy and paste template — digital workstation rules
ACCOUNT: business only
MAILBOX: 4 folders + 2 rules + signature
TEAM: 1 per project / department
CHANNELS: 1 topic = 1 channel
FILES: YYYY-MM-DD_project_vNN
MEETING: agenda + decisions + actions
MOBILE: priority notifications + quiet hoursShort version
Treat the most common case and check the result.
Remote
Share the link and check access before the workshop.
48 hour challenge — apply tomorrow
Choose a real mission and replay the complete process: framing, shared space, preparation, animation and report. Time 45 minutes and write down the three actions that saved you time.
- I know how to sequence framing, organization, preparation and reporting.
- I distinguish between email, chat, channel and meeting depending on the need.
- I review decisions and actions before closing.
Frequently asked questions
Should you put everything in Teams?
No. Email remains relevant for external, formal and traceability purposes. Teams is used for internal exchanges, decisions and shared files.
How many channels to create?
One channel per clear subject, with one general channel. If a channel is only used once, a message or chat is enough.
How to avoid unnecessary meetings?
Write the expected result. If the meeting produces no decisions or actions, a structured message is often enough.
What is the first deliverable of a collaborative project?