Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 41 Next »

WORK IN PROGRESS (ME & PAGE)

Mural board retention policy:

 I'll let you hide the rules, as long as you follow them! TL;DR please add all new Mural boards below, every 6-8 weeks review and keep as-is (still active) or: delete / file on LAN re: transitory file policy (expand for details and support links)

“The Rules” 💪

  • When you create a new Mural board, please add the link below

  • Once a board is inactive, meaning you have not touched the work (project, initiative, version, session, engagement) for 6-8 weeks:

  • Please delete transitory boards — anything not essential to understanding government business, examples:

    • day-to-day operations context

    • brainstorming or casual collaboration (no decisions or learner records, just rough working materials)

  • Please file non-transitory boards on the LAN that contain information that must be retained, examples:

  • If unsure about information retention, please consult the Transitory Information Records Management Guide

To be tested:

  • how might we build trust and accountability into this process?

    • rather than one person managing this admin, how can we each take ownership of our file management?

    • and ‘chunk’ it into regular work so it isn’t an awful end of year task (agility)

    • even better, how might we reframe this from ‘admin’ to design? Could this be an opportunity to flex our content strategy and content governance chops (UX skills) as we evaluate and maintain the content underpinning our DA service & products

  • how could we use the tools and methods available to us?

    • e.g. a calendar reminder every 8 weeks to do a file & Mural cleanup, perhaps there is a ‘small’ ticket every 4th sprint (8 weeks) to create the time and space for us to do this work - allowing us to collaborate when needed

    • try this, bring experiences to retrospective, iterate

  • how might we build this into onboarding and offboarding flows?

    • when folks join, the expectation is clear, and there are supports (e.g. clear guidance, reminders and tickets in sprints) in place

    • should folks move on, files are managed before they go, and there are supports/time in place to do so - no orphaned or mystery content for someone else to try to clean up later

Mural board index:

Boards are organized by team, then primary function (decision to be tested).


Sprint 18 action items:

Those with licenses have:

  1. added any current working Murals (active w/in last 6-8 weeks) to the table above ^

  • Tess Good please check box when complete
  • Priya S., please check box when complete
  • Derek Masselink, please check box when complete - how can we support Jamie & Rosa?
  • Kim Zinke, please confirm your current working boards with Tess - we’ll work together to index them here
  1. worked through Mural boards you created/own and:

    1. filed any record documents

    2. deleted any transitory boards that have been inactive for 6-8 weeks

Those without licenses have:

  1. ethically-bribed a license-holder to help them out with any legacy boards they own? TBC

  2. Can use the current OneNote as a way to audit your boards

Working session on Tuesday Dec 19 @ 11am


  • No labels