Richard Yu is the Chief Product Officer at LucidLink, where he leads product strategy for the company’s cloud-native file system used by distributed creative and enterprise teams worldwide. Rising to prominence in the 2010s as an enterprise SaaS product leader, he became known for building mission-critical platforms that turn complex workflows into scalable, repeatable systems. He is widely regarded for his focus on outcomes over output, pushing organizations to measure success by customer impact rather than feature volume.
Previously, as Chief Product Officer at Formstack, he oversaw a no-code workplace productivity platform adopted by over 35,000 organizations across healthcare, financial services, and education. Under his leadership from 2022 to 2024, the company expanded its automation footprint across forms, documents, and e-signature workflows, helping customers digitize key processes end to end. He became known for driving cross-functional execution between product, marketing, and go-to-market teams to accelerate subscription growth and retention.
His career highlights include serving as Senior Vice President of Product at Litmus, where he led a four-year stretch of category leadership that earned multiple G2 and TrustRadius awards for product adoption and customer satisfaction. Earlier, as Vice President of Product Management and Head of Product Management and User Experience at Marketo, he guided one of the world’s largest marketing automation platforms through a period when thousands of B2B organizations relied on it to orchestrate multi-channel campaigns. Across these roles, he has spent more than 25 years building teams, products, and businesses at the intersection of SaaS infrastructure, marketing technology, and data-driven customer engagement.
Listen to the full conversation on Spotify
Listen on Apple Podcasts
Learn how LucidLink’s “invisible product” design philosophy connects to Marty Cagan’s high-integrity commitments framework and why the best product strategies are testable assumptions, not finished artifacts.
“We have users who experience it for the first time and kind of call it magic,” Rich Yu tells me. “So it is a bit magical, but obviously there’s no magic in technology. It’s just technology.”
He says this with the calm of someone who’s heard the word magic a hundred times from customers and has learned to take it as engineering validation rather than compliment. Rich is the Chief Product Officer at LucidLink, and his product makes cloud-stored video files act as if they’re sitting on your local machine. You open your Finder, there’s a mount point, and the files are just there. Editors on The Bear scrub through footage with zero latency. No syncing. No downloading. No waiting.
The company just won a technical achievement Emmy for this. And Rich’s philosophy for what comes next is to make the whole thing vanish.
Richard Yu has spent 25 years in product and marketing leadership—Formstack, Litmus, Marketo—before landing at LucidLink, a cloud storage collaboration platform headquartered in San Francisco with an engineering office in Sofia, Bulgaria. The company powers post-production workflows for major streaming shows and found its product-market fit during COVID, when media teams went home and discovered that collaborating on large files remotely was, in Rich’s words, “just not tenable.”
LucidLink solved that with streaming technology that caches intelligently enough to make remote files behave locally. The result is a product whose ideal user experience is one you don’t notice.
I ask Rich what “it just works” actually looks like from the inside—because from a product design perspective, aspiring to be invisible is a strange thing. We spend our careers building interfaces, flows, and experiences that demand attention. Rich is trying to do the opposite.
“We’ve really aspired to become invisible almost in the user experience,” he says. “I know that sounds ironic because as creators and builders of products, we always talk about what’s the user experience and what’s the UI look like.” He holds the irony for a beat. “But ultimately, if we’re thinking about the core value proposition—making large files stored in the cloud act and behave as if they were local on your machine—that’s something that should just happen.”
I tell him about the declining weekly active users problem. A previous guest worked on translation software and discovered that as the product got smarter, people used the app less. For most teams, that graph is a crisis. For utility products, it’s proof of success.
“Exactly,” Rich says. He gets it immediately. For LucidLink, the dashboard exists so administrators can manage permissions and check billing. But the actual value—the streaming, the speed, the absence of friction—that lives underneath everything. The best interaction is the one where a user opens a file, does their work, and never once thinks about the infrastructure making it possible.
We drift into strategy, and Rich surfaces the question that shapes how he approaches product decisions: Are we building outcomes, or are we building outputs?
He’s careful to credit the framework to others—”folks have blazed the path before me”—but the way he deploys it reveals conviction earned through experience. Early-stage companies need outputs. You need to ship the MVP, get it into market, learn. That’s the job. But once you have adoption and momentum, the game changes.
“The value is what is typically called the outcomes,” he says. “Are users really using your product? Are they happy? Is there a community that’s excited and engaged? And then ultimately those outcomes are also company or business outcomes. Is the company growing and successful as a result of the customers being successful?”
This connects to something else Rich is thinking about: the danger of high-integrity commitments.
I bring up Marty Cagan’s framework—the idea that product teams should avoid locking into hard delivery dates unless the situation is truly existential. We’re going to lose this customer if we don’t ship. The business is under threat. Those are the only moments where committing to a specific scope by a specific date makes sense.
Rich admits he falls into the trap himself. “As a product leader, I have accountability to my peers, to my executives, to kind of say, okay, we are gonna ship X by Y date,” he says. “I mean, that’s sort of one of the key anti-patterns in a way—that we are trying to constantly hit very specific dates with projects and initiatives that are not deterministic in that way.”
He catches himself. “But I fall into that sort of trap myself because, let’s face it, in the business world, if we don’t have some forcing functions to get things done, work can fill up the space that it’s given.”
The nuance matters. Deadlines aren’t inherently destructive. The anti-pattern is when hitting the date becomes the only thing you’re striving toward. When shipping replaces thinking. When the forcing function forces shortcuts in discovery, in design, in engineering.
“It forces maybe shortcuts to be taken in the discovery and exploration and validation of that threat,” Rich says. “And then shortcuts taken in terms of the design and the actual engineering of the solution against the threat.”
I push further: when you do make a high-integrity commitment, you need a team that believes in it. Not just one that executes against it, but one that owns it.
“That’s where breaking down the silos across the three functions to creating this true triad ownership is critical,” Rich says. “The ownership in that high-integrity commitment is not engineering by themselves. It’s not design by themselves. It’s not product by themselves. It’s really all three.”
The conversation turns to strategy and Rich offers what might be the most honest thing a product leader has said to me in 165 episodes of this podcast.
“Any strategy, no matter how polished or how baked or how succinctly articulated—they’re just a set of assumptions and hypotheses,” he says. “Hopefully backed by sufficient data and research. But ultimately it’s a thesis. It’s a thesis until you’ve actually achieved the outcome that the strategy is trying to point towards.”
I’ve watched the anti-pattern play out in real time. A product leader presents a strategy. The team pushes back. Instead of engaging, the leader hedges: Well, it was more of a thesis. A work in progress. They were hedging to save face. But Rich is saying something different—he’s saying all strategy is thesis, and that’s not a weakness. It’s how the work actually gets done.
“I’ll go on a limb that even the smartest strategists out there, the most successful folks in technology, are probably always just running one or two steps ahead of reality,” he says. “And they’re trying to really figure things out.”
He reaches for the scientific method. Hypothesize. Test. Verify. Iterate. It sounds basic—cliché, even. But his point is that the discomfort most product leaders have with strategy isn’t that they’re doing it wrong. It’s that they haven’t accepted the nature of the work. Strategy is a hypothesis you test with product decisions. The roadmap is the experiment. The outcomes are the data.
“I really believe that strategy is formed in that cauldron,” he says. “Product roadmaps are formed in that cauldron. And great products are built using that sort of scientific method.”
There’s one more thing Rich keeps circling back to, and it might be the connective tissue between the invisible product and the hypothetical strategy.
He describes how his teams do quarterly reviews to examine the assumptions they made when deciding to prioritize, build, and ship specific features. Did we achieve the user outcomes we assumed? Did those outcomes ladder up to the business outcomes they were supposed to?
“This is hard to do,” he admits. “Because you can always say it didn’t happen because we didn’t market it correctly, we didn’t sell it well. There are lots of mitigating factors. Nonetheless, I think it’s really important for all the product triads to hold themselves accountable.”
The anti-pattern is top-down mandates. When strategy flows from a single leader and everyone else is just executing, accountability evaporates. “Oh, we built this because Rich told us to do it,” he says, narrating the dysfunction. “And then if it doesn’t work out, it’s not anybody’s fault but Rich’s or Rich’s boss.”
He calls it demoralizing and dysfunctional. But the word that sticks with me is erodes. Trust erodes when leaders mandate without inviting the team into the hypothesis. It erodes when outcomes are never checked against assumptions. It erodes when shipping is the metric and nobody asks what happened after the feature went live.
Rich Yu builds a product designed to be invisible. He leads with a philosophy designed to be the opposite—transparent about what’s known, honest about what’s uncertain, accountable to what actually happens when the hypothesis meets reality. The invisible product. The visible strategy. The thesis that never pretends to be a conclusion.
