⭐ XP 0/0
⏱ 00:00
ASDAN Studio Β· Community Project Β· Week 2 of 6

The Site's Need

BUILD Pathway Β· ASDAN Studio Β· Community evidence

Progress SoW Β· BUILD ASDAN AutΒ 1 Β· 2026–27 Β· Community evidence Β· Week 2πŸ… Banks: ASDAN/UAS community evidence
Spark: Good design meets a real need.

Success looks like

  • I can describe what our site actually needs
  • I can back a need with something we observed
  • I can match a need to what we can build
Aspire Β· rank the site's needs β€” which one matters most, and to whom?

Teacher Print Tools β€” Week 2

Retrieval Quiz

Arrival Task – What Do You Already Know?

1. Say it

What does a green space need?

Any honest answer counts β€” say it out loud.

2. Spot it

Big or small β€” what fits the site?

Any honest answer counts β€” say it out loud.

3. Point to it

Point to a feature a site might need.

Any honest answer counts β€” say it out loud.

Starter

Today at a Glance

Key Question: What are we building today β€” and where does the evidence go?
πŸ’‘

Big Idea

Good design meets a real need.

SPARK
🎲

Today We Play

Match it up

GAME
🧱

The Wall Grows

Onto the Project Board (our partner sees it)

AUDIENCE
πŸ…

It Banks

ASDAN/UAS community evidence

EVIDENCE

Talk first, then we play β€” every voice counts here.

I Do

The Model β€” The Site's Need

Key Idea: Good design meets a real need.
Step 0 of 3

Finding out what the site and its users need.

Finding the need means looking and asking: photos of the site, words from its users. Evidence beats assumption every time.

Turning a need into a design requirement.

A requirement is a need made testable β€” 'must survive wind', 'must be low enough for wheelchair users'. If you can't check it, it isn't a requirement yet.

Checking our idea fits the space.

Checking fit is holding our idea against the space: the size, the ground, the access. A brilliant design that doesn't fit the site is a mistake with good handwriting.

We Do

Match it up

How it works: Every card has a partner. Say which one before you tap β€” the tap only tells you if you were right.Found: 0/4
Planter
Wildlife box
Bench
Sign

I Do

Proving It β€” The Evidence Loop

Key Idea: Launch extension: one written line β€” the one thing our design must get right, or it isn't worth building.
Step 0 of 3

Documentarian

photo the needs list.

Annotate

'our design must ___'.

Witness

staff tick 'identified a site need', sign.

For the moderator, not just the folder

A tick says it happened. A witness statement says what you did. Before the photo is filed, the adult writes one sentence naming the thing they actually saw you do — and rings whether you did it Supported, Standard or Stretch.

That ring is the part that counts. It is the difference between “the class did this” and “this candidate did it, at this level, with this much help.” The witness sheet prints with every pack.

We Do

Match the Asset to the Need It Meets

Step 1: Tap a card, then its partner. Step 2: Watch the WAGOLL write itself. Score: 0/4
Planter
Wildlife box
Bench
Sign
The people who walk past not knowing what this place is
The birds with nowhere to nest since the hedge went
The visitors who stand because there's nowhere to sit
The bare corner nobody looks at twice

Needs observedEvidence not assumptionRequirements setBoard updated

Independent Work

Independent Work β€” Studio Time

Instructions: Work at your level. Evidence goes in your ASDAN portfolio β€” Documentarian photo + annotation + witness tick β€” ASDAN/UAS community evidence.
15:00

🀝 With support

Task: Match the site-need cards to our asset β€” one pair is done as a worked example β€” then move your MUST-HAVE card to the top.

Steps: One step at a time β€” adult support is right there. Photo when you’re proud of it.

πŸ‘€ On your own

Task: List the site's needs from the photos, then agree two requirements our design must meet.

Steps: Work the task through β€” photo as you go, annotate at the end, witness tick before you pack up.

πŸš€ Take it further

Task: List the site's needs from the photos, then agree two requirements our design must meet. Stretch: rank the site's needs β€” which one matters most, and to whom?

Steps: Task first, stretch second β€” and your annotation should explain the why, not just the what.

Lundy Loop

Lundy Loop β€” Your Voice on the Wall

Why: Article 12 β€” your view counts here, and it genuinely changes what happens next.

πŸšͺ SPACE

The Project Board is a real-stakes space β€” our partner sees it β€” but it's still safe: nothing goes up without your say-so, and 'pass' is allowed.

πŸ“£ VOICE

Say one thing the site needs that the photos do not show.

πŸ‘₯ AUDIENCE

The partner sees what we noticed β€” noticing well is how a project earns trust.

⭐ INFLUENCE

The needs you pin become the design requirements. They decide the shape of the build.

Exit Ticket

Exit Ticket

Instructions: Answer independently. Own words β€” no wall-peeking.

1.

I can describe what our site actually needs β€” true for you today? Say how.

Point to today’s work as your proof.

2.

I can back a need with something we observed β€” true for you today? Say how.

Point to today’s work as your proof.

3.

I can match a need to what we can build β€” true for you today? Say how.

Point to today’s work as your proof.

Slide 1/10
πŸ…πŸ“ΈβœοΈ

The Site's Need β€” banked!

What the design must meet βœ…

βœ“ I can describe what our site actually needsβœ“ I can back a need with something we observedβœ“ I can match a need to what we can buildβœ“ Onto the Project Board (our partner sees it): Share one requirement with the group. Today's outcome goes onto the P…Next lesson: Our Team Roles β€” who does what. DOCBUILDCHECK
⏸ MID-POINT PEER CHECK

Pens down β€” quick partner check!

πŸ“£ Show your partner where you’re up to. Check together against today’s success: I can describe what our site actually needs and I can back a need with something we observed. If something’s missing, help them add it β€” kindly.

2 minutes max. Then I’ll resume the timer.