Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve Add FY Budget for CANs #3350

Open
6 tasks
kimschulke opened this issue Jan 23, 2025 · 1 comment
Open
6 tasks

Improve Add FY Budget for CANs #3350

kimschulke opened this issue Jan 23, 2025 · 1 comment
Assignees
Labels
design-debt something we need to go back to and change or update improvement UX task UX-team related tasks and to-dos

Comments

@kimschulke
Copy link
Contributor

kimschulke commented Jan 23, 2025

Goals

  • Make it more clear that the "previous FY carry forward" displayed in the grey box is a suggestion (the amount unspent/available from last FY) and it's not automatically added into the budget
  • Improve the interactions for adding the FY budget for the first time and editing it there after
  • Add an option to reset the budget back to TBD OR
  • Enable the user to enter $0 as a valid FY Budget
  • Review quotes below for additional changes or improvements

UX Tasks

  • Explore options to improve the design
  • Review/discuss options with the team
  • Review/discuss options with OPRE
  • Refine design based on feedback

Dev Tasks

  • Update frontend based on designs
  • TBD

Additional Context

Resources

@kimschulke kimschulke added design-debt something we need to go back to and change or update improvement UX task UX-team related tasks and to-dos labels Jan 23, 2025
@kimschulke
Copy link
Contributor Author

kimschulke commented Jan 23, 2025

Previous FY Carry Forward Card

“If its carry forward, adding money should be additive. If it’s last year budget, it shouldn’t be additive. Its last years budget, not least years carry forward”
“You’re using the wrong label. What this should say is Previous FY, no carry forward, its not a carry forward”

Possible improvements

  • Change “Previous FY Carry Forward” to “Last FY Available Budget (unspent)” or something similar
  • Sheila does not think of last years available budget as carry forward until its been manually entered as such, so presenting the suggestion of "previous FY carry forward" is not coming through as a suggestion

Fake data

“We’re getting to the point where we need to use real data in this otherwise I can’t tell you if its working properly”
“Its hard for me to get past the fake data at this stage in the game”

Possible improvements

  • Less demo, more real life experience in the app!

Add FY Budget Button Label
Sometimes they add $ to the FY budget so the word “Add FY Budget” is a little confusing if it’s not additive from what was entered previously.

Possible improvements

  • After input is entered into the component, change the button to “update” so it doesn’t look additive to the original amount
  • Or change the button from “add” to “enter”

Interactions on Add FY Budget

“In that box where it says $4 million (FY25 CAN Budget) delete the 1st 0.. oh so even though its there, you cannot edit it”
“Even though I see $5million, that is not a figure that I can edit? [frank explains its a placeholder value]
“I want to be able to edit the $5 million and be able to make it $5 million and $47…I want it to be minimal effort. So if the $5 million could be there and I could simply edit that, that would be best”
“I want to put in a # and every time I come in after I want that # there so I can edit it”

Possible improvements

  • Agreed! This matches the best practice for user input into components
  • Sheila was expecting the placeholder input in the FY25 CAN Budget component to be editable, but its not
  • Possible solution might be to get rid of any “placeholder text” and retain whatever the user enters and make it editable (just like our other components work on edit agreement. User input always stays where they input it
  • Then “Add FY Budget” button would change to “Update FY Budget” button after an initial value is entered

$0 as a valid amount

"you cant enter in $0? oh.. well might need to think that one through"
"what if I put $5million into the wrong CAN? How do I get rid of that $ 5million?"
"we need $0 as an option, negative # never"

Possible improvements

  • Enable $0 as a valid input

Display Last FY Budget for 1 Year CANs

"if its a 1 year CAN, I would like it to say Last FYs Budget"

Possible improvements

  • Display a card for 1 year CANs that says "Last FYs Budget"
  • Make sure instructions get edited as needed to match this new component being here
  • Could make 1 card that shows in both 1 year and 5 year CANs, show what the FY Budget was Last FY and if there is anything left over/available/unspent

Re-setting the budget

"[in regards to TBD as an unspecified budget} thats perfect.. thats perfect..I'm fine with that"
"$0 is the same as no budget, I just need a way to get it back to no budget [undo if something is entered incorrectly]"

Possible improvements

  • Leave as is and they can temporarily enter $0 for anything they need to undo or remove or add a reset button back to TBD

Future Improvements on adding/subtracting specific amounts

"in the future, I'd like to be able to enter the change budget #. Minus $350k or add $275k, so I don't have to do the math outside, but thats down the road. For now, we'll do math. That will come when we do the recoveries [de-obligations] and thats when it will be important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design-debt something we need to go back to and change or update improvement UX task UX-team related tasks and to-dos
Projects
None yet
Development

No branches or pull requests

3 participants