Ben Williams
9 statements across 1 episodes · 5 bullish · 1 bearish · 1 people on the record · first statement Nov 6, 2022 by Ben Williams · said 11 times in 1 episodes since 2023 · across every show →
On the record as a speaker too: Ben Williams's record, appearances and statements → this page counts the times other people say the name.
Mentions by year
brought up most by Lenny Rachitsky (10), Christine Itwaru (1)
tap a year for its mentions
2023 11 mentions in 1 episode
Everything said about Ben Williams, oldest first
Nov 6, 2022 positive
Loop-based models are the most effective way to articulate growth strategy
“The best way I've found to articulate a growth strategy that fulfills the promise of usefully guiding the team's execution. It's the loop based model we forge as specific kind of documentation that, that I think is great around that. Being able to identify the…”
Nov 6, 2022
Effective growth engineers happily discard code and embrace imperfection
“The devs that really thrive in a growth context are the ones that are motivated by moving quickly, iterating to create measurable impact. They're not attached to their work. They embrace imperfection as part of the process. They happily discard their code, the…”
Nov 6, 2022 positive
Developer tool adoption requires integrating directly into workflows to protect flow
“Flow is just this incredibly important concept for developers and you want to strive to keep them in that flow for as long as possible. So the GitHub kind of pull requests are a great example of that. Someone can sign up for Snyk and they could theoretically b…”
Nov 6, 2022
Ben Williams: Vision statements must describe end states without mentioning products or solutions
“The vision is the Nirvana state that you aim to enable for your users and customers in five to 10 years. It's something that could equally be enabled by your competitors if you don't execute effectively or efficiently or quickly enough. You can always prefix a…”
Nov 6, 2022
Snyk structures core product teams by function and growth teams by outcome
“So most of the org is functional ownership based. There are a lot of really complex domains in the core product. So having that localized knowledge is important to be able to kind of own and run the code that team ship. The growth teams on the other hand are s…”
Nov 6, 2022 positive
Nov 6, 2022 negative
Assigning growth to core product teams without new processes usually fails
“Teams in growth need to work differently in some ways from R and D teams working on core product, assuming otherwise, and just giving growth responsibility to an existing team without working with them. To implement appropriate ways of working, I think it's a …”
Nov 6, 2022 positive
Williams: Product-led founders must intentionally design early acquisition loops into the product
“So if your acquisition strategy is product led, then understanding and being intentional about your early acquisition growth loops, I think is an essential founder's responsibility. Dedicating time there to design those loops into the product. It's key.”