20VC: The 4 Phases of Effective Decision-Making, The No 1 Quality of Good Decisions, How To Approach Effective OKR Setting & Why Your Operating Cadence is the Backbone of Your Culture with Shishir Mehrotra, Founder & CEO @ Coda
Posted on 25th September 2020 by Harry
Shishir Mehrotra is the Founder & CEO @ Coda, the startup that brings all of your words and data into a flexible all-in-one doc. To date, Shishir has raised over $140M from some great names including Greylock, Kleiner Perkins, General Catalyst, NEA and Homebrew to name a few. Prior to founding Coda, Shishir spent an incredible 6 years at Google in a couple of different roles; first as Director of Product for Youtube Monetisation and then moving to Youtube VP of Engineering, Product and UX. Before Google, Shishir was with Microsoft for 6 years as a Director of Program Management. Shishir also serves on the board of Spotify.
To check out the incredible resources and core themes discussed by Shishir in the episode, check it out here.
1.) How Shishir made his way into the world of tech, came to be VP of Engineering, Product and UX @ Youtube and how it led to founding Coda?
2.) What is the No 1 quality of a good decision? How does Shishir think through reversible vs irreversible decisions? What are the 4 phases of decision-making? When should decisions be based on speed vs not? How can teams adjust questions to come to more productive outcomes?
3.) How does Shishir encourage debate and dissent within team discussions? How can leaders build deep trust with their teams? How can leaders create true democracy for idea sharing and meritocracy? Should ideas always be acted on immediately? What are the pros and cons?
4.) How does Shishir think about and evaluate his own operating cadence? How has this changed over time? How does Shishir approach time allocation? What have been his core learnings? How does Shishir divide his time between proactive and reactive tasks?
5.) How does Shishir approach OKR setting? What can leaders do to create aspirational and inspirational goals? How should goals be correctly communicated across orgs? How many OKRs should one team/person have? How should attribution across OKRs be given?