Your group has generated a wide board of ideas and starred three. Today you are applying the developing stage of design thinking: you stop generating and start filtering.

A starred idea is still only a title. By the end of this period your group will hold one developed solution on a single page: what it does, who it serves, how it works, what it costs, and what could go wrong.

If you have fewer than three stars, take two minutes now to star from the full ideation board. If you cannot open the Collaborative Task Ideation document in the Strand 2.1 folder, tell the teacher before Part 2 starts.

Developing means taking the strongest one or two ideas and making them real enough to test. Design teams filter with three questions. Sort every claim through all three before you commit.

An idea that clears only one of the three is not ready. The one you develop should be the idea that survives the hardest honest pass through all three.

Two moves this period. First, practise the three-lens filter on the board so the whole class shares the same test. Then your group applies that test to your own starred ideas and writes the one-page developed solution.

This page is collaborative-task groundwork for your Digital Portfolio (Strand 2.1). It is not an Applied Learning Task on its own, but it is the solution document you will need for the implementing lesson next in this sequence and for later Portfolio in Action evidence of the collaborative task.

Part 1: filter practice (about 8 minutes). Drag each card into the lens it belongs to: feasibility, desirability or viability. Some cards could fit more than one lens. Place each where you would defend it, and be ready to say why. When the class is settled, discuss the two prompts on the activity aloud as a group (no typed answers on this page). Note which cards caused the longest argument: those are the questions your own idea must answer in writing.

Part 2: choose and develop (about 27 minutes). Open your Collaborative Task Ideation document and your problem-definition statement. Run each starred idea through all three lenses out loud as a group. Drop any idea that fails two lenses. If two still stand, pick the one a community stakeholder could take seriously next month, not the one that only sounds clever in the room.

Then write Collaborative Task Solution in your Strand 2.1 folder. One page. Every group member saves their own copy. Cover all five headings:

• What it does: one plain paragraph on the solution itself
• Who it serves: the people named in your problem definition, not "the community" in general
• How it works: the steps a stranger could follow
• What it would cost: rough but real figures (venue, materials, print, transport, time, or a small community/ETB grant). "Not much" is not a figure
• Risks: at least three things that could go wrong, and what you would do about each

If a heading is empty, the solution is not developed yet. Cost and Risks are non-negotiable exit checks: finish any incomplete page before the next lesson. Capture anything from the Part 1 talk that changes your choice under Risks or How it works on Collaborative Task Solution.

Think about these with your group (talk only; no typed answers on this page):

• Which starred idea did you leave behind, and which lens killed it: feasibility, desirability or viability?
• If a community stakeholder read your one-pager tonight, which heading would they challenge first, and what evidence would you need by next lesson?

Then close the page properly: add at least one sentence to Collaborative Task Solution under the weakest heading (often Risks or What it would cost), naming either the evidence you still need or the lens that killed the dropped idea. No empty Cost or Risks when you save.

Today you applied the developing stage of design thinking to your collaborative task.

• Feasibility, desirability and viability as three separate tests, not one vague "is it good?"
• Filtering your starred ideas until one solution survived an honest pass through all three lenses
• Writing Collaborative Task Solution (Strand 2.1 Digital Portfolio groundwork for the collaborative task and later Portfolio in Action evidence): what it does, who it serves, how it works, cost and risks
• Naming what you left behind and why, so the next stage builds on a real choice rather than a favourite title

Next lesson you move to implementing: a realistic plan a community stakeholder could recognise as a credible proposal. Bring a complete Collaborative Task Solution with you.