← BackReference (opens in a new tab)

The partial import

A bulk operation succeeds for most records and fails for some. · PM Drills · 30 · 30 sec–2 min

The partial import · 30 sec–2 min

Situation

Ninety of one hundred records import successfully.

The interface shows a generic error. The user uploads the file again and duplicates the successful records.

Think before scrolling

What behavior should the product promise?

Define partial success, retry scope, duplicate protection, and recovery information.

How a strong PM thinks

Make the result specific and recoverable.

Show which records succeeded and which failed, with actionable reasons. Preserve the failed subset for correction and make retries safe. Decide with engineering whether the operation should be atomic or allow partial completion.

The interface cannot repair unclear backend semantics. Acceptance criteria should cover the confirmed result and the next permitted action, not just the initial upload.

Takeaway

Partial success is a first-class state.

Users need enough detail to recover without repeating work that already happened.