Here are detailed notes from the transcript:

Main Topics Discussed:

Work Process Philosophy: The intentional design of a "non-optimal" work process.
Balancing Art vs. Business/Process: The concern that rigid processes can stifle creativity ("kill the art").
Team Growth and Its Impact: Challenges and changes in work processes as a team expands.
Value of Unstructured Time and Ruminating: The necessity of allowing time for deep thought and exploration in creative work.
Current Work Model: Description of the speaker's team's loose, trust-based, remote work structure.
Critique of Formal Methodologies (e.g., Agile, Scrum): Analysis of their utility and their detrimental effects on certain types of work and talent.

Key Points and Arguments:

Intentional Non-Optimal Process: The speaker's team's work process is not optimally efficient by design.
Preserving Art: The primary concern, especially as the team grew during "The Witness" development, was that making the process too much like a "business" or a rigid "product-output" system would "kill the art."
Need for Creative Incubation:
- Creative work requires time to "figure things out" and make them "the best version."
- This can lead to periods where team members might not appear to be actively "doing much work" because the leader/developer is figuring out direction or people are ruminating.
Challenges of Scale: This loose approach becomes more expensive and problematic as the team gets bigger. While still practiced, it is done less today.
Current Loose Model:
- Characterized by a "very loose" structure.
- Occasional meetings, not many.
- Remote work (due to COVID, but also some remote staff existed before).
- High trust in hired individuals to execute ideas from start to finish with minimal feedback, primarily from a "couple teammates," not the speaker or the whole company.
Critique of Agile/Scrum and Similar Methodologies:
- The team does not use programming methodologies like Agile or Scrum.
- These methodologies are categorized as useful for specific types of people:
  - Individuals who would otherwise be "totally unproductive" (e.g., new to programming, struggle to focus).
  - Those for whom work is "just a job" (working for money, not deeply passionate).
- They provide "regularity and discipline and expected results" to improve output for these groups.
"Band Pass Filter" Effect: For highly capable or creative individuals ("people who know some math"), these rigid processes act like a "band pass filter." They filter out poor results but also filter out "amazing outlier results."
Value of Diverse Talent and Non-Linear Progress:
- Rigid processes prevent the inclusion of individuals who might be "bad at certain things" but "amazing at certain other things."
- They prevent the necessary time for "ruminating" which can lead to innovative breakthroughs that don't show "results on something for a long time."

Important Facts or Data Mentioned:

The Witness: A specific game project where the team started to become large, prompting concerns about process rigidity.
COVID: The pandemic is cited as a reason for current remote work, though some remote employees existed prior.
Agile and Scrum: Specific programming methodologies mentioned as examples of rigid processes the team avoids.

Conclusions or Recommendations:

The speaker's team intentionally avoids highly structured, "optimal" work processes (like Agile/Scrum) to foster creativity and artistic output.
They prioritize an environment that allows for individual rumination, diverse talent (even with eccentricities), and the emergence of "amazing outlier results," rather than standardizing performance for average productivity.
While recognizing the utility of formal methodologies for certain contexts (e.g., less experienced or less passionate workers), they reject them for their own creative endeavors because they believe such processes ultimately "forbid" and "select away" the unique contributions essential to their work.

Thoughts on Kanban, Scrum, etc - Jonathan Blow