Behaviors Book
“Know the problem you are solving” is about knowing the specific problem and for whom this problem exists. It isn't about knowing what solution a persona lacks but about truly understanding a persona's needs and challenges.
Over the past several years, as I’ve been helping teams and organizations improve their ability to deliver software products that are desirable, viable, and feasible, I have been experimenting with a Behavior Framework that has proven to be rather effective. And I’d like to share it with you in hopes that you find it useful and that you provide me feedback on your experiences with it.
My plan is to write a series of blog posts all related to the behaviors framework. Some of them will be about a specific behavior. Some of them will be about tools or techniques that help teams express one or more of the behaviors. Some of them will be my own experiences. And some will be damn near complete fiction.
A lot of teams have a backlog of some sort and some form of Kanban board — whether it is Jira, Trello, Monday, Asana, MS Project, or a bunch of post-its on a wall. These are all ways of making the work visible. But they aren’t enough.
There are two key aspects to making the work visible; what is the work and how is the work progressing.