← Jake Jayakaran

SPRUCE / DESIGN LANGUAGE

CONFIDENTIAL WORK

This write-up explains my work, decision-making and impact. Project imagery has been removed, along with confidential details, proprietary concepts and sensitive metrics.

portfolio available upon request

SPRUCE / PHYSICAL DESIGN LANGUAGE

Establishing a physical design language.

Establishing a physical design language.

Establishing a physical design language.

I led the creation of a scalable physical design language for Spruce, turning a collection of individual products into a recognizable family while preserving enough flexibility to support very different categories and use cases.

I led the creation of a scalable physical design language for Spruce, turning a collection of individual products into a recognizable family while preserving enough flexibility to support very different categories and use cases.

Role

Design strategy lead

Team

Two designers, an intern & an external agency

Duration

4 mo

Status

Confidential

My contribution

Design-language strategy, physical design principles, product application, development, and cross-functional alignment.

Managed 2 industrial designers and 1 design intern; served as process leader and single point of contact for the external design agency.

Three key decisions

01

01

Principles before form.

Principles before form.

Decision: Defined the relationships that make a product recognizable before exploring aesthetics.

Rationale: A shared foundation could survive changes in product architecture.

Tradeoff: Slower initial progress in exchange for stronger long-term consistency.

02

02

Recognition without repetition.

Recognition without repetition.

Decision: Separated consistent design cues from elements that could adapt across categories.

Rationale: Build family resemblance while preserving each product’s performance and context.

Tradeoff: More nuanced decisions than simply repeating geometry.

03

03

Design for evolution.

Design for evolution.

Decision: Built a language that could absorb future technologies and product categories.

Rationale: Create a framework that could scale beyond individual products.

Tradeoff: Some near-term opportunities were excluded to preserve long-term flexibility.

A shared direction for future products.

A shared direction for future products.

Reduced ambiguity during concept development and created a repeatable framework for evaluating future design directions.

Additional project information may be discussed where disclosure is authorized.