The Question to Ask First

Most arguments in this subject are arguments about which module is at fault. One question moves past that.

The question

Which boundary does this cross?

Ask it of any wrong figure, any failed report, any proposal.

What the answers mean

"None — it is inside scheduling." A module problem, and the module's own subject covers it.

"Scheduling and time capture." The exception process, the tolerance, or an unrecorded swap.

"Time capture and payroll." Rule ownership, the interface, or the cut-off.

"Absence and everything else." The day-to-hours conversion, or a path that was never wired.

"All of them." Identity or reference data, which sit underneath all four.

That last answer is the commonest and is the one people reach last.

Why it works

It replaces "whose fault is it" with "where is it", which is answerable and which nobody has to defend.

It routes the investigation immediately instead of through three departments in sequence.

And it identifies the pattern: three problems at the same boundary in a quarter is a boundary to rebuild, not three incidents to correct.

The second question

Who is accountable for that boundary?

If the answer is a name, the investigation has an owner.

If the answer is a meeting, you have found the actual problem, and it is the one the note on ownership is about.

Using both

The first locates the fault.

The second determines whether it will be fixed or corrected repeatedly.

Neither requires buying anything, and both are harder to answer than any question a vendor will ask you.

The collection in one line

Master identity and reference data once, write down which system owns which rule, reconcile the boundaries monthly, and give the chain an owner.

Everything else here is the detail of doing that.

Three at the same boundary is a rebuild

The pattern worth watching.

Individual incidents get corrected; patterns get fixed.

Three problems at the same join in a quarter means the join is wrong, not that three unfortunate things happened.

Keep the record of causes from the reconciliation, because that is what makes the pattern visible at all.

A practical configuration prompt

During configuration, use how the product works to prompt questions about identifiers, ownership and output. Treat the page as a starting point and document each assumption.