Here’s something for UX’ers and people who hire and manage UX’ers: I’ve updated the UX Kit for 2019.

I originally created this document as a guide for product management and development teams that wanted to incorporate user experience research and design practices into their processes, but weren’t sure how to do it.

Over the past 10 or so years it’s grown to cover new areas, including:

  • UX strategy and content specialist roles
  • How UX contributors function in agile software development environments

The most recent update includes minor corrections, updated salary information, and the addition of other publicly-available UX resources.

The UX Kit is available under a Creative Commons Attribution-Share Alike 4.0 International License. Support open culture! You can learn more about this license here: http://creativecommons.org/licenses/by-sa/4.0/

Get the UX Kit

Here’s another resource that I wanted to share with the UX community: I’ve created a template and example for a daily research recap.

I created this template as a way to quickly communicate research results to team members and stakeholders on a daily basis.

One of the more important lessons I’ve learned during my UX career is that it’s vital for UX practitioners to keep team members and stakeholders informed and aligned. Another lesson I’ve learned is speed of communication is critical in this brave new world of agile/lean product ideation, design, and development.

As the people who glean insights from users and customers, we should strive to communicate our results quickly. At the same time, we need to be clear that daily recaps should not take the place of considered analysis.

This template is intended to communicate “here’s what we’re seeing after n user sessions” as opposed to “here’s the results, now go write stories and code to this information.” When you use it, you should ensure that this understanding is shared.

It’s set up as an email, but you could just as easily drop it into Slack, Jira Agile, etc.

The template is here: https://docs.google.com/document/d/1VqgNCnlwG89WVjI7wjK3SD_6AMhKGMjUhpBW6zkdYjs/edit

Like the UX project planner, I’ve licensed it under the Creative Commons Attribution-ShareAlike 4.0 International License. As a Creative Commons work, it’s yours to use, modify, adapt, etc. Please share it, improve it, and enjoy!

UX’ers, I made a thing for you: check out version 1.0 of an open source UX project planner / tracker template I’ve been working on for a few months.

I created it as a tool to document a user experience project in an efficient and collaborative manner, as well as give clients/stakeholders visibility and accessibility into various aspects of the project.

We all know the importance of setting appropriate stakeholder expectations, attaining alignment among contributors and stakeholders, and ensuring that your project schedule, process and data are accessible by all involved.

The planner / tracker is my solution to these challenges. It’s not perfect, but it functions well as a “one place for everything” resource. You can use it to frame up the project, identify contributors and approvers, lay out the schedule, design and document your recruiting and session protocols, record your project meeting notes, and even enter your raw notes from observations or interview sessions.

Best of all IMO, your client or stakeholder can comment inline on whatever section you need reviewed. Because I’ve utilized document headings and subheadings, you can do neat things like tell the client (via email, Slack, semaphore, etc.) something like:

Hi all, I’ve drafted the recruit request and put together an initial schedule of session times and dates.

Could you please review these and provide comments and/or approvals?

The recruit request is here:

http://docs.google.com/document/foo#heading=recruitheadingID

And the participant schedule is here:

http://docs.google.com/document/foo#heading=scheduleheadingID

Some other thoughts:

  • Leave the outline sidebar on. It’s incredibly useful for jumping between sections.
  • I’d like to add a section for initial data synthesis, and possibly analysis. I just figured getting this out in the world was more important than making it perfect.
  • As you read it, you’ll see references to other tools that I employ for project work, such as SlackGoogle DriveMoqups, etc. Obviously, use what works for you. But I highly recommend including direct links to any external resources in the project planner itself.

I’ve set permissions for this as “viewable, copyable and downloadable by all.” So you should be able to just save a copy to your own G Drive, or download it to use in Word. Fair warning, I make no claims regarding formatting fidelity outside of Google Docs.

I’ve licensed it under the Creative Commons Attribution-ShareAlike 4.0 International License. As a Creative Commons work, it’s yours to use, modify, adapt, etc. Please share it, improve it, and enjoy!

Here’s a short URL for the planner / tracker: http://bit.ly/uxprojecttemplate