A bit of a late write up, sorry about that I’m preparing to be gone for a week. The late update does mean we get to include what we got from Thursdays Docs meeting as well.
We need a clear component list
Defining components to get a clear line on what we wish to focus on for each iteration will help greatly. The definition of a component is not necessarily just a single page in the admin, but the flow of a task. An example f a component would be “media in posts”, this would be the flow of users adding media to their post, from wanting to add it till it’s actually in their post, and would thus mostly involve the media modal, but some users may not know how to properly work it and go to the Media page to upload first (that would mean we failed at making the media modal obvious/simple enough to use, and it should be looked into).
An important element to this is knowing what core components each of our components relate to (if we can use core components for things even better, no relationship table required, but I know some components can be too narrow). Drawing relations makes it easier for us to trac what we discover.
Started planning for how local user testing can be performed, utilizing WordCamps or Meetups.
Being able to do actual testing with users should help leverage the problem we have with online user testing services and time constraints. How to record the data was discussed, and we touched on what kind of setup that might be the most appropriate for this in regard to sitting on your own laptop or looking over shoulders of users. When possible using your own laptop is the most beneficial as it will allow you to do screen recordings. Emphasis on getting users permission was made, as privacy is important, and if they don’t want it publicly posted we need to respect that.
@kpdesign suggested we check with meetup organizers to see what they often find their users struggling with, we should check in with @jenmylo to find a good way to keep that dialogue flowing, since meetups are a reoccurring event it would be beneficial to keep in touch with organizers there.
There was some interest for following the interview route. I’m personally not familiar with it but will be looking into what others have been doing here to see if it’s a viable approach as well, the more data the better, I like data.
I will be gone for week 22, from Monday 26th of May, for mandatory military training, but I hope you’ll keep up the good work for Monday and continue the great work we’ve begun. What I’d like to see happen during next week is a draft of the component list