▶Max Schoening previously held roles as a product manager at Google and a design leader and engineer at GitHub. (Claims 2, 4, 5, 6)May 2026
▶While Schoening was at GitHub, the product review process prioritized functional demonstrations over written documents, following a "demos, not memos" philosophy. (Claims 1, 20)May 2026
▶At Notion, a cultural shift is underway where non-engineers, such as designers and product managers, are increasingly contributing directly to the production codebase using AI tools. (Claims 22, 39, 14)May 2026
▶Schoening has observed a decline in Figma usage among some designers at Notion, who are now opting for code-based prototyping to better simulate interactive AI experiences. (Claims 40, 58, 19, 28)May 2026
▶Schoening champions the trend of merging roles for PMs, designers, and engineers enabled by AI, yet he also cautions that this convergence could lead to a detrimental loss of deep specialists if not managed carefully. (Claims 22, 39 vs. 29)
▶He asserts that AI has made the initial 10% of any project 'effectively free,' but simultaneously observes that the overall quality and reliability of software has not improved in the last year, suggesting a tension between ease of creation and quality of output. (Claim 13 vs. 23, 55)May 2026
▶Schoening's core product philosophy is that great products have a 'tiny core' feature that is exceptionally good, yet he also predicts a return to broad, general-purpose software reminiscent of 1990s tools like FileMaker Pro, creating a contrast between focused excellence and broad utility. (Claim 54 vs. 47, 59)
▶He holds the contrarian view that 'knowledge work' functions as a form of universal basic income, implying many roles are non-essential, while his professional focus is on building sophisticated tools to optimize the productivity and workflows of these same knowledge workers. (Claim 18)May 2026
Not enough data for timeline
Sign up free to see the full intelligence report
Get started free