Group items tagged

We also welcome and will actively help volunteers who want to write a GTD plug-in

Chandler shouldn’t be construed as an implementation of the GTD methodology or any other methodology

how to turn Goals into Next Actions

appreciate that there is a difference between the two

the GTD label actually scares people away.

people who knew about Chandler’s past association with GTD assumed they needed to subscribe to a particular way of doing things in order to succeed with the product

even more useful as that user pulls in other people to collaborate

We want happy users be successful evangelists for Chandler

web widgets that might be deployed in different contexts — iGoogle, Facebook, on an iPhone, etc.

widgets should be compelling to a new user who does not use the desktop, in addition to providing features that complement the desktop. Eventually, the widgets can be building blocks

misperception in the press

Being a CalDAV reference implementation is not a priority.

the Microsoft product with the most overlap with our design objectives is probably OneNote

web widgets (in the browser, on mobile devices and on the desktop)

not trying to be a GTD specific tool

Chandler’s philosophy is different enough from GTD that it would be misleading to call Chandler a GTD tool

Our best articulation of our core value to date is: Chandler is a way to manage and collaborate on ideas using: A List View built around the idea of the Triage Workflow A Calendar View Chandler Hub Sharing Service

the user problem we are serving is an emerging market

there isn’t a shared, public vocabulary to describe what we’re doing

Better product messaging so that people understand what ‘user problem’ we’re trying to solve and how we’re trying to solve it.

more ways to get data in and out

we will not be implementing CalDAV scheduling

We’re not looking to be a cheaper alternative to Outlook/Exchange. This means we’re not investing in support for free/busy-style scheduling. We’re not looking to be the ‘everyman’s’ version of Microsoft Project or Bug and Ticket-Tracking systems. This means we’re not investing in support for complex task and project management, e.g. task dependencies, tracking percent done, time estimates, robust support for assigning tasks, etc. We’re also not going to be implementing the GTD methodology.

Who column always displays ‘Edited by’ when an item has been modified by a fellow subscriber

depending on whether the message is Inbound or Outbound

event dates usually trump all other dates

alarm date

display something even if it’s the wrong thing some of the time

what’s a thought *about* a task

increasingly blurred

substance of the task

what’s a task

inspired by user feedback

starred items (furtively used as tasks)

users who regarded *everything* they put into Chandler as a task, thereby rendering a specialized “Task Label” superfluous

Modeling “Task-ness” well is critical to both workflow and usability in Chandler so rest assured that we will continue to work through it!