Aglet

What to learn from a confusing import workflow

The durable lesson from import confusion is a small, explicit contract for input, mapping, validation, persistence, and recovery. Preserve the distinction between a supported local workflow and an unbuilt provider connection so onboarding content remains useful and truthful as the product evolves.

Keep the lesson for the next incident

  1. Write the input contract

    Document supported source shape, required fields, normalization, duplicate behavior, partial outcomes, and the action that confirms a mapping. State unsupported sources clearly and explain what the result page can and cannot prove about saved data.

  2. Keep mapping fixtures

    Save synthetic fixtures for valid, empty, malformed, duplicate, mixed-validity, interrupted, and retry states. Assert preview, destination fields, durable outcome, and result copy. Attach fixtures to the work record without retaining customer exports or credentials.

  3. Define recurrence signals

    Reopen review when preview and saved fields diverge, duplicate handling changes, a partial result becomes ambiguous, or copy implies a source is supported when it is not. Record fixture size and provider-observation limits and assign an owner for each boundary.

What to carry forward

Close learning with the supported input and mapping contract, deterministic fixtures, clear unsupported boundaries, and recurrence triggers. The library should make future import review faster without turning an unverified expectation into a product promise for future reviews.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow