Tell us what is difficult today
Describe the activity that currently takes too much explanation or causes confusion. It might involve recording a trial, finding the right item, comparing observations, or sharing a set of records. Explain who encounters the issue and what the team needs to decide next.
A description is enough for the first message. There is no need to attach a research dataset, private participant information, instrument credentials, or confidential project files. Suitable handling arrangements can be discussed before material is shared.
Agree the scope and inputs
A proposal should name the activities, outputs, exclusions, client inputs, reviews, responsibilities, timing, and commercial terms. It should distinguish research and interface prototyping from production software implementation. Confirm access to domain knowledge and existing documentation rather than assuming it will be available.
The team may need to decide what a field means or which role can confirm a record’s status. Those are not merely implementation details. Identify the people responsible for resolving them so a prototype does not fill important gaps with guesses.
Use reviews to refine the question
A concrete record or interface often reveals that the original problem was described too broadly. The team may discover that the main difficulty is identity, missing context, or an unclear review responsibility. Review points provide a place to decide what the next activity should address.
New questions should be prioritized and agreed rather than silently expanding the work. Changes affecting deliverables, responsibilities, or timing need a recorded scope update. A narrower prototype that examines the important uncertainty can be more useful than a larger demonstration with undefined behavior.
Close with a usable transfer
A completed contribution should identify delivered versions, example materials, decisions made, limitations, and unresolved work. The client should know which outputs can inform an implementation brief and which are exploratory concepts.
Ownership, confidentiality, permitted use, retention, and ongoing support require appropriate written agreement. Availability, price, and schedule depend on the actual engagement. An email inquiry begins a conversation and does not commission a system or create a delivery commitment.
