Skip to main content

Home/ Chandler Project/ Group items tagged workflow

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
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 : Zero Point One Email 20060508 - 0 views

chandlerproject.org/...ZeroPointOneEmail20060508

shared by Graham Perrin on 22 Dec 08 - Cached
  • Pull down emails that have special headers
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      I don't understand this point.
  • one-time import of an Inbox
  • Proposed Plan
  • ...21 more annotations...
  • Email support for collaboration workflows
  • DnD from select email clients
  • One-time download of new mail with special Chandler headers
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Is this implemented in 1.0.2?
  • One-time download of new mail from select IMAP folders
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      My sense is that this is implemented in 1.0.2.
  • Set up IMAP server
  • allow users to move email from their existing email account to the desktop
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      In 1.0.2 I suspect that e-mail is copied (not (copied then deleted) moved).
  • provided they are on the same machine
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Can we more clearly define 'same machine'?
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      I see no requirement for IMAP client and Chandler Desktop to be on the same computer. IMAP client at computer A communicates a user-initiated move of a message to one of three Chandler Desktop-specific IMAP mailboxes. Chandler Desktop at computer B performs a one-time download from those three mailboxes.
  • early adopter, metrotechnicals as experimental email users
  • One-time download of new mail from IMAP
  • Basic message composition
  • Required features for supporting collaboration workflows
  • Reply, reply all, forward
  • Send and receive
  • rich text editing
  • draft, queued, sent, read, unread, needs reply, replied to, forwarded
  • email status column
  • Email threading support
  • overall clustering solution
  • stamping communications workflows
  • Features not targeted for 1.0
  • Drag and drop emails and attachments from other email clients
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
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 : Get Started - 0 views

chandlerproject.org/...GetStarted

shared by Graham Perrin on 22 Dec 08 - Cached
  • Collaborate on Notes and Events over Email
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      IMHO the e-mail capabilities of Chandler 1.0.2 require special explanation. Some explanations are offered within the FAQ, http://www.diigo.com/annotated/faf93764c6f6f5eb9a29268ad4b472de
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      The number and nature of the special explanations, criteria and limitations of e-mail in Chandler Desktop make me think that 'Email' its sub-headings, as currently presented in 'Get Started', should not appear in Get Started.
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      I suggest leaving references, from the Get Started page, to pages that are dedicated to: (1) an overview of e-mail in Chandler Hub and Chandler Desktop, and of limited communications with IMAP and POP servers; (2) using Chandler Desktop to configure an IMAP server, and understanding the workflows (in particular, the aspects that are one-way, periodic (Chandler Desktop sync) and incremental (the effect of adding messages to a Chandler-specific mailbox that was previously synced)); (3) e-mail in Chandler Hub; (4) e-mail in Chandler Deskop.
    • Graham Perrin
      Graham Perrin on 22 Dec 08
       
      Critically: the overview should contain no instructions on use; it should present, in pictures and in few words as possible, the current workflow and vision, plus maybe no more than one vision of the future.
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

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 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

The Chandler Project Blog » Blog Archive » Thoughts on where OSAF is heade... - 0 views

blog.chandlerproject.org/...f-is-headed-in-the-coming-year

shared by Graham Perrin on 24 May 09 - Cached
  • forget the In/Out email workflow thinking
  • In/Out should not be that special
  • don’t force me to think in the MUA model
  • ...1 more annotation...
  • reply/forward etc icons in the top bar should go
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 - 14 of 14
Showing 20▼ items per page