Streamlining Design operations | Toronto JS

A case study on how I solved async collaboration challenges for TorontoJS design team

👤 Role

Product Designer

💼 Industry

B2B SaaS · Community Operations

📅 Duration

July 2025 - Present

Metro-X
Metro-X
Metro-X

Navigation chaos

Inefficient Workflows

Irrelevant Content

Collaboration Gaps

#2
Manual Overhead

Teams spent 5-8 hours weekly maintaining fragmented documentation. Information outdated within days of creation

#3
Incident Cascade Effect

Without relationship visibility, small issues became major outages

#4
Scaling Impossibility

→ Manual mapping broke down exponentially as infrastructure grew

"We can see all our entities but have no single source of truth for relationships."

#1
Visibility Gap

See also

© Made by Meghna Aggarwal with creativity, lots of ctrl+z, and coffee. ⋆.˚☕︎

⏱ Toronto, ON •

16:05

© Made by Meghna Aggarwal with creativity, lots of ctrl+z, and coffee. ⋆.˚☕︎

⏱ Toronto, ON •

16:05

© Made by Meghna Aggarwal with creativity, lots of ctrl+z, and coffee. ⋆.˚☕︎

⏱ Toronto, ON •

16:05

Create a free website with Framer, the website builder loved by startups, designers and agencies.