11 minutes

Your team learning rhythm and resource-sharing plan

One page the team can write together: what you will do, who hosts, how to take part another way, what gets shared, and what this plan will never record.

What you’ll be able to do

Write a one-page team learning rhythm and resource-sharing plan that names the practice, the host rotation, a second way to take part, and what is deliberately not recorded.
Compare the responses to this question and explain your choice: How should the supervisor handle this?
Draft a team learning rhythm and resource-sharing plan for your work, including the practice and its frequency, hosting and rotation, taking part another way.

Making optional true

Most teams have been told that something is optional and learned that it was not. The word has been worn thin, and a staff member who hears it applies a reasonable discount. The repair is not a more emphatic promise. It is structure: things that are true about the design whether or not the current supervisor is thoughtful, and that a new supervisor cannot quietly reverse.

That means writing down the negative space. A plan that says what will happen is ordinary. A plan that also says what will not happen — no attendance list, no collection of anything anyone writes, no mention of participation in performance conversations, no effect on assignments or opportunities — does something a promise cannot. It gives a staff member a sentence they can point to, and it gives the next person in your chair a standard to inherit.

The other half of the page is sharing. Most teams already share resources badly: a stream of links with no explanation, which buries the two that mattered. One rule fixes most of it. Anything shared carries one sentence saying who it is for and why it is worth their time. Keep the original source intact and describe it honestly rather than quietly replacing it with your own summary, and say plainly when something is required reading and when it is simply available.

A team learning rhythm and resource-sharing plan

One page a team writes together, naming the practice, who carries it, how else to take part, what gets shared, and what will never be recorded.

The practice and its frequency Twenty-five minutes at the start of our monthly team meeting, on material connected to something we are about to decide. Time is work time and does not have to be made up.

Hosting and rotation A different host each month from a volunteer rota, using the shared one-page outline: what we are looking at, why it matters to our work, two questions, what we might do differently. The supervisor hosts no more than twice a year.

Taking part another way The host posts a half-page note and the two questions within a day. Anyone can respond in writing, at any hour, or not at all. The slot alternates between morning and midday so it is not always built around one kind of schedule.

What gets shared, and where One shared space. Anything posted carries one sentence naming who it is for and why it is worth their time. Original sources stay intact and are described accurately. Required reading is labeled as required; everything else is simply available.

What this plan does not do No attendance is recorded. Nothing anyone writes in a reflection is collected, read or repeated. Participation is not mentioned in performance conversations, is not a factor in assignments or opportunities, and appears in no list anywhere. Completion counts toward no DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.

Season, check-in point and how it ends Runs for one season. At the check-in we ask three questions: is it still connected to our work, is there more than one real way in, and is it still worth the time. If the answer is no, we close it on purpose and say what we learned.

Copy the six fields, fill them in as a draft, and take the draft to your team as something they can change — including the option of deciding that now is not the time.

Browse and download only. Staff notes are not typed or saved on this page.

Five signals that make optional true

There is no list. Not a roster, not a note in a file, not a recollection you draw on later.
Declining is met with nothing at all — no follow-up, no gentle check-in, no second invitation aimed at one person.
The supervisor is sometimes absent, and the session runs perfectly well without them.
A second, genuinely equivalent way to take part exists, and is used by enough people to be normal rather than exceptional.
Nobody is named in any summary, upward or sideways, for taking part or for not taking part.

Questions you will be asked, and answers that hold up

Does this count toward my required training?

No. This is voluntary learning and it is separate from the department's required training. Completion here does not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception. Say this early and in writing, because a staff member who is unsure will treat everything as mandatory and nothing as safe.

Will anyone see what I wrote?

No. Reflection prompts are private and nothing written in them is collected, stored against a person or read by anyone. If a colleague chooses to share a thought in a session, that is their choice in that moment and it does not become a record.

What if my team is too busy this quarter?

Then say so plainly and pause it with a date to look again, rather than letting it fade. A stated pause keeps the practice credible. A slow disappearance teaches everyone that commitments here are decorative.

Can we bring in people from outside the division?

Yes, and this is often where the most useful sessions come from. Community co-designers, disabled advisors, families, interpreters and culturally specific organizations can shape or lead a session. Compensate them, be specific about what you are asking for, give them enough notice, and tell them afterwards what changed. They are partners in this work, not participants in staff training.

How do I know it is working?

Look at the work. A rewritten notice, a changed agenda, a question raised in a contract discussion that nobody was asking a season ago. If you cannot point to anything in the work after a full season, that is worth knowing — and it is a reason to change the design, not a reason to start counting people.

Write down what you will not do

What you can change

You control whether the plan states its limits in writing, which is the only part of it that outlives your intentions.

What to watch for

Do not rely on the team trusting you. Trust is not transferable, and the person who reads this plan after you leave will follow what it says rather than what you meant.

Your next step

Add the paragraph naming what is not recorded to your draft, read it out to the team when you share it, and keep it in place when the plan is next revised.

A supervisor wants a team learning rhythm that is genuinely optional. Which combination does the most to make that true?

Saying clearly at each session that participation is voluntary, and thanking people who attend.

No attendance record, nothing written collected, an equivalent second way to take part that people actually use, and no place in any routine where not taking part would show.

Keeping a private list of who attends so that support can be offered to those who do not.

Making the sessions short enough that attending costs almost nothing.

Try a situation

A DSD supervisor drafts a monthly team learning rhythm and shares it as optional. Two days later, a staff member stops by privately and asks whether choosing not to take part will be noticed in her performance review.

How should the supervisor handle this?

Reassure her that it will not be noticed, and thank her for asking.

Treat the question as information about the design: put in writing what is and is not recorded, separate this plainly from required training and from performance review, remove any place where non-participation would be visible, and say the same thing to the whole team rather than only to her.

Raise it at the next team meeting and ask whether anyone else shares the concern.

Carry this forward

Optional in writing and observed in practice is coercion with better manners. What makes optional true is structural: no attendance record, no reflection collection, a real second route in, and no place anywhere that non-participation shows up.
A plan that says what it will not do is more reassuring than a plan that promises good intentions, because the next supervisor inherits the structure rather than the promise.
Resource sharing works on one rule: one sentence saying who it is for and why it is worth their time. Keep original sources intact and describe them accurately rather than replacing them with a summary.
End a rhythm on purpose when it has done its work. A practice that is quietly allowed to die teaches the team that these things do not last; one that is closed with a short review teaches the opposite.

A scenario about a staff member privately asking whether declining will be noticed, a completed one-page plan with a host rotation and a second route in, and a knowledge check on what makes optional true.

Draft the one-page plan for your own team, then take it to them as a draft they can change — including the right to say that the whole thing is not worth doing right now.

Your next step

What in your current routines would show that someone had not taken part?

Check whether attendance appears in any note, list or summary you keep

Check whether your one-to-one meetings ask about it, even informally

Check whether the people who take part are the ones you think of first for opportunities

Write the sentence you will say to the whole team about what is not recorded

Browse and download only. Course notes are not typed or saved on this page.

Mark this lesson complete

Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.