Skip to content

ON Feedback - 2025-06-26

TL;DR

Strong validation of batch upload prototype. Amanda confirmed it's "exactly what we needed" and appreciated the visual distinction between uploaded vs ML data. Key request: ability to edit invalid rows directly in UI rather than re-downloading.

Overall Sentiment
Direction validated Yes
Stage shown Prototype (pre-build)
Ready for next stage Yes
Blocker for them? No

Source

  • Transcript: 2025-06-26-batch-upload-forecast-settings.md
  • Date: 2025-06-26
  • Participants: Amanda Mitt (Treasury), Rodrigo Cabrera (Treasury), Yulia Ershova (Treasury)
  • Context: Prototype walkthrough session - Emma presented UI mockups for feedback

This Iteration: Validation

What they validated about the current design:

  • Column mapping with AI - "I think it's exactly what we were... the need we had"
  • Visual distinction for uploaded data - "I like how it would be easy to track what was manually... via spreadsheet"
  • Duplicate detection - "The duplicate I think it's helpful as well"
  • One category per file - "For us it's easy this way... we have one with talent, that's payroll, one with tax"
  • Download invalid rows - Accepted as workflow for fixing and re-uploading

Important Nuances

  • Duplicate detection currently only compares against other manual entries, NOT against ML predictions. Amanda asked about this - flagged as future consideration.
  • "ASAP" dates in their files need special handling - could default to next Thursday (payment run day)

Future Iterations: Suggestions

High Value

  • Edit invalid rows directly in UI - "That would be nice if you could just already fix it immediately" rather than download/fix/re-upload

Medium Value

  • Auto-detect category from file - Currently requires user to select category; future could infer from content
  • Compare uploads against ML predictions - Flag duplicates where ML already predicted similar amount/date

Longer Term

  • Integration with Google Sheets directly - Their tax/talent trackers are Google Sheets, not downloaded files

Questions Asked

  • "Are we able to see [duplicates] in case there's any historical similar payments coming from the AI?" → No, only compares manual entries for now

Raw Feedback Quotes

"I think it's exactly what we were... the need we had right. And I like how it would be easy to track what was manually kind of... via spreadsheet. Yeah, looks exactly what we needed." - Amanda Mitt

"The duplicate I think it's helpful as well in case there's... any historical similar payments coming on from the model from the AI. Are we able to see it in that case? No, right." - Amanda Mitt

"For us it's easy this way, right, Rodrigo, because we have like the different forecasts, we don't have like a mix of categories. Usually we have one with talent, that's payroll, one with tax." - Amanda Mitt

Action Items

  • [ ] Consider UI for editing invalid rows directly during upload
  • [ ] Flag duplicate detection against ML as future enhancement