My status updates – what can I improve?
I've been posting weekly status updates for awhile now (since August 9, 2009). I think they're an important part of communicating exactly what it is I (and the rest of the Firefox team) am working on, and how things a progressing. Not only that, it's a great way of getting unsolicited feedback, as I often get comments on these posts. So from my point of view, these posts been a great success.
But I want to know if I can improve them. What would you like to see more of? Or less of? Should I have more detail on what I've achieved, or what I'm planning? Should I be less whimsical? Should I reflect more on the past week, and on life in general? Should the format be altered? Should I include more pictures of cute kittens with amusing captions?
No related posts.
Join Mozilla
Recent Posts
- Status Update: AppTabs, Extension Manager UI
- Status update: Extension Manager UI, App Tabs
- Status update: Extension Manager UI
- Status update: Extension Manager UI, Tab matches
- Status update: Extension Manager UI Redesign
Categories
- Firefox (34)
- House Redesign (1)
- Mozilla (45)
- Personal (5)
- Status Update (13)
- Taskfox (4)
- Ubiquity (9)
Twitter: theunfocused
- @jinghuaz see http://tcrn.ch/d2tIBw
- @johnath indeed, my Run-DMC knowledge is mostly limited to their "walk this way" remix (which is epic, ftr)
- @damons welcome. enjoy our complementary earthquakes.
- @socialspace because then there'd be no film to make (seriously: weak plot device)
- @IBA52 aren't they at the mercy of the insurance companies though? and they'll cut costs where ever possible
- @dietrich if i could expense it, i'd seriously consider it!
- @dietrich all these photos of thai food are making me very jealous
- @AirNZFairy yes, i wish i could take my partner to queenstown for labour weekend - we've been working too hard lately and need a break :)
- @ChristianSonne i'm gonna hold you to that
- @neilio i noticed that too - you can collapse every subsection except "Store"
February 24th, 2010 - 17:35
I always see your status updates on twitter, but the post title is always so generic… just look at it, even your website says “related posts: status update, status update.” Maybe you could add a few key words to the title?
Thanks.
February 24th, 2010 - 22:09
I think some more personality to the updates would be nice. Adding what you like or dislike about the project, some more background, things that could change with your work, whether you liked doing it, about working with your teammates, etc.
February 25th, 2010 - 02:08
Mitcho’s suggestion is spot-on. Perhaps the date in the title, instead of/as well as keywords.
February 25th, 2010 - 03:48
We (the planet team) should really put together a “tips” blog post or something on what we’ve seen works best for folks who want to use a blog as part of their communication.
Some things I’ve personally noted over the years:
1. Repetitive titles stink as noted by other comments. Theming titles, or prefixing with “status update:” work better. Mention what it’s about in the title. People scan those to decide if they will read or skip in their feed reader or on planet.
.
2. Include links to bugs, wiki’s, and other places for folks to join/participate/feedback when applicable. It goes a long way.
3. Avoid just mentioning a bug # without mentioning what it is in context. Also avoid mentioning a bug and not giving the bug # (or link to bug). Don’t tease
4. Some more technical discussion can sometimes be much more engaging and encourage readership. Robert O’Callahan demonstrates this more than anyone these days.
5. Pictures get folks attention. Screenshots, mockups, wireframes, cats (preferably in humorous situations with captions).
6. Demo’s get peoples attention (see hacks.m.o, aza’s blog has that tendency).
I read virtually every mozilla dev blog for the past several years. I’ve also noticed on my own that the above really makes a distinction between what gets passed over and what gets read/commented on.
Just my $0.02