Ted Low
I craft design systems that scale and brands that shine.
Ted Low
I craft design systems that scale and brands that shine.
Ted Low
I craft design systems that scale and brands that shine.
About
About
Hey-o, I’m Ted Low, a senior designer with over a decade of experience in design systems and branding.
I’m currently working on PENN Entertainment / theScore’s core design system, Alley-oop, which covers industry leading brands such as ESPN BET, theScore, Hollywood Casino, and Penn on mobile and web. Additionally, I work with a broad range of stakeholders on exploratory initiatives that deepen brand equity and connect our apps and services with new partners.
Work
Work
Work
Carousel
Component deep dive
Explore
Carousel
Component deep dive
Explore
Carousel
Component deep dive
Explore
Alley-oop
Branding a design system
Explore
Alley-oop
Branding a design system
Explore
Alley-oop
Branding a design system
Explore
Icons
Stylizing and tokenizing
Our icon tokens were inconsistently organized and stylized. The library was scattered across multiple files, making it hard to navigate. The automated pipeline (a script to parse Figma .json through GitHub) lacked flexibility for iconography. Icons were styled and sized inconsistently. Designers and developers often struggled to find the correct icons in the repositories.
We established guidelines for designing icons and centralized the library. The guidelines provided icon sizing, style, and padding, ensuring consistency across the library. The library was held in one Figma file, where both designers and developers can find the tokens easily (we improved search by adding keywords to components) and the design system team can more easily manage them.
This resulted in fewer inquiries about where icons could be found in the repo, and greater consistency between design and development. Inquiries about icon locations dropped by 64%. The guidelines on the documentation site have streamlined the design process and removed significant ambiguity when making decisions. It has also provided (non-systems) designers with the ability to create their own icons.
Icons
Stylizing and tokenizing
Our icon tokens were inconsistently organized and stylized. The library was scattered across multiple files, making it hard to navigate. The automated pipeline (a script to parse Figma .json through GitHub) lacked flexibility for iconography. Icons were styled and sized inconsistently. Designers and developers often struggled to find the correct icons in the repositories.
We established guidelines for designing icons and centralized the library. The guidelines provided icon sizing, style, and padding, ensuring consistency across the library. The library was held in one Figma file, where both designers and developers can find the tokens easily (we improved search by adding keywords to components) and the design system team can more easily manage them.
This resulted in fewer inquiries about where icons could be found in the repo, and greater consistency between design and development. Inquiries about icon locations dropped by 64%. The guidelines on the documentation site have streamlined the design process and removed significant ambiguity when making decisions. It has also provided (non-systems) designers with the ability to create their own icons.
Icons
Stylizing and tokenizing
Our icon tokens were inconsistently stylized and organized.
The library was scattered across multiple files, making it hard to navigate. The automated pipeline (a script to parse figma .json through github) lacked flexibility for iconography. Icons were styled and sized inconsistently. Designers and developers often struggled to find the correct icons in the repositories.
Guidelines for designing icons were established and the library was centralized.
I established clear guidelines for icon sizing, style, and padding ensuring consistency across the library. The icon token library was centralized in to one file in Figma, where both designers and developers, can find the tokens easily (we improved search by attaching keywords to components) and the design system team can manage them easily.
This resulted in less inquiries of where icons could be found in the repo and greater consistency between design and development.
Inquiries about icon locations dropped by 64%. The guidelines on the documentation site now provides clear guidelines for designers when creating new icon, which has streamlined the design process and removed a ton of ambiguity when making decisions. It has also provided (non-systems) designers with the ability to create their own icons.
Request portfolio deck ↗
Shelter
B2B ecommerce product
Shelter’s wholesale ordering process wasn’t scalable or user-friendly. Orders were handled via emailed Excel sheets that buyers filled out and sent back—slow, error‑prone, and disconnected from real product comparison. For a Canada‑wide cannabis company serving medicinal, recreational (select provinces), and wholesale customers, the experience fell short of what buyers needed.
I led the design of a B2B wholesale shopping experience that made comparing and purchasing products straightforward. To accelerate delivery, I reused proven components from the direct‑to‑consumer product, then adapted the patterns for data‑dense workflows. I studied tools that excel at comparisons and tables (Dropbox, Google Drive, Notion) and implemented sortable columns, keyword filters, non‑modal product and cart views, and quick‑add interactions—creating a more objective, data‑driven purchase flow.
Though Shelter was shut down shortly after release, late‑cycle user testing showed the experience was “night and day” better than the email‑and‑Excel approach. Buyers could evaluate products faster, reduce friction in order creation, and stay in context while building carts—validating the design’s direction even within a shortened window.
Shelter
B2B ecommerce product
Shelter’s wholesale ordering process wasn’t scalable or user-friendly. Orders were handled via emailed Excel sheets that buyers filled out and sent back—slow, error‑prone, and disconnected from real product comparison. For a Canada‑wide cannabis company serving medicinal, recreational (select provinces), and wholesale customers, the experience fell short of what buyers needed.
I led the design of a B2B wholesale shopping experience that made comparing and purchasing products straightforward. To accelerate delivery, I reused proven components from the direct‑to‑consumer product, then adapted the patterns for data‑dense workflows. I studied tools that excel at comparisons and tables (Dropbox, Google Drive, Notion) and implemented sortable columns, keyword filters, non‑modal product and cart views, and quick‑add interactions—creating a more objective, data‑driven purchase flow.
Though Shelter was shut down shortly after release, late‑cycle user testing showed the experience was “night and day” better than the email‑and‑Excel approach. Buyers could evaluate products faster, reduce friction in order creation, and stay in context while building carts—validating the design’s direction even within a shortened window.
Shelter
B2B ecommerce product
Shelter’s wholesale ordering process wasn’t scalable or user-friendly. Orders were handled via emailed Excel sheets that buyers filled out and sent back—slow, error‑prone, and disconnected from real product comparison. For a Canada‑wide cannabis company serving medicinal, recreational (select provinces), and wholesale customers, the experience fell short of what buyers needed.
I led the design of a B2B wholesale shopping experience that made comparing and purchasing products straightforward. To accelerate delivery, I reused proven components from the direct‑to‑consumer product, then adapted the patterns for data‑dense workflows. I studied tools that excel at comparisons and tables (Dropbox, Google Drive, Notion) and implemented sortable columns, keyword filters, non‑modal product and cart views, and quick‑add interactions—creating a more objective, data‑driven purchase flow.
Though Shelter was shut down shortly after release, late‑cycle user testing showed the experience was “night and day” better than the email‑and‑Excel approach. Buyers could evaluate products faster, reduce friction in order creation, and stay in context while building carts—validating the design’s direction even within a shortened window.
Request portfolio deck ↗