Screen flows are often treated like admin tooling.

Screen flows are often treated like admin tooling.

Build it. Make it work. Move on.

But for a lot of users, a screen flow 𝘪𝘴 Salesforce. It’s the only interface they touch. The only place where the system asks them to do something.

That makes screen flows user-facing products, whether we treat them that way or not.

When flows are designed purely around logic, they technically work but still feel clunky. They interrupt the rhythm of the day. They create hesitation and quiet workarounds.

When flows are designed like products, something shifts.

The language feels familiar. The pacing makes sense. The experience matches how the rest of the system behaves. It feels like part of the work, not an extra task bolted on at the end.

That consistency matters more than most people realize. It sets expectations. It builds trust. And it quietly improves data quality because users aren’t fighting the experience.

At Lenticular, we think of screen flows the same way we think about any other product surface. Who is this for? What are they trying to accomplish? What should this 𝘧𝘦𝘦𝘭 like in the middle of their day?

𝗚𝗼𝗼𝗱 𝗳𝗹𝗼𝘄𝘀 𝗱𝗼𝗻’𝘁 𝗳𝗲𝗲𝗹 𝗹𝗶𝗸𝗲 𝗮 𝘁𝗮𝘀𝗸. 𝗧𝗵𝗲𝘆 𝗳𝗲𝗲𝗹 𝗹𝗶𝗸𝗲 𝗽𝗿𝗼𝗴𝗿𝗲𝘀𝘀.

https://www.linkedin.com/feed/update/urn:li:activity:7424451703032160256