Build cross-unit collaboration
5 min read
Lesson objectives
- Turn a shared training goal into roles and dependencies across operations, finance, and IT while resolving resource conflicts.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
Imagine launching a program for new customer-service staff. Operations wants everyone started within a week, finance sets a cap on facilitation cost, and IT needs five days to prepare accounts. ‘Everyone must collaborate’ tells nobody what to deliver or when. The APTD outline includes knowledge of building professional relationships and of organizing collaboration among units such as finance, operations, and IT. Turn that scope into a testable shared outcome, a dependency map, and an agreement that makes conflicts visible. Here the goal is for each new employee to complete a system task before serving a real customer, not merely to appear on an attendance list.
State the common result first: ‘Eighty employees complete a practical task using their own accounts by the end of week three.’ Then ask each unit what it controls and what it needs. Operations owns employee lists and release times from shifts. IT creates accounts and tests access. Finance approves facilitation spending. You design the task and coordinate dates. Order matters: the system exercise cannot be tested before accounts exist, and the room schedule cannot be fixed before release times are known. A delayed task should show its consequence on the schedule rather than surprising the team on session day. This map also prevents every obstacle from being turned into a dispute about someone’s attitude.
Distinguish the decision owner, the person doing the work, those consulted, and those informed. For cohort dates, operations supplies shift constraints, you propose a learning schedule, IT reviews system capacity, and an authorized manager approves the plan. Listing four people as equally ‘responsible’ can freeze a decision. Give each deliverable one functional owner, a deadline, and observable evidence: ‘The IT lead demonstrates successful sign-in for 20 test accounts by Tuesday.’ When a unit rejects a date, ask which measured constraint it cannot meet instead of questioning its willingness to cooperate. The constraint may require a new sequence, or it may expose a decision beyond the team's authority that needs escalation.
Negotiate the conflict rather than hiding a concession. If operations can release only 20 employees per session, 80 employees require four cohorts. At two hours each, that is eight facilitator hours but 160 learner attendance hours across all participants. Do not confuse those figures in a resource estimate. If finance cannot pay for four sessions, compare alternatives that preserve individual practice: perhaps a short self-paced introduction followed by applied time, or internal facilitation if a competent facilitator is available. Record each option's effect on staff time, practice quality, and delivery cost. Packing all 80 into one session might cut facilitator cost yet make simultaneous testing of 80 accounts impossible. Ask IT for capacity evidence before approving that shortcut.
In the follow-up meeting, ask for evidence before impressions. How many accounts passed sign-in? How many employees can operations release? Has finance approved the budget line? Mark each item complete with proof, delayed with an alternative, or awaiting a decision by someone with authority. Invite the unit that sees an overlooked risk; silence is not consent. Close with a brief record of what changed, who approved it, and how affected staff will hear. If only 12 of 20 accounts work, do not write ‘IT is almost ready’ and keep the cohort date automatically. Compare the eight missing accounts with the test deadline and choose a retest or a shift. Strong working relationships keep disagreement focused on a shared criterion rather than on motives.
Lesson summary
Turn a shared training goal into roles and dependencies across operations, finance, and IT while resolving resource conflicts.