Feedback items
Paste into a team channel
How the rows are built
- Each row is one mismatch type from the scorecard, plus one row for disputed rep records.
- Loads affected counts distinct loads, and rows are sorted by it.
- Who fixes it is a fixed choice per type: setup problems go to deployment config, extraction gaps go to Product and Engineering, and a wrong rep record goes back to the customer's data.
- A pattern blocks go-live for a shipper that is not ready when the pattern repeats there or the shipper is under the bar.
- Disputed records never block go-live, because disputed fields are left out of the match rate.
One question
How does feedback from deployments reach Product today?