Share strategy between teams without losing context

A corporate team agrees a priority: reduce unplanned service stops. A product team needs that context when comparing pump designs. Copying a slide into another workshop may convey the words, but it leaves the receiving team to work out where the statement came from and whether it has changed.

Research on connected management toolkits examines how tools can be selected and combined to support strategy work. In software, a useful handoff must also preserve the source, the receiving context and the rules for change. [1]

Connect the source tools to Workspace Outgoing on the canvas. Choose the items and shared fields, approve receiving workspaces in the same organisation, inspect the live preview and enable sharing. The selection can cover all items or a narrower set, such as starred or selected items.

Approval to receive a publication does not make the recipient a member of the source workspace. Private prompts and discussions stay there. Share the fields the receiving team needs; this is not an export of every underlying database field or conversation.

In the receiving workspace, connect Workspace Incoming to the approved publication. Reviewed updates keep the accepted version until the team accepts a newer version. Automatic updates apply published changes without opening the Incoming tool. Connected downstream tools continue to use their normal incoming workflow.

Use reviewed updates when a team needs to discuss a changed requirement before revising its plan. Use automatic updates when keeping the shared inputs current is appropriate. Neither choice turns a source update into automatic approval of every downstream decision.

Item lineage and history let a reviewer trace the source and publication version. If the source withdraws an item or sharing stops, previously accepted content retains a visible status and history rather than silently disappearing.

In the pump example, the product team can connect the shared service priority to a Linking Grid and assess which functions address it. That assessment remains an explicit local judgement. The corporate team can share the need without deciding the engineering answer.

For several source teams, use distinct publications and Incoming tools so each handoff has a clear purpose. Agree who owns each source, which fields are shared and who reviews a material change.