Kassen Qian

1. Know Your Team's Dunbar Number : Building real relationships both broadly and deeply within the company while not overextending. Engineers should have a keen and current understanding of not only what the work is, but also the decisions behind each product feature. Context is king for cross-functional teams.

You can ship product like Figma, with this Coda doc

Problem 2: The need for a central source of truth - A change in plans (whether it was a priority or a launch date) was impossible to coordinate across all of these documents.

Three consistent themes for identifying winning product organizations:

Fixed time, variable scope.

Early career years are painful. You feel like an idiot 98% of the time - lost, confused and insecure. I wish I had a cheat sheet of principles for my first job. So I put one together. Here are 20 things about building a career I wish I knew sooner:

0/ How to get started in Crypto - the Playbook. I have a lot of new followers, and a ton of web3 curious who have DMed me we. So I wanted to share some lessons learned from my 18-month journey going all in. These are notes I took for myself. 🐇 🕳 A multi-thread thread 🧵👇

4. Don't Confuse Micromanagement with Miscommunication: Contextualize why it needs to be done in the first place.

Most PR/FAQs are rejected, and the ones that pass often generate further questions that need to be answered. This is a feature, not a bug. Spending time up front to think through all the details of a product preserves your company's resources to build products that will yield the highest impact for customers and the business.