Geoff Charles
15 statements across 2 episodes · 5 bullish · 1 bearish · 1 people on the record · first statement Aug 6, 2023 by Geoff Charles · said 5 times in 3 episodes since 2023 · across every show →
On the record as a speaker too: Geoff Charles's record, appearances and statements → this page counts the times other people say the name.
Mentions by year
brought up most by Lenny Rachitsky (4), Sri Batchu (1)
tap a year for its mentions
2023 5 mentions in 3 episodes 2 per episode
Everything said about Geoff Charles, oldest first
Aug 6, 2023 neutral
Aug 6, 2023 neutral
Ramp freezes new features if teams breach quality and confusion metrics
“And if that number is a slightly elevated, we're basically saying you can't ship any new features. You need to fix these things. And so, yeah, there's just these types of controls, but basically trying to standardize across the teams. This is your percentage o…”
Aug 6, 2023 positive
Fast-moving teams should stress-test product decisions at GA, not pre-beta
“It's the difference between a beta and the GA that that's where we really get plugged in when we make the decision to go live. To the rest of the customer base and asking sales to start selling. That's where I'll really come in and stress test the hypotheses a…”
Aug 6, 2023 neutral
To protect deep work, check email once daily and Slack hourly
“Turn off notifications. Quit Slack. When you're doing deep work, check your emails once a day and just like literally go through them in like five minutes. They're off the times. Most of them are useless. Check Slack only at the top of the hour.”
Aug 6, 2023
Aug 6, 2023 positive
Anchoring on revenue targets and design prototypes drives extreme product velocity
“You're able to move super, super fast. If you have those two things in mind, the market and the revenue goal, because we're very revenue driven as a company and the designs that, that can really keep you anchored on, on what this could look like.”
Aug 6, 2023 positive
Aug 6, 2023
Shield new product teams from organizational chaos until product-market fit
“Small teams have a single threaded focus give them the resources they need to execute, big lofty goals, very tight timelines, and then like shield them from the chaos that is the rest of the organization. Basically don't bother them and don't even tell the res…”
Aug 6, 2023 positive
Interactive visionary prototypes shared via video walkthroughs dramatically increase product velocity
“Having designers spend more time creating more visionary prototypes and then sharing those out in videos. It just has just huge impact on, on how exciting work is and how excited the team are. And so just providing that clarity is massive. And I think just aga…”
Aug 6, 2023 positive
Aug 6, 2023 negative
Ramp avoids OKRs for product teams to prioritize direct roadmap velocity
“I stay away from them from a product perspective, because again, I want to focus on velocity, which is just output, which is your roadmap. But they could, they're pretty strong at more of the cross-functional side of things as well as the financial side of thi…”
Aug 6, 2023 neutral
Aug 6, 2023
Writing rather than reading is the best way to improve clear thinking
“You could read things and that's helpful, but I don't think that reading makes you necessarily think better. It makes you more wise. But the best way to increase your capacity to think is to actually do the thinking. And so that's where I see writing. If you'r…”
Aug 6, 2023 neutral
Charles requires public weekly goals and uses 1-on-1s only to unblock reports
“I basically have teams, all my directs post their goals every week. First thing Monday, the goal there is to also have them review each other's goals. I have a one-on-one template that I basically use to keep on track of how progress is being made. But I certa…”
Nov 29, 2023
Charles: Asking about a candidate's hardest challenge reveals agency and grit.
“I asked, what's the hardest thing you've ever done? And I asked that because working at ramp is hard. I want to understand like what hard means for them. I want to understand why it was hard. I want to understand how they overcame that difficulty, how they wor…”