Brotherly Love, Pure Communism, John Lennon and... OSS?

This article is worth amplifying...

A Matter of Focus...

I read an interesting article in New Scientist magazine recently.

The topic is MULTI-TASKING. I found some recognizable behavior in the article--both my own and others that I know. The article begins telling a story about talking on a cell phone while driving--not an unfamiliar topic to most. But I keyed in on some key messages. As we evolve technology so aren't we devolving patience and FOCUS.

Ever attend a Webinar and find yourself distracted by Email?
Ever attend a meeting and find yourself distracted by Blackberry?
Ever skim a document on your laptop while having a conversation with a colleague?
Ever meet with a peer or stakeholder and you find yourself :
(1) daydreaming?
(2) crafting your next dialogue in your head?
(3) wondering when this person will get to the point or mention the key phrase or position that they could have just TXTD U B4?
(4) Ever ask a employee to summarize a month's worth of work in a one-pager?
You know who you are...

The article in the zine indicated a human needs to repeat multitasked behavior 2000 time before we are productive (Remember the I Love Lucy with the conveyor belt of chocolate?) But there is a key difference...the behavior of corporate America is seldom repetitive and manufacturing oriented. We may need to build web screens, databases and develop log file solutiosn-- but rarely for the same customer spec with the same 4GL and version.

The point of this post is that there is clear behavior shift happening. I am not willing to stretch to the ADD debate but clearly cultural norms are shifting. We need repeatable process with customize results. (What does that mean?) We have access to and consume gobs more information than our grandparents did. We also need to react in seconds and not days. Gone are the times when we prepared proposals...met at the end of the week and a memo got distributed from a VP with the lightening speed of Inner Office Snail Mail. Decisions are expected at near real-time. Our new systems specs call for that behavior. Production = $, Production requires Thinking, therefore Think less=Produce More. We gain a breadth of information at varying levels of expertise and yet control with authority over less.

The modern day architect must be proficient in the Top 10 list of all the systems they support, know the customer and respond with a persona and tone that is customized to the audience, know and influence the IT strategy and roadmap, break ties in design debates and later justify the decision to the CIO with powerpoint not UML, and in a pinch debug a log file for a critical system with a memory leak.

And we wonder why its so difficult to hire good architects!
Take a breather, FOCUS, and skip that non-critical meeting to have a seat next to your developer and understand her perspective and insight.

Ask yourself when the last time you spoke and LISTENED to a system's REAL end-user?