Showing posts with label Ivory Tower. Show all posts
Showing posts with label Ivory Tower. Show all posts

December 21, 2016

The Pundits Know Sh*t

If you haven't seen any of the many videos flying around about everyone who said "Trump will never be president," then you should.

Presumably, these were people in the know--senior politicians and statesmen, experts galore including scientists and professors, news media, talk show hosts, comedians, and Hollywood stars.

Virtually none could even imagine him winning as they "promised" and "guaranteed" it and even swore they would leave the country otherwise.

But as we all now know, they were completely wrong and misguided. 

Similarly, in a book review today in the Wall Street Journal of "Public Intellectuals," the big mouth know-it-alls out there or what my friend's father used to call "intellectual idiots" failed to predict all the black swan events.

From the fall of the Soviet Union to 9/11, the Internet bubble and recession of 2001 to the mortgage meltdown and financial collapse of 2008, from the Arab Spring to Brexit...the pundits are all left looking like schmendricks!

Whether this is caused by personal biases, shortsightedness, herd mentality, or incompetence, the educated intellectuals just don't seem to be able to see around that next bend anymore than the rest of us. 

Moreover, because of their walled-off elite status, they are functioning and talking through loud speakers from their ivory towers rather than from the real man's world of everyday hardships and challenges. 

As I often tell one of my esteemed colleagues, it's not how often or how loud you say something, but how sincere it is. 

The pundits typically miss it (although they seem so smart when talking with 20-20 hindsight about what happened and why), and as contrarians already know, it typically pays to do the opposite of what the so-called experts tell you. ;-)

(Source Photo: Andy Blumenthal)
Share/Save/Bookmark

April 2, 2011

The Cost of Underestimating Technology


While research is important and I respect the people who devote themselves to doing this, sometimes they risk being disconnected from reality and the consequences associated with it.

From the Wall Street Journal, 2 April 2011--two economists calculated that "$1,700 is the benefit the average American derives from personal computers each year."

They call this the "benefit we get from computers above and beyond what we pay for them."

To me, this figure seems inconsistent with common sense and the realities on the ground.

In an information age, where we are connected virtually 24 x 7 and can download hundreds of thousands of apps for free, endlessly surf the internet, shop and bank online, get much of our entertainment, news, and gaming on the the web, and communicate around the globe by voice, video, and text for the cost on a monthly high speed connection, I say hogwash.

Moreover, we need to factor in that most of us are now information workers (about 20%) or depend on technology in performing our jobs everyday and earning our living.

Just yesterday in fact, the Wall Street Journal reported that more people work for the government (22.5 million--forget the private sector information workers for the moment) than in construction, farming, fishing, forestry, manufacturing, mining, and utilities combined!

Additionally, at work, we are using computers more and more not only for transaction processing, but also for content management, business intelligence, collaboration, mobility (and robotics and artificial intelligence is coming up fast).

Finally, technology enables breakthroughs--in medicine, energy, environment, education, materials sciences, and more--the impact of technology to us is not just now, but in the potential it brings us for further innovations down the road.

So is the benefit that you get from computers less than $5 day?

I know for me that's the understatement of a lifetime.

Apparently by some, technology continues to be misunderstood, be undervalued and therefore potentially risks being underinvested in, which harms our nations competitiveness and our collective future.

As much respect as I have for economics, it doesn't take an economist to think with common business sense.

Share/Save/Bookmark

February 26, 2011

The Lens of Leadership



I read an interesting article in Harvard Business Review (March 2011) called “Zoom In, Zoom Out” by Elizabeth Moss Kanter.


In the article, Kanter states that “the best leaders know when to focus in and when to pull back.”


The idea is that like a camera lens, we can choose to zoom in or out—and change perspectives in the way we see the world.


Perhaps, more importantly in my mind, it is the change in our perspective, that can change the way we, as leaders, behave across three dimensions—in handling ourselves as people, in decision making, and in problem solving.


I have summarized in the graphic (above) how the different perspectives of when we zoom IN and OUT manifest across those three critical leadership dimensions.


Overall, zooming IN and OUT with our leadership lens differs in terms of the impact of Ego versus Institution on how we view the situation; whether decisions are driven primarily by politics or principles; and whether problems get solved using quick fixes or long-terms solutions.


Zooming IN: helps us get into the weeds and deal with the dirty details. It involves dealing with people, process, and technology issues—up close and personal. Typically, to get a problem fixed—there are internal politics and some horse trading involved. Resolution of the problems on the ground are typically based on “who you are and who you know” and being structurally, situationally, and practically-oriented.


In contrast, Zooming OUT helps us see the big picture and focus on principles. It involves pulling back from the nuts and bolts to focus on the long-term strategy. Problems are treated as puzzle pieces that fit neatly into patterns. These are used to find “underlying causes, alternatives, and long-term solutions.” Sometimes appearing a little remote or aloof (reserved), at the extreme like an ivory-tower effort, the focus is clearly on the Institution and vision setting.


According to Kanter, “the point is not to choose one over the other, but to learn to move across a continuum of perspectives.


I would say that zooming IN is typically more like a manager and OUT generally more like a leader. But that a polished leader certainly knows when and how to zoom IN to take the management reins, when appropriate, and then zoom OUT again to lead in the broader sense.


One thing that I think needs to be clear is that those that can effectively build relationships and teamwork will show greater success whether zooming IN or OUT.


In the end, we can all learn to go along and get along as each situation dictates. As they say, “blessed be the flexible for they never get bent out of shape.”

Share/Save/Bookmark

July 10, 2010

Let Our People Think!

The leaders, planners, architects, and consultants in the proverbial ivory tower have become a poignant metaphor for what ails our organizations.

The elitist “thinkers” go into seclusion, come up with the way ahead for the organization, and then proclaim to everyone else what should be done and how it should be done—to be successful.

How nice. The “know-it-alls” tell everyone else (who obviously don’t know anything) how to do their jobs. Isn’t that empowering (not!)?

Harvard Business Review (July-August 2010) has a great article called “The Execution Trap” about the failure of the traditional strategy-execution model where executives dictate the strategy and expect everyone below to mechanically carry it out.

The strategy-execution model is analogous to the human body, where the brain instructs the body parts what to do. The executives choose what to do and the employees are treated as the brainless doers.

Typically executives take advantage of this separation of strategy and execution by patting themselves on the back for a “brilliant strategy” when results are good, but blaming the employees for “failed execution” when results come in poor.

Of course, in this thoughtless and thankless management model, employees feel disconnected, helpless, hopeless, and “invariably, employees decide simply to punch their time cards rather than reflect on how to make things work better for their corporation and its customers.” In the management model, employees are not true partners with leadership and they know it and act accordingly.

As a result, leadership turns to hiring outside consultants rather than working with their own organization, making what appears as “unilateral and arbitrary” decisions and this ends up alienating employees even further. It becomes a vicious cycle of alienation and hostility, until the entire capacity to strategize and execute completely breaks down.

HBR puts forward an alternative to this called the choice-cascade model, in which executives make “abstract choices involving larger, longer-term investments, whereas the employees…make more concrete day-to-day decisions that directly influence customer service and satisfaction.”

The metaphor here is of a whitewater river, where upstream choices set the context for those downstream. But the key is that “senior managers empower workers by allowing them to use their best judgment in the scenarios they encounter,” rather than just throwing a playbook of policies and procedures at them to follow dutifully and mindlessly—without application, deviation, or even emotion.

In the choice-cascade model, “because downstream choices are valued, and feedback is encouraged, the framework enables employees to send information back upstream” and as such employees play an important role in the initial strategy development.

The big difference in the two models is in the support that we can expect to get from our employees. In the strategy-execution model, where executives pit themselves against employees, you end up with employees that are alienated and do only what they have to do. In contrast, in the choice-cascade model, where executive and employees team to develop the strategy and then empower employees at every level to execute on it—responsibly and with a sense of ownership—everyone not only does what they are told, but they do what needs to be done to be jointly successful.

Which organization would you want to work in?


Share/Save/Bookmark

December 3, 2009

Federal Computer Week - Discussion of ITIL and EA

Services listed under ITIL and enterprise architecture models are
different in nature, said Andy Blumenthal, chief technology officer at
the Bureau of Alcohol, Tobacco, Firearms and Explosives, who did not
speak on behalf of the agency.

“When we talk about services in an EA context, we refer to those that
are used for mission and business purposes,” he said. “In contrast,
ITIL-type services are underlying support functions to the customer,
such as problem identification and resolution. An example of an EA
service versus an ITIL service would be a document management solution
versus a help desk or network management function.”

...

“Traditionally, architecture efforts have been notorious for being an
ivory-tower effort that results in shelfware,” Blumenthal said. ITIL
proponents also tend to be squirreled away in data centers and not
inclined to consult with architects.

A cultural shift is necessary, Blumenthal said. Enterprise architects
in particular must become more user-oriented if they’re going to stay
relevant in a changing technology environment, he added.

To read the entire article go to:
http://fcw.com/articles/2009/12/07/comparing-ea-and-itil.aspx


Share/Save/Bookmark

September 2, 2009

Are Organizational Values Valuable?

Many organizations have a value statement that identifies what traits are most important to them.

Organizational values are similar to an enterprise architecture in that the organizational values identify a type of target state for organization members to strive for and adhere to.

The purpose of value statements is to guide people’s behaviors, decisions, and interactions.

For example, one police department that I looked up has value statements around the traits of integrity, pride, service, and fairness. A city that I found had value statements for passion for community, integrity in work, and results through collaboration. A non-profit organization had values of leadership, integrity, excellence, and impact.

As you read the value statements they give you a sense of the organization in terms of who they are, or actually more like what they believe in.

But do they really—i.e. are organizational value statements something that people in the organization are aware of, understand, can locate, recite, or summarize, and moreover, are the values actually used to guide behavior?

Or are these value statements written by leadership, human resources, or some strategic planning function in the organization as an ivory tower effort, and then published in the organization’s glossy annual plan and/or on their website, but never really communicated with or adopted by the people in the rank and file?

The question is not posed in order to be cynical, but to genuinely ask: are organizational value statements “true values” or are they more marketing and branding glitz?

With few exceptions, I would challenge most to identify whether their organization even has a value statement, let alone what it is. Moreover, the last time, they thought of and considered the organizational values in making a decision or taking an action.

Then why do organizations have value statements?

Perhaps, organizations intuitively or through management best practices know that they need to have values, because they are genuinely important. Just like as individuals we have personal values (be they religious or otherwise) that “tell” us who we as human being are and guide our behaviors, so too as organizations, we need to identify the values that will be our “moral compass” and define our organizational identity.

The problem though comes when organizational values are developed as a “project”—a time bound task or “to do” for someone or some committee who researched it, developed it, and got approval on it; but not managed as a “program”—an ongoing endeavor and commitment to create awareness, educate, and even enforce the values through performance rewards and recognition.

Moreover, culture and peer pressure are vey powerful forces that drive employee behavior, whether they consciously are aware of it or not. So many values are indeed employed in day-to-day interactions, but they may not be explicit and they may not be the same values that are actually in the organization’s value statement. That is because the informal network and implicit values may actually be more prominent and powerful in driving people’s behaviors that the formal and documented one in the organization.

The key is for leaders to genuinely commit to the values and their use across the organization. The leaders need to provide for the values to be widely communicated (on wall hangings, pocket cards, employee reference guides, Intranet and so on) and they need to be referred to in periodic communications (speeches, announcements, broadcasts, meetings, etc.). They need to be living, breathing values that touch people daily (and obviate the implicit and unsanctioned ones).

Further, leaders need not only talk about the values, but also they need to exemplify them. In other words, leaders need to practice what they preach and lead by example using the values to drive decisions and actions in a way that is transparent to all.

What I learned when I developed user-centric enterprise architecture is that any ivory-tower exercises or development of organizational shelfware is by definition a failure, and therefore we need to treat all of our strategic planning and management functions as a real-world effort.

If we could do that with both EA and organizational values, it would be great to integrate them and use them to drive an explicit target state for both the performance and the business perspectives, as well as a human capital perspective of the architecture.


Share/Save/Bookmark

November 16, 2008

Enterprise Architecture Plans that Stick

I read a great little book today called Made to stick by Chip and Dan Heath about "Why some ideas survive and others die."

As I read this, I was thinking how very applicable this was to User-centric Enterprise Architecture in terms of making architecture products and plans that stick—i.e. they have a real impact and value to the organization and are not just another ivory tower effort and ultimately destined as shelfware.

The Heath brothers give some interesting examples of stories that stick.

Example #1: A man is given a drink at the bar by a beautiful lady that is laced with drugs and he finds himself waking up in a bathtub on ice with a note that tell him not to move and to call 911—he has been the victim of a kidney heist and is in desperate need of medical attention.

Example #2: Children Halloween candy is found tampered with and there is a scare in the community. The image of the razorblade in the apple is poignant and profoundly changes people’s perception of and trust in their neighbors.

Now, you may have heard of these stories already and they probably strike a deep chord inside everyone who hears them. Well, surprise—neither story is true. Yet, they have lasting power with people and are remembered and retold for years and years. Why do they stick, while other stories and ideas never even make it off the ground?

Here are the six necessities to make ideas have lasting, meaningful impact and how they relate to enterprise architecture:

Simplicity—drilldown to essential core ideas; be a master of exclusion; come up with one sentence that is so profound that an individual could spend a lifetime learning to follow it. In enterprise architecture, keep information products and plans straightforward and on point.

Unexpectedness—violate people’s expectations; surprise them, grab people's attention; I call this the shock factor. In architecture, we can use principles of communication and design (for example identify critical relationships in the information) to garner people’s attention, and help them come away with actionable messages.

Concreteness—use concrete images to ensure our idea will mean the same thing to everyone. In enterprise architecture, we can use information visualization to make information and ideas more concrete for the users (i.e. “a picture is worth a thousand words.”)

Credibility—promote ideas in ways that they can be tested, so that they are credible to the audience. An example is when Reagan was running for president and he asked Are you better off today than 4 years ago. This brought the message home and made it credible with voters in ways that pure numbers and statistics could not. For architects, the roadmap provided to the enterprise must be credible—it must have the level of detail, accuracy, comprehensiveness, and currency to garner acceptance.

Emotions--make your audience feel something; people feel things for people not for abstractions. In architecture and planning, we need to inspire and motivate people in the organization effectively influence, shape, and guide change. Remember, there is a natural resistance to change, so we need to appeal to people intellectually and also emotionally.

Stories—tell stories that are rich and provide for an enduring mental catalogue that can be recalled for critical situations in later life. Often, architects create isolated products of information that describe desired performance outcomes, business processes, information flows, systems, and technology products and standards; however, unless these are woven together to tell a cohesive story for the decision makers, the siloed information will not be near as effective as it can be.

These six principles spell out SUCCES, and they can be adeptly used successfully by enterprise architects to hone information and planning products that enable better decisions. These are the types of architectures that stick (and do not stink) and are truly actionable and valuable to the organization.


Share/Save/Bookmark