You are applying design thinking today. Your group already has a developed solution. A strong idea is not a plan. A plan names the first real action, who owns it, what it costs, and what has to be true before the next step can start.

If your group still has two competing ideas, pick one in two minutes before you open the planner. Choose by who the solution serves and one first action you can name. Implementation needs a single solution.

Your reader is a community stakeholder, not your teacher. They should recognise the proposal as credible even if your group never delivers it yourselves.

These three words shape every line of today's plan. Read them before you open the planner.

Use the pathway planner to map your group's solution from idea to something running in the community. Fill milestones across four time horizons and four tracks: actions, people, resources, and dependencies.

Rules that keep the plan honest

• The first two weeks must contain at least one real action a named person could start this month.
• Every later step must name what it depends on.
• Resources need a rough cost or source, not just the word "funding".
• Owners are roles a stakeholder would recognise (committee chair, Foróige project worker, local authority parks officer, school principal), not only your group initials.

Work in this order

1. Planner (about 8 minutes): fill the grid with milestones your group can defend.
2. Near-horizon check (about 5 minutes): read the first-two-weeks column down. Empty early cells mean the plan is still a wish. Fix them before you write.
3. Write-up (about 17 minutes): open the Collaborative Task Implementation Plan template your teacher has placed in the Strand 2.1 Digital Portfolio folder (or create it now as Collaborative Task Implementation Plan[GroupName] in the format your class uses). Aim for about one page if time is tight; two pages if the grid is solid. A community stakeholder should be able to read it cold.
4. Individual paragraph (about 5 minutes): each member adds their own short note under the plan.

Required headings in the plan document

• Solution and who it serves (opening line)
• Steps with owners, timing, resources and dependencies
• Risks and early-warning signs
• Individual contribution (each member): which single step you are most personally able to contribute to and what you would actually do; one dependency that still worries you; and who outside the group would need to own that dependency. One honest paragraph is enough.

Each group member keeps a full copy. This plan sits in your Digital Portfolio under Strand 2.1 and can be drawn on as Portfolio in Action evidence for the collaborative design-thinking work.

Quick share (2–3 minutes): one group reads only their first-two-weeks column aloud. The class names one strength and one empty or weak cell.

Then talk these through with your group, and with the person beside you.

• If a community stakeholder read only your first two weeks, would they trust the rest of the plan? What would make them stop reading?
• Credible does not mean your group must deliver every step. Which parts of your plan properly belong to other people or organisations, and have you named them honestly?

Today you applied the implementing stage of design thinking to your collaborative solution.

• Implementation turns a developed idea into timed steps with owners, resources and dependencies
• A stakeholder is the real reader of the plan, not only your teacher
• A dependency is what must already be true before a later step can start
• You built a pathway of milestones, then wrote a Collaborative Task Implementation Plan for Strand 2.1
• You named the step you are most able to contribute to, plus a dependency that still worries you and who outside the group would own it
• A credible plan can involve other organisations; your group does not have to deliver every line