# What job should your business records do?

Design business records around the decisions and handoffs they support. Help colleagues find the current agreement, source and next action when needed.

By Daltn editorial team. Published 2026-11-01.
Canonical: https://daltn.tech/feeds/jobs-to-be-done-business-records/

## What should business records help your team do?

Business records should help another person make the next decision or continue the work accurately. Test whether they can find the customer, source, current agreement and next action without reconstructing every conversation. Keep fast capture where it helps, then connect important details to the relevant job so the handoff remains clear.

## Keep these in mind

- Investigate the situation that caused a person to reach for a tool.
- Preserve useful habits while fixing the failure that matters.
- Measure whether the owner can complete the real job, not just fill a new database.

## Start with the last time the problem happened

An owner may say they need a CRM. Ask what happened most recently that made them say it. Perhaps a customer asked what had been agreed while the salesperson was absent.

The answer was split between a voice note and a revised quote.

The [Christensen Institute’s Jobs to Be Done explanation](https://www.christenseninstitute.org/theory/jobs-to-be-done/) focuses on progress in particular circumstances. For record-keeping, those circumstances are more useful than a broad label such as small-business owner. A shopkeeper handling a queue faces a different situation from a consultant preparing a quarterly review.

Do not begin by asking whether the person likes a proposed feature. Reconstruct the event first: what triggered it, what they tried, what worried them and how they knew they were finished.

## Translate tools into practical jobs

A notebook can be fast to use during a call. A chat can preserve the original customer wording. A spreadsheet can make a balance easy to calculate.

Each may do one part well while making retrieval or handoff difficult.

Situation | Progress the owner wants | Test for a new workflow
--- | --- | ---
Customer calls unexpectedly | Answer what was promised | Can the correct agreement be found quickly?
Owner leaves the shop | Let a colleague continue | Can the colleague identify the next step?
Customer disputes an amount | Explain the balance | Can records and adjustments be traced?
Work changes during the day | Avoid losing the amendment | Can people see the approved revision?

## An illustrative interview about a notebook

An owner records orders in a pocket notebook because customers often call while the owner walks around the workshop. Entering a long form at that moment is unrealistic. The notebook’s speed is a benefit that a replacement must respect.

The failure appears later when a colleague cannot read an abbreviated note. They cannot tell whether Friday means delivery or payment. The job for the replacement is to capture quickly and resolve the important ambiguity before someone acts.

Simply turning the notebook into a longer digital form may make the owner abandon it.

The Institute’s [three critical considerations graphic](https://www.christenseninstitute.org/wp-content/uploads/2024/05/JTBD-3-considerations-graphic.pdf) also highlights functional, social and emotional dimensions. In this example, confidence that a colleague can continue may matter alongside retrieval speed.

## Test one scenario with real constraints

Choose a common event and run it through the current and proposed workflow. Keep the input realistic: incomplete customer wording, background noise or a changed date. Ask the user to explain the output in their own words.

1. Interview a few people about a recent specific record-keeping problem.
1. Write the triggering situation and desired progress in one sentence.
1. Identify what the current workaround does well.
1. Test a narrow alternative using realistic information and interruptions.
1. Check retrieval, handoff and correction, not just successful capture.

## Make the result easy to judge

For a delivery amendment, test whether the next person can find the approved address and its related order. For a payment promise, it is whether the amount, expected date and verification state remain clear.

Test the record with someone who did not handle the original conversation. Can they find the source, identify the customer or order, and explain the next step? Try text, a document and a voice note if those are common inputs.

The format matters less than whether the next person can continue accurately without reconstructing the entire history.

Avoid treating every interview as a market-size estimate. Qualitative stories help explain behavior and design tests. They do not prove how many customers will buy or what every industry needs.

## Common questions

### How can we tell whether a business record is useful?

Ask whether another person can make the next decision or continue the job using it. They should find the customer, source, current agreement and next action without reconstructing every previous conversation.

### Should fast capture replace structured records?

Use each where it helps. A quick note preserves a detail while work moves. Connect important commitments to the relevant customer or job, then test the handoff before choosing a format.

## Sources

- [Jobs to Be Done Theory, Christensen Institute](https://www.christenseninstitute.org/theory/jobs-to-be-done/): Supports progress-in-circumstances as the central concept.
- [Three critical must-knows about Jobs to Be Done, Christensen Institute](https://www.christenseninstitute.org/wp-content/uploads/2024/05/JTBD-3-considerations-graphic.pdf): Supports attention to functional, social and emotional factors.