TNA Mobile Activity Cards

01 The Stakes / Problem

The right artifact for a desk. The wrong one for a floor.

ZYOD's TNA module had a Multi Style Table: every style, every stage, delay reasons, comments, history. Right for a planner at a desk. Wrong for the team leads, fabric chasers, and warehouse supervisors the dates actually belonged to. They were on the floor, with no monitor.

Try it on a phone

Sales > Sales Order Search by SO, brand name, supplier name… Export

Sales Order

TotalItems: 23455 | USD: 4583940.43

GMV BookedQty: 23455 | USD: 4583940.43

GMV InvoicedQty: 23455 | USD: 4583940.43

GMV ActiveQty: 23455 | USD: 4583940.43

Actual date on time/early Actual date later than planned date

TNA ↑Target Dispatch date ↑Current stageActivity det.FitPPFPTSize SetFabric InhouseCuttingStitchingEmbroideryPrintingDyeingWashingFinishingPackingFinal InspectionDispatch

Style: WWDR001_01Brand: RELIANCE-SHEINSO-id: SO-1234

6 Jul, 2024 R2

Fabric InhouseTarget: 1 Jun, 2024 | Late (11d)Depends on: Lab Dip App…go to chat

DaysTarget dateActual date

Late (4d)1 Jun, 2024 R1-

Early (1d)1 Jun, 2024 1 Jun, 2024

On time (11d)1 Jun, 2024 -

—4 Jun, 2024 -

Late (11d)6 Jun, 2024 17 Jun, 2024

—9 Jun, 2024 -

—16 Jun, 2024 -

—20 Jun, 2024 -

Not in route— —

—24 Jun, 2024 -

—27 Jun, 2024 -

—30 Jun, 2024 -

—2 Jul, 2024 -

—6 Jul, 2024 -

Style: WWTS014_02Brand: RELIANCE-SHEINSO-id: SO-1238

4 Jul, 2024

DaysTarget dateActual date

Late (11d)1 Jun, 2024 R11 Jun, 2024

Early (1d)1 Jun, 2024 1 Jun, 2024

—3 Jun, 2024 -

On time (2d)5 Jun, 2024 5 Jun, 2024

—8 Jun, 2024 -

—11 Jun, 2024 -

—15 Jun, 2024 -

Not in route— —

—18 Jun, 2024 -

—21 Jun, 2024 -

Not in route— —

—25 Jun, 2024 -

—28 Jun, 2024 -

—1 Jul, 2024 -

—4 Jul, 2024 -

Style: WWKD007_01Brand: RELIANCE-SHEINSO-id: SO-1241

2 Jul, 2024 R1

Fabric InhouseTarget: 1 Jun, 2024 | Late (11d)Depends on: Lab Dip App…go to chat

DaysTarget dateActual date

On time (11d)1 Jun, 2024 -

On time (0d)1 Jun, 2024 1 Jun, 2024

—3 Jun, 2024 -

Late (3d)5 Jun, 2024 8 Jun, 2024

—10 Jun, 2024 -

—14 Jun, 2024 -

Not in route— —

—22 Jun, 2024 -

—25 Jun, 2024 -

—28 Jun, 2024 -

—2 Jul, 2024 -

1-20 of 97

The desktop Multi Style Table, the system of record this had to sit on top of, not replace. Coded from the original design with sample data, scroll it sideways to follow a style from sampling to dispatch; switch to “On a phone” for the naive version of this project.

One late fabric dateDrag the line

3stages hit
before anyone knew

Fabric Inhouse

Cutting

Stitching

Finishing

Found

Found when someone next opened the table. By then it had moved through three stages.

Illustrative timeline, not measured dates.

Why the table failed the floorPick a gap

The gapCouldn't find your work

A factory-wide view. A lead owning twelve SOs still had to hunt.

What answered itFilters on one shared list: My SOs, Needs Attention, Due this week

Two systems that weren't talkingTry “Add the card”

System of recordThe tableFabric · On trackLast updated at the desk

System of workThe floorFabric · Failed inspectionKnows, but can't write it down

2versions of the truthThe table and the floor aren't talkingNo shared record

Illustrative status values.

Constraint

The flows and the table were already designed. My job wasn't to reopen the information architecture. It was to decide what a standing worker needs from that data in the next ten seconds.

02 Who Was Stuck

Three roles, one floor, different questions.

Look through each rolePick a role

Needs

“What's mine, what's red, what I can escalate without leaving the line”

Owns: A set of styles across all four stages
Before: Verbal updates and periodic desk checks

Activity cardReads first

1StatusDue date

StyleBrand

Contacts2Assignment

CommentPhoto3EscalateReassign

Three jobs. Same list. Different questions. That's why I didn't split the product into three apps.

These roles come from the brief and from how TNA was already used, not a fresh round of interviews. Worth confirming against how these teams actually worked.

03 Your Thinking

A table is a reporting object. A card on the floor is a decision object.

“Shrink the table to a phone” fails. Instead I asked every field in the table one question, and the order of the answers became the card.

03/Information hierarchy

Does this change what someone does in the next minute?

Drag or tap a field

Seven fields from the table. Pick one, then the shelf it belongs on.

4 tensions, and the call on eachPick one1 of 4

the table held everything a planner might need.

The call

Keep what changes a floor decision. Put the rest behind a tap.

If a worker has to open every card to know what's on fire, the component has already lost.

04 The Solution

A card component that didn't exist in the design system.

Built from scratch, then dropped into the existing ERP. Each piece answers one question a floor worker actually asks.

DelayedDue : 12 June, 2025R2

Fabric InhouseGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

On holdDue : 12 June, 2025R2

Fabric InhouseGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

On TrackDue : 12 June, 2025R2

Fabric InhouseGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

CompletedDue : 12 June, 2025R2

Fabric InhouseGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

“What needs my attention right now, standing up?”

Status system

On track / needs attention / delayed, readable before the card is opened
Color is the triage layer, not decoration

On TrackDue : 12 June, 2025R2

Fabric InhouseGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

“Who do I talk to, and why does this card exist?”

Context on the face

Style, brand, contacts, and assignment on the card face
No second screen for the basics

Hi Sam!

8 tasks

DelayedDue : 12 June, 2025R2

Fabric InhouseGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

On holdDue : 12 June, 2025

Fabric InhouseGPT WWDR5047_02RaymondsSO-4567

Sales: Monika S. Merch: Praksh

On TrackDue : 14 June, 2025

CuttingGPT WWDR5051_01Reliance-SHEINSO-4571

Sales: Monika S. Merch: Praksh

DelayedDue : 16 June, 2025R1

StitchingGPT WWDR5051_02Reliance-SHEINSO-4571

Sales: Monika S. Merch: Praksh

On TrackDue : 18 June, 2025

Fabric InhouseGPT WWDR4988_03RaymondsSO-4580

Sales: Monika S. Merch: Praksh

CompletedDue : 20 June, 2025R2

FinishingGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

On holdDue : 21 June, 2025

CuttingGPT WWDR4988_03RaymondsSO-4580

Sales: Monika S. Merch: Praksh

On TrackDue : 24 June, 2025

StitchingGPT WWDR5047_02RaymondsSO-4567

Sales: Monika S. Merch: Praksh

“What do I do about it, right here?”

Actions on the card

Comment, escalate, reassign, and attach a photo on the card
The audit trail starts at the problem, not in a 6pm recap

Hi Sam!

3 tasks

DelayedDue : 12 June, 2025R2

Fabric InhouseGPT WWDR5047_01RaymondsSO-4567

Sales: Monika S. Merch: Praksh

On holdDue : 12 June, 2025

Fabric InhouseGPT WWDR5047_02RaymondsSO-4567

Sales: Monika S. Merch: Praksh

On TrackDue : 18 June, 2025

Fabric InhouseGPT WWDR4988_03RaymondsSO-4580

Sales: Monika S. Merch: Praksh

“What's actually mine, right now?”

Filters on a shared list

Needs Attention, My SOs, Due this week
Bulk-select delayed work to escalate, reassign, or comment in one go

How the card fits a dayStep through it

Open the app

Red and yellow wait under “Needs attention.”

Step 1 of 3

The Multi Style Table didn't go away. Planners still need a dense board. The app is the execution layer the table was never going to be.

05 The Detailed Impact

100% adoption is the number I can stand behind.

100%

adoption across the three launch factories

GurgaonAdopted
GurgaonAdopted
JaipurAdopted

People who had no TNA access unless they walked to a desk now track material, fabric, and SKU status, coordinate across departments, and escalate from the phone, at the moment the decision is happening.

Before

Status lived on a desktop
Delays showed up when someone next opened the table
Escalation was a call or a walk

After

Status visible and editable from the floor
Delays flagged the moment they were seen
Escalation and photo evidence in one motion

Add metrictime from spotting an issue to logging it, desk vs. mobile

Add metricdesk walk-backs per shift

Add metricescalations logged per week, before vs. after

Adoption is the one number with hard data behind it. Floor tools that miss the job get quietly abandoned; this one didn't. I'd rather leave the three above blank than invent them.

06 Limitations & What's Next

What I would not claim.

Scope

The card, its states, and the filters. The data model and core flows were locked: I didn't decide which fields existed, only which ones earned a place on a standing worker's first screen.

01
Floor connectivity: a card that needs a clean network is still fragile in parts of a factory.
02
Language: English UI on a Gurgaon / Jaipur floor is a real adoption risk as this spreads.
03
Conflicting status between roles: who wins when the chaser and the lead disagree on a stage.

The problem was never “make TNA mobile.” The company had a source of truth only one job could use. Production speed depends on the other jobs writing into it while they work.

Which fields change a decision in the next minute?
Do we optimize for my list or for the line?
Where does an update have to live so the data stays honest?
What can stay one component across factories so rollout doesn't become a design project every time?

TNA Mobile Activity Cards

The right artifact for a desk. The wrong one for a floor.

Sales Order

Three roles, one floor, different questions.

A table is a reporting object. A card on the floor is a decision object.

Does this change what someone does in the next minute?

Keep what changes a floor decision. Put the rest behind a tap.

One shared list, with role on top as filters.

Comment, escalate, reassign, and photo live on the card.

Design against the ERP's data, not a floor plan.

A card component that didn't exist in the design system.

Status system

Context on the face

Actions on the card

Filters on a shared list

100% adoption is the number I can stand behind.

What I would not claim.