Teamwork

Teams of helpers ship features. Teams of co-owners ship products. The difference is whether each person believes the thing is theirs - and whether they have the tools to act on that belief without permission.

Compiled From Existing Signal

What's already implicit in the wiki:

• Co-ownership > recruited execution. From Ownership Drives Building: helpers leave; co-owners stay through the messy middle.
• Teach tools, then trust. Same page: the higher-return move is to teach the techniques and frameworks, then let teammates apply them to ideas they own.
• Boil lakes together. From Builder Ethos: the bar for completeness is set by the team's modal behavior. One person who cuts corners drags everyone to that floor; one person who boils the lake raises it.
• Modal communication style. From User Profile: concise > complete, tables

  prose, direct recommendations > option menus, "do it" = execute. A team that adopts these defaults moves faster.

Open Questions for Kevin

• What's a team you've been on that worked unusually well? What were the ingredients?
• What's a team that should have worked but didn't? What was actually missing?
• Do you prefer small teams of high-agency people, or larger teams with clearer roles? Why?
• How do you feel about consensus - necessary, overrated, situational?
• What do you do when a teammate is blocking the team without realizing it?
• Where does teamwork end and leadership / ownership begin?

Connections

---

Timeline

• 2026-04-21 | Page created as part of philosophies-batch-2026-04-21. Compiled from existing signal. Marked as needing deeper Kevin-specific input. Source: User, 2026-04-21