Texitag: from a recycling dashboard to a closet companion
Waste Management asked for a web dashboard to track garment lifecycles. People don’t think about recycling at a desk, so it became a scan-first mobile product that lives next to the closet.
5 monthsfrom first research to a working prototype
3industry partners: Waste Management, EON and Under Armour
Role
UX research, strategy, UI design, prototyping
Team
Sole designer, with sustainability consultants
Timeline
Aug–Dec 2023
Context
University project at Thomas Jefferson University, with Waste Management, EON and Under Armour
Waste Management asked for a web dashboard to track garment lifecycles. Early feedback showed that people don’t think about recycling at a desk, so I turned the dashboard into a scan-first mobile app that lives next to the closet, and designed how the tags would reach people in the first place.
In short
Problem
Textile waste kept growing even as people said they cared about sustainability. Consumers didn’t know when or how to recycle clothes, and recyclers couldn’t trace garments.
Opportunity
People make decisions about clothes at the wardrobe, the laundry basket and the bin. A product at those moments could turn good intentions into habits, and give WM the data it lacked.
What I did
Researched the problem, pivoted the brief from a web dashboard to a scan-first mobile product, and designed it end to end, with sustainability consultants on the data WM needed.
Outcome
A working prototype in five months, plus a rollout plan for QR tags on bins and in stores.
Proudest decision
The pivot. A dashboard nobody opens tracks nothing.
01 / Context and constraints
Three parties who rarely share information.
Texitag connects three parties who rarely share information. Consumers own and dispose of clothes. Brands make and tag them. WM collects and processes them. Consumers want ease and a reason to bother; WM wants data on what is worn, reused and recycled.
Behaviour change, not a task. Nobody needs to track their clothes, so the product had to create the motivation it relied on.
Tags don’t exist yet. The scan model depends on QR tags that brands and retailers would have to adopt.
Two customers. WM sponsored the work, but consumers decide whether it gets used.
02 / What research told me
The gap is clarity, not awareness.
I combined early feedback from consumers with working sessions with sustainability consultants, who knew which metrics WM needed to report.
0moments in an ordinary day when someone thinks about recycling a jacket at a desk.
Most people say they care about sustainability, but they don’t know when a garment is done, where it should go, or whether recycling it makes a difference.
The gap was clarity, visibility and motivation, not awareness. And people don’t engage with sustainability at a desktop.
03 / Key design decisions
Four decisions that shaped the product.
Scan-first: the product opens where the clothes are.
01
Move the product from the browser to the closet
Context
The brief was a web-based dashboard.
Options
A — build the dashboard as scoped
B — a dashboard plus a mobile companion
C — mobile-first and scan-based, with dashboard views inside the app
Choice
C.
Why
Decisions about clothes happen at the wardrobe, the laundry basket and the bin, not at a desk. Scanning puts the product at those moments.
Trade-off
WM’s reporting moved to aggregate data from the app, not a dashboard consumers browse.
Evidence
WM scoped a web dashboard. I showed them the early feedback that people don’t engage with sustainability on desktop, and we built a mobile, scan-first product instead.
02
Give every garment a story
Context
People throw out clothes they’ve stopped noticing.
Options
A — a simple list of owned items
B — a lifecycle view per garment: how long you’ve owned it, how often it’s worn and washed, and whether it’s sat idle
Choice
B. Scanning a garment opens its lifespan, wears, washes and current state.
Why
Seeing that a jacket has gone unworn for months turns “reuse, donate or recycle” into a concrete question.
Trade-off
It needs logging. A one-tap “Wore it” from the closet view keeps the effort low.
03
Reward keeping clothes in use, not only throwing them out
Context
Rewarding recycling alone can encourage people to throw clothes out sooner.
Options
A — a reward for recycling only
B — eco credits for reusing, donating and recycling, plus short nudges with facts and goals
Choice
B. Adding your first garment earns 100 points, and every reuse, donation or recycling earns more.
Why
Small, frequent rewards build the habit, and rewarding reuse keeps the incentive pointed at the right outcome.
Trade-off
Rewards need funding. In-store discounts from retail partners were the plan to pay for them.
04
Design how tags reach people, not just the app
Context
Scanning only works if garments and bins carry tags, and today they don’t.
Options
A — assume brands will tag garments
B — design the rollout with partners: QR tags on garbage and recycling bins, in-store discounts for scanning, and education across the app, print and municipal content
Choice
B, scoped with the sustainability consultants.
Why
A habit product with no way in has no users. The bins and stores are where the first scan happens.
Trade-off
Adoption depends on partners outside the product team.
04 / Outcomes
A prototype, and a way in.
5 monthsfrom first research to a working prototype
3industry partners: Waste Management, EON and Under Armour
100points for the first garment added, then more for every reuse
1 tapto log a wear from the closet view
A working prototype in five months from first research, developed with WM, EON and Under Armour, and a rollout plan for tags on bins and in stores.
For WM, the value is the data: aggregate patterns of wear, reuse and recycling that support its reporting. For people, the value is a reason to care about one jacket at a time.
05 / What I would do differently
What I would do differently.
Solve the cold start first
Most clothes in a closet today have no tag, so I’d design manual and photo-based adding before polishing the scan flow.
Test retention, not only usability
For a habit product, the question is whether people come back, so I’d run a two-week diary study.
Design the data agreement
Users should see exactly what WM receives, and why.