When I sit down with product leaders who’ve spent decades shaping how Silicon Valley builds products, I’m always struck by how their career arcs echo the very lessons they now teach. Michael Margolis is no exception.Michael started his career as an anthropologist, stumbled into educational software in the late 90s, helped scale Gmail during its formative years, and eventually became one of the first design researchers at Google Ventures (GV). For fifteen years, he sat at the intersection of startups and product discovery, helping founders learn faster, save years of wasted effort, and—sometimes—kill their darlings before they drained all the fuel.In our conversation, Michael didn’t just share war stories. He laid out a concrete, repeatable framework for product teams—whether you’re a PM at a FAANG company or a fresh hire at a Series A startup—on how to cut through noise, get to the truth, and accelerate learning cycles.This post is my attempt to capture those lessons. If you’re an early to mid-career PM in Silicon Valley trying to sharpen your craft, this is for you.From Anthropology to Gmail: The Value of Unorthodox BeginningsMichael’s path to Google wasn’t a linear “go to Stanford CS, join a startup, IPO” narrative. Instead, he started in anthropology and educational software, producing floppy-disk learning titles at The Learning Company and Electronic Arts. That detour turned out to be foundational.“Studying anthropology was my introduction to usability and ethnography,” Michael told me. “It gave me a lens to look at people’s behaviors not just as data points but as cultural patterns.”For PMs, the lesson is clear: don’t discount the odd chapters of your own career. That sales job, that nonprofit internship, or that side hustle in teaching can become your secret weapon later. Michael carried those anthropology muscles into Gmail, where understanding human behavior at scale was just as critical as writing code.Actionable Advice for PMs:* Audit your own “non-linear” career experiences. What hidden skills—interviewing, pattern-recognition, narrative-building—could you bring into product work?* When hiring, don’t filter only for straight-line resumes. The best PMs often bring unexpected perspectives.The Google Years: Scaling Research at Hyper-speedMichael joined Gmail in 2006, when it was still young but maturing fast. He quickly noticed how different the rhythm was compared to the slow, expensive ethnographic studies he had done for consulting clients like Walmart.com.“At Walmart,” he explained, “I had to compress these big, long expensive projects into something faster. Gmail demanded that same speed, but at enormous scale.”At Google, the prime “clients” for his research were often designers. The questions he answered were things like: How do we attract Outlook users? How do we make the interface intuitive enough for mass adoption?This difference matters for PMs: in big companies, research questions often start downstream—how to refine, polish, or optimize. In startups, questions live upstream: What should we build at all? Knowing where you sit in that spectrum changes the kind of research (and product bets) you should prioritize.Jumping to Google Ventures: Bringing UXR Into VCIn 2010, Michael made a bold move: leaving the mothership to become one of the very first design researchers embedded inside a venture capital firm. GV was trying to differentiate itself by not just writing checks but also offering operational help—design, hiring, PR.“I got lucky,” he recalled. “GV had already hired Braden Kowitz as their design partner, and Braden said, ‘I need a researcher.’ That was my break.”Working with founders was a shock. They didn’t act like Google PMs. “It was like they were playing by a different set of rules. They’d say, ‘Here’s where we’re going. You can help me, or get out of my way.’”That forced Michael to reinvent how he showed value. Instead of writing reports that might sit unread, he had to deliver insights in real-time, in ways founders couldn’t ignore.The Watch Party Method: Stop Writing ReportsHere’s where the gold nuggets come in. Michael realized traditional reports weren’t cutting it. Instead, he invented what he calls “watch parties.”“I don’t do the research study unless the whole team watches,” he said. “I compress it into a day—five interviews with bullseye customers, the whole team in a virtual backroom. By the end, they’ve seen it all, they’re debriefing themselves, and alignment happens automatically. I haven’t written a report in years.”Think about that. No 30-page decks. No long hand-offs. Just visceral, shared observation.Actionable Advice for PMs:* Next time you run a user test, insist that at least your core team attends live. Skip the sanitized recap slides.* At the end of a session, have the team summarize their top three takeaways. When they say it, it ...
Más
Menos
Jan 19 20261 h y 11 m