Showing posts with label Business Process Reengineering. Show all posts
Showing posts with label Business Process Reengineering. Show all posts

June 24, 2019

The Goal is Automagically

Wow, I couldn't believe that this is a real word.

Automagically.

I thought my colleague was using it as a gag. 

But when I asked Dr. Google, there it was. 

Automagically - Automatically + Magical

It refers to the use of computer automation and how when well-implemented it seems almost like the process is magical, ingenious, and oh, so easy. 

So this is the goal for us that all our processes and efforts should be poof--automagically done and  there it is! ;-)

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

April 20, 2018

Understanding Genius

So working in a place with scientific geniuses and even a history of Nobel Prize winners is serious business. 

I see things that I don't know what they are. 

I meet people that I don't understand what they do. 

But in all cases, I am in awe of the smart and good people and the work they are doing to advance us. 

Here was an example this week in randomly meeting someone and starting up a conversation:
Andy:  Hi. I'm Andy.  What do you do here?
Him:  I'm [so and so].  I do neutron scattering.
Andy: [Gulp followed by big smile] I know absolutely nothing about that.
Him:  Well, what do you do?
Andy:  I'm doing process engineering and enterprise service management.
Him: [Smile] I know absolutely nothing about that. 
Get the picture.

One for the books right.

In another instance, when asked what their group does, someone leans into me and goes:

"We fix sh*t."

I could tell he meant it. 

And you know what--I absolutely believed him.  ;-)

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

September 25, 2016

You Changing My What

So change agents are some of the most sought after...yet most abhorrent individuals on this planet. 

We all recognize that things can be better, and on one hand, we want someone to come and help us make it so...a change agent!

However, change is painful and frequently results in unintended and unwanted consequences, and so on the other hand, we hate change agents. 

Many change agents may not just change things that need to get changed and fixed, but they may change a lot of things that were working just fine before, thank you.  

Can anyone say reorganization? 

Moreover, change agents may not be changing things for the right reasons like the good of the organization.

Instead they may be self promoters, control freaks who have to do things their way, or they may be serial job hunters--next stop change everything and get the heck out of Dodge!

Change agents may work with people to get requirements, input, and vet the issues and the solutions or they may just be paying lip service to others, only to really shove their or someone else's agenda down your throats. 

You see there is healthy change that is based on genuine learning, growth, and maturity, and then there is change that is destructive, diabolical, and selfish. 

When you decide to change something, what's your motivation and your goal--is it to right the wrongs in the organization, reengineer business processes, and introduce new technologies or is it to change for change's sake alone. 

Yes, we did something. Check the box. Tell the management committee. We earned our keep and oh yeah, then some. We changed something, anything. Hip Hip Hooray. Bonus time!

So either you'll get an award and promotion or you'll get asked accusingly and threateningly, "Who told you to change that?!"

Change which has no real support or merit is dead on arrival (DOA), and will be gone, gone, gone long after the change agent is gone.

So don't freak out--the b.s. changes are either going to kill the organization or simply end up in Fresh Kills landfill.

The real changes may actually make you stronger. ;-)

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

September 26, 2013

Flowchart Your Programming


Flowcharts have been used for quite some time for visualizing and organizing business processes and making them more efficient (e.g. business process reengineering).

Now flowcharts are being used to build and link reusable programming code.

NoFlo or Flow-Based Programming (FBP) simplifies application development by using libraries of pre-written code and then dragging and dropping them into your process flows. 

This leverages objected-oriented programming (OOP) and uses modules of open-source code, which are linked together to create a full program that solves a business problem.

The flowchart helps to avoid spaghetti code by providing for a more organized, modular, object-based development environment. 

These flowcharts can not only be a collaborative tool where developers can build or map code, but can also be part of the systems documentation that ensures a higher-level of understanding of the total programming solution. 

NoFlo raised over $100K on Kickstarter in 45 days in order to advance this project from Javascript to iOS, Android, and Python platforms as well. 

To me, this programming paradigm seems to have real legs:
- A process-based model for decomposing solutions
- Simple information visualization through a common flowcharting toolset, and 
- Reusable object code from programming libraries in the cloud. 

I'd say YesFLo--this makes a lot of programming sense. ;-)
Share/Save/Bookmark

April 22, 2012

I Hate Paper

Paper has been around for approximately two thousand years, since it's invention in China, and it has served as the medium of choice for recording and sharing information ever since. 

However, enter the age of information technology and we are now able to capture, process, and store far more information, quicker, cheaper, and more efficiently than we ever could with paper. 

Combine that with the environmental impact and the need to conserve, and we have numerous federal laws calling for the reduction or elimination of paper, to the extent practical.

1) The Paperwork Reduction Act (1980) calls for the Office of Management and Budget (OMB) to regulate collection of information and establish information policies to reduce the paper handled by the government. 

2) The Government Paperwork Elimination Act (1998) mandates the use of electronic forms, filings, and signatures for official business with the public. 

3) E-Government Act (2002) requires use of the Internet to improve citizen access to information and services. 

All three are a recognition of the need to move from costly paper-based processes and the management of maintenance of mountains of paper records to instead leverage information technology to re-engineer and improve the way we perform information management. 

It's funny, but for me it's almost become a personal crusade to make better use of information technology to perform our mission and business of government more effectively, and I personally keep as little paper records, as possible--instead choosing to manage predominantly online--and it's great.   

Aside from having a cleaner office--no paper files, I enjoy all the benefits of electronic filing, search, and the ability to quickly share files with others in the office without having to rummage through a stack of papers 3 feet deep! 

Working in some areas that are still paper intensive for case management and so on, I have taken on the mantra, which I frequency cite of "I hate paper!" 

No, I don't really hate it, but in order to change decades old manual and paper intensive processes, we need to exaggerate a little and tell ourselves and other we hate it, so we can help change the inefficient and costly status quo. 

You can only imagine how surprised I was to read in The Atlantic (20 April 2012)--that "Paper: [Is] The Material of the Future."

Essentially, the article touts the new developments with paper using nanotechnology to make it water-proof (although you can still write on it), magnetic, fluorescent, and even anti-bacterial. 

Imagine paper that you can stick to your file cabinet, spill coffee on, light up the room with, and even keep you from getting sick--yes, that's fairly impressive!

However, while these new features are wonderful indeed and will increase the usability of paper as well as improve records management of them, I do not want to see us get complacent with reducing our use of paper and making better use of technology.  

Even with these cool nano-tech improvements to paper coming our way, I am still going to say, "I hate paper!"

(Source Photo: here with attribution to Earthworm)

Share/Save/Bookmark

April 16, 2011

Wake Up To Advanced Technology


Yet another air traffic controller asleep on the job today--OMG.
Everyone is upset--as they should be--safety and lives are at stake.

Hello.

Come in...

Is anyone down there?

We need to land.

We have an emergency on board (someone is sick or perhaps the plane is in imminent danger or maybe it's been hijacked).

I guess we need to call back later.

That's CRAZY!

Silence is not golden, in these cases.

In the government (as in private sector control rooms), there are a lot of round the clock duty stations--watching our airports, our borders, and critical infrastructure.

We rely on people to be alert for any problems and be prepared to step up to the plate to take necessary action to safeguard our nation.

When people are "asleep at the switch," they are not only abrogating their basic duty (for which they are getting paid), but they are endangering others and this is obviously unacceptable.

We know this intuitively.

Why has this gotten so out of control lately--Is this a new phenomenon or just one that is coming to light now? Are people taking advantage of the system, genuinely exhausted, or disillusioned with their jobs and giving up--so to say?

There are a lot of questions that need to be explored and answered here and I would expect that these answers will be forthcoming.

Because it is not just a matter of reacting with a doubling of the shift or clamping down on the people involved--although that maybe a good first step to stop the proverbial bleeding; but obviously more needs to be done.

For decades, air traffic control (ATC) has relied on controllers on the ground to guide planes on the ground and in the air, despite new technologies from autopilot to Global Positioning System (GPS) and from on-board transponders to advanced cockpit displays.

Many hardworking government and commercial sector employees have been working to change this through modernization of the processes and systems over the years.

By increasingly leveraging advances in technology, we can do more of what people--like the ATCs and many other of our hardworking watchstanders--are currently being asked to do manually.

This doesn't mean that there is no human (AWAKE! is the expectation) watching to make sure that everything is working properly, but it does mean that the people may be in some instances an augmentation, rather than the primary doers.

In the end, people have got be in control, but technology should be doing as much of the heavy lifting as it can for us and perhaps, as we are a failsafe for technology, technology can in some instances be a backstop for human error and frailty.

It doesn't make us weak to admit our limitations and look not only for people and process changes, but also for technology solutions to help augment our personal capabilities.

(Credit Picture: PN.PsychiatryOnline.org)

Share/Save/Bookmark

July 2, 2010

Why Take Out The Trash Anymore?

I am fascinated by unusual uses of technology. And in fact, that’s what I love about technology—is that it literally applies to every aspect of our lives.

In a sense, I think of technology as one of G-d’s precious gifts to mankind to better the world—when it's used for good—such as for improving communications, curing illness, and inventing new materials.

(Of course, there has been so much focus on technology being used to create “bigger and badder” weapons that can destroy the planet, but hopefully, we are spared from such morale and intellectual insanity and hatred.)

So now technology is striking again... but in an area that you wouldn’t necessarily expect.

Wired Magazine (July 2010) has an article called “Canada Sucks: Montreal’s vacuum system will make taking out the trash a breeze.”

“In 2012, Montreal will unveil an $8.2 million [4 mile] tube network to service a downtown arts district.” The trash system called Envac is already operational in other cities such as Barcelona, London, and Stockholm. It incorporates separate inlets/chutes for waste, recycling, and compost; sensors that relay load information to system operators; large industrial fans that can crank up from 45 mph to gale force to flush obstructions through a subterranean slipstream; and automated software that directs the trash to appropriate dumpsters in central collection facilities for transport to landfills, recycling centers, and composting plants; And the Canadian system will be controlled remotely from Envac headquarters in Stockholm 3600 miles away.

I was surprised and excited to see such an innovative use of technology for such a seemingly mundane task as garbage removal (i.e. I wouldn’t normally associate garbage and technology, but this article gave me a new reason to think more broadly on this topic).

Truly, technology is a game-changer. And we can think about everything we do, question it, reinvent it, and make for a better future.

The only condition is that we look beyond the surface of how we do things do things today and envision them anew for tomorrow.


Share/Save/Bookmark

June 21, 2010

Focus Future

I was on vacation in Miami last week and had the opportunity to spend some time (when not on the beach and in the pool) in one of my favorite off the beaten path bookstores, where I spend some time perusing “The Power of Now” by Eckhart Tolle.

Some fascinating points that stuck with me:

- Focus on the now—to achieve peace and happiness—and not on the past or the future, because the past carries with it all sorts of baggage and the future weighs on us with anxieties.

- The focus on now can be viewed as more important than the past or the future, even though the past provides us our identity and the future with the hope of salvation.

The emphasis on now is an intriguing viewpoint for me, because by nature and profession, I am a strategist, architect and planner—I look always to the future to make things better than they are today. I routinely ask how can we use technology or reengineer our business processes to surpass the now.

I also do this based on my religious upbringing that taught me that our actions—good and bad—affect our merit for the future—in this world and “the next.”

In both cases, “the now” is but a steppingstone to the future. So while, I think living in the now can certainly help us wall off the mistakes of the past and worries about the future, I do not really see it as fulfilling our mission of learning from the past and growing into our futures.

While it may be simpler, more enjoyable or just more comfortable to focus on the present, it seems a little naïve to me to ignore where you come from and where you are going.

Maybe Eckhart Tolle doesn’t care what is in the future and he is blissfully happy in his ignorance, but I for one am more comfortable focusing on the future (except when I’m on vacation in Miami Beach).

I guess what I’m saying is, I love the now in that it refreshes and rejuvenates me. But I also think of it as ultimately leading toward a desired future state, and I think it’s more productive to focus on what can and must be done to make the world a better place tomorrow.


Share/Save/Bookmark

April 16, 2010

Breaking Down Organizational Bottlenecks

Improving organizational performance is often grounded in identifying bottlenecks (constraints) and fixing them, so that the firm runs better, faster, cheaper than before and at an advantage to it’s competitors.

Enterprise architecture helps us to locate the bottlenecks through an understanding of our business processes, information flows, and systems and then facilitates our reengineering these though business process improvement and the introduction of new technologies.

Harvard Business School (HBS) put out a working paper in February 2010 called “The Strategic Use of Architectural Knowledge by Entrepreneurial firms,” by Carliss Baldwin that describes how “an entrepreneurial firm can use architectural knowledge to unseat a larger incumbent.”

The premise is that knowledge is a firm’s most critical resource, “including knowledge about how to assemble resources to pursue an opportunity.”

We can architecturally disassemble and assemble our resources and processes whereby we—“isolate the bottlenecks” and then “alleviate the bottlenecks.”

This process is grounded in modularity theory, where we use architectural knowledge to modularize (or breakdown) a complex system into its functional components as well as address how these components are related (through their interfaces).

Once we decompose the firms business, data, and systems into its modular components, we can then “remodularize” (or assemble) them into strategically more effective systems for doing business.

Moreover, the paper suggests that the firm “insources bottleneck components and outsources non-bottleneck components,” so as to focus resources (and innovation) on the trouble spots—the areas that are potentially a source of competitive advantage.

Fixing bottlenecks can produce valuable differentiators for a company that we would not want shared with those outside the organization and made available to competitors.

In my opinion, bottleneck functions can also be outsourced, whereby we decide to “let the experts handle it,” when the functions are not strategic in nature. For example, many companies outsource things like payroll and basic call center functions, and it enable the organization to focus its energy and efforts on its core mission.

The notion that enterprise architecture itself is a strategic differentiator for organizations that know how to wield the architecture knowledge is critically important. Through decomposition and assembly of processes and enabling technologies, we can create stronger organizations that not only reduce bottlenecks, but also drive improved decision-making in terms of what to invest in and how to source those investments.

While many organizations treat architecture as a compliance only mechanism and reap little to no benefits from it, those that understand EA’s strategic significance can use the knowledge gained to their organization’s competitive advantage.


Share/Save/Bookmark

November 27, 2009

Right In Front of Us, but We Are Blind to It

Last week, there was a 13-year-old boy, with Asperger’s syndrome, who ran away from home and rode away in the NYC subway system for 11 days undetected!!!

The boy went missing with $11 dollars in his pocket. “According to CNN, the boy's mother says he survived on fast food and candy he purchased in the subway system. He spent the majority of his time riding the trains. He wore the same clothes for the duration and lived underground, sleeping in subway cars and using underground restrooms.”

Many people were out looking for this boy, including the police, but neither the searchers nor the extensive surveillance apparatus in New York picked him out. Apparently, no one on the trains reported seeing this kid riding endlessly around 24x7, and the boy was invisible to the myriad of hardworking transit workers and officers who are all over the transit system, until day 11 when finally one officer recognized the boy from his missing picture.

How can a boy be there for almost two weeks, but be seemingly invisible to the thousands of riders and workers passing thru the subway system and what can this teach us about leadership and organizations?

Information Overload—This is truly the information age. We have morphed from not having enough information to being flooded with it and not being able to process it. With the missing boy on the NYC MTA subway system, he was literally lost amidst the more than 5 million riders a day and 468 stations. This is a common situation these days where we have access to stores of information, on databases and through the Internet, yet we frequently struggle to find the golden nuggets of information that really mean something. Post 9-11, our military and intelligence communities are being flooded by sensor information from a vast network of resources, and the challenge now is to find innovative ways to process it quickly and effectively—to find the proverbial “needle in the haystack” and to stop the next potential attack. Our organizations in the public and private sectors need faster, more accurate, and finely tuned systems to find the dots, connect the dots, and see the picture.

Process Matters—According to Digital Journal, “the disappearance was reported to police immediately, who treated it as a runaway. After five days had passed, it was being treated as a missing persons case.” The police were following their processes in handling this little boy, but it resulted in five days passing without the assumed more intense search that occurs with a missing persons case. Lesson to note is that having standardized, documented business processes are important in efficiently managing operations, but we should not get so caught up in the process that we become rigid and inflexible in handling cases according to the specific situation. While I am not an expert in this, the question does come to mind, whether the search for a child with a known disability may have been escalated/elevated sooner? And the point, I am really trying to make is that we need to keep our organizations and processes agile and responsive so that we can act meaningfully and in time.

Break through the Apathy—Having been a former New Yorker (and I suppose, it never truly leaves your blood), I am well aware of the accusations and jokes made about rudeness and apathy from people in the “city that never sleeps.” NY is a tough town, no doubt. The people are quick and sharp. They work and play hard. They are good, productive people. But living in a city with 8.3 million people in one of the most dense urban centers of the world can take a toll. Even with major clean-up efforts in recent years, NYC still has its fair share of crowding, pollution, and crime and this can take a toll on even the best people. I remember daily sights of panhandling, poor and ill people, aggressiveness not limited to the yellow cabbies. I suppose, one disabled boy could get lost amidst the city chaos, but the challenge is to break through the apathy or callousness that can easily overtake people and continue to care for each and every person that needs our help. This is no small challenge in a city with a 21.2% poverty rate (US Census Bureau 1999), let along in a world where 1 in 4 (or 1.3 billion persons) live on less than $1 a day. As leaders, we need to push for caring over apathy and for seeing and acting versus blinding ourselves to the pain and misfortune of others.

Could we have found this little boy sooner? Maybe. Could it have ended a lot worse? For sure.

While this missing persons situation is now over, we need to prepare ourselves for future events and contingencies. We can do this by continuing to create better systems and mechanisms to process information better, faster, and cheaper—it’s not longer just the quantity of information, but the quality and it’s timeliness and relevance; by reengineering our business processes so that we are alert, nimble and responsive—rigid processes lead to hard and fast rules that serve no one; and building camaraderie with one another—seeing that we are more the same, than we are different—and that everyone matters—even a kid underground in a subway system spanning 656 long and winding miles.

And lest anybody think I’m giving New Yorkers a hard time, believe me when I say – it is “the city” that has given me the street smarts to navigate the Beltway and challenge anyone who says that something can’t be done!


Share/Save/Bookmark

October 31, 2009

Complexity, plain and simple

There is the old saying that rings true to basic leadership: “Keep it Simple Stupid,” (or KISS) yet for various reasons people and organizations opt or are compelled toward complexity.

And when things are complex, the organization is more prone to mistakes, people to misunderstandings, and leadership to mismanagement--all are points of failure in the dynamics of running an organization.

Mistakes can be costly from both a strategic and operational standpoint; misunderstandings between people are a cause of doubts, confusion, and hostility; and mismanagement leads to the breakdown of solid business process and eventually everything goes to pot.

An interesting article in the Wall Street Journal, 26 October 2009, defines four types of complexity:

Dysfunctional—This is the de facto complexity. It “makes work harder and doesn’t create value…research suggests that functional complexity creeps into a company over years through the perpetuation of practices that are no longer relevant, the duplication of activities due to mergers or reorganizations, and ambiguous or conflicting roles.”

Designed—This is an odd one…why would you design in complexity? “Executives may deliberately increase the complexity of certain activities or they may broaden the scope of their product offering, because they expect the benefits of those changes to outweigh the costs.” Example cited: “Dell believes that configuring each product to individual specs, rather than creating them all the same, makes customers more likely to buy from the company.”

Inherent—I guess this is the nothing I can do about it category, it just is hard! “The difficulty of getting the work done.” Plain and simple, some jobs are highly complex Mr. Rocket Scientist.

Imposed—This is the why are they doing this to us category—external factors. This “is largely out of the control of the company. It is shaped by such entities as industry regulators, non-governmental organizations and trade unions.” I would assume competitors’ misdeeds would fall into this one as well.

Whatever the reason for the complexity, we know implicitly that simplification, within the realm of what’s possible, is the desired state. Even when the complexity is so to say “designed in” because of certain benefits like with the Dell example, we still desire to minimize that complexity, to the extent that we can still achieve the organization’s goals.

I remember years ago reading about the complexity of some companies’ financial reports (income statements, balance sheets, statements of cash flows…) and news commentators questioning the authenticity of their reporting. In other words, if you can’t understand it—how do we know if it is really truthful, accurate, or the full story? Well-publicized accounting scandals like Enron, HealthSouth, and many others since around the mid-1990’s come to mind.

Generally, we know that when something is veiled in a shroud of complexity, there is often mismanagement or misconduct at play.

That is not to say that everything in life is simple—it isn’t. Certainly advances in the sciences, technology, and so on are not simple. Knowledge is incremental and there is certainly lot’s of it out there to keep us all occupied in the pursuit of life-long learning. But regardless of how complex things get out there—whether dysfunctional, designed, inherent, or imposed—we should strive to make things easier, more straightforward, and as effortless and trouble-free, as possible.

Will simplification get more difficult as a goal as our society continues to advance beyond the common man’s ability to understand it?

Yes, this is going to be a challenge. It used to be that graduating from high school was the farthest most people went with their education. Then college became the goal and norm for many. And now graduate and post-graduate studies are highly desirable and expected for many professional careers. It is getting difficult for people to keep us with the pace of change, breadth and depth of knowledge, and the advancement in technical fields.

One of the antidotes to the inherent complexity seems to be greater specialization such as in medicine, technology, engineering and so forth. As knowledge advances, we need to break it up into smaller chunks that people can actually digest and handle. The risk is that the pieces become so small eventually that we can lose sight of the bigger picture.

Complexity is here to stay in various forms, but we can and must tackle at the very least the dysfunctional complexity in our organizations. Some ways we can do this include breaking down the silos that impede our collaboration and information sharing; architecting in simplification into our strategic, operational, and tactical plans; building once and reusing multiple times (i.e. through enterprise and common solutions); filling gaps, reducing redundancies, and eliminating inefficiencies; reengineering our business processes as a regular part of “what we do”, constantly innovating better, faster, and cheaper ways of doing things; thinking and acting user-centric, improving the way we treat our people; and of course, being honest, transparent, and upright in our dealings and communications.


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

October 10, 2009

Making Something Out of Nothing

At the Gartner Enterprise Architecture Summit this past week (October 7-9, 2009), I heard about this new math for value creation:

Nothing + Nothing = Something

At first, you sort of go, WHAT?

Then, it starts to make a lot of sense.

Seemingly nothings can be combined (for example, through mashups) to become something significant.

When you really think about it, doesn’t this really happen all the time.

INFORMATION: You can have tens or thousands of data points, but it’s not till you connect the dots that you have meaningful information or business intelligence.

PEOPLE: Similarly, you can have individuals, but it’s not until you put them together—professionally or personally—that you really get sparks flying.

Harvard Business Review, October 2009, put it this way:

Ants aren’t smart…ant colonies are…under the right conditions, groups—whether ant colonies, markets, or corporations—can be smarter than any of their members.” This is the “wisdom of crowds and swarm intelligence.”

PROCESS: We can have a workable process, but a single process alone may not produce diddly. However, when you string processes together—for example, in an assembly line—you can produce a complex product or service. Think of a car or a plane or a intricate surgical procedure.

TECHNOLOGY: I am sure you have all experienced the purchase of hardware or software technologies that in and of themselves are basically useless to the organization. It’s only when we combine them into a workable application system that we have something technologically valuable to the end-user.

Whatever, the combination, we don’t always know in advance what we are going to get when we make new connections—this is the process of ideation, innovation, and transformation.

Think of the chemist or engineer or artist that combines chemicals, building blocks elements, or colors, textures, and styles in new ways and gets something previously unimaginable or not anticipated.

In a sense, organization and personal value creation is very much about creating relationships and associations between things. And a good leader knows how to make these combinations work:

Getting people and organizations to work together productively.

Generating new ideas for innovative business products or better ways of serving the customer.

Linking people, process, and technology in ever expanding ways to execute more effectively and efficiently than ever before.

Enterprise architecture shares this principle of identifying and optimizing relationships and associations between architectural entities such as business processes, data elements, and application systems. Typically, we perform these associations in architectural models, such as business process, data, and system models. Moreover, when we combine these models, we really advance the cause by determining what our processes are/should be, what information is needed to perform these, and what are the systems that serve up this information. Models help architects to identify gaps, redundancies, inefficiencies, and opportunities between the nothings to improve the greater whole of the something.

The real enterprise architect will make the leap from just describing many of these elements to making the real connections and providing a future direction (aka a target architecture) or at least recommending some viable options for one.

Nothing + Nothing (can) = Something. This will happen when we have the following:

  • The right touch of leadership skills to encourage, motivate and facilitate value creation.
  • The allocation of talented people to the task of combining things in new ways.
  • And the special sauce—which is everyone’s commitment, creativity, and hard work to make something new and wonderful emerge.


Share/Save/Bookmark

October 6, 2009

Measurement is Essential to Results

Mission execution and performance results are the highest goals of enterprise architecture.

In the book Leadership by Rudolph Giuliani, he describes how performance measurement in his administration as mayor of NYC resulted in tremendous improvements, such as drastic decreases in crime. He states: “Every time we’d add a performance indicator, we’d see a similar pattern of improvement.”

How did Giuliani use performance measures? The centerpiece of the effort to reduce crime was a process called Compstat in which crime statistics were collected and analyzed daily, and then at meetings these stats were used to “hold each borough command’s feet to the fire.”

What improvements did Giuliani get from instituting performance measurements? Major felonies fell 12.3%, murder fell 17.9%, and robbery 15.5% from just 1993-1994. “New York’s [crime] rate reduction was three to six times the national average…far surpassed that of any other American city. And we not only brought down the crime rate, we kept it down.”

How important was performance measurement to Giuliani? Giuliani states, “even after eight years, I remain electrified by how effective those Compstat meetings could be. It became the crown jewel of my administration’s push for accountability—yet it had been resisted by many who did not want their performance to be measured.”

From an architecture perspective, performance measurement is critical—you cannot manage what you don’t measure!

Performance measurement is really at the heart of enterprise architecture—identifying where you are today (i.e. your baseline), setting your goals where you want to be in the future (i.e. your targets), and establishing a plan to get your organization from here to there through business process improvement, reengineering, and technology enablement.

In the end, genuine leadership means we direct people, process, and technology towards achieving measureable results. Fear of measurement just won't make the grade!


Share/Save/Bookmark

November 11, 2008

Improving Project Management and The Total CIO

IT projects are notorious for coming in late, over cost, and not meeting the customer’s needs.

CIO.com has an excellent article on ways to improve project management in an article entitled, “When Failure is Not an Option,” by Meredith Levinson (3 July 2008).

For organizations, good project management is a critical success factor!

“Project management is the number-one success factor for getting anything done in the organization. A firm’s ability to execute its strategy lies with its ability to manage projects,” according to Sam Lawler, the director of GlassHouse Technologies’ project management practice.

Yet, for years, organizations have faulted CIOs and IT departments with failed IT projects. As recently as 2004, a study by The Standish Group found that only 29% of IT projects “were completed on time, on budget, and with all features and functions originally specified.”

Project management methodologies work when business and IT work together as a team.

There are various methodologies being employed to try to improve project’s success, such as PMBOK and ITIL. However, IT projects’ success depends on IT and business people working together to achieve results; if this partnership and collaboration doesn’t happen, then no PM framework will bring us the project success we desire. Our organization’s business people are critical to ensuring project success—they develop the business case, identify requirements/functional specifications, realign and improve business processes, and test technical solutions to ensure they meet mission and business needs.

No longer is it about tossing the proverbial hot potato to IT and then pointing fingers and assigning blame when something doesn’t work right. Instead, the business and IT people are on the same team, sharing accountability, and working toward the success of the project and the enterprise.

Performance measurement is a must:

Improved project management needs to be accompanied by measurement of project success and reporting on these to executive management. We can’t manage what we don’t measure. And we need transparency to senior management to ensure that everyone—business and IT—have “skin in the game.”

Further, there are trade-offs in project management between cost, schedule, and scope/performance. Changing one affects the others, so we need to manage projects harmoniously in this triad. If for example, a project is delayed or costs more, but delivers on added functionality requested by the business, then the project can still be a success. At the end of the project, success is defined by the business!
Share/Save/Bookmark

October 21, 2008

Lessons from High School Dropouts for The Total CIO

The Wall Street Journal, 21 October 2008, reports some shocking statistics on high school dropouts.
  • “In the nation’s 50 largest cities, the graduation rate [in four years] was 52%.”
  • The graduation rate was as low as 25% in Detroit.
  • “Only about seven in 10 students are actually finishing high school.”
  • “Dropouts are disproportionately represented in the criminal justice system, including about 75% of state prison inmates.”
  • “The difference in lifetime salary for a dropout and a high school graduate is about $300,000.”
  • Cutting the number of dropouts in half would generate $45 billion annually in new tax revenue.”

So obviously there is a very compelling case for reducing the high school dropout rate and having students graduate!

What is being done to address this issue?

One new program was started in the city of Houston called “Reach Out to Dropouts.” In Reach Out, “volunteers, including Mayor White and school superintendent Abelardo Saavedra, visit the homes of students who haven’t returned to school.”

How did this start?

The mayor “was troubled by the fact that while the private industry could track inventory world-wide, school systems could not track students.” But then he took this further, by reaching out to students in person, and finding out why they quit, and how the city could help them return (for example, money, childcare, tutoring and so on).

What are the results?

“Reach Out has recaptured more than 5,500 dropouts in the city since it started in 2004.”

One student summarized it this way: “They were saying I was so smart and they didn’t know why I wasn’t in school, that I was too smart to just drop out. It got to me, kind of.”

This is powerful stuff!

To me there are some profound lessons here for the Total CIO:

First is the personal touch. The CIO’s job is providing information technology solutions for the business and this is great. However, IT is not a replacement for having a personal touch with people. Technology solutions need to complement people solutions.

In the case of the Reach Out program, it’s not enough for our schools to track students like inventory or assets using attendance systems, but we need then take the tracking information and apply it with people and process to get in there and actually help the students come back and graduate. The technology along can’t do this; only people can!

In general, IT solutions must follow people’s requirements and process improvements. You cannot build IT solutions for yesterday’s process (sending letters home or calling the truancy officer); you must build it for today and tomorrow’s way of doing business (personally finding out what the problem is and then remediating it). The bottom line is that the CIO has to be forward-thinking rather than reactive: Implementing technology solutions and then modifying or customizing it to mimic existing processes is not the answer. Rather, the CIO needs to work with the business to modernizing the process and then apply the appropriate technology as an enabler for enhanced results.

With the Reach Out program to help students graduate, the City of Houston didn’t just track the dropouts, but they looked at what was being done to solve the problem and bring kids back into the education system. If sending letters home to parents wasn’t working, for example, then perhaps getting out from behind the desk and going to the student’s homes would. Through this new way of “doing business,” the educators and politicians are showing genuine care and concern, and tailoring solutions to the needs of individual students—and it is working!

The personal touch with people, and reengineering process to match what they need, is crucial for solving problems and implementing technology solutions.


Share/Save/Bookmark

October 4, 2008

Why a New Blog Called the Total CIO?

As you all know, I have been leading and promoting the concept of User-centric Enterprise Architecture for some time now.

After hundreds of blog posts and numerous articles, interviews, and speeches, I believe it is time to expand the core principles of User-centric EA to encompass all that a CIO can and should do to implement best practices that facilitate total mission success.

Thus, the concept of the "Total CIO".
  • The Total CIO is mission-driven. He or she never compromises on delivering IT solutions that meet business requirements. In today's world this means capturing and managing customer requirements, synthesizing business and IT for effective strategy as well as efficient tactical implementation.
  • The Total CIO is holistically minded. He/she employs best practices from various disciplines (IT, business process reengineering, human capital, etc.) to move the mission forward through infomation technology. This quality speaks to innovation, expansiveness, and thinking outside the box without ever losing sight of the goal.
  • The Total CIO is customer-centric. He/she focuses on making it easier for people to use technology. That means he/she is focused on helping people deliver on the mission. This means that rather than speaking in jargon and creating shelfware, he/she delivers useful and usable information and technology to benefit everyone from the CEO to front-line personnel.

I look forward to your comments and input.
Share/Save/Bookmark