Showing posts with label Silos. Show all posts
Showing posts with label Silos. Show all posts

May 6, 2014

How NOT To Interview For A Job

So I am at this place of business this evening, and I overhear someone trying to apply for a job.

Note, I feel bad for the guy who is looking for extra work, but the interview just is going all wrong. 


- Easy-Smeasy - He asks "What is the easiest part of the job?" Ugh, didn't sound exactly like he was looking for a challenge.


- Keep your head down - He exclaims, "And never do someone's else's job!" What about helping where the help is needed?


- Great facilities you got here - He ends with, "And when I work here, my kids are really going to love coming to use the facilities here all the time!" Not exactly, a what will I do for you strong ending. 


I didn't get to hear the whole interview dialogue, but this was enough to get the idea about some things not to do in an interview. 


The funny/sad thing was, I think this gentleman really thought that he was going to get the job after all. ;-)


(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

March 30, 2014

Corporate Dictators Gone Wild

Interesting book review in the Wall Street Journal on Moments of Impact--corporate strategy meetings. 

The authors, Ertel and Solomon, see strategy meetings as critical for "to confront radical challenges" "cope with fast-changing threats", and confront competition.


It is an opportunity to:


- Look at the big picture, including industry trends.


- Hear different points of view from as broad array of perspectives as possible (instead of the usual "fences and silos" that prevail in corporate life).


- Decide to change ("Creative Adaptation") or to stay with tried and true strategies ("stick to their knitting").


The book reviewer, Adrian Woolridge, though has a much more skeptical view of these strategy sessions calling them "dull, unstructured time-sucks" and "more often than not, [they're] a huge waste of time":


Why?


- They produce "airy-fairy nonsense."


- Rather than abandoning the corporate hierarchy, the sessions anchor in "status hierarchy."


- Outside strategy "experts" brought in "are nothing more than cliche-mongers."


- The "games" are silly and non-impactful.


- Often rather than strategic conversations, we get "lazy consensus," where decisions are driven by senior managers with a bone to pick or a reorganization in mind.


What's the truth...as usual, somewhere in between these 2 states of idealism and cynicism.


We can choose to take planning seriously to bring people together to solve problems creatively and gain consensus and commitment or we can use strategy as bogus cheerleading sessions and to manipulate the sheep to do what the seniors already know they want.


If we really work as a team to press forward then we can accomplish great things through our diversity and strength, but if strategy is nothing but corporate dictators gone wild, then the cause is already lost to the competition.


(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

November 23, 2011

Where The Biggest Nuts Rise To The Top


According to an article in Mental Floss (November/December 2011) engineers at the Advanced Dynamics Laboratory in Australia in 1996 researched how to mitigate The Muesli Effect, which describes the paradox of how, for example, cereral in boxes tend to separate with the smaller stuff lingering on the bottom and the large chunks rising to the top. This is the opposite of what you'd expect in terms of the larger, heavier pieices falling to the bottom--but they don't.

This is also known as The Brazil Nuts Effect, because the largest nuts (the Brazil Nuts) can rise to the top. While in physics, this may be good, in leadership it is not.

With leadership, the Muesli Effect can led to situations where cut-throat, unethical, workplace operators push their way to the top, on the backs of the masses of hardworking individuals. Unfortunately, these workplace "bullies," may stop at nothing to get ahead, whether it means manipulating the system through nepotism, favoritism, outright descrimination, or political shinanigans. They may lie, steal, kiss up, or kick down shamelessly disparaging and marginalizing coworkers and staff--solidying their position and personal gain, which unfortunately comes at expense of the organization and it's true mission.

Some really do deserve their fortune by being smarter, more talented, innovative, or hardworking. In other cases, you have those who take unjustifiably and ridiculously disproportionately at the expense of the others (hence the type of movements such as 99% or Occupy currently underway). This corruption of leadership begs the question who have they "brown-nosed," what various schemes (Ponzi or otherwise) have they been running, how many workers have they exploited, suppliers squeezed, partners shafted, and customers and investors have they taken advantage of.

Countless such ingenious leaders (both corporate and individual) rise by being the organizations false prophets" and taking advantage of the "little guy"--some examples whether from Enron, WorldCom, HealthSouth, Tyco, MF Global, and Bernie Madoff are just a few that come to mind. These and other examples can be found as well in government, non-profit, as well as educational institutions.

Interestingly, the Museli Effect occurs when you shake a box vertically. However, if you rock it side-to-side, then you reverse the effect and larger and heavier pieces of chaff fall to the bottom letting the precious kernels rise to the top.

This is similar to organizations, where if you focus on working horizontally across your organization and marketplace--on who you serve, your partners, suppliers, investors, and customers in terms of breaking down barriers, building bridges, and solving customer problems--then the real gems of leadership have the opportunity to shine and rise.

In the age of social networking, information sharing, collaboration, and transparency, the reverse Muesli Effect can help organizations succeed. It is time to stop promoting those leaders who build empires by shaking the organization up and down in silos that are self-serving, and instead move to rewarding those that break down stovepipes to solve problems and add real value.

(Source Photo: here)


Share/Save/Bookmark

March 12, 2011

Civic Commons-A Lesson In Sharing

Love this concept on Civic Commons that was presented at the Gov 2.0 Summit (2010) and is now becoming a reality.

Presented by Bryan Sivak the CTO for DC--Civic Commons is about governments collaborating and building technology once and reusing multiple times, rather than reinventing the wheel over and over again--a critical enterprise architecture principle.

Governments have similar needs and can share common solutions--products and projects--for these.

A number of successful examples:

1) DC and San Francisco building Open 311 (which I wrote about in a prior blog).
2) Minnesota building a $50 Million Unemployment Insurance System and then sharing it with Iowa who implemented it at less than 1/2 that.

Some initial products that have been committed:

1) White House IT Federal Dashboard
2) Track DC (Operational Dashboard)
3) San Francisco Master Address Database Geocoder
4) New York Senate's Open Legislation Application

And more will be coming...all of which can be used and improved upon.

It is great to see so many state governments collaborating--across the Nation--from Seattle to LA, Boston, San Francisco, NY, and Chicago. Moreover, they are coordinating with the Federal Government, as well as with supporting organizations, such as OpenPlans, Code For America, O'Reilly Media, and more that are helping with coordination, facilitation, and support.

This is another great step in breaking down the silos that separate us and becoming more efficient in working together and learning to share what can benefit many.

Share/Save/Bookmark

September 24, 2010

The User-centric Web

David Siegel has written a book called “Pull: The Power of the Semantic Web To Transform Your Business” (Dec. 2009).

The main idea is that businesses (suppliers) need to adapt to a new world, where rather than them “push” whatever data they want to us when they want, we (consumers) will be able to get to the information we want and “pull” it whenever we need it (i.e. on demand).

Siegel identifies three types of data online of which less than 1% is currently visible web pages:

  • Public Web—what “we normally see when searching and browsing for information online: at least 21 billion pages indexed by search engines.
  • Deep Web—includes the “large data repositories that requires their internal searches,” such as Facebook, Craigslist, etc.—“about 6 trillion documents generally not seen by search engines.”
  • Private Web—data that “we can only get access to if we qualify: corporate intranets, private networks, subscription based services, and so on—about 3 trillion pages also not seen by search engines.”

In the future, Siegel sees an end of push (i.e. viewing just the Public Web) and instead a new world of pull (i.e. access to the Deep Web).

Moreover, Siegel builds on the “Semantic Web” definition of Sir Tim Berners-Lee who coined the term in the 1990s, as a virtual world where:

  • Data is unambiguous (i.e. means exactly the same things to anyone or any system).
  • Data is interconnected (i.e. it lives online in a web of databases, rather than in incompatible silos buried and inaccessible).
  • Data has an authoritative source (i.e. each piece of information has a unique name, single source, and specified terms of distribution).

While, I enjoyed browsing this book, I wasn’t completely satisfied:

  1. It’s not a tug of war between push and pullthey are not mutually exclusive. Providers push information out (i.e. make information available), and at the same time, consumers pull information in (access it on-demand).
  2. It’s not just about data anymore—it’s also about the applications (“apps”). Like data, apps are pushed out by suppliers and are pulled down by consumers. The apps make the data friendly and usable to the consumer. Rather than providing raw data or information overload, apps can help ready the data for end-user consumption.

All semantics aside, getting to information on the web is important—through a combination of push and pull—but ultimately, making the information more helpful to people through countless of innovative applications is the next phase of the how the web is evolving.

I would call this next phase, the “user-centric web.” It relies on a sound semantic web—where data is unambiguous, interconnected, and authoritative—but also takes it to the next level, serving up sound semantic information to the end-user through a myriad of applications that make the information available in ever changing and intelligent ways. This is more user-centric, and ultimately closer to where we want to be.


Share/Save/Bookmark

June 25, 2010

TEAM: Together Everyone Achieves More

People are selfish; they think in terms of win-lose, not win-win. The cost of this kind of thinking is increasingly unacceptable in a world where teamwork matters more than ever.

Today, the problems we face are sufficiently complex that it takes a great deal more collaboration than ever to yield results. For example, consider the recent oil spill in the Gulf, not to mention the ongoing crises of our time (deadly diseases, world hunger, sustainable energy, terrorism).

When we don’t work together, the results can be catastrophic. Look at the lead-up to 9-11, the poster child for what can happen if when we fail to connect the dots.

A relay race is a good metaphor for the consequences of poor teamwork. As Fast Company (“Blowing the Baton Pass,” July/August 2010) reports, in the 2008 Beijing Olympics, the USA’s Darvis Patton was on the third leg of the race, running neck and neck with a runner from Trinidad when he and his relay partner, Tyson Gay, blew it:

“Patton rounded the final turn, approaching…Gay, who was picking up speed to match Patton. Patton extended the baton, Gay reached back, and the baton hit his palm. Then, somehow it fell. The team was disqualified.”

Patton and Gay were each world-class runners on their own, but the lack of coordination between them resulted in crushing defeat.

In the business realm, we saw coordination breakdown happen to JetBlue in February 2007, when “snowstorms had paralyzed New York airports, and rather than cancel flights en masse, Jet Blue loaded up its planes…and some passengers were trapped for hours.”

Why do people in organizations bicker instead of team? According to FC, it’s because we “underestimate the amount of effort needed to coordinate.” I believe it’s really more than that – we don’t underestimate it, but rather we are too busy competing with each other (individually, as teams, as departments, etc.) to recognize the overarching importance of collaboration.

This is partly because we see don’t see others as helping us. Instead we (often erroneously) see them as potential threats to be weakened or eliminated. We have blinders on and these blinders are facilitated and encouraged by a reward system in our organizations that promotes individualism rather than teamwork. (In fact, all along the way, we are taught that we must compete for scarce resources – educational slots, marriage partners, jobs, promotions, bonuses and so on.)

So we think we are hiring the best and the brightest. Polished resume, substantial accomplishments, nice interview, solid references, etc. And of course, we all have the highest expectations for them. But then even the best employees are challenged by organizational cultures where functional silos, “turf wars”, and politicking prevail. Given all of the above, why are we surprised by their failure to collaborate?

Accordingly, in an IT context, project failure has unfortunately become the norm rather than an exception. We can have individuals putting out the best widgets, but if the widgets don’t neatly fit together, aren’t synchronized for delivery on schedule and within budget, don’t meet the intent of the overall customer requirements, and don’t integrate with the rest of the enterprise—then voilá, another failure!

So what do we need to become better at teamwork?

  • Realize that to survive we need to rely on each other and work together rather than bickering and infighting amongst ourselves.
  • Develop a strong, shared vision and a strategy/plan to achieve it—so that we all understand the goals and are marching toward it together.
  • Institute a process to ensure that the contributions of each person are coordinated— the outputs need to fit together and the outcomes need to meet the overarching objectives.
  • Reward true teamwork and disincentivize people who act selfishly, i.e. not in the interest of the team and not for the sake of mission.

Teamwork has become very cliché, and we all pay lip service to it in our performance appraisals. But if we don’t put aside our competitiveness and focus on the common good soon, then we will find ourselves sinking because we refused to swim as a team.


Share/Save/Bookmark

March 28, 2010

How To Brainstorm and Not Tempest

Thinking “out of the box” is fundamental to free us from the prevailing status quo. Brainstorming can enable us to tackle problems creatively and open up new possibilities for the future.

An Insight piece from Psychology Today (February 12010) called “[How To] Brainstorm” by ChiChi Madu points to some of the typical challenges with brainstorming and offers a new approach to it.

The challenge: “A typical brainstorming session can involve clashing personalities, uneven contributions, hurt egos, and hours of precious work-time wasted.”

When people come together to brainstorm, there are two things going on—one is the brainstorming and the other is the interaction between the people. And if the interaction is not collaborative and is dysfunctional because of the pervasiveness of functional silos, groupthink, competitiveness, or power politics, then the brainstorming and overall problem solving is going to suffer as a result.

Let’s face it, productivity is in large part of function of people’s ability to pull together rather than push apart!

A new approach: One way to work more collaboratively comes from an approach called “brainwriting,” by Peter Heslin. Brainwriting works as follows:

  • Write—Everyone writes an idea, in a different color pen on a piece of paper and passes to the next person.
  • React—Each person reacts to the idea they received and adds their own idea—“feeding off the others.”
  • Review—Once the slips of paper have about five ideas, they move to the center of the table for “systematic consideration of each.”
  • Select—Everybody lists their favorite ideas and the most popular ones are selected.

What is great about brainwriting is that everyone has a chance to contribute ideas, to have their ideas considered by others, and for them to consider the ideas of their peers carefully and thoughtfully. Moreover, brainwriting actually facilitates ideas to be incrementally built and improved on by having group members feed-off of the idea they received, rather than just hastily dismissing them or talking over others. Finally, since everyone has to put ideas and reactions to ideas down on paper, no one can just “sit it out” and not participate—and the more earnest the participation, the better the brainstorm will be.

People can innovate amazing things, solve problems, and really work together constructively when: the underlying process facilitates information exchange, collaboration, and the freedom to say what they really think. If we encourage and facilitate more brainwriting activity and other constructive engagement between people, we will be able to take on and resolve the ever larger and more challenging issues facing our organizations and society.


Share/Save/Bookmark

February 9, 2010

Why The Customer Should Be The Center Of Our Professional World

It’s intuitive that organizations should manage oriented to serve their customers, because it’s the customers who keep them in business. Yet, in the name of “shareholder value,” many organizations continue to put short-term results at the forefront of their decision-making and this ends up damaging the long-term success of the organization to the detriment of its owners.

Harvard Business Review, January-February 2010, in an article called “The Age of Customer Capitalism” by Roger Martin states that “for three decades, executives have made maximizing shareholder value their top priority. But evidence suggest that shareholders actually do better when firms put the customer first.”

The author continues: “Peter Drucker had it right when he said the primary purpose of a business is to acquire and keep customers.”

Clearly, we serve our customers in the service of our mission. Our mission is why we exist as an organization. Our mission is to provide our customers with products and/or services that satisfy some intrinsic need.

The equation is simple:

Shareholder Returns = f (Customer Satisfaction)

Shareholder returns is a function of and positively correlated with customer satisfaction, as HBR notes. If we serve our customers well, the organization will thrive--and so will the owners—and if we do this poorly, the organization will die—and the owners will “lose their shirts”.

The problem with concentrating exclusively on stock price is that we then tend to focus on short-term returns versus long-term results, and the shareholder ends up worse off in the end.

“The harder a CEO is pushed to increase shareholder value, the more the CEO will be tempted to make moves that actually hurt the shareholders…short-term rewards encourage CEOs to manage short-term expectation rather than push for real progress.”

The article cites companies like Johnson & Johnson and P&G that “get it.” They put the customer first and their shareholders have been rewarded handsomely—“at least as high as, if not higher than, those of leading shareholder-focused companies.”

One good example of how J&J put customers first is when in the 1982 Tylenol poisonings, in which seven Chicago-area residents died, J&J recalled every capsule in the nation, “even though the government had not demanded it.”

Another good example in the article is Research in Motion, the maker of the BlackBerry. They recognized the importance of the customer versus the focus on the shareholder and already “in 1997, just after the firms IPO, the founders made a rule that any manager who talked about the share price at work had to buy a doughnut for every person in the company.” The last infraction by the COO had him delivering more than 800 doughnuts—the message was heard loud and clear.

These examples are in seemingly stark contrast to the recent handling by Toyota of its brake problems, in which there has been delayed recalls and the government is now investigating. As The New York Times (8 February 2010) reported: “The fact that Toyota knew about accelerator deficiencies as far back as December 2008 “raises serious questions about whether car manufacturers should be more forthcoming when they identify a problem, even before a recall,” said Robert Gifford, the executive director of the Parliamentary Advisory Council for Transport Safety, a nonprofit group that seeks to advise British legislators on air, rail and road safety issues.” Note: this is out of character for Toyota, which historically has been a car company known for its quality and safety.

As a long advocate for User-centric Enterprise Architecture, I applaud the organizations and the people that put the customer first—and by this, I mean not by words alone, but in deeds. It is easy to put the customer into our mission and vision statements, but it is another to manage our organization with a true service creed.

While the HBR article emphasizes short-term shareholder value as main culprit diverting us from a positive customer-focus, there are really numerous distractions to realizing the vision of a customer service organization. Some examples include: organizational politics that hinder our ability to accomplish our mission; functional silos that are self-serving instead of seeking the best for the enterprise; certain egocentric employees (a minority) that put personal gain or a lack of strain above a service ethos; and of course, greedy and corrupt individuals that seek to profit at the expense of the customer, perhaps even skimping on product quality and customer service, thereby even endangering health and safety.

While most people are essentially good and seek to do the right thing, the organization must put in place controls to ensure that our focus is never distracted or diminished from our customers. These controls include everything from establishing values, policies, processes, requirements management, product development, training, testing, measurement and reporting, and best practices implementation in order to ensure our finest delivery to the customers, always.


Share/Save/Bookmark

November 1, 2009

Decoding Decision-Making

Decision-making is something we have to do every day as individuals and as organizations, yet often we end up making some very bad decisions and thus some costly mistakes.

Improving the decision-making process is critical to keeping us safe, sound, and stably advancing toward the achievement of our goals.

All too often decisions are made based on gut, intuition, politics, and subjective management whim. This is almost as good as flipping a coin or rolling a pair of dice.

Disciplines such as enterprise architecture planning and governance attempt to improve on the decision-making process by establishing a strategic roadmap and then guiding the organization toward the target architecture through governance boards that vet and validate decisions based on return on investment, risk mitigation, alignment to strategic business goals, and compliance to technical standards and architecture.

In essence, decisions are taken out of the realm of the “I think” or “I feel” phenomenon and into the order of larger group analysis and toward true information-based decision-making.

While no decision process is perfect, the mere presence of an orderly process with “quality gates” and gatekeepers helps to mitigate reckless decisions.

“Make Better Decisions,” an article in Harvard Business Review (HBR), November 2009, states, “In recent years, decision makers in both the public and private sectors have made an astounding number of poor calls.”

This is attributed to two major drivers:

Individuals going it alone: “Decisions have generally been viewed as the prerogative of individuals-usually senior executives. The process employed, the information used, the logic relied on, have been left up to them, in something of a black box. Information goes in [quantity and quality vary], decisions come out—and who knows what happens in between.”

A non-structured decision-making processes: “Decision-making has rarely been the focus of systematic analysis inside the firm. Very few organizations have ‘reengineered’ the decision. Yet there are just as many opportunities to improve decision making as to improve other processes.”

The article’s author, Thomas Davenport, who has a forthcoming book on decision-making, proposes four steps (four I’s) organizations can take to improve this process:

Identification—What decision needs to be made and which are most important?

Inventory—What are the factors or attributes for making each decision?

Intervention—What is the process, roles, and systems for decision-making?

Institutionalization—How do we establish sound decision-making ongoingly through training, measurement, and process improvement?

He acknowledges that “better processes won’t guarantee better decisions, of course, but they can make them more likely.”

It is interesting that Davenport’s business management approach is so closely aligned with IT management best practices such as enterprise architecture and capital planning and investment control (CPIC). Is shows that the two disciplines are in sync and moving together toward optimized decision-making.

One other point I’d like to make is that even with the best processes and intentions, organizations may stumble when it comes to decision making because they fail into various decision traps based on things like: groupthink, silo-thinking and turf battles, analysis paralysis, autocratic leadership, cultures where employees fear making mistakes or where innovation is discouraged or even frowned upon, and various other dysfunctional impediments to sound decision-making.

Each of these areas could easily be a discourse in and of themselves. The point however is that getting to better decision-making is not a simple thing that can be achieved through articulating a new processes or standing up a new governance board alone.

We cannot delegate good decision-making or write a cursory business case and voila the decision is a good one. Rather optimizing decision-making processes is an ongoing endeavor and not a one-time event. It requires genuine commitment, participation, transparency, and plenty of information sharing and collaboration across the enterprise.


Share/Save/Bookmark

October 23, 2009

Business Process Reengineering and Enterprise Architecture

User-centric EA analyzes problem areas in the organization and uncovers gaps, redundancies, inefficiencies, and opportunities; EA uses this information to drive business process reengineering and improvement as well as to introduce new technologies to the enterprise.

According to the Office of Management and Budget (OMB) Circular A-130, Management of Federal Information Resources, business process reengineering needs to take place to achieve the benefits of new information technology: “Moreover, business process reengineering should accompany all attempts to facilitate a transaction through information technology. Often the full benefits will be realized only by restructuring the process to take advantage of the technology. Merely moving an existing paper based process to an electronic one is unlikely to reap the maximum benefits from the electronic system.”

In the book The 21st Century Organization by Bennis and Mische the authors explain how organizations can reinvent themselves through reengineering.

What exactly is reengineering?

Reengineering is reinventing the enterprise by challenging its existing doctrines, practices, and activities and then innovatively redeploying its capital and human resources into cross-functional processes. This reinvention is intended to optimize the organization’s competitive position, it value to shareholders, and its contribution to society.”

What are the essential elements of reengineering?

There are five:

  1. A bold vision
  2. A systemic approach
  3. A clear intent and mandate
  4. A specific methodology
  5. Effective and visible leadership”

What activities are involved in reengineering?

  • “Innovating
  • Listening to customers
  • Learning
  • Generating ideas
  • Designing new paradigms
  • Anticipating and eclipsing competitors
  • Contributing to the quality of the workplace and the community
  • Constructively challenging established management doctrines”

“Reengineering the enterprise is difficult. It means permanently transforming the entire orientation and direction of the organization. It means challenging and discarding traditional values, historical precedents, tried-and-true processes, and conventional wisdom and replacing them with entirely different concepts and practices. It means redirecting and retraining workers with those new concepts and practices...The very cultural fiber of the enterprise must be interrogated and redefined. Traditional work flows must be examined and redesigned. Technology must be redirected from supporting individual users and departments to enabling cross-functional processes.”

What are the goals of reengineering?

  • “Increasing productivity
  • Optimizing value to shareholders
  • Achieving quantum results
  • Consolidating functions
  • Eliminating unnecessary levels of work”

Reengineering seeks to increase productivity by creating innovative and seamless processes…the paradigms of vertical ‘silo’ tasks and responsibilities is broken down and replaced with a cross-functional, flatter, networked structure. The classical, top-down approach to control is replaced with an approach that is organized around core processes, is characterized by empowerment, and is closer to the customer....Reengineering constructively challenges and analyzes the organization’s hierarchy and activities in terms of their value, purpose, and content. Organizational levels and activities that represent little value to shareholders or contribute little to competitiveness are either restructured or eliminated.”

What is the role of EA?

EA is the discipline that synthesizes key business and technology information across the organization to support better decision-making. EA develops and maintains the current and target architectures and transition plan for the organization. As OMB recommends, in setting enterprise targets, EA should focus first and foremost on business process reengineering and then on technology enablement. If the organization does not do process reengineering first, the organization risks not only failing to achieve the benefits of introducing new IT, but also causing actual harm to the organizations existing processes and results. For example, adding a new technology without reengineering process can add additional layers of staff and management to implement, maintain, and operate the technology instead of creating a net resource savings to the organization, from more efficient operations. Similarly, without doing reengineering before IT implementation, the enterprise may actually implement IT that conflicts with existing process and thus either require timely and costly system customization or end up adversely impacting process cycle time, delaying shipments, harming customer satisfaction, and creating bloated inventories, and so on.

Bennis and Mische predict that in the 21st century “to be competitive, an organization will have to be technology enabled…the specific types of technology and vendors will be unimportant, as most organizations will have access to or actually have similar technologies. However, how the organization deploys its technological assets and resources to achieve differentiation will make the difference in whether it is competitive.”


Share/Save/Bookmark

September 22, 2009

Organizational Politics and Enterprise Architecture

Organizations are intrinsically political systems, “in the sense that ways must be found to create order and direction among people with potentially diverse and conflicting interests.”

“All organizational activity is interest-based…an organization is simultaneously a system of competition and a system of collaboration.” Because of the diversity of interests… [the organization] always has a latent tendency to move in diverse directions, and sometimes to fall apart.

Organizational politics is founded in Aristotle’s idea “that diversity of interests gives rise to the ‘wheeling and dealing’, negotiation, and other processes of coalition building and mutual influence that shape so much of organizational life.”

“Organizational politics arise when people think differently and want to act differently. This diversity creates a tension that must be resolved through political means…there are many ways in which this can be done: aristocratically (‘We’ll do it this way’); bureaucratically (‘We’re supposed to do it this way”), technocratically (‘It’s best to do it this way’), or democratically (‘How shall we do it?’). In each case the choice between alternative paths of action usually hinges on the power relations between the actors involved.”

Power is the medium through which conflicts of interest are ultimately resolved. Power influences who gets what, when, and how.” Organizational power is derived from formal authority, control of scarce resources, control of information, use of structure, policies, and rules, and so on.

(Adapted from Images of Organization by Gareth Morgan)

Recognizing the importance of organizational politics—individual, group, and special interests, as well as the resulting conflict, and resolution through the levers of power is critical in User-centric Enterprise Architecture.

EA works within a diverse organization, takes competing interests and organizational conflicts, and turns it into common objectives and goals and the striving towards their achievement.

Enterprise architects work across organizational boundaries to synthesize business and technology to create interoperability, standardization, efficiencies, enterprise and common solutions, and integration.

Through the target architecture and transition plan, EA seeks to transform the organization from its intrinsic conflicts into a force with unity of purpose and mind to achieve ever greater accomplishments.


Share/Save/Bookmark

October 14, 2008

The Enlightened Enterprise and the Total CIO

The Total CIO is responsible for the strategy, operations, and governance of everything IT.

The strategy ensures that we are doing the right things and doing them the right way. It’s the CIO’s vision, goals, and objectives for developing IT solutions that meet business requirements.

The operations is providing for core IT functions like voice and data communications, information, applications, infrastructure, security, and so forth,

The governance is how we make decisions about IT. Through good governance we enhance visibility of IT requirements and projects, enable better communication and vetting, share risks, and prioritize, authorize, and control IT investments.

Architecture and Governance Magazine, Volume 4, Issue 2, has a good article titled “Bringing IT Governance from Theory to Action.” (by Davin Gellego and Jon Borg-Breen)

The problem is complexity:

“Even as technology has simplified and become almost invisible to most audiences, the complexity of maintaining technology is reaching a breaking point for information technology organizations…little time is invested between the lines of business and IT to communicate corporate goals and how technology can support these goals. The mandate is simply ‘do more with less.’”

The solution is governance:

Lines of business and IT can no longer work in their respective vacuums. This new interconnectedness means that what affects one now affects all. If problems are no longer confined to one functional area, solutions can’t be either. IT governance defines accountability and decision making and simplifies the challenges of consolidation, outsourcing, and increased visibility—ensuring IT expenditures deliver real business value.

The traditional organizational paradigm was silos. Everyone works for their particular unit, division, line of business and so on. Each is functionally and organizationally independent. Each develops their own strategy, products and services, customer base, and so on. Each has their own profit and loss statement. Working with other divisions, conducting joint product development, sharing information or ideas, cross-selling, and other collaborative efforts are discouraged, shunned, minimized, and looked at with suspicion. It’s every line of business or man for themselves. A unit that is not “producing” gets disciplined, downsized, reorganized, spun off, or otherwise eliminated. A division head that isn’t meeting their targets is toast! (Interestingly enough, people traditionally work in a “division”—that very word connotes separation, distinctiveness, and divisiveness.)

The enlightened paradigm is cross-functional. Everyone works for the enterprise. Each unit of the enterprise is part of a functional whole. The whole is greater than the sum of the parts. Collaboration, integrated product teams, working groups, information sharing, cross selling, corporate brand, interoperability, standards, component re-use, and other unifying activities are encouraged, taught, mandated, recognized, and rewarded. Performance measures take into account not only how your division is doing, but how it is contributing to overall mission of the organization. The goals of each individual and unit are aligned to the enterprise.

In the enlightened enterprise, The CIO is not running “the IT division,” but rather is providing IT services and solutions to the enterprise. In this paradigm, the CIO requires a structured and mature governance process, so that all stakeholders have a voice at the table and can influence the decision process and ensure more successful project delivery. IT governance provides for a consistent, collaborative decision process. Governance bring business and IT subject matter experts together to communicate, make visible, align, share risks, vet, prioritize, and issue decisions.

“The most successful enterprises engage in both business and IT in investment decisions. IT governance strengthens and clarifies the connection between corporate goals and IT initiatives. And with both business and IT aware of the strategic benefits of a given initiative, the initiative has a far greater chance of company-wide adoption and success.”

In the enlightened enterprise, “no line of business or IT department is an island. What affects one, affects all.” And in this environment, it is The Total CIO who can reach out across the enterprise bringing a unifying IT strategy, a sound, reliable, secure, and cost-effective operations platform, and a governance process to communicate, make visible, share risks, and make better decisions through the participation of all the pertinent IT stakeholders.


Share/Save/Bookmark

June 21, 2008

Fusion Centers and Enterprise Architecture

An important way to share law enforcement and intelligence information in a physical setting is through fusion centers.

Government Technology’s Emergency Management Magazine, Spring 2008, states “the ultimate goals of any fusion center is to prevent terrorist attacks and to respond to natural and man-made threats quickly and efficiently.”

“Data fusion involves the exchange of information from different sources—including law enforcement, public safety, and private sector—and with analysis, can result in meaningful and actionable intelligence and information…The fusion process allows relentless re-evaluation of existing data in context with new data in order to provide constant updates.”

Fusion centers bring together federal, state, local, tribal, and private sector subject matter experts to share information, provide risk and threat assessments, and provide a coordinated response.

“Nearly every state now has a fusion center to address gaps in data sharing.” In the fusion center, there is real time video monitoring that can be panned and zoomed, GIS mapping capabilities and the ability to amalgamate information. The advantage of the fusion center is that all participant organizations have the potential of seeing and hearing the same thing at the same time—although local authorities “cited difficulties accessing federal information systems.”

Not all fusion centers are permanent; some only are formed to deal with special security events like the Olympics and so forth. But those that do function 24x7 hone the skills of the participants by having them work together in a steady ongoing fashion.

While you would think that technology would do away with the need for fusion centers, since the information can be shared virtually, and therefore participants would not need to be co-located, there are benefits to having people deal with people from other organizations face-to-face.

As a User-centric enterprise architect and one who believes strongly that the human capital perspective is under-appreciated or neglected altogether, I appreciate the need for fusion centers, joint operations centers, interagency coordination centers, and the like to share not only information and technology resources, but to actually work together, cooperate, coordinate, and build stronger ties across functional and organizational silos. This is really what “enterprise” architecture is all about—breaking down the silos and building a unified, more effective and efficient organization.

The fusion center solution acknowledges that the challenge of law enforcement, intelligence, and counter-terrorism efforts needs to go beyond pure information technology initiatives. We can’t afford to just have siloed agencies and organizations working out of their own “corners.” There is a need for people to come together and collaborate in a face-to-face environment.

As architects, there is an erroneous tendency to focus on technology solutions. This is suboptimal. We need to look at business process improvement and reengineering, the introduction of new technology, and continuing to build an ever more skilled, innovative, and cohesive work force. This User-centric EA approach ties to a three-pronged approach of people, process, and technology.

Share/Save/Bookmark

June 15, 2008

Emergency Incident Management and Enterprise Architecture

When a disaster or emergency strikes, who is in charge—federal, state, local, or tribal authorities? Police, fire, rescue, medical services, public works, environmental response professionals? Who has jurisdiction? How is incident response coordinated?

“The National Response Framework (NRF) presents the guiding principles that enable all response partners to prepare for and provide a unified national response to disasters and emergencies. It establishes a comprehensive, national, all-hazards approach to domestic incident re

  • describes how communities, tribes, states, the federal government, private-sectors, and nongovernmental partners work together to coordinate national response;
  • describes specific authorities and best practices for managing incidents; and
  • builds upon the National Incident Management System (NIMS), which provides a consistent template for managing incidents.” (http://www.dhs.gov/)
National Incident Management System:

  • While most emergency situations are handled locally, when there's a major incident help may be needed from other jurisdictions, the state and the federal government. NIMS was developed so responders from different jurisdictions and disciplines can work together better to respond to natural disasters and emergencies, including acts of terrorism. NIMS benefits include a unified approach to incident management; standard command and management structures; and emphasis on preparedness, mutual aid and resource management.” (http://www.fema.gov/)

Government Technology’s Emergency Management Magazine, Spring 2008, reports that “only willing partners coming to the table, treated as equals, will prove effective in establishing a national standard for incident response.”

Why are there so many issues in coordinating incident response?

  1. Miscommunication—“the ideal scenario is that everyone uses the same system and terminology when responding, which allows disparate agencies to come together quickly and avoid miscommunication when confusion ultimately rules—during disasters.”
  2. Jurisdictional egos—“Jurisdictional egos can become involved, along with personal history and interagency ‘baggage.’…it can be messy at best, especially as leaders emerge, each wanting to highlight their agency’s accomplishments and not be superseded by another.”
  3. Lack of interagency and cross-jurisdictional training—“We need joint training, planning and exercises with all potential partners if we’re ever going to fix the issue of unified command…[additionally, there is a] lack of practice in how, in larger, cross-jurisdictional responses, the elected officials aren’t used to working in tandem with other jurisdictions during emergencies.
  4. Subordination is not in the law—“It is not in our nature and governance for one jurisdiction to subordinate itself to another, especially in crisis. As such, the solution will need to be the establishment of mechanisms that allow for joint action via a coordinated response.”

As a citizen, I frankly do not care about responders’ terminology, egos, training, or distaste for subordination—when there is a true crisis, I (like I believe any sane person) wants help to come, come quick, and come effectively. I want lives saved and property safeguarded.

From an enterprise architecture perspective, I acknowledge the challenge that we face in coordinating incident response among a broad spectrum of stakeholders and emergency response experts. However, at the same time, I cannot help but marvel at the current federated system of emergency response. I believe that emergency response needs to mature to one where there is absolute crystal clear chain of command and a solid, unified approach to dealing with disaster. All necessary and appropriate resources need to be brought to bear to help people in disaster and a coordinated response is a must.

Certainly, while there are technical issues in establishing common data standards, mechanisms for information exchange, interoperable systems, and securing these, it seems that the biggest issue is cultural. People and agencies are continuing to function in a siloed mentality despite the clear need for a unified approach to dealing with disasters as well as with the large, complex, and global problems that we face. I believe that this only underscores the need for “enterprise architecture” and that it is becoming more and more obvious that each of us doing our own thing is not going to enable us to solve the great issues of this century.


Share/Save/Bookmark

February 18, 2008

Leadership, Change, and Enterprise Architecture

Enterprise architecture is about planning, managing, and measuring change in an organization. To effect change requires true leadership, and this requires multiple skills.

In the book, The Leadership Triad by Dale Zand, three essential forces of leadership are presented—knowledge, trust, and power. These leadership forces guide constructive organizational change.

“Like three horses pulling a chariot, these forces, if coordinated and working together, provide a swift and exhilarating ride. But if one force is mismanaged or pulls against the others, the ride is bumpy and can end in disaster.”

Effective leaders integrate the three forces of knowledge, trust, and power to drive effective change and maintain efficient operations in their organizations: “They know what should be done, they have the trust of their people, and they use power appropriately:

  1. Knowledge—“leaders know or can find out what should be done…they have vision and they know how to fulfill that vision. They set clear, challenging goals, and they know what needs to be done to reach the goals…they know how to gain access to the knowledge of others, and they know how to work with people to convert that knowledge into action.”
  2. Trust—“people trust effective...leaders, giving them loyalty and commitment… [They] earn trust by disclosing relevant information, sharing influence, and competently using knowledge. They earn trust by fairness in their dealings with others—fulfilling the spirit of their agreements, sharing rewards and hard times and not abusing their power.”
  3. Power—“leaders use their power appropriately. They know how to be directive or to delegate. They know how to review and evaluate constructively. They know how to be consultants, providing guidance rather than issuing commands.”

Why not just lead in a command and control fashion like in the military or law enforcement organization?

“The heroic fantasy of one person at the head of a column and followers shouting ‘charge’ as they mount the battlements is outdated. Instead leaders need to learn to use the sensing, searching, and thinking ability of all people within the organization.”

How are these leadership skills similar to those necessary for implementing enterprise architecture?

Knowledge, trust, and power are the cornerstones of an enterprise architecture program.

1. EA makes information transparent and provides information products to distribute knowledge and enable better decision-making. EA information is critical to decision-making, particularly in terms of ensuring sound IT investment management decisions, IT planning, analysis of problem areas—uncovering gaps, redundancies, inefficiencies, and opportunities--driving business process improvement, reengineering, and the introduction of new technologies to the organization.

“In the twentieth century society crossed…into the information age, marked by the emergence of the knowledge organization.”

“Competitive advantage in the information age is in constant jeopardy—knowledge is fluid, and creative thinkers leapfrog over existing knowledge.”

“Knowledge travels with the speed of thought, but can be blocked by the smallest emotional barrier. It can enlighten the entire organization’s operation, yet it can easily be concealed if people do not want leaders to see it. People throughout organizations continually acquire and create important, critical knowledge about customers, [suppliers], products, technology, costs, and competitors. But that knowledge can remain hidden and inaccessible to leaders. In the new world leaders need to liberate knowledge and creative thinking at all levels and in all corners of the organization. To compete, leaders need to move knowledge from where it is to where it can be used to define and achieve appropriate goals.”

EA helps to synthesize information and liberate knowledge to meet strategic goals.

2. EA is based on the trust of business and technical leaders and staff across the enterprise. EA synthesizes business and technology information. It relies on the trust of divisions, departments, and subject matter experts (SMEs) throughout the organization to share (and not hoard) information and build a results-driven, process-oriented, interoperable, standardized, cost-effective organization, rather than a siloed, ineffective one. In an EA-directed organization, siloed functions and management relinquish their own personal interests and perhaps, selfish motives and instead plan for the good of the overall organization. For example, decisions on IT investments are made based on enterprise priorities and cost-benefit-risk-architecture considerations, rather than who has the money to spend.

“Trust regulates the disclosure of information—how open people are with relevant information…trust regulates mutual influence—how receptive people are to each other’s goals and concerns, and trust regulates control—the intention to fulfill the spirit of a decision and willingness to rely on another person to implement her part of the decision.”

“Mistrust causes people to censor, delay, and distort relevant information. Social uncertainty compounds ambiguity, masks difficulties and deprives leaders of the opportunity to make high-quality decisions

3. The EA Board (chaired by the chief enterprise architect) ensures that proposed new IT projects, products, and standards align to and comply with the enterprise architecture. EA must have the power to mandate and enforce alignment and compliance or else the target architecture and transition plan is just a sham that will not yield enterprise results and achieve stated goals. Additionally, EA must have the ability to require SMEs to contribute regularly to the development, maintenance, and use of the EA. The business and technical SMEs are the owners of the EA content and must be partners with the EA team in ensuring that the architecture is kept current, accurate, and complete.

“Power is the ability to influence others so that they do or do not do something.”

“Leaders have legitimate power to determine the process by which decisions will be made.”

Knowledge, trust, and power are three dimensions of leadership that are the foundation for an effective EA program. EA ensures that the information needs of the organization are met in terms of business and technical baseline and target architectures and transition plans. EA relies on the trust of its organizational partners in the business and technical domains to share information and adhere to architectural decision and standards that are in the best interests of the overall organization, rather than any one individual, group, or function. And finally, EA requires the power to ensure alignment to and compliance with the architecture and the decisions of the architecture board or else EA is just a paper tiger and will fail.


Share/Save/Bookmark

January 19, 2008

“Tear Down Those Silos!” and Enterprise Architecture

One of enterprise architecture’s “targets” is to transform the organization from being purely monolithic, functional-based silos (like operations, sales, marketing, finance, HR, legal, IT and so on) to an interoperable, cost-effective, mission and results-driven enterprise.

Matejka and Murphy in the book, Making Change Happen, clearly states that a “barrier to the successful implementation of any change is the division of the organization into silos. The grouping of the same or similar tasks (creating pockets of specialized knowledge) provides distinct opportunities for the disruption of the seamless implementation of new strategic initiatives.”

The authors ask “what is a silo and why does the term have such a negative connotation these days?

They then consult that Random House Dictionary for definitions of silo, as follows:

“A silo is ‘a tall, cylindrical structure in which grain is stored’ or ‘a sunken shelter for storing and launching missiles.’ Hmm. Very interesting. So a silo is a valuable protector of precious materials, but a single –purpose, single-use, fragmented, isolated, fairly impenetrable piece of organizational architecture.”

What makes organizational silos the enemy of change and transformation?

  • Professional jargon
  • Professional memberships
  • Turf and resource protection
  • Comfort zones…Discrimination”
“In a specialized professional department, is the employee’s real allegiance to the company or to the profession? The answer might surprise you. Many managers we have worked with would privately state that it is the profession.” This is why in functional- based siloed organizations, they cannot achieve the unity, integration, and synergy to make successful change happen."

To break down the silos and implement true “enterprise” architecture, you don’t need to get rid of the functions (since they serve a purpose and are important), you just need to use cross-functional teams, reward cross-functional performance and strategic thinking, broaden the perspective of functional silos by providing cross functional training and development.

Share/Save/Bookmark