Plan and deliver a campaign across departments

Coordinate a campaign in one Node Cluster project with collaborators from different departments, shared tasks and supporting material.

Use a finite project for a campaign with a defined outcome, such as a website launch or customer event. The example below uses Marketing as the owning department and Sales as a collaborator.

1. Establish the project and outcome

Create Autumn launch in Marketing and choose Project. Record the target outcome, audience, intended launch date, and owner in the available project description and notes.

If you started the plan as an unpublished project, publish it to Marketing when ready and review its access there. Publishing moves the existing project; do not create another campaign project just to place it in the department.

2. Turn the plan into owned tasks

Create tasks such as Agree the campaign brief, Draft the landing-page copy, Review the sales handoff, Approve launch assets, and Confirm launch readiness. Assign real people and dates where the team has made a commitment.

Use the Design Canvas when a visual plan helps explain the campaign. Keep the actionable work in tasks so the team can find and update it through All Tasks and the relevant views.

3. Involve the other department

Give the Sales collaborators the appropriate access to this project. They do not need a Marketing primary department merely to contribute here. They also do not need a Marketing creation exception unless they must create new projects there.

Review the assignment policy. If a collaborator should reassign work to another person, their project permissions and the policy must permit that action.

4. Keep context easy to find

Use Notes for the brief and decisions. Use Files for the project’s assets and supported references. Check external file access with someone from the collaborating department. A visible link is not proof that the provider lets that person open it.

Use task progress notes for decisions specific to one outcome. For example, record why a launch asset is blocked and who can resolve the issue rather than leaving the entire explanation in a separate conversation.

5. Run the readiness review

Open Overview in Team mode and confirm the campaign scope. Inspect unfinished tasks, blockers, and unassigned work. Open each critical task to check its completion criteria; a summary count is not a substitute for an explicit readiness decision.

After launch, record the outcome and remaining follow-up tasks. Mark completed work Done. If ongoing campaign operations continue, decide whether they belong in a stable BAU project.

You are finished when: Marketing and Sales can find the same campaign, see their responsibilities, and explain the next decision without creating parallel task lists.