Episode

Key Takeaways

David Allen expresses long-standing frustration with the current state of GTD software, noting a decline in functionality.
Eric Mack proposes five principles for productivity software design to guide developers toward more effective tools.
Effective GTD software should support user thinking and avoid extraneous features that create friction.
Productivity relies on robust systems, competent personnel, and tools that prevent information 'leaks.'

David Allen invited Eric Mack to discuss five principles for productivity software design, hoping to inspire developers including those at Microsoft.
Allen noted a loss of features in Microsoft 365 compared to Mack's earlier GTD software, e-productivity, calling it a step backward in functionality.
The conversation aimed to address Allen's long-standing frustration with the lack of ideal GTD software, despite the apparent simplicity of its core concepts.

Eric Mack recounted his early 1990s work on Personal Information Managers (PIMs), including sketching desired software screens in 1995.
Mack attributes the complexity of creating effective GTD software to developers overlooking its common-sense principles.
Early software like ActionEar failed by attempting to encompass the entire GTD system while competing with resource-rich companies like Microsoft.
By 2019, seeing no significant PIM advancements, Mack decided to share his designs publicly for others to build upon.

Many GTD software developers lack a deep understanding of GTD, leading them to create tools that try to 'do the thinking' for the user.
Eric Mack's e-productivity software assisted thinking by flagging projects without next actions with a 'frowny face,' facilitating user engagement.
The goal is to design digital systems that support, rather than perform, user thinking, with early examples like ActionEar's 'post-it note' feature categorizing tasks.
A two-minute timer was utilized for project brainstorming, demonstrating a system designed to support thought processes.

The discussion introduces the concept of a 'broken workplace' where environments and tools dictate thinking, often imposed without user input.
Tools are defined as personal and user-chosen, like a favorite pen, contrasting with imposed systems.
Software is criticized for adding numerous extraneous features beyond its core benefit, which 'muddies the value' and introduces friction.
Speakers emphasize personal responsibility in tool use, asserting that tools like PowerPoint or Outlook should not shape one's thinking.

The conversation highlights that both effective organizational systems, such as Kanban and Agile, and competent people are crucial for producing quality products.
A poor system or inadequate management of a good system inevitably leads to negative outcomes.
The GTD methodology is presented as a functional system that requires active and functional utilization by individuals to achieve high productivity.

Eric Mack outlined five principles for productivity software design: 'no leaks,' 'attract more than repel,' 'all features must pass the 30-60-90 test,' 'add productive value, not burden,' and 'would David Allen or Eric Mac use this.'
The first principle, 'no leaks,' requires a trusted system that prevents inherent, unannounced information leaks, such as a project lacking a defined next action.
Early GTD applications evolved from enforcing action creation to using simple 'sad face' or 'happy face' indicators to guide users non-intrusively.
These visual indicators, initially temporary, were retained due to positive user feedback, with one CEO noting their utility in highlighting project needs to employees.