Case Study · Product Evolution · In Reconstruction

When a Product Needs a Second Generation, What Should Actually Change?

MY POD 2.0 was designed and developed by Gizmospring for Gizmospring U.S. — a second generation whose problem-first story is being reconstructed with the original project team, around the project's authentic imagery.

This headline is a structural placeholder. The verified central problem — and the one-sentence account of what actually changed — replaces it once the interview is complete.

ProductMY POD 2.0

Product EvolutionCapability tags pending verification

MY POD 2.0 — original project cover imagery from the Behance study library

01 / What's verified so far

Project owner

Gizmospring U.S.

Design & development

Gizmospring

Original project team

Anson Lee, Esme Lo & the Gizmospring team

Development tools

Rhinoceros (CAD) · Keyshot (rendering) · Photoshop

Original publication

September 2021

Case-study status

Problem-first reconstruction in progress

Everything on this page is limited to what the original project verifiably documents — ownership, authorship, toolchain and imagery. The problem statement, insights and engineering narrative will be added only after the original project team's account is collected.

02 / A Second Generation Shouldn't Just Look Different. It Should Work Better.

Evolution Begins by Separating What to Keep from What to Fix.

The project is named MY POD 2.0 — the second generation is a documented fact. What it changed, and why, is not yet. Product evolution starts by separating what should be preserved from what needs to change — and both lists are being reconstructed from the original team's account before anything is claimed here.

The first generation, as documented

Gizmospring created MY POD 1.0 in partnership with CalExotics — a single-button device paired with a discreet UV-sanitizing case. Its documented mission: make carrying a personal wellness product feel as casual and acceptable as carrying a pair of wireless earbuds.

Hygiene designed in — a UVC light inside the case sanitizes after each use
Elegant simplicity — a single button cycles through the device's modes
Pocketable form, refined from the cues of minimalist consumer electronics
Delivered end-to-end — industrial design, engineering design, mass production and logistics

Verified · official Gizmospring project record

MY POD 1.0 — the single-button device inside its open UV-sanitizing case, authentic project photography

MY POD 1.0 light colorway — device and closed case, front-facing authentic project photography

First generation

MY POD 1.0

What worked?

Pending · team account

What didn't?

Pending · team account

What had users learned?

Pending · team account

Second generation

MY POD 2.0

What should be preserved

The behaviors, qualities and details the first product had already earned in users' hands — identified before a single sketch is drawn, so a redesign never discards what the product was actually valued for.

MY POD's preserved list · pending verification

What needs to change

The usability, mechanical and manufacturing problems the first product exposed — separated from cosmetic preference, so the second generation is driven by evidence rather than by novelty.

MY POD's change list · pending verification

The comparison will be judged on

UsabilityErgonomicsMechanismsPerformanceMaterialsCleaningAssemblyReliabilityManufacturing

Verified improvements — where they exist — will be published with the authentic 1.0 vs. 2.0 study imagery once the comparison is evidenced. The difference between generations will not be reduced to cosmetics.

Version 2.0 should be evidence of what you've learned — not simply evidence that you've redesigned it.

03 / We don't write the story until we know the problem

Reconstructed Before It's Rewritten.

Most case studies are written backwards from finished renders. MY POD 2.0 has the renders — but a picture of a product is not the story of the problem. So the narrative is being reconstructed with the original project team first, and the authentic project imagery reorganized around it once the central problem is clear.

Problem

Insight

Design Question

Exploration

Engineering

Validation

Outcome

Every stage pending · awaiting the original team's account

The product & its people

Who was the client — and who was the intended user?
What is MY POD, and what did MY POD 1.0 do?
Where and how was the product actually used?

Why a 2.0

What limitations or complaints existed in the previous product?
What did the client originally ask Gizmospring to improve?
What did Gizmospring discover that nobody had identified?

The hard parts

The biggest usability problems.
The biggest mechanical and manufacturing problems.
What was benchmarked — and what user research was observed?

The proof

What directions were explored and rejected — and why?
What prototypes were built and what testing was performed?
Did MY POD 2.0 enter production — and what changed from 1.0 to 2.0?

04 / The study library, organized by the story each image tells

Every Image Must Earn Its Place in the Narrative.

The original MY POD 2.0 study is being audited image by image and sorted into the nine chapters it can support — retained where it tells the story, re-cropped where the story needs a tighter frame, and never replaced where the authentic image already speaks.

Audit status — the Behance MY POD 2.0 gallery sits behind a sign-in wall (adult-content flag), so the collected library combines the accessible 2.0 cover with six authentic first-generation modules from the official Gizmospring project record — integrated as Context, Human Factors and Engineering evidence. Each 2.0-specific module is categorized the moment the original team provides access.

Authentic imagery only

3 modules · collected

Context

Existing product / use environment / user.

The world the second generation entered — the first product, the hands it lived in, the environment it was used in.

Pending collection

Research

Benchmarking / observations / user insights.

What the team looked at, measured and heard before drawing anything.

Pending collection

Exploration

Sketches / alternative concepts / form studies.

The rejected paths — the breadth a second generation was chosen from.

2 modules · collected

Human Factors

Ergonomic studies / interactions / dimensions.

The body's demands on the product: grip, reach, proportion, motion.

1 module · collected

Engineering

CAD / exploded views / mechanisms / internal architecture.

How the concept was made physically true — geometry, assembly logic, moving parts.

Pending collection

Materials

CMF / textures / material development.

What the product is made of, and what that material asks of manufacturing.

Pending collection

Prototyping

Physical models / iterative prototypes.

The growing-up sequence — each build answering a question the last one raised.

Pending collection

Validation

Testing / interaction evaluation.

Evidence, not opinion: the trials that decided what shipped.

1 module · 2.0 cover

Outcome

Finished product / production / lifestyle.

The second generation as it exists now — production reality, in use.

Generated imagery — allowed

Diagrams, process maps, annotated comparisons and simplified technical explanations — generated only where an important concept cannot be communicated by the existing project assets.

Generated imagery — never

No fictional development photographs, prototypes or engineering internals generated and presented as actual project evidence. The authentic study library is the only evidence.

Figures continue the case study's sequential numbering from the hero cover (Fig. 01); each collected module is re-cropped only where the narrative needs a tighter frame.

05 / Concept exploration

We Weren't Exploring Shapes. We Were Exploring Answers.

The project's concept sketches and development imagery will not be presented as a gallery. Each direction is organized by the problem it attempted to solve — what it tested, what it taught, and whether anything from it survived into the second generation.

Direction A

What problem was this trying to solve?

Pending · project-team account

What worked?

Pending · project-team account

Why wasn't it selected?

Pending · project-team account

Authentic concept sketches and development imagery from the study library sit beside this direction once the gallery is collected.

Direction B

What assumption did this test?

Pending · project-team account

What did the team learn?

Pending · project-team account

Authentic concept sketches and development imagery from the study library sit beside this direction once the gallery is collected.

Direction C

Carried forward

What insight eventually moved into the final design?

Pending · project-team account

Authentic concept sketches and development imagery from the study library sit beside this direction once the gallery is collected.

Direction explanations are published only from the original team's own account — no direction, rationale or learning is reconstructed on the team's behalf.

Concept development isn't about generating more options. It's about learning which decisions move the product closer to the right answer.

06 / Human factors

The Product Had to Work With the Body, Not Just Around It.

Human factors is documented here as verified physical interactions — the seven questions below, answered by the original project team's account, never inferred from the imagery alone. The project's ergonomic and interaction studies sit beside each answer as the gallery is collected.

MY POD 1.0 — a hand holding the open case, the device's control ring illuminated, authentic project photography

The documented interaction

The first generation's control was a single button — one press cycling through the device's modes — inside a case that closed around the product and sanitized it. One control, one motion, no learning curve: that is the interaction baseline the second generation inherited.

Verified · official Gizmospring project record

MY POD 1.0 — control interface detail: the circular button with its illuminated ring inside the open case, authentic project photography

Where the product contacts the body

Every interface point, and what each one is asked to do.

Pending · verified team explanation

How it is positioned

The stable orientation the product is designed to be used in.

Pending · verified team explanation

How it is controlled

The physical controls, and where they sit relative to the hand.

Pending · verified team explanation

What movements occur

Motion between product and user during actual use.

Pending · verified team explanation

What must remain stable

The geometry and structure that holds its position.

Pending · verified team explanation

What needs to flex or move

The elements designed to give, bend or articulate.

Pending · verified team explanation

How different user dimensions affect the experience

How the design accounts for variation between users.

Pending · verified team explanation

Annotated diagrams — allowed

Conceptual annotated diagrams will be generated to explain ergonomic decisions the team has actually verified — contact points, stability, articulation — once those decisions are documented.

What this section will never do

Infer how the product works from its images. Every interaction published here comes from the original project team's own explanation.

Human factors isn't making a product look ergonomic. It's engineering around how a person actually uses it.

07 / Engineering architecture

The Form Was Only the Outside of the Problem.

The engineering behind MY POD 2.0 is documented as requirement chains — every internal decision traced back to the requirement that forced it, and the constraint that made it hard. Components are never listed without the problem they solve.

How each engineering decision is documented

InputUser / product requirement

ConstraintWhat made that requirement difficult?

SolutionWhat did Gizmospring change?

ResultWhat improvement did the solution create?

Chain 01

Input