Startup customer research in Albany needs a maintenance routine when the proposed service, audience or assumptions change. Keeping old notes is useful only if the team can tell what they describe and whether they remain relevant.
This scenario is wholly fictional. Iris is developing an imagined Albany appointment-based service, and Mal helps organise its research notes. They are planning a routine for maintaining evidence. No actual interviews, customer responses or business results are reported.
Iris starts with a decision rather than a survey
Iris wants the research file to help decide whether the service description needs revision. Her first instinct is to add a repeating survey to the calendar, but Mal asks which uncertainty the survey would investigate.
They instead give each research question a place in a working list. One proposed question concerns whether people can distinguish making an enquiry from receiving an appointment. The routine will begin by checking that list rather than collecting fresh responses simply because a date has arrived.
Mal gives the existing notes a clear status
The pair’s imagined file contains draft questions, assumptions and a proposed discussion guide. Mal separates those materials so that none can be mistaken for completed research. A planned conversation does not become evidence because it has a participant heading.
For later work, Iris would want to retain the question, method and relevant version beside any observations. business.gov.au’s research guidance recommends recording what was investigated, the methods, insights and actions. The pair uses that structure to organise a possible future record, without inventing findings to fill it.
A service change creates a review trigger
Iris considers offering appointments at a different kind of location. Mal points out that an earlier explanation of arrival would no longer describe the same service. They mark the related question for review rather than assuming previous material would still apply.
The trigger is the changed service arrangement, not a claim that customers now have different preferences. Iris keeps that distinction in the note: something in the offer changed, so the team must investigate whether its explanation still works.
They keep observations separate from their interpretation
Mal proposes two fields for any later research note: what was observed and what the team thinks it might mean. That would make it harder for a tentative interpretation to become an unqualified statement about Albany customers.
The pair refers to the UK Government’s user needs guidance, which emphasises evidence and the user’s actual problem. They use it as design guidance rather than local law. Their routine would ask whether each proposed need has support instead of presenting a preferred feature as a discovered requirement.
Iris limits what the record needs to hold
They discuss the difference between retaining useful context and collecting a detailed personal history. For their proposed enquiry-description exercise, unnecessary identifying information would not help explain whether the wording was understood.
Before conducting research, Iris would need an appropriate arrangement for participants, information handling and record access. The pair does not upload customer records or assume that replacing names makes existing material suitable for every use. Their maintenance plan includes checking what information is genuinely needed.
Mal assigns an owner to unresolved questions
A question can remain in a file indefinitely when everyone assumes someone else will investigate it. Mal proposes that each open question identify who will decide its next step and what decision it relates to.
Iris would handle questions about the service offer; another appropriate person might need to advise on a specialist issue. The record would distinguish customer research from requirements that cannot be resolved by asking whether someone likes the idea.
They plan a brief review rather than a fresh study every time
The proposed review asks whether the service, intended audience or important evidence has changed. A new study would follow only when a relevant question needs investigation and the method is suitable.
The working review note would cover:
- The decision the research is intended to support.
- The current status of the question and supporting material.
- Any change that could make earlier evidence less relevant.
- The next action, responsible person and reason for it.
A review could therefore end with no new study, provided the reason is recorded honestly.
Iris preserves earlier versions without confusing them
If the description changes, Iris would keep the relationship between the old draft and the material used to assess it. Mal suggests marking superseded notes clearly rather than deleting context or quietly applying old observations to a new offer.
They also plan to avoid repeatedly sharing copies across unrelated folders. The aim is a record people can follow, with an understood current version, not a larger archive whose apparent size suggests more evidence than it contains.
The routine ends with a bounded next action
Iris and Mal finish their fictional planning session with an open question about the enquiry wording and a proposed method to investigate it. They have not established demand, completed a trial or proved that the service should launch.
Their maintenance routine supports that next decision: keep the evidence understandable, revisit it when circumstances change and distinguish what is known from what remains to be learned.