Studio Landing Hero

Made Studio’s value visible through Build, Render, and Instructions.

Owned the hero direction within a broader landing page redesign, structuring a product-led story around Studio's three core workflows: Build, Render, and Instructions.

My role: Hero concept · product storytelling · final asset production
Team: Cross-functional plus a community manager
Timeline: 2024

The 30-second story

Challenge

Make Studio's value visible at a glance when its core workflows were not central to the hero experience.

Key move

Centered the hero on Build, Render, and Instructions, showing each workflow directly in the product instead of relying on static product messaging.

Execution

Storyboarded a continuous sequence, created a custom hummingbird model with collaborators, and delivered the final motion assets and responsive specifications.

Result

Created a clearer path from Studio's core workflows into the broader feature set and the wider BrickLink ecosystem.

Problem

Studio's existing landing page introduced its core workflows, but they were not central to the hero experience. Competing elements weakened the hierarchy and made the product's value difficult to grasp at a glance.

Studio’s previous landing page, before the redesign — Studio's previous landing page, before the redesign.

Process

Reframing the message

Rather than introducing Studio through static product messaging, I structured the hero around three core workflows, Build, Render, and Instructions, and demonstrated each one directly in the product.

Early Build in Studio concept presented to the product manager — A quick visual prototype proposing a simpler, product-led hero direction.

Storyboarding the motion

I mapped each message to a corresponding product action and storyboarded the transitions to keep the sequence brief, clear, and continuous.

Hand-drawn storyboard mapping each message to a product action

Refining the visual content

I worked with a community manager and a colleague with deep Studio expertise to develop a custom hummingbird model. From there I screen-recorded and edited the full sequence, refining compositions, viewing angles, and transitions to clearly demonstrate each workflow.

Final handoff

I delivered the final video assets, timing specifications, and responsive layouts, working closely with the frontend developer to ensure the hero behaved as intended.

Final video asset with timing specifications — The delivered asset with timing specifications: “Build” at 0:00, “Render” at 12:15, and “Instructions” at 17:16.

Outcome

The final landing page created a clearer journey from Studio's core workflows into its broader feature set, helping prospective users understand both what they could create and how the product fit into the wider BrickLink ecosystem.