Open Benbaillou opened 2 years ago
New Jordan's feature Hi @gigicobos, @entrotech @fancyham - Here is the created issue for the Jordan's new feature suggestion => automate the status of the organizations after a certain amount of time. ex: "Approved" => "Needs verification" after 6 months
Please let us know your comments.
@souronion - here is an issue I created. I would love your design comments on this one.
I made a note on Figma based on Github issue #1150. https://www.figma.com/file/9hPmNSsyaH2VMGNz5mffmI/Suggestions-Admin?node-id=640%3A106
Green color comments are my questions and I’d like to clarify. Especially this section.
Questions
Should we create 3 steps - Why => because some organizations may include more exceptions than the one above that need a manual check 1.1 The organisation is identified as "To be changed to Needs Verification" 1.2 The admin volunteers are notified of the status to be changed for the organizations 1.3 The admin volunteers can manually confirm the need for status changing or amend the need
Should we stretch the automation to "Submitted" status - why => it looks like some organizations have been submitted for verification for more than a year.
Hi all — Could you describe Jordan’s exact goals and (if possible) how it might translate into the filter criteria for an organization search?
For example, it’s unclear to me what the ‘exception for 12 month old permanently closed’ rule would do for Jordan and how it translates into an if-then or search criteria statement?
Gotta translate Jordan’s ‘business rules’ into computer logic, so first to understand exactly what he’s trying to do, how he does it now, and then we can see how to translate that into designs and code.
If possible, could you write the rule logic super-explicitly (which will also identify where we have gaps in understanding what he needs)
For example, something like:
I think that would help us be really specific about what needs to be built.. start with the human rules then we can move to the logic.
Also, something to consider is perhaps a solution would be building a single report table with these three rules as pre-canned filters… Then the admin can press a button to enter the search criteria, get the list of matching orgs, and then batch change them manually to ‘needs verification’?
That might allow us to reuse existing code, rather than building customized stuff where the logic is hidden away inside the program.
Also, side thought: Please consider putting all our sketches into the main Figma document, so it’s not easily lost and it’s perhaps easier for collaboration?
What I think I’m reading is:
Jordan needs to: A. Re-validate ‘permanently closed’ places every 12 months or so to make sure they’re still permanently closed B. Re-validate ’temporarily closed’ places every 2 months to see if they’ve reopened C. Re-validate all other places every 6 months to ensure their info is up-to-date.
Is that right?
If that’s the case, I think group A would be an enormous list and I’d suggest double-checking that rule. If a listing is permanently closed, why re-check it?
Thank you @fancyham. I read your comments and these are great insights. I will move the sketch to the main Figma document.
It would be good to meet with Jordan and learn his goal. So we understand his goal and solve the right problems. I still try to understand the requirements.
Thanks @fancyham for your comments
Your understanding for group A, B and C is correct. The exceptions for permanently (A) and temporarily (B) closed means that those organisations will not be checked after 6 months, but after 12 and 2 months respectively.
Best would be to schedule a call with Jordan indeed.
Action
From our meeting:
Seems like Jordan may really be looking for a ‘last published date’ which currently doesn’t exist (‘accepted date’ gets erased when org is changed to ‘needs verification’ so is not useful for his purposes).
A ‘last published date’ can be calculated using records in the database from multiple fields. If that field is added to the table and in the criteria/filter dialog, Jordan can sort by that date. (Still probably useful to have shortcuts for things like “older than 12 months” or “older than 2 months” so filter shortcuts/buttons may still be useful)
@Benbaillou, @fancyham, @entrotech Created 3 key screens based on the last meeting discussion. https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=4525%3A8835
Questions
Key screens are updated. https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=4675%3A8847
I need to talk to Jordan to get feedback.
Adding screenshot of design for easy reference:
@fancyham, Thanks! I will attach screenshots next time!
Script for Feedback Session with Jordan https://docs.google.com/document/d/1509JrScM7dA-QhCEWiL0X1Ds-mAjzzV6H-3BZmgfXmQ/edit?usp=sharing
Attendees: Jordan, Seiko, John, Bryan This session is recorded: https://drive.google.com/file/d/1-2-wv_7WIRMIA1D-T4h4UYelb_2FC5bd/view?usp=sharing
What is Jordan really looking for? He wants full automation. When the time comes, the Approved status changes to Needs verification automatically.
Clarify how often status is verified
Jordan’s current workflow Video: around 12:30 https://drive.google.com/file/d/1-2-wv_7WIRMIA1D-T4h4UYelb_2FC5bd/view?usp=sharing Figma: https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=4819%3A8996
We are going to build this in stages instead of going to full automation right away. We have some concerns about full automation. For example, it is difficult for a user to undo a mistaken action. Also, the admin user doesn’t have much control.
Why are we going to build this automation in stages?
Stages:
I took screenshots from the video and made Jordan's current workflow. We can save around 17 clicks for one organization by automating uncheck confirmed checkeboxes. https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=4819%3A899
Meeting Note: March 17, 2022 @entrotech, @sei1122, @fancyham
Next Steps: Dev team starts development: Confirmed checks should be automatically unchecked when changing the status from Approved to Needs verification.
Seiko: start designing control panel for volunteer admin
Meeting note: April 20, 2022 Preset filter and the edit screen designs
https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=5110%3A907
2
Preset filter edit screen design iterations. @fancyham
https://www.figma.com/file/D3oq9QOXl0rFkwrEUJbABs/FOLA-Design-System?node-id=5136%3A9285
Created Issue #1228 to implement the "Stage 1" step in the issue description above.
Meeting note July 28: When we finish developing the published date column on the Verification admin table, We schedule a meeting with Jordan. We'd like to ask
@entrotech Ready for dev tasks!
Added John as assignee as this is ready for Dev work.
@entrotech Following up on this, as it was approved for dev tasks by Rylan 3 weeks ago. Is this in your pipeline to proceed on with the dev team?
Moving to PM board Backlog, to discuss how the Admin Panel functions now and if any further development is needed.
Overview
Project team: PM: @Benbaillou Eng: @entrotech Design: @fancyham UXR: TBD
Type of project: New feature
What User Problem are we solving? Currently, Admin volunteers manually select the organisations that were "Approved" to move them to "Needs Verification". They face the problems of
Lowering the quality of the data displayed on the map
What are we building? We are building a feature that automatically changes the status of the organisations from " Approved" to "Needs verification" in the administration panel: When the admin volunteer connects to the admin panel, he can see which organisations need to be updated from " Approved" to "Needs verification" status.
Notes:
Source of the solutions User interview with Jordan Smith (LA Work) 12 Jan 2022
Questions
What a success looks like - What are our Goals? (TBD)
We want to increase the accuracy of our data A metric could be to measure the number of organisations with a "Approved" status of > or < 6 months A success could be to have x number of organisations with " Approved" status < 6 months
Action Items
Resources/Instructions
Admin Panel => Status highlight
Admin Panel => Date of approval
Organisation details => Closing status