Why product managers should frame every product task as a Job To Be Done

A Founder's Notebook

Edited excerpt from Replacing The User Story With The Job Story by Alan Klement:

The problem with User Stories as a framework to think about product is that they make too many assumptions and don’t acknowledge causality. When a task is put in the format of a user story — “As a [type of user], I want [some action], so that [outcome]” — there’s no room to ask ‘Why?’. You’re essentially locked into a particular sequence with no context.

A far better framework is what I call Job Stories, an idea from the really smart guys at intercom. Frame every design problem as a Job, focusing on the triggering event or situation, the motivation and goal, and the intended outcome: When _____ , I want to _____ , so I can _____ . For example, “when an important new customer signs up, I want to be notified, so I can start a conversation with them.”

View original post 182 more words

Featured Image -- 67

On Managing Developers

TechCrunch

I’ve been a software engineer, a novelist, a journalist, and a manager–and managing developers is easily the trickiest thing I’ve ever done. (Not the hardest. But the trickiest.) I don’t pretend to be an expert, or a great manager. But I can assure you I am someone who screwed up a lot along the road to being better. Here are some mistakes from which I have learned:

Just Because You’re In Charge Doesn’t Mean You’re In Control

The great irony of management is that the higher up you go, the less actual control you have. When you are but a humble coder, you make the computer do exactly what you want; when you’re a manager, you only hope that people understand what you want, and then trust/pray that they do it both correctly and in a timely manner.

Developers turned managers, especially “full-stack” (aka “dilettante”) developers like me, often have…

View original post 1,217 more words

Why Bitcoin Matters

Bitcoin will enter gaming big time

Marc Andreessen

A mysterious new technology emerges, seemingly out of nowhere, but actually the result of two decades of intense research and development by nearly anonymous researchers.

Political idealists project visions of liberation and revolution onto it; establishment elites heap contempt and scorn on it.

On the other hand, technologists – nerds – are transfixed by it. They see within it enormous potential and spend their nights and weekends tinkering with it.

Eventually mainstream products, companies and industries emerge to commercialize it; its effects become profound; and later, many people wonder why its powerful promise wasn’t more obvious from the start.

What technology am I talking about? Personal computers in 1975, the Internet in 1993, and – I believe – Bitcoin in 2014.

One can hardly accuse Bitcoin of being an uncovered topic, yet the gulf between what the press and many regular people believe Bitcoin is, and what a growing critical…

View original post 3,060 more words