we often experience situations where we are faced with overlapping problems
it looks a little like this ... 1/n
...except, often no one really takes the time to define the problem(s). Instead they brainstorm a bunch of ideas predicated on implicit perceptions of the problem(s)
the danger here, of course is that... 2/n
...if you bring three people together they might each see different things
One person sees one problem
One person sees two slightly overlapping problems
One person sees a parent problem with three child problems 3/n
Even when people see "the problem" they often have different perceptions of the problem
Sees the whole problem, but not sub-problems
Does not see the overarching problem
Sees it all
Note how this guides approaches... 4/n
Very different.
Oh, then we have another problem.
Every book says "DEFINE THE PROBLEM". Well..it is a moving target 5/n
And just when you think you've dialed it in, you bring a new person into the fray and they say ... 6/n
Which is all to say that the problem solution distinction is more like a mushy sandwich of nested problems, nested solutions, emerging problems, emerging solutions, expanding problem scopes, different perspectives, re-articulation, learning
It is hard. The End 7/n
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Funny thing is that I both agree some people are really good at certain things
AND I also believe that certain environments are conducive to elevating everyone such that one person being really good at something doesn’t mean much (though it is helpful)
1) PMs and designers focus on the "next thing" 2) Developers work on the "current project"
What's wrong with this?
Outcomes suffer, even if it feels more efficient.
Why ...?
2/n While seemingly more efficient -- it causes problems:
1) information loss 2) "resetting costs" during transfer of knowledge 2) distances developer from "the problem" 3) higher work in progress (WIP), less flow 4) split focus for PMs/designer
So...
3/n When thinking about starting together, teams get a little paralyzed because they somehow can't imagine all focusing on research/discovery
You have...
A: The status quo
B: How they imagine starting together
C: How it happens in practice
But there's one huge trap that I see teams fall into.
Start with the Why not the Way
Visualizing work is not the goal. ___ is the goal.
What do I mean?
1/n: Imagine if you emptied out all of your messy drawers just for fun. Well..
2/n: You would have succeeded in making a big mess and reminding yourself how messy you are, and how much you like collecting old subway cards, but you wouldn't have really achieved anything.
Now say you....
3/n: Started by committing to a powerful mission of making it easier to find things. You spend valuable time every day checking multiple drawers.
Or committing to a more public display of keepsakes and caring for your things better?