[Design] Negotiation and Scheduling
mimi at osafoundation.org
Wed Dec 7 08:08:26 PST 2005
What if it was just text? No attempt by the system to capture
people's time preferences in any "official capacity." The main
difference would be, that since the conversation/negotiation was
captured as a "chat conversation" attached to the event, everyone
could see everyone else's scheduling issues and therefore respond in
more targeted ways.
ie. In the example where Tom replies to the meeting organizer that
Wednesday doesn't work, but Tuesday afternoon would be okay...and
then Joyce replies separately to the organizer that Wednesday is wide-
open for her, but doesn't mention anything about Tuesday...How would
Joyce's message have been different if she had been able to see Tom's
reply right on the event?
On Dec 6, 2005, at 8:35 PM, Davor Cubranic wrote:
> Mimi Yin wrote:
>> Below is just one proposal for how we might improve the
>> negotiation process for scheduling. Cutting down noise in
>> negotiation, while providing a flexible framework for important
>> discussion that's easy to keep track of.
> I love the fuzzy time frame workflow. This would leave Outlook
> eating dust big time.
> I have a feeling the user experience for crafting a response to an
> invitation will be the real challenge to design, precisely because
> of the kinds of situations like "Joyce said any time Wednesday was
> good for her, but didn't explicitly say Tuesday wasn't an option".
> Giving too many options for ranking or an elaborate UI to express
> preferences would make it a real pain to use. Maybe if a user only
> makes say three top choices, and then the response "behind the
> scenes" includes other possible times that would still work for the
> user, it would be easier to go into subsequent rounds of
> negotiation once the first round failed.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Design" mailing list
More information about the Design