Content
@
0 reply
0 recast
0 reaction
July
@july
Most problems are encountered long after the seeds of the issue has been planted. Sometimes "fixing" the problem is less about fixing the symptom and more about root causing and discovering the underlying reason why its happening. It feels like often you start really by understand the issue at hand, at a deeper level before you can even think about what's going on. However, root causing the issue is, but honestly, a lot of work -- because if forces you to really understand in as much as depth as possible today (with today's knowledge) why something is happening, and you constantly have to doubt what you know, and go deeper into the problem. And sometimes you don't have enough time, or don't have enough domain knowledge, or we collectively as a species don't know of a better way to solve that problem yet
2 replies
8 recasts
58 reactions
July
@july
I even think about this with my kids, as an example -- when I encounter an issue, it's less about fixing my kids behavior, but I try to think about what are the circumstances and situations that led to A) this type of behavior emerging and B) what did I do, or someone else in their vicinity to do to make this behavior normal over time C) what can I start doing today to change this behavior in the long run. The short term thinking way is to just yell at them, but the long term way is to change myself and my behavior I kinda think similarly about designing or engineering as well, coincidentally.
2 replies
0 recast
31 reactions
tyler ↑
@trh
Along human lines, I've found it's helpful (and interesting) to ask, "what contributed to this?" It's multidimensional and looks at the system over time rather than merely its end state. One of my notes in "Difficult Conversations" (the book I stole the contribution language from) says to "trade contexts, not just conclusions".
0 reply
0 recast
1 reaction
