Website study / An example for Garden studios
Fern & Frame
How do you turn “I want more space” into an informed project conversation?
A garden studio is a considered purchase with a long list of practical dependencies. The website should help someone move from an imagined working day to a plausible brief, without implying that a photograph settles planning, site access or technical feasibility.
- The buyer
- Explain the day
- The website
- Explore the fit
- The working side
- Prepare a project
Connection diagram · proposed system, not measured results
01 / Behind the website
The space has to suit a life and a site.
A buyer may begin with a feeling rather than a specification. The useful research question is how to support that early thinking while gradually introducing the constraints that make a project viable.
- 01
The future user
Wants a quieter place to work, make or unwind and may not yet know the right size or specification.
- 02
The shared decision-maker
Needs to understand the household trade-offs, likely disruption and what still needs checking.
- 03
The project reviewer
Needs intended use, location, access and constraints before assessing feasibility or arranging a survey.
The uncertainty to remove
The three use routes make a broad category easier to recognise in everyday language. We would test whether “Work”, “Make” and “Unwind” match buyers’ thinking rather than assuming that three choices are magically optimal.
Progressive detail can help a novice stay oriented, provided it does not withhold material information. Planning, permissions, site conditions and indicative cost dependencies should appear when they are relevant to the decision.
02 / Behind the website
Every visible choice should earn its place.
The green composition combines an aspirational studio with a practical plan. The design opportunity is to keep those layers connected so a visitor understands what can be imagined and what still needs investigation.
- 01
Begin with intended use
Work, making and relaxation are understandable starting points; the detailed brief would allow mixed uses rather than forcing a false category.
Check it: Ask participants to choose a starting route and explain whether their actual intended use fits.
- 02
Show the real dependencies
Available space, access and power are visible beneath the main image. Each can lead to a practical explanation and an honest “not sure yet” answer.
Check it: Give a scenario with restricted access and check whether the participant identifies it as something to discuss.
- 03
Use a plan to explain scale
A plan sketch can connect furniture, circulation and intended use without pretending to be a final site drawing.
Check it: Ask a visitor what the plan does and does not establish; record any belief that it is an approved specification.
Method behind these choices: How People Read Online: New and Old Findings (source, new tab).
03 / Behind the website
Understand the purchase and the project handover.
The website should help people discover fit, while the proposed private workspace helps the team investigate feasibility. Those are related tasks with different levels of certainty.
- Reconstruct recent enquiries
Ask prospective buyers what first triggered the idea, what they searched and which constraints they discovered late.
- Map the feasibility questions
Work with a knowledgeable project reviewer to separate early facts from questions requiring a site visit or specialist advice.
- Prototype the brief in stages
Try an intended-use route, a simple space explanation and a concise site questionnaire using plain language.
- Check comprehension and review value
Observe a buyer completing the brief and a reviewer using it. Look for both confusion and information that has been collected unnecessarily.
Three realistic tasks for a prototype
Explain the right starting route
Choose a route for the supplied mix of work and leisure needs.
Check that the visitor can still describe a mixed-use requirement.Identify a site constraint
Find what to do when garden access is narrow or power requirements are unknown.
Record whether the page encourages a responsible next step instead of false certainty.Prepare a useful first brief
Submit intended use, approximate space and known constraints from a fictional scenario.
Score completeness and distinguish missing knowledge from a confusing question.
What would make this an honest evaluation?
Do not reward the design merely for increasing submissions. A wave of poorly matched enquiries can create more work. Define what makes an enquiry sufficiently complete for the next review.
A staged test would compare brief completeness, misunderstanding and avoidable follow-up. Signed-project rates require a longer observation window and careful attention to seasonality, budget and site suitability.
Research practice: Using moderated usability testing (source, new tab).
04 / Behind the website
Original words. A reason for every page.
The strongest content would explain choices and constraints with the business’s own knowledge. It should help a visitor become better informed without turning a sales page into unqualified planning or construction advice.
| Question or search intent | Original page response | Evidence to gather first |
|---|---|---|
| “garden office for everyday work” | An intended-use guide covering practical needs and questions to explore. | Real configurations, working-day needs and technical review of factual claims. |
| “garden studio narrow access” | A clear explanation of why access matters and when the team must investigate. | Installation methods, access review process and verified limitations. |
| “garden room project steps” | A project journey that distinguishes initial enquiry, survey, proposal and agreement. | The operator’s actual responsibilities, dependencies and customer decisions. |
Search phrases would be checked against real demand and buyer wording, including location where the service is genuinely available. Each page would answer a distinct question rather than repeat one sales paragraph across towns.
Project visuals would be labelled at the correct stage: concept, indicative plan or agreed design. The writing would be reviewed whenever specifications or responsibilities change.
Search phrases here are research seeds, not verified search volumes, rankings or traffic forecasts. Keyword research would validate demand, location, language and competition before publication.
05 / Behind the website
Make the assumptions visible.
A long purchase journey should not be reduced to clicks. This model follows relevant visits through qualified enquiries and reviewed proposals to a signed project, with every rate conditional on the stage before it.
Change the assumptions
Trace a considered project funnel
The fictional figures help compare assumptions, not predict how many garden studios will sell.
Illustrative calculation · not a forecast
- Expected qualified enquiries
- 45
- Expected reviewed proposals
- 18
- Expected signed projects
- 3.6
The arithmetic, openly shown
Qualified enquiries = relevant visits × qualified rate ÷ 100Proposals = qualified enquiries × proposal rate ÷ 100Signed projects = proposals × signed rate ÷ 100
These are expected counts under invented stable rates. They do not account for time lag, staffing capacity, planning decisions, seasonality, cancellations or financial contribution. A fractional result is an average, not a partial building.
From an attractive calculation to a trustworthy decision
Use cohorts because an enquiry received this month might sign several months later. Comparing this month’s visits with this month’s signed projects can join unrelated buyers and produce a misleading rate.
Record why enquiries are not suitable, with a limited consistent taxonomy and appropriate retention. A better page might reduce unsuitable contacts while total submissions fall; that could still be useful if the agreed objective is a clearer project pipeline.
06 / Behind the website
A guided brief can become a controlled project workspace.
The optional software would keep uncertainty visible as the idea moves towards review. It would not replace technical judgement, site investigation or the relevant approvals.
- 01
Use and requirement builder
Capture the daily activity, approximate space and priorities without forcing a visitor to know a construction specification.
Information in: Use cases, people, desired features and uncertain answers.
Useful output: An editable first brief with explicit assumptions. - 02
Site information review
Organise permitted photographs and constraints for a named reviewer.
Information in: Access details, approximate dimensions and relevant site information.
Useful output: A completeness checklist and questions for follow-up. - 03
Proposal version history
Keep scope, options and assumptions together when the project changes.
Information in: Human-approved specifications, dependencies and commercial information.
Useful output: A traceable proposal rather than conflicting email attachments. - 04
Client decision workspace
Show outstanding choices and the meaning of each stage to the buyer.
Information in: Approved project status and decisions assigned to specific people.
Useful output: A simple shared view of what is known and what needs action.
Permissions, human decisions and things that can go wrong
Site images can reveal private homes and addresses. Uploads would need appropriate access restrictions, validation, retention and a clear purpose. Public examples would require permission and should not expose a customer’s location.
If a buyer changes the intended use or site dimensions, dependent decisions should be marked for review. No automated message should confirm planning compliance, structural suitability or a fixed installation date without the appropriate human approval.
Potential software only. These modules are not running behind the pictured website. Requirements, integrations, data protection, capacity, cost and support would be agreed before a real build.
07 / Behind the website
Evidence informs the idea. Testing earns confidence.
Research on visible choices and real user needs can inform this journey. It does not establish planning feasibility or a universal psychological trigger for a high-value home purchase.
- Define a qualified enquiry
Agree the minimum useful information and distinguish it from commercially attractive but unverified assumptions.
- Make uncertainty explicit
Check that “not known” answers survive into the team’s review rather than becoming default technical facts.
- Test the changing brief
Alter a key requirement and verify that the proposal and outstanding questions remain consistent.
Read the sources and the limits of each one
Learning about users and their needs (source, new tab)
Investigate users’ goals, current approach and difficulties. Treat untested internal opinions as assumptions.
Scope: Public-service research guidance includes people who use, provide and support a service.
Limit: Transferable practice guidance, not a B2B revenue experiment or a claim that research has already been conducted for these concepts.
How People Read Online: New and Old Findings (source, new tab)
People commonly scan for information, with reading depth varying by task, motivation, focus and person.
Scope: The publisher summarises eyetracking research spanning 13 years, more than 500 participants and over 750 hours.
Limit: Reading is not always shallow and no single scanning pattern fits every page. This is not a measured sales uplift for these concepts.
Memory Recognition and Recall in User Interfaces (source, new tab)
Visible choices and contextual cues can support recognition instead of asking people to recall information unaided.
Scope: A cognitive-psychology explanation applied to menus, search and interface content; published January 2024.
Limit: A design heuristic, not proof of universal behaviour or a specific conversion increase. Labels still need testing with the intended audience.
Using moderated usability testing (source, new tab)
Observe actual or likely users attempting believable tasks to reveal language, navigation and interaction problems.
Scope: Guidance covers recruitment, neutral task instructions, consistent discussion guides and accessible sessions.
Limit: Small qualitative tests expose contextual problems; they do not establish population conversion rates or commercial causation.
Creating helpful, reliable, people-first content (source, new tab)
Create original, useful content for an intended audience, drawing on genuine knowledge and clear sourcing; apply SEO to help that content be discovered.
Scope: Google’s published content self-assessment guidance, including purpose, originality, accuracy and trust.
Limit: Guidance is not a ranking guarantee. Length, exaggerated claims and copied summaries do not substitute for useful information.
SEO Starter Guide (source, new tab)
Write useful original content, anticipate the words different readers search for, and connect related pages with descriptive links.
Scope: Official introductory guidance on content, discoverability, images, search titles, snippets and site organisation.
Limit: Google does not guarantee indexing or first place. Search snippets may come from page text rather than the meta description; keyword repetition is not a sound strategy.
Involving Users in Evaluating Web Accessibility (source, new tab)
Working with disabled users reveals practical barriers; combine it with standards-based accessibility evaluation.
Scope: Guidance covers user evaluation, assistive technology, reporting scope and cautious interpretation of small studies.
Limit: User testing alone does not establish WCAG conformance, and a few participants cannot represent every disability or access need.
Web Vitals (source, new tab)
The published good-experience thresholds are LCP at most 2.5 seconds, INP at most 200 milliseconds and CLS at most 0.1.
Scope: Assess the 75th percentile of real page loads, separately for mobile and desktop, across all three Core Web Vitals.
Limit: These are performance targets, not measured results for the concepts. A laboratory result is diagnostic and is not equivalent to representative field data or a sales forecast.
Your business would have its own starting point
Start with what the customer wants their day to feel like.
Darren can help translate that everyday ambition into the questions, information and practical checks a real project would need.