Unblocking Backlog Jams

on YouTube ↗39m

" summary

A sudden import of 300+ accessibility issues turns into a multi‑dimensional spreadsheet workflow using Notion/modern spreadsheets to hide noise, convert columns to selects, add counts and group views by component platform and impacted population. The process exposes that many reports are duplicates or obsolete and enables focused packs of related fixes; the team clears 142 issues in 2.5 months and reduces a two‑year estimate to manageable sprints.

AI-written summary · about

" chapters (35)

1. 0:00Intro
2. 0:28One day hundreds of JIRA tickets showed up in my inbox...
3. 1:19This triggered my fight or flight response.
4. 2:05Some simple math told me...
5. 2:44We had created a log jam.
6. 4:27The Theory of Constraints
7. 8:03Conventional wisdom
8. 8:54Understanding how accessibility audits are performed
9. 9:59Often focused on the output
10. 10:27and ignorant of the input
11. 10:55Often very repetitive due to how we reuse our code
12. 11:21Often ignorant of "easy" vs "hard" in the underlying systems
13. 11:53Often ignorant of metrics and relativ importance of the page
14. 12:20e.g. alt text is missing
15. 13:03How do you eat the proverbial elephant?
16. 16:53Hitting the limitations of JIRA
17. 17:45It was easier to triage in Excel
18. 18:42Which page is effected?
19. 19:31Which component is effected?
20. 20:06Which WCAG violation?
21. 20:39New dimensions appear!
22. 21:31Can we leverage modern spreadsheeting applications?
23. 22:18How-to create a multi-dimensional accessibility audit.
24. 23:48Import data
25. 24:22Hide columns
26. 25:07Convert columns to selects and multi-selects
27. 25:57Color code
28. 26:35Add Counts
29. 27:31Add dimensions
30. 31:05How'd it work out for us?
31. 32:12Some thoughts on improving workplace satisfaction via the backlog process
32. 34:04Avoid extensive audits, start with a few core templates first.
33. 35:06Deliver issues in small packs of related issues.
34. 36:35Gamify the experience, progressively increase the difficulty
35. 37:43Give a s#!% about accessibility before legal shows up.

" related talks

• 17mVisualization to the rescueBartosz Zbierajewski, Wojciech Buras · AgileByExample 2016
• 36mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at ScaleFlorian Mierzejewski · TechLead Conference 2025: AI in Orgs
• 10mPractical tech-debt prioritizationSahana Carlsen · LeadDev Berlin 2023
• 45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI IssuesNaresh Jain · Agile India 2021
• 48mGet It Right the 1st Time: Stop 80%+ of A11Y Bugs During DevelopmentSachin Gupta, Glenda Sims · axe-con 2024
• 01h 02mPrioritizing Remediation of Accessibility IssuesKarl Groves · Inclusive Design 24 2014
• 33mHow to make your application accessible (and keep it that way!)Joel Hawksley · Rocky Mountain Ruby 2024
• 35mAvoiding the Petard: Triage at Scale in Firefox QuantumEmma Humphries · foss-north 2018