Usability.ie
What you receiveEngagements & scopePublic-service teamsCapability summaryMethod finderBrief builder
My own project

Growing space needs
clear expectations.

A grower needs to know what a request means. A host needs to understand demand, privacy and the steps before an introduction. The public interface should support those decisions consistently.

5 September 2026

Homegrown

Homegrown is my own project. This is an expert review of its public site.

Type

Expert assessment

Evidence

Public interface

Status

Recommendations recorded

Date

5 September 2026

My own projectHomegrownEDITORIAL COVER
01 / The service question

Can growers and hosts distinguish interest, suitability, an introduction and an agreed arrangement?

02 / Scope & evidence

A bounded view.
Not the whole story.

The homepage, Find a Plot, Open Your Space, host listing form and Galway page. The source records desktop/mobile presentation, public copy, navigation, selected form and keyboard checks. No form was submitted and no private matching, enquiry or payment records were accessed.

What already helps

Separate routes for growers and hosts make the audience distinction visible. The grower form asks for a rough area rather than a street address, and the matching explanation says both sides decide whether to meet. Those features are observable; understanding and operational fulfilment remain separate questions.

03 / The findings

From observation
to a useful check.

Finding 01Observed inconsistency · no data reconciliation completed

Give demand figures one definition.

Observed
Different public areas showed people and request figures without explaining how those measures related.
Recommended
Use an approved, dated source and explain the definition. Do not simply make two numbers match without reconciling the records.
Verify next
Compare the rendered summaries against an approved aggregate, including the measure and refresh date.
Finding 02Observed inconsistency · correction proposed

Keep county summaries consistent.

Observed
Galway waiting-time summaries differed between public routes. The review establishes the inconsistency, not the correct current waiting time.
Recommended
Use a common evidence source and date; qualify estimates and link to a reliable route when a current figure is not established.
Verify next
Recheck every repeated county summary. A content correction must not imply new plot availability.
Finding 03Structural issue

Make the route to main content predictable.

Observed
The sampled DOM did not consistently include a main landmark across the inspected templates.
Recommended
Provide a consistent main-content structure and a working skip link, preserving useful content order.
Verify next
Repeat structural and keyboard checks, and agree assistive-technology coverage in any wider evaluation.
Finding 04Observed rendering issue · correction proposed

Show a meaningful review date.

Observed
The Galway demand panel rendered “Updated undefined.”
Recommended
Render a valid approved date or an explicit unavailable-date message. Do not invent freshness.
Verify next
Check both a valid-date and a missing-date state.
04 / Delivery status

Keep the verbs accurate.

Completed

Public-page inspection, dated evidence and prioritised recommendations.

Not implemented

No Homegrown source changes or remediation outcomes are claimed in the source review.

05 / Next questions

What to investigate
with people next.

A later study could ask growers to explain what submitting a request means and hosts to explain when contact details are shared.

Understand usability testing ↗