If you ship features fast but users don't use them, it's usually one of two reasons:

The feature doesn't solve the core problem yet

Users can't tell how to finish the job with it

Tooltips and guides don't fix either one. They add more for users to read and more for the team to build.

Before you add anything, ask two questions:

What do we want users to do here?

What's stopping them?

Then remove what doesn't help them get there. In a complex workflow, that's usually a step, a field or an option nobody needed.

Remove first. Build only what's still missing. Build less. Get more of it used.

Just wrapped a product video for BuildAspect 🎬

They help builders and interior designers manage product selections together. The challenge was speaking to both audiences in one video, so we followed a single selection from the designer's spec all the way to the builder's install.

Lots of UI animation, and a client who cared as much about the story as the visuals.

Following one selection from the designer's spec to the builder's install is a smart way to serve two audiences in one story. How did you keep the UI readable on small screens: zoom in on the key fields, or rebuild simpler screens just for the video?