Skip to main content

Home/ Chandler Project/ Group items tagged today

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Graham Perrin

Chandler Wiki : Scoble Follow Up Screen Shots - 0 views

chandlerproject.org/...ScobleFollowUpScreenShots

004250 event mini calendar preview schedule landscape today

shared by Graham Perrin on 24 May 09 - Cached
Graham Perrin

Chandler Getting Started Guide - Chapter 6: Triage Workflow and Stamping - 0 views

chandlerproject.org/...6-TriageWorkflow.html

shared by Graham Perrin on 22 Dec 08 - Cached
  • Today, many people do this by flagging emails or maintaining a task list. The problem is
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      This is a 'Getting Started Guide'. Keep it positive :) Talk of problems, behavioural patterns and visions should be elsewhere (the wiki is fine); simply refer from the Guide to the wiki.
  • have been added to the User Interface
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Comments such as this belong in 'What's new' flyers, or in release notes. People who are truly using this Guide to get started are unlikely to have an interest in project history or design changes.
  • has been improved: better native
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Whilst I'm getting started, I don't want to read that things were worse.
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

The Chandler Project Blog » Blog Archive » What is Chandler supposed to be... - 1 views

blog.chandlerproject.org/...dler-supposed-to-be-for-anyway

shared by Graham Perrin on 24 May 09 - Cached
  • wider range of tools
  • workflows are knit together via a wide variety of interoperation techniques
  • Chandler is meant to live in the middle of all these tools
  • ...26 more annotations...
  • pull all the disparate bits and pieces of information
  • into a contextualized, personal and shared ’source of truth’
  • the user interface we have today
  • contains vestiges of the ‘old’ way of thinking
  • proceed to lighten-up the app so that it’s a more accurate reflection of what Chandler is meant to do
  • focus on the quick item entry bar
  • the way to create new items in Chandler
  • see the messages you sent/received from Chandler
  • less of a “Mail Application”
  • credibility as a useful product
  • huge amount of effort and $$ we need to expend to be acceptable as a complete email solution
  • trust is important
  • move my group’s calendaring over
  • my own TODOs
  • Hopefully contact/address book stuff is next
  • Mail, iCal, Address Book
  • all separate, all highly functional
  • no clutter
  • the roles of the programs aren’t confused
  • interfaces aren’t cluttered up but there’s a heck of a lot of functionality
  • deceptively simple
  • Enterprise CRM’s are too complex and can only be used effectively when connected
  • fundamental link up between people and events, complex tasks and so on
  • I may be using ‘workflow’ differently
  • a loose framework of usage patterns
  • workflow-centric designs that bridge silos
1 - 4 of 4
Showing 20▼ items per page