Illustrative field case; no visit, business, or customer is being described. Picture a property-maintenance job marked complete by a technician. The office still needs to decide whether the record is ready for its next step. That gap is a research question, not a software opportunity yet.
Agree on the observation before opening the notebook
Do not pose as a customer, applicant, employee, or community member to gain access. Ask for an organized research session. Explain the purpose, what you want to observe, what you will record, how notes will be used, who may see them, how long you will keep them, and how the participant can withdraw.
The GOV.UK Service Manual guidance on research consent recommends covering those points and documenting consent. Its privacy guidance also calls for limiting and protecting participant data. Treat that as a practical safety baseline, not universal legal advice. Check the rules that apply to the people, data, and jurisdiction involved.
Put in scope
- One start event and one end event.
- The roles, artifacts, decisions, and permitted exceptions needed to answer the research question.
- Redacted or synthetic examples where real records are unnecessary.
Keep out of scope
- Names, contact details, addresses, client content, photos, amounts, and identifiers you do not need.
- Screen copies, recordings, or documents without explicit authorization.
- Any public example until publication rights and redaction are clear.
If consent is unclear, the observation stops. A founder’s curiosity does not outrank someone else’s privacy or a business’s confidentiality.
Take notes in time order
A clean process diagram drawn from memory hides the useful bits: the wait, the message outside the main system, the record that needs rechecking. Start with a blank chronological log and let the operator’s sequence replace your assumptions.
| Time or order | Actor | Action | Input | Output | Decision / next owner |
|---|---|---|---|---|---|
| _____ | _____ | What happened, without interpretation | Permitted record or signal | New or changed artifact | Who decides what happens next? |
| _____ | _____ | _____ | _____ | _____ | _____ |
| _____ | _____ | _____ | _____ | _____ | _____ |
Ask open, neutral questions about a real example: “What happened next?” “Which record did you check?” “Who could move it forward?” “Can you show the structure with sensitive details removed?” The GOV.UK guidance on in-depth interviews recommends real examples and neutral prompts. It does not make one account representative of a trade.
An illustrative closeout prompt, not an observed process
The rows below are possible prompts for a property-maintenance closeout session. They do not claim that firms use these steps or use them in this order.
| Possible moment | Ask to locate | Question |
|---|---|---|
| Field work ends | The status or record the technician changes | What tells the next person that work is ready for review? |
| Office review begins | The artifact used to decide whether the record can move | Which missing item, if any, blocks the next decision? |
| An exception appears | The request, owner, and return path | Who resolves it, and where does the updated state become visible? |
| Billing or approval continues | The reference needed by the next role | Which closeout fact matters to that decision? |
Official product documentation can help you prepare vocabulary. Jobber documents jobs, visits, statuses, scheduling, notes or attachments, and invoicing-related states in its Job Basics page. Housecall Pro documents an estimate-to-job-to-invoice/payment flow in its training material. Those pages tell you what the products document. They do not tell you how the business in front of you works.
Draw the expected path and one exception path
First draw what the participant says should happen. Then reconstruct one authorized exception. The second map may loop, branch, or leave the main system. Do not call that a “pain point” yet.
| Exception log | Question to answer |
|---|---|
| Trigger | What made the expected path stop or change? |
| Detection | Who noticed, and in which record or conversation? |
| Temporary action | What did the person do next? |
| Decision owner | Who could accept, reject or escalate the result? |
| Return path | How did the work rejoin the normal process, if it did? |
| Unknown | What was not shown, remembered or authorized? |
Do not invent frequency, delay cost, hours lost, or money held. Record only the consequence the permitted evidence supports. If the person cannot show or recall it, leave the field blank.
Four columns prevent a fictional field insight
| Column | What belongs there | Example |
|---|---|---|
| Participant’s words | A consent-safe paraphrase or authorized quote. | “The coordinator checks the record before the next step.” |
| Observation | What the researcher directly saw in the authorized session. | A status changed after a missing field was added. |
| Hypothesis | Your explanation, clearly marked as yours. | The handoff may fail because required items are not visible together. |
| Product question | A bounded question the evidence now permits. | Would an exception list support the coordinator’s decision without changing the source system? |
The distinction also matters when notes leave the room. GOV.UK’s notes and recording guidance recommends separating observation from interpretation and obtaining agreement before recording. Remove personal and confidential details before any wider use.
Make the wedge earn its boundary
Suppose the research produces this hypothesis: a closeout-readiness list could show which jobs lack a required item and who owns the next action. Do not jump from that sentence to a reminder platform.
| Boundary | Decision to make | Reject the wedge when |
|---|---|---|
| Source | Which existing record is permitted and reliable enough to read? | The useful state exists only in inaccessible or inconsistent material. |
| Decision | Does the product flag a missing item, or judge whether evidence is acceptable? | The promised result quietly requires human expertise you cannot bound. |
| Action | Does it report the next owner, draft a reminder, or change a status? | The action requires permissions or consent the first version cannot support. |
| Service | Who handles records that do not fit the expected contract? | Every case becomes custom investigation. |
Do not build a vertical CRM, automatic reminders, mobile capture, accounting sync, AI evidence review, or a dashboard of invented delay costs. One authorized cycle can sharpen a hypothesis. It cannot establish a market, a recurring frequency, or a pattern across trades.
Accept, narrow, or reject this handoff
Accept the wedge only when an authorized observation identifies a stable source, a real decision owner, and an output that changes the next action. Narrow it when the useful result requires less automation than you expected. Reject it when access is inappropriate, the exception is all judgment, or the current process works well enough. Then stop. Evidence from one trade does not transfer to another.