Field note: A technically elegant instrument can fail if it arrives at the wrong time, repeats information, requires unreliable connectivity, or offers no visible benefit to the people providing data. Feasibility is part of research quality.
Operational question
What is the minimum information needed for the decision, and where can it be captured accurately without disrupting safe operations?
A workable method
- Build a question-to-field map. For every item, identify the research question it supports, the planned analysis, and the action a result could influence. Remove fields with no clear use.
- Select the best workflow moment. Capture data when the event is fresh and the required evidence is available. Avoid adding a separate process when a trusted operational record already exists.
- Prototype with intended users. Observe completion under realistic time, device, lighting, language, and connectivity conditions. Ask what participants believe each question means.
- Return value and monitor quality. Show how information is used, provide useful summaries, and monitor missingness, straight-line responses, timing, and site variation.
What this looks like in practice
Instead of a long end-of-month training survey, a vessel team records a two-minute structured debrief after a scheduled drill, with optional voice notes synced when connectivity permits and a monthly feedback summary returned to the crew.
Evidence to collect
Choose a small set of measures before implementation. Record the baseline, the source of each measure, the review cadence, and who is authorized to act on the result.
- completion and missingness by site and role
- median completion time and reported burden
- evidence that collected fields inform a real decision
Field checklist
- Write the decision, accountable owner, and decision date.
- Describe the current workflow and the conditions that shape performance.
- Confirm the source hierarchy, permissions, and local requirements.
- Test the method under representative—not merely convenient—conditions.
- Review both intended outcomes and burden on the people doing the work.
- Record a change, escalation, and stop rule before results arrive.
Watch-out
Do not collect identifiable or sensitive information merely because it may be useful later. Apply data minimization, clarify consent and authority, limit access, and define retention before collection.