Audit Log
Venminder
My Role:
- Primary Designer
- Research
- Wireframes
- High Fidelity Design
- Prototyping
- User Testing
Tools:
- Balsamiq
- Visual Studio
- Zoom
Team:
- Designer
- Product Manager
- 3 Back-end Devs
- 1 Front end Dev
- 1 QA person
Challenge:
In response to consistent demand, a feature of great importance has been recognized. Client admins are now expressing the need for the capacity to identify and monitor the users responsible for edits within the Venminder app.
Goals:
- Allow administrators to investigate who made changes within the Venminder app and when.
- Search and filter results.
- Column sort.
- Download results.
- Set alerts based on actions.
Process Summary:
-
Discovery
- Discuss vision and direction with product manager
- Stakeholder interviews
- Identify personas
- Evaluation of existing product and processes
- Gather and review feedback from customers
- Story mapping
-
Ideation
- Sketch ideas on paper
- Low fidelity wireframes in Balsamiq
- Internal Reviews, design iterations
- High fidelity mockups using HTML prototype
- External reviews with select CAB (client advisory board) members
- Internal user stories, Size project
-
Validation
- User testing with internal teams
- Pilot testing with select CAB members
- Post launch interviews with CAB members
Discovery:
Stakeholder interviews
What we learned
- All add, edits and deletes need to be auditable.
- Audit entry needs to be made for each change, as a separate entry.
- Audit entry should include user name, date/time of edit, changes made from/to.
- User access to make changes is permission based using the admin panel.
- Changes currently tracked by spreadsheet and emails.
- Stakeholders should have access to view and search audit logs.
- Ability to set alerts that notify someone that changes were made to a critical vendor.
- Most clients mentioned vendor and product profiles as a major issue.
Filter Exercise:
Filter Exercise: Working it out for future releases.
We needed to work out and document the areas of the site to be included in the audit log, and expanding the filters for future releases.
- First release the action menu was not available.
-
Filters Release 1:
- Vendor/Product: Includes ALL products for the vendor.
- Area: Includes ALL actions for selected area.
- Filters Future Release:
-
Option 1
- Vendor: Select the vendor, which includes ALL products for that vendor, same as release 1.
- Area: Select area of the site for audit.
- Action: This selection based on the area selected.
-
Option 2
- Vendor: Select the vendor to audit changes.
- Product: Based on vendor selected.
- Area: Select area of the site for audit.
- Action: This selection based on the area selected.
Ideation:
Wireframes: Balsamiq
Audit Log: First release covered just the log tab with changes made to the vendor/product profiles.
Audit Log: Downlads and Alerts would be in later releases.
