(skip to the first story for fast reading)
Why “MeetET”? Because we will unlikely market our new product as “email-task-manager”, that's both too long and doesn't address its advantage. “Efficacy” perhaps is a better name, but before a final name is decided, mentioning MeetET gives a context of how a properly marked product blends into daily life. MeetET is short for “Meeting, Email-Task manager”.
Why stories? Because life is a story but we always want to patch it up with use case here and use case there. Instead of skipping use-cases, I did WORK on use cases, but I am still losing the picture of overall user experience: the change good software can do to make life better. Thus the stories. The validity of use cases are less mysterious given stories. Also, having user story helps the design integrity. Disneyland is not designed by only analyzing user need and use cases, the general experience delivered is their advantage, their design is highly integral.
What is a good story? A story doesn't describe the user interface, nor the use case in traditional sense. It depicts user's life and user's software, how she uses it, in such a narrative style that everyone can understand. It is both terse and content-rich. Its target audience is not only developers but also users, to let them validate these stories. Notes to software developers are separate.
After lived in Beijing for three years, Alice went back to her hometown YY. She doesn't know where in the end life is going to take her to, but at least she is staying for the year to give birth to her baby, perhaps out of the feeble wish of not letting the child start with a drifting life such as hers. In a sunny afternoon shortly after her arrival, she find herself having tea with her old friends in college: Bob, Coral and a few others.
The reunion brought a lot of memories. Alice is not particularly the sociable type, not as much as her “party animal” friends, but having the advantage of studying in the medical school of her hometown, not far away from her own house, she did host parties at her home backyard, from time to time, and thus developed some decent relationships. Her usual party guests are of the calm type: researchers, classmates, professors, and even doctors of the hospital where she had the internship. After graduation, she stayed teaching in the college and worked as a lab assistant, eventually her home party become the center of attention of local health-care and medical professionals. That is, of course, all before she left YY for better career opportunities.
“So where do these people meet now?” “Nowhere. Since you left, they don't meet. They live their own lives.” Dissatisfied with the situation, Alice encouraged Coral, former lab assistant trained by Alice, to take the lead and start connecting people again, for Alice herself is unlikely to be in town in the future, thus cannot keep doing parties. Coral likes the idea, but asked Alice to help organize the first a few parties. Alice notes down that she should “re-discover” her old contacts and invite them to the next party, which Coral will host.
After the party, Alice started to discover her old contacts. Most of them gets to know Alice before “Linked-in” was invented, thus they are kept in Alice's private addressbook, which is in her old desktop computer. She had been using the Addressbook shipped with Windows 2000, actually, as a part of Outlook Express. There are a few categories, two of them Alice is interested in: “Professional Practitioners”, “College contacts”, “Classmates”. All college contacts should be invited, even the clerks may be interested to be in the party just to get connected to the professionals, and they may forward the invitation to others they know by work. The “Classmates”, are gradually turned into either “Professionals” or “College contacts”. “So, perhaps I should start by assigning new categories for each of the classmates.” Alice think, “but why bother? Since my job is not here, they don't make any difference to me now. But no, I still need a category for college contacts, because I may specifically batch mail to my old college contacts in the future: what if I decided to find a job in the college and settle down in YY?”
She is not using Outlook Express any more. A year ago she switched to MeetET. She knows she can save Outlook Express contacts to a file, and import it to MeetET. Alice thinks, instead of re-assign categories in Outlook Express, it would be easier to import all of them to the handy MeetET and update categories there.
So here is Alice at the beginning again. She imported “Professional Practitioners”, labeling them as “Medical & Health-care”. Why change the name? Since she left her home-town her contacts expanded. She now have all kinds of professionals, like lawyers, among her contacts. “Professional Practitioners” isn't as descriptive any more. Besides, she already has many labeled with “Medical & Health-care”. In order to tell locals from contacts of Beijing, who should not receive local event invitations, she made all imported contacts “Locality” to be “YY”: there is an option for that during importing.
The trouble comes when Alice imports “Classmates”. Many of them are also in the category of “Professional Practitioners” and “College Contacts”, but that's not the real problem, since MeetET knows to identify and merge duplicates. The real problem is most of them are no longer living in YY. MeetET has this message to Alice:
After all these, she add a todo list item: “When Coral arranged the party, I should send email invitation to my contacts to introduce Coral and her party. All my Medical & Health-care contacts in YY should be invited.” There is nothing more to do now. It's too early to write and send invitations. Alice needs to wait for Coral to fix the event. So Alice wrote an email to Coral:
I checked and found 150 contacts to send the party invitation to. After these years, I don't know how many still remember me, not to mention showing up in the party. Perhaps less than 10 would come. I should let you know my contact list, but consider many email address will not be valid any more, I will send the invitation myself and receive lots of returned emails. When I refined my contact list after the event, I will send them to you. I'll certainly make the audience aware the next party invitation is likely to be from you instead of me.
Please, when you fixed the time, location, invitation text, send them to me so that I'll make my invitations. Great to know you intend to volunteer the event organizer!
I'll be inviting my contacts, but don't forget to invite your own contacts too -- I don't know everyone in town!
The cafe is nicely decorated. Alice raise the concern that the cafe is a bit too stylish, and perhaps a bit too noisy. “I would hesitate before going there if I received the invitation”, said Alice. Together they figured instead of hosting the event in someone's home backyard, or a cafe, the “right” home of it should be in the college. And, to add a reason for guests to come, they should organize it a public presentation / training followed by a free-talk dinner party, in the campus. Event starts at 16:00, a professor or doctor would give a speech, inviting colleagues, medical workers in town and students, or, once in a while, patients too, with a poster as a invitation. The topics range from latest medical discovery, ways to work-around the buggy health insurance system, to how to sit properly in front of a computer.
1.Need to communicate with reputable speakers among her old friends about the idea of this speech/dinner event, get their support by having them host the speech the first a few rounds.
2.This event needs a name.
3.Find the school officials to let them agree and arrange conference rooms. This shouldn't be difficult, because the officials wants to look active to their superiors, thus needing events.
4.Do we need a hit success to kickstart? Yes we do, without a decent group of people already sticking together, if the first a few events ain't populated and successful, it would be hard to slow-start. To be that successful, there should be posters, announcement from school intranet, etc, for the first a few events.
5.Coral would need Alice's help in the first a few events, perhaps 3 of them, but Alice is likely to be giving birth in the next 3 months. Coral perhaps has to try to host the second and third event, or use other friend's help.
The two, sitting in a cafe, decided that Alice is to invite speakers for the first event and to prepare a list of potential speakers for Coral. The rest are all Coral's tasks. Alice is to be watching over the event on the email.
They went through all contacts, and find 16 people they should talk to about speaking. During this, Coral reminds a few people, who are also contact of Alice, but wasn't there on Alice's contact book. Alice entered these contacts with her phone, with label and “locality” too. MeetET allows returning to the previous context after the new contacts added.
Then, Alice use the email icon to start a draft email with the 16 star-marked people in recipients. She is not sure what to write there, so she wrote “need to discuss the event and invite first speakers”, and saved the draft as a task. The task, is, of course, to actually write the email, which she doesn't want to do in the cafe without her keyboard. She is not sure if she would address these people together or one by one, since there are senior professionals who better be addressed individually. But that's to be decided later.
073-8837268, email@example.com, Sales Representative, of Dongfen medical equipments.
When the email is gone, her mobile phone then entered a view where the recent activities are listed there. Of them, the most recent, is the draft email with 16 recipients. She put that to the new folder too.
Having observed all these, Coral asks if she could use the powerful new tool, and soon she got one, too.
(the story is not over, I have plots for the coming days. Perhaps these stories look complicated, but having been a groupware service provider for 8 years I guarantee I observed or experienced things in real life can be complicated like that, and we are not going to design a solution only to solve the simple issues, there are already tons there, and they don't offer enough capacity for busy managers or even normal users who are stuck with efficiency problem.)
Open questions to the ETs (the developer of this product):
1.What do you suppose user do with their notes above? It is not Alice'svv to do list (e.g. the last bullet point is only informative), nor others todo list on which Alice has to keep an eye. Would user write the notes in paper? Would user write them in mobile phone? I suppose paper or tablet is faster than a phone, so she would use a piece of paper if she is not with her tablet. In both case, what should user do with it? One guess, they process them into their project folder: one as a todo item; many as a watchlist item; the last one as a memo (or simply discard it). In this case, this note is an INBOX queue. The other guess is the user will never look at this note again, it fades away slowly, which is what happens now without a good MeetET software – Sould MeetET change that, or just cope with the facts?
2.Should user use a label or a folder on email-tasks? The mailbox folder, as a tree UI widget, is not a good idea on the small mobile phone screen, but its concept as a collection or queue still have its merits. A folder is naturally a collection, an exclusive container, a method to address efficiency (Getting Things Done carefully reviewed the necessity of containers), while a label is naturally informative. You can imagine all messages in a project forms a folder, while the label could be “To Do”, “Useful for later reference”, “I love it, it's a good idea, one day may fruit.” For an easy-to-use product, label is probably enough. For efficiency, perhaps we need Folders. I am still thinking and rethinking these concepts.
Alice added the following items to the newly created YYevent folder:
1.She already have a draft email to the 16 potential speakers. It's a todo item.
2.She wrote an email to suggest a name of the event, to Coral.
3.She has a watchlist item: Coral should send her the draft of first event's invitation.
4.She has a watchlist item: school official arrangement,, meaningCoral should forward her communication with the school official or the result of it.
5.She has a watchlist item: She should expect Coral to send her the poster design.
Now, she discard yesterday's project note, because everything on that note is now in her work-flow. She didn't set any alarm on these watchlist items, because Coral should set the pace. If she did, she will get related items back to her INBOX queue when things she expect did not take place.
Alice received an email from Coral, saying the school official is happy with the idea, and arranged location. When Alice file this email under YYevent folder, together with a terse “it's great” reply, she was offered if this new email is expected, along with her watchlist items. She choose to close the expectation “” with it.