| 1 | Backups Were Not Tested | 21 |
| 2 | Branding Overshadowed Usability | 11 |
| 3 | Counselling on Wound Care | 10 |
| 4 | Documentation Became Outdated Quickly | 6 |
| 5 | Demanding Clients, led to delayed deal | 3 |
| 6 | Code Conflicts and Unmanageable Collaboration | 3 |
| 7 | Incomplete Stakeholder Engagement | 2 |
| 8 | Training Skipped for Non-Technical Staff | 1 |
| 9 | Misconfigured Roles and Permissions | 0 |
| 10 | Monitoring Was Passive | 0 |
| 11 | Soft Launch Feedback Was Ignored | 0 |
| 12 | Metadata Harvesting Failed | 0 |
| 13 | No Fixity Checks in Place | 0 |
| 14 | QC Introduced Too Late | 0 |
| 15 | Submission Steps Too Complex | 0 |
| 16 | Difficulty in adopting new technology | 0 |
| 17 | Inadequate Data Cleaning | 0 |
| 18 | Poor Environment Replication | 0 |
| 19 | Schema Not Aligned with Repository Users | 0 |
| 20 | Tool Chosen Without Community Fit | 0 |
| 21 | Overengineered Architecture | 0 |
| 22 | UAT Process Documentation for CMS Upgrades | 0 |
| 23 | Website Downtime Troubleshooting | 0 |
| 24 | Lack of centralised documentation control | 0 |
| 25 | Low utilisation of digital resources | 0 |
