Skip to main content

Home/ Chandler Project/ Group items tagged 004250

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

Chandler Wiki : Browser Design - 0 views

chandlerproject.org/...BrowserDesign

004250 hierarchy

shared by Graham Perrin on 25 Jan 09 - Cached
  • computer file systems
  • book stores and supermarket aisles
  • hierarchical org charts
  • ...57 more annotations...
  • Trees abound in
  • trees prevail
  • they clearly limit us
  • Semi-lattices are non-polar, where do you start, where do you end?
  • Reality and the human brain's ability to grok it are far more complex than a tree
  • dumbing down isn't always a bad thing
  • you don't really understand something unless you can explain it in 5 words
  • Let's improve on the software
  • too strict, too dry, too simplistic
  • browse the same data via many different trees
  • visual information mapping hasn't already taken over the world
  • that break the tree
  • brains ARE really really good at seeing relationships
  • linear doublethink
    • Graham Perrin
      Graham Perrin on 25 Jan 09
       
      Graham: review!
  • stop-motion semi-lattice building
    • Graham Perrin
      Graham Perrin on 25 Jan 09
       
      Graham: review!
  • extremely adept at looking at the same data and reorganizing it into different trees in rapid succession
  • in one file cabinet, on one bookshelf, in one way
  • forcing us to look at our data
  • semi-lattii
  • Challenge: Find balance between trees
  • distorts the truth
  • expressive but often not communicative
  • same data in as many different kinds of trees as they want
  • start at any point in the tree
  • same data, different perspectives
  • rotate the tree
  • visual cues that seemed to burst forth with meaning begin to feel meaningless, random, disorienting
  • "watch" in "slow-motion" or user manipulated motion
  • future Chandler may have a richer graphical interface
  • different tree organizations of the same data
  • Overlaying the visualizations
  • composite semi-lattice
  • richness of semi-lattii
  • feed it to users in a way they can easily understand: trees
  • All parameters set in the browser are reflected in the Search bar
  • Saved rules
  • better than limiting users to a single tree
  • better than overwhleming users with a semi-lattice
  • "dumbing down" the data for the user
  • avoid UI shock via information overload
  • present users with the full-force and complexity of their information in a way that is understandable
  • possible, even within the confines of the 2-dimensional
  • easily walk from one tree to another
  • breaking away from hierarchy and how people used to hierarchies of folder are coping
  • http://weblog.edventure.com/blog/_archives/2004/4/19/36468.html
  • the freedom and amorphous-ness of a search-centric navigation paradigm
  • a little built in structure
  • Dashboard view / triage workflow as a point of entry
  • search to get within range
  • navigate using contextual clues to find the exact item
  • fixed hierarchies present a workflow bottlenck
  • we know what topic to file something under, but we don't know where that topic belongs in the hierarchy
  • pilers never bother to file
  • something new comes along to screw up the hierarchy
  • unwieldy taxonomies with duplication and confusion
  • Sometimes we don't know what we're looking for until we see it in context
  • brain's ability to use environmental clues to remember things
Graham Perrin

Chandler Wiki : Top Usability Issues - 0 views

chandlerproject.org/...TopUsabilityIssues

004250

shared by Graham Perrin on 16 Jan 09 - Cached
  • Remove and Delete mental model
  • Data integrity issues (aka repo getting corrupted)
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      AFAIR a bug was fixed. Reference?
    • Graham Perrin
      Graham Perrin on 18 Jan 09
  • Spheres (way to group collections)
  • ...9 more annotations...
  • Focus Switching from one view to another should retain focus on the existing record [already reported] even if it would not appear in the new view.
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      To me, this behaviour feels extraordinarily weird. I need to understand the rationale.
  • drag items from the detail pane
    • Graham Perrin
      Graham Perrin on 16 Jan 09
  • anything that requires the use of Alt-keys
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      Choice of accelerator keys must be careful.
  • and doesn't offer a drag-and-drop alternative, is a problem
  • We need another button
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      I use: command-F to find, /f command-L for Lucene, /l
  • information between 'sync with self' PCs
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      I have half an eye on http://www.dotmobile.us/
  • corrupted way too often
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      Is this not fixed?
    • Graham Perrin
      Graham Perrin on 18 Jan 09
  • starting day of the week
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      Is this not done? (Related to locale, or choice of language.)
  • Define and clearly communicate what plugins (esp. third-party) can and cannot do
    • Graham Perrin
      Graham Perrin on 16 Jan 09
       
      +1
Graham Perrin

The Chandler Project Blog » Blog Archive » Chandler and GTD? - 0 views

blog.chandlerproject.org/...chandler-and-gtd

004250 GTD goal action knowledge

shared by Graham Perrin on 14 Jan 09 - Cached
  • GTD is not our single focus
  • Supporting knowledge work is. (Blog post coming soon.)
  • Chandler will continue to improve for GTD practitioners
  • ...6 more annotations...
  • 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
Graham Perrin

The Chandler Project Blog » Blog Archive » Andre Tries Out the New "Indepe... - 0 views

blog.chandlerproject.org/...he-new-independent-detail-view

Chandler GTD bucket item project list note task to-do VTODO 004250

shared by Graham Perrin on 14 Jan 09 - Cached
  • Andre keeps two items open all the time in separate windows:
  • The first is something he calls a “Bucket” item
  • The second is a GTD Projects List. Andre consults this list repeatedly throughout the day
  • ...1 more annotation...
  • saves me the trouble of having to leave the Chandler item I’m working with, find the GTD Projects List item, and then find my way back to the original item.
Graham Perrin

The Chandler Project Blog » Blog Archive » How do you use the Chandler Das... - 0 views

blog.chandlerproject.org/...you-use-the-chandler-dashboard

Chandler Desktop Dashboard reality 004250 collection item view wish event

shared by Graham Perrin on 25 Dec 08 - Cached
  • the Dashboard purely as a place to collect new notes, an “intake” area
  • collections must be initially kept out of the Dashboard
  • everything that could possibly be worked on right now needs to be in one place. I use the Dashboard to answer the question, ‘what should I work on next’. Every Collection is in the Dashboard
  • ...6 more annotations...
  • 30 going at a time
  • a cross-collection view of all their data where the could process items regardless of what collections
  • what’s new across all of your collections without having to click on individual collections one-by-one
  • Dashboard collection in Chandler
  • ground for experimentation
  • no way to view items that are in the Dashboard but not in any other collections
    • Graham Perrin
      Graham Perrin on 24 May 09
       
      I did wish for this in the early days, but in practice I don't require this type of view.
  • Graham Perrin on 25 Dec 08
     
    Interesting use cases.
Graham Perrin

Chandler Wiki : The Element Of Time - 0 views

chandlerproject.org/...TheElementOfTime

004250

shared by Graham Perrin on 23 Dec 08 - Cached
  • Attaching semantics to items
  • organizing data, needs to be a separate workflow
  • separate UI affordances
  • ...3 more annotations...
  • adding structure to data
  • Getting to the root of the problem with user scenarios
  • The question remains: How do people get an eagle-eye view of their data?
Graham Perrin

Chandler Wiki : Chunking Over Time - 0 views

chandlerproject.org/...ChunkingOverTime

004250 hierarchy

shared by Graham Perrin on 22 Dec 08 - Cached
  • no apparent rhyme or reason for the way in which sub-folders and sub-sub-folders are arrayed, making it difficult for you to predict as you navigate through each level of the hierarchy, what sub-levels will appear. It also makes the hierarchy as a whole, difficult to grok once you opened up a few branches of the hierarchy. You're presented with an array of relationships and no easy way to chunk them down
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Fine criticism of a hierarchy.
Graham Perrin

Chandler Wiki : Principles Of Grok - 0 views

chandlerproject.org/...PrinciplesOfGrok

004250

shared by Graham Perrin on 22 Dec 08 - Cached
  • Graham Perrin on 22 Dec 08
     
    Excellent UI stuff!
Graham Perrin

[chandler-users] Collections: Calendar view: presenting and setting aside overlays [was... - 0 views

lists.osafoundation.org/...003437.html

004250 confusion misinterpretation

shared by Graham Perrin on 22 Dec 08 - Cached
  • collection icon resembles any/all of the following: * a mobile phone * a clipboard * an envelope, in flight, dropping downwards Anyone: please, what _is_ that icon?
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      The icon with four interpretations from one person is in fact a fifth thing: a 'tag'!
Graham Perrin

The Chandler Project Blog » Blog Archive » OSAF's Next Steps - 0 views

blog.chandlerproject.org/...osafs-next-steps

004250

shared by Graham Perrin on 22 Dec 08 - Cached
  • Chandler succeeds at meeting the needs of users who are tracking ‘knowledge work’
  • Chandler is not oriented around calendaring per se or around a complicated task and project landscape with many dependencies
  • we want Chandler to be more viral. We want Chandler to be easy to explain to others. We want Chandler to be found in contexts where people are already spending time. We want Chandler to be
  • ...17 more annotations...
  • 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
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      CalDAV scheduling is just one aspect of CalDAV; see http://caldav.calconnect.org/standards.html
  • 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.
  • Graham Perrin on 22 Dec 08
     
    February 6th, 2008 at 11:17 pm
Graham Perrin

Chandler Wiki : Vision - 0 views

chandlerproject.org/vision

004250

shared by Graham Perrin on 22 Dec 08 - Cached
  • Custom Attribute
  • Custom Attribute
  • The Chandler Knowledge Worker
  • ...42 more annotations...
  • Information is the substance of their work and more information is the output of their work: Research, proposals, priorities, direction and decisions?
  • knowledge is gained and shared
  • how people actually work
  • (too) many interesting things
  • There's something wrong with the way data
  • doesn't flow between the tools we use to manage, process, organize our information
  • software should be modeled around information
  • technological barriers
  • too much copying and pasting
  • false assumption that information management tasks are binary
  • false assumption underlying most productivity software that information and the organizational structures needed to manage that information are essentially static
  • A lone email languishes for a long time in your Inbox and then all of a sudden, blooms into an unending thread which dies down
  • the thread is revived and mushrooms into a full scale project
  • Three weeks later
  • you barely give it a thought
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      I tend to find myself involved in: at one extreme, very many varied small tasks, which are recorded/archived then intentionally forgotten; and at the other extreme: projects about which thought extends months or even years later. Between the two extremes: for me, things are hazy.
  • the same workflow hiccups show up again and again
  • an information management environment with built-in workflows that mirror what people hack together
  • three basic workflows everybody seems to construct for themselves, regardless of what tools they use
  • varying degrees of complexity and automation
  • These three workflows however, need to exist independently of each other
  • no complicated rule-builder
  • push-button interface
  • always assume a need for iteration and change over time
  • Peeling the Onion
  • Allow Organization to Change and Flow
  • the entire gamut of organizational affordances
  • Tagging
  • Filing, Rules, et cetera
  • won't ever be asked to decide between them
  • turn it into a Custom Attribute
  • Add semantics to a Tag
  • Custom Attribute
  • Drag a Tag or a Cluster to the sidebar
  • a Cluster: a way to thread items together, a way to reflect dependencies
  • Group collaboration systems exist in parallel with personal communication tools
  • does not scale down to work for small groups
  • the majority of the significant emails we send are sent while still in a draft-state
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      This is very thought-provoking.
  • Future
  • a well-defined end-user information model
  • by modeling the user experience around how people work today and the substance of that work, we can be more than just another software tool and instead aspire to be a system for information management: A smarter way to work. A better environment for collaboration
  • We want Chandler to be able to talk to other applications
  • As we make Chandler's end-user information model richer, the number of interesting applications to talk to will increase. This is one of the many areas where we hope that people in the community will help increase Chandler's ability to talk to other applications
Graham Perrin

Chandler Wiki : Nutshell Cartoons - 0 views

chandlerproject.org/...NutshellCartoons

004250

shared by Graham Perrin on 22 Dec 08 - Cached
  • Information is the substance of their work and more information is the output of their work: Research, proposals, priorities, direction and decisions?
  • knowledge is gained and shared
  • how people actually work
  • ...17 more annotations...
  • (too) many interesting things
  • There's something wrong with the way data
  • doesn't flow between the tools we use to manage, process, organize our information
  • software should be modeled around information
  • fundamentally non-linear, non-binary nature of information work
  • processing and re-processing information to help you stay focused on the task(s) at hand
  • everything you can't and shouldn't be doing right now
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      These things are the ones that tend to throw in a 'pot' for later action.
  • many of the messages we send are really still drafts
  • too much copying and pasting
  • organized around your data and the semantics
  • not around which feature you used to create them
  • or over which transport protocol
  • Not around which file format
  • new Kinds of Items
  • designed to let you re-define what it means to be a PIM
  • personal definition of "Personal Information"
  • Extend the existing schema of Attributes
Graham Perrin

Chandler Project - Welcome - 0 views

chandlerproject.org

004250 item manage

shared by Graham Perrin on 18 Dec 08 - Cached
  • confluence
  • simple items which can interact and be managed with one other
Graham Perrin

The Chandler Project Blog » Blog Archive » Later sort improved - 0 views

blog.chandlerproject.org/...later-sort-improved

004250 triage alarm manage

shared by Graham Perrin on 24 May 09 - Cached
  • focus on a few at a time
  • items are “triaged”
  • Mostly, I just want to know what’s coming soon
  • ...3 more annotations...
  • the LATER section gives me that
  • I’m always assigning alarms to anything I don’t want to think about right now
  • my NOW section is much more manageable and I’m calmer
Graham Perrin

The Chandler Project Blog » Blog Archive » Laura Garcia says: "The single ... - 0 views

blog.chandlerproject.org/...-greatest-thing-about-chandler

004250 task to-do VTODO message e-mail event calendar

shared by Graham Perrin on 24 May 09 - Cached
  • confluence of tasks, emails, and appointments
  • simple items which can interact
  • managed with one other
  • ...1 more annotation...
  • separating these items into hard categories with totally different interfaces makes organization more, not less, difficult
Graham Perrin

CiviCRM Impressions (Mimi Yin) - FLOSSUsability - 0 views

flossusability.org/...CiviCRM_Impressions_(Mimi_Yin)

004250

shared by Graham Perrin on 24 May 09 - Cached
  • There is NO such thing as a right answer
  • Technologies change
  • many UI design principles are at least on the surface, directly contradictory
  • ...11 more annotations...
  • the same piece of software has to serve all
  • sometimes diametrically opposing
  • Different users have different needs
  • every specific environment in which the software is deployed is unique
  • users change
  • Don't assume people like, need, want to do things in a particular order
  • Don't overwhelm users with too many options
  • iterative process
  • iteratively trying different approaches
  • iterative explorations
  • direct user validation through interviews and testing
Graham Perrin

The Chandler Project Blog » Blog Archive » Next Steps for the Task Stamp - 0 views

blog.chandlerproject.org/...next-steps-for-the-task-stamp

Chandler item event message note task to-do VTODO triage star stamp label 004250

shared by Graham Perrin on 24 May 09 - Cached
  • don’t understand the point of marking some of my Notes as Tasks
  • proposal for extending the range of Item Kinds in Chandler
  • re-instate Tasks
  • ...10 more annotations...
  • extremely basic notion of Contacts
  • Reference Kind
  • don’t propose this instead of the Now/ Later/ Done system, but adjunct to
  • enter deadlines
  • see my tasks organized by those deadlines
  • and not necessarily a “to do” item
  • compilation of reference information
  • a configurable Chandler would be the most scalable solution
  • NOTES or REFERENCE feature would be useful
  • keep track of “reference material” that you want to keep around forever, just in case
Graham Perrin

The Chandler Project Blog » Blog Archive » What makes a Task a Task? - 0 views

blog.chandlerproject.org/...what-makes-a-task-a-task

Chandler item event message note task to-do VTODO triage star stamp label 004250

shared by Graham Perrin on 24 May 09 - Cached
  • Star isn’t so much a replacement for Tasks
  • trouble figuring out when to call something a Task
  • distinction between a task or todo
  • ...8 more annotations...
  • substance of the task
  • increasingly blurred
  • what’s a thought *about* a 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!
  • Graham Perrin on 24 May 09
     
    Tria
1 - 20 of 23 Next ›
Showing 20▼ items per page