Skip to main content

Outlook Lists: Unexpected Behavior Problem

We ran into a problem recently in Outlook which has given me a new "pattern" I want to think about more. Here is the basic problem.
  1. Outlook stores the addresses from email messsages one "bucket" which it uses to autofill the TO field in new messages.
  2. There is a different "bucket" which contains all of your contacts.
  3. It makes sense that these "buckets" are seperate since you send and receive emails to and from more people than are in your contact list and it's nice to have those autofill when you are corresponding.Its like having a public area for the masses and then a subset of those emails which is private and includes friends, family and associates.
  4. There are ways of moving information from the autofill bucket to the contact bucket by right clicking on the address in the TO field and choosing ADD TO CONTACTS. This moves from public to private.
  5. It's also makes sense that your contact list should show up in the autofill. If contacts is a subset of everyone and everyone is in the autofill then contacts should show up in the autofill.
What about deleting? This where we ran into our problems.

One of our staff created two distribution lists in her contacts. They had similar names (which might not be the best practice but that isn't germane to our discussion). After a while, one was no longer needed and she deleted it. To follow the same mental framework from above, she deleted it in the "private" area. This however, left it untouched in the "public" area.

The next day, unbeknownst to her, she sent out a 300 person email to the wrong distribution list. This was because the "wrong" one, the one she deleted, still came up in the autofill area. However, since it didn't appear in her contact area, she didn't even know she needed to be on the lookout for such a problem. She (naturally) assumed it was gone. In fact, the only way we determind what had happened was after an hour of sleuth work was to start to type in the autofill and could the number of options which appeared and compare it to the number of options in her contacts. When there was an extra one in the autofill, we figured out what had happened. As you might guess, that was not our first action.

I like the two bucket approach but perhaps there needs to be tighter integration.

Possible Patterns to make this more user friendly
  1. When something is deleted in contacts it is deleted in the autofill (but not necessaruly vice versa)
  2. When deleting, present an option to delete in autofill as well.
  3. Have a more visible way of editing your autofill list. Currently, I don't believe there is any way to view the list of emails in the autofill, let alone edit it. I don't mind this being hidden and the autofill happen "by magic" by in situations like this it might be better to demystify it.
Random thoughts from a tech incident.
Labels:

Comments

Post a Comment

Popular posts from this blog

Creating Stories and Tasks in Jira: Personas and our Software Development Team

Part of the CI/CD Development Series The next step is developing who is on our hypothetical development team. Given that it has a React front end and ColdFusion as the Server Side language, I came up with the following personas, all of which have their own needs and considerations for our development environment. I've listed all the jobs that need doing, not the people involved since, even on a small team or a team of one, these "hats" are all worn by someone, even if it's the same person. Personas for our Project Dev Ops Coordinator - The person responsible for smooth and accurate deployments CF Developer - The person responsible for the API and fulfillment code development and maintenance. React Developer - The person responsible for the front end development Database Coordinator - The person responsible for the schema, data, up time and, presumably the testing databases used by the developers. Lead Developer - The person responsible for coordinat...
6 comments
Read more

As the Dev Ops Manager, I need to start planning our CI/CD release process

Part of the CI/CD Development Series Once we have our Deployment Diagram designed, we need to figure out out to get from here to there. If the end point is the appropriate server environment, the starting point is the developer with his/her hand on the keyboard. These steps take place on a variety of machines, within various process and can changes based on what files are checked in or not. At the moment, we've only created the early basics as seen below. The Beginning of our Deployment Activity Chart Even though there is quite a long way to go there are some elements which we have already been determined. For example We have determined the broad strokes of our technology stack. This is going to be React on the front end and ColdFusion on the server side. We have determined that we are going to be using linting on both the CF and React paths. CFLint for the CF and ESLint for the Javascript We have determined that we are going to be formatters - CFFormat for CF and...
Post a Comment
Read more

As the Dev Ops Coordinator, I need to set up our git repo into several branches with the appropriate permissions for each one

Part of the CI/CD Development Series The core of every CI/CD process is the code repository whether it be Git, Mercurial, SVN or whatever. The general idea is that it allows multiple developers (or whomever) to access your code in the appropriate way in the appropriate level. This can either be the ability for anyone to pull an open source project but not write to the repo directly or full access to a developer on your team to create branches, push to master or anything that needs doing. For our project, we're using git although the hosting provider was up for discussion between Github, Bitbucket by Atlassian or CodeCommit on AWS. We decided to go with AWS for two reasons. 1. We are going use other tools in AWS as part of the build so we decided to keep it all together. 2. We needed to solidify the ins and outs of using IAM for the process. Basic Steps Create the Repo Create the branches we need Use IAM to apply the appropriate permissions to each branch and to set up ...
1 comment
Read more