Plan the output before arranging the canvas
Describe what the group should produce: an organised set of problems, a selection of approaches or a process with unresolved questions. These outcomes need different spaces. Collecting ideas requires room for independent contributions, while deciding requires criteria and a traceable selection method. Build the board around that task instead of including as many available templates as possible.
Divide the session into a few recognisable working areas. Give each a short instruction, expected contribution and indication of when it will be used. Allow enough space for the expected participants without scattering them across an unmanageable canvas. A starting area with the purpose, sequence and a simple orientation marker particularly helps people unfamiliar with the tool.
Test access and operation with real accounts
Check that participants can open the board and edit it as required. Test external accounts and managed devices separately. Sharing that works within your organisation may not work for guests. Follow the permitted tools and data arrangements; confidential material does not automatically belong in an openly accessible guest area.
Ask someone to create, move and find a small test contribution. This shows whether basic operation is understood and accidental changes are noticeable. Prepare a short opening exercise without subject-matter pressure. A minute spent learning the controls may prevent a later contribution being lost simply because someone cannot create the required object.
Make contributions readable and identifiable
Agree a simple writing convention, such as one thought per card expressed as a short complete sentence. A keyword may be obvious to its author but have several meanings for others. In a problem collection, identify what or who is affected without adding unnecessary personal information. Use colour as a supplement; text or another explicit marker should still convey the meaning.
Plan time to read and clarify before combining or evaluating contributions. Similar-looking cards may describe different causes. Ask before merging them into one statement. Keep differing views visible rather than removing them through early categorisation. With a larger group, moderated consolidation may work better than everyone moving cards simultaneously across the canvas.
Assign facilitation and an alternative route
Decide who guides the group and who handles technical questions. If the facilitator must also solve every access problem, participants can lose their shared position. Explain at the start how to request help and where new contributions belong when the current area becomes crowded.
Prepare a simple alternative for individuals, such as speaking a contribution that the facilitator enters visibly. Changing the entire tool mid-session may create more problems than it solves. If access fails broadly, adapt the process; do not later imply that everyone worked equally on the board. Record the limitation when interpreting the outcome.
Turn the board into usable follow-up
Reserve closing time for results, open questions and next actions. A colourful canvas is not yet an allocation of work. Transfer agreed actions with owners and timing into the designated working record. Preserve the connection to the workshop so that later readers can understand how the selection was made.
Test the intended export or continued sharing with an example. Are the texts readable and important areas included? Do necessary connections or comments remain available, or must they be captured separately? Decide how long editing will continue and who coordinates changes afterwards. The session then ends with usable material rather than a link whose meaning nobody can explain a few weeks later.
