Roeder: Unfocused technical advisory board meetings impose productivity taxes on engineers
Alex Roeder · a16z Podcast | Building the Right Technical Advisory Board · Jan 2, 2019 · at 13:24
Alex Roeder shares advice on managing technical advisory boards effectively without wasting internal engineering resources.
0:00 / 0:26exact quote · 26.0s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“So, if you're gonna invite other people in, be really sure that they know why they're there, and I mean, I sit on these things to help. There's really no other reason. Like, it's fun and interesting, and you meet smart people, and you're there to help. So when people have questions I'm around, and the other people are around. That's why they do these sorts of things. But otherwise, make sure it's not a tax. It's like, oh, it's a presentation I have to give to a bunch of people to get approval for my thing, and I'm just wasting time. So that's kind of, that's one way I think you can fail.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Alex Roeder
Roeder: Technical advisory boards work best with informal, real-time problem solving
“I think the best arrangements are when The company's just super, not too formal about it, just really honest about what they're, instead of, oh, I have a technical advisory board meeting next week, oh shoot, like I have to think of an agenda, and now it's a to…”
Roeder: Evaluate potential technical advisors by presenting real company problems
“Giving, you know, giving real problems that you're working on is, is one of the better ways to understand, get real signal from people, so I would just talk about where the company is, why you're putting it together, some of the things you're grappling with, a…”