UX/UI - Start here

If you’re new to UX

Design Systems

Design principles

Podcasts

Measuring, OKRs

Manager vs IC

Design Management

Friends of UX / Cross-functional areas

UX Writing

Engineering 101

Product Management

Business strategy

Research

Behavior Science

Data & AI

Data for UXers 101

Basics of machine learning

Generative AI

Brain Technology

Better meetings

Productivity

Jobs to be Done

Learning from experts

<aside> 💬 You might be familiar with user stories, perhaps from your product partners, you know those statements in JIRA tickets that read something like… “As a user, I want the ability to filter and sort all tables, and rearrange all modules on the dashboard”. I’m here to tell you there is a better way! Keep reading.

**There’s nothing wrong per se in a user story like that one, the problem is that it doesn’t tell you much about what the user wants to accomplish by filtering and sorting and rearranging.

If you focus on understanding the outcome the user wantsthe job to be done, you will find that there are multiple solutions available to you.

The first article below will be a good intro.

</aside>

Replacing the user story with the job story

Know Your Customers’ “Jobs to Be Done”

<aside> 💬 Now that you know the basics, the two articles below will help you learn how to write what JTBD people call job stories, they’re like user stories but more nuanced to include the context in which the user finds themselves in, and the outcome they’re trying to accomplish.

</aside>

Replacing the user story with the job story

5 tips for writing a job story

When Coffee and Kale Compete

If you’re looking to get more into the philosophy of JTBD I think this is a great book, the digital version is also free.

When Coffee & Kale Compete | Jobs to be Done Book — Revealed

← Previous

Using Aether

Next →

Documentation example

DS 1