With reflection & reading, I've realized that I've pretty much always IMPLICITLY taken a systems approach to technology. I've been trying to frame what I like/do more EXPLICITLY in systems language ("finding points of leverage for tech")—but it's kludgy. Thoughts on what works?
-
Show this thread
-
For example, applying tech as... - A wedge on business process/operations - A shim to make (non-digital) user experience measurable and legible [increase user voice] - Coordination/collective action through friction reduction+better acquisition More on point, but confusing.
2 replies 0 retweets 7 likesShow this thread -
Replying to @allafarce
I find that the most difficult thing to explain about a systems approach is the effect of time scales. Most folks live in short-run product environments (that's how the incentives are structured, in part, because that's what's easy to measure)...and they can't see the beyond.
2 replies 1 retweet 8 likes
You can explain that there *is* a beyond, and that it's powerful (in a bounded-predictions way), and that what separates your work from the other style isn't what framework you're using. But they can't hear it.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.