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?
-
-
This isn't bad, per sae. Folks need to be able to do as well as connect dots. Wicked effective teams try to join these up. The systems side doesn't need to be constantly engaged (usually).
-
Annnnnyway, a danger sign is when you put your "brain trust" over in a corner instead of having the connected to the actual product and exploring it's uses and users. Takes better-than-average managers to tolerate the uncomfortable questions that get generated.
End of conversation
New conversation -
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.