Finite and Infinite Games — James Carse's 1986 book — makes a distinction that cuts straight to the heart of how product teams lose themselves. A finite game is played to win; an infinite game is played to keep playing. Most product organizations speak infinite-game language (mission, vision, long-term value) while running finite-game operations — sprints measured by velocity, OKRs that terminate, roadmaps that 'ship.' The confusion isn't cosmetic. It quietly corrupts what you optimize for. Carse noticed that finite players need the boundary rules to stay fixed, because their identity depends on winning inside them; infinite players change the rules when necessary to continue the play. Dewey called something adjacent to this 'warranted assertibility' — the idea that knowledge isn't a destination but a sustained process of inquiry that you keep open. Put these together and you get a specific diagnosis for a common product pathology: the team that declares a problem 'solved' after shipping, rather than treating the ship as an opening move in a longer investigation. The feature closes the sprint. The question should stay open. Monday is a good day to notice which 'done' items on your board are really just paused inquiries you've agreed to stop paying attention to.

Pick one item your team marked 'done' in the last quarter — what would you discover if you treated it as the starting position of an investigation rather than the end of one?

Drawing from American Pragmatism / Process Philosophy — James P. Carse (Finite and Infinite Games, 1986) with John Dewey (Logic: The Theory of Inquiry, 1938)