The Integrated Task

Integrated workplace communication means carrying one clear purpose across different channels. A meeting lets people test an idea, ask questions, and agree on action; an email records the recommendation, responsibilities, and next step. The wording can change with the channel, but the facts, proposal, and requested decision should remain consistent. If the meeting suggests one plan and the follow-up email quietly changes it, colleagues may leave with different expectations.

Use one realistic situation to connect the skills in this lesson. For practice, assume a support team handled 120 customer requests last month, and 40 received a first response after one business day. The team has an existing shared inbox, no budget for new software, and a midday handover that may leave requests without a clear owner. The task is to discuss a practical response in a meeting and send a follow-up email that turns the discussion into an agreed next step.

Read the Situation and Audience

Before speaking or writing, separate known facts from interpretations. The figures show how many requests waited too long for a first response; they do not explain why the delay happened. They do not show how long it took to resolve each request, either. Calling this a staffing problem or claiming that the handover caused every delay would go beyond the evidence. A careful communicator states what the information shows, then labels any explanation as a possibility to check.

Consider what each audience needs to decide or do. A manager may need to know whether the proposal requires extra spending and how its results will be reviewed. Team members need clear ownership and a workable handover. Both groups need a specific request, not only a description of the problem. A two-week pilot using the existing inbox is a proportionate proposal: it has a defined timeframe, assigns responsibility, and gives the team a chance to review evidence before deciding whether to continue.

Contribute Clearly in a Meeting

In a meeting, make the point easy to follow by moving from evidence to recommendation to next step. A useful opening is, ‘Last month, 40 of 120 requests received a first response after one business day.’ Then distinguish the proposed action from the known facts: ‘I recommend a two-week pilot with one named owner per shift and a short midday handover.’ Finish with a decision request, such as, ‘Could we confirm the shift owners by Thursday?’ This sequence gives listeners context, a practical option, and something concrete to respond to.

Use meeting language that makes space for clarification and disagreement. You might ask, ‘Do these figures exclude weekends?’ or say, ‘I agree that ownership needs to be clearer. I suggest we test the shared inbox process before requesting new software.’ If a colleague raises a concern, acknowledge its relevance before responding: ‘That is a fair concern about workload. Could we track missed handovers during the pilot as well?’ Avoid presenting a suggestion as an agreed decision until the people responsible have confirmed it. If a point is unresolved, say so and name who will follow up.

Write the Follow-Up Email

A useful follow-up email makes the meeting outcome scannable without retelling the whole discussion. Begin with a subject that names the decision or action, such as ‘Two-week shared inbox pilot: confirm shift owners.’ In the opening, give only the context readers need. State the recommendation directly, explain why it fits the situation, and make the requested action and deadline unmistakable. If the meeting has not approved the pilot, ask for approval rather than writing as though the decision is final.

A concise sample could read: ‘Subject: Two-week shared inbox pilot: confirm shift owners. Hi team, Last month, 40 of our 120 customer requests received a first response after one business day. I recommend a two-week pilot using our existing shared inbox, with one named owner per shift and a brief midday handover. This requires no new software. During the pilot, we can track first-response time and missed handovers, then review the results before deciding whether to continue. Could each shift confirm its owner by Thursday? Thanks, Maya.’ The message uses the figures as context, offers a bounded test, identifies measures, and asks for one specific action. It does not promise that the pilot will solve the delays.

Review Across Channels

Before sending, compare the email with what was said and agreed in the meeting. Check that the figures are accurate, the recommendation has not changed, and the message distinguishes proposed actions from approved ones. Check also that the named action, owner, deadline, and review point are clear. A reader who missed the meeting should still understand what is being proposed and what response is needed. A reader who attended should not find a new commitment introduced without discussion.

Finally, revise for plain language and a professional tone. Replace vague wording such as ‘We should improve the process soon’ with a specific action and date. Remove unnecessary background, but keep enough context for the audience to understand the reason for the recommendation. In the meeting, allow time for questions; in the email, make it easy to reply with a decision or confirmation. The aim is not to sound formal for its own sake. It is to help colleagues understand the evidence, evaluate a practical recommendation, and act on the same agreed plan.