I must have tried as many different ways as I have had projects in my career. I don’t know what is the problem, but I just suck at consistently keeping people informed in the same way.
The bigger problem is that if I am not providing updates to other people than it is likely I am doing a bad job keeping track for myself. That really should be the central reason for doing it in the first place but without external accountability I’m just a lazy ass.
Today I had 5 minutes so I decided to write my boss an email just to give him a glimpse into where I am with things. I used this model:
I am working on 7 projects at the same time right now at different stages of development so I wanted to give him just a taste of what is going on where.
Project name and a one liner about the last thing I accomplished was the bare minimum I thought was necessary. Two bullets indicating what is going to happen next and what risks may be incurred seemed to be the additional two most relevant pieces of information.
Finally, the red/yellow/green flags are really just to make the one page scan-able so he can see that I have 2 projects on green, 1 on yellow and 4 on red and without my whining – but knowing what the issues highlighted are – see that there are blockers or resource problems making that happen.
How do you keep people up to date about what you’re working on on a regular basis? How do you provide project updates to your peers and bosses?
Today I watched a really great presentation by Peter Morville and Mark Burrell at UIE discussing search patterns. I have to admit that the only reason why I attended is because Peter was speaking and I always love what he has to say, because I very rarely have to actually design search interfaces.
After the presentation I actually started asking myself why the hell is it that I so rarely have to design for search behaviors. The reality is that oftentimes I’m designing for existing services where search is an existing capability and iterating it is never in scope.
One of the problems with that, which became more apparent to me after the presentation, is that treating search as a separate behavior from browse is really misguided. I thought about this problem before but could not quite articulate it very well until today.
Historically I had been taught and understood search and browse as distinct elements – which they are visually and from a UI elements standpoint – but from a behavioral perspective, they really are not, rather, they are part of a continuum. A spectrum of discovery behaviors if you will.
If we think, for example, about how faceted classification emerges in search interfaces and in browsing interfaces it becomes really clear how intertwined they are.
One of my questions to Peter during the presentation (which unfortunately did not get addressed but hopefully will be part of the UIE follow-up podcast) was if he had identified patterns of use of faceted search and if there were any emergent patterns that could help answer if faceted search is more appropriate for a particular kind of content or context — and when it might not be appropriate.
Faceted browse/search is a hot topic at work and I feel like it’s been historically a random requirement that ends up on a project brief because of process inertia. Someone saw it somewhere and thought it was cool so decided that it should be applied to the kind of content we are surfacing for our audience.
I have no good evidence to substantiate my hypothesis at this point (unless lack of examples in the wild is enough), but I suspect that for our content – namely video content, generally in the entertainment realm, frequently movies, series and other TV programs – having faceted search as a primary tool for discovery is really inappropriate.
How can I make a compelling argument that this particular pattern is not the right fit when I am not sure what is? I’ve seen it fail in usability tests but that only makes people try to fix it and improve it, not to try a completely alternate solution that might be appropriate. Any ideas out there?
Also, I’m not on a crusade against faceted search, I am just looking for ways to 1) articulate that there might be a problem picking this particular pattern 2) explore other ways to do it (both in the context of use and content I described). Any ideas are welcome.
Regardless, I think it will help me in the future to frame the scope of what I need to design for when dealing with content discovery behaviors by thinking about them in the browse-search spectrum. At least I expect that to give me a better argument to combat feature requirements void of context.
You know I’m not a fan of new year’s resolutions, but I am a fan of projects with accountability, so I signed up to participate in Project 52.
Per the project’s page:
Project52 is a personal challenge geared toward getting fresh content on your website. The goal is to write at least 1 new article per week for 1 year. Because we all know what it‘s like to procrastinate on our content. A website is not just a fresh design that can be uploaded to the web and forgotten about!
Let’s see how I do this thing!