Showing posts with label Requirements. Show all posts
Showing posts with label Requirements. Show all posts

October 28, 2019

Card Ya

Thought this was novel in the store. 

They have a digital calendar with the date from 21 years ago.

It says:
To Purchase Tobacco Products You Must Have Been Born On Or Before This Date.
 Thank you for showing you I.D.

Ah, easy to match the DOB on the I.D. presented to the date on the calendar.  

Nothing to calculate, no mistakes. 

They raised the age for smoking (cigarettes and vaping) in Maryland to 21 on October 1, so it's the same requirement as for drinking alcohol.

Luckily for me (even though I'm over 21), I don't really do either--definitely not the smoking, and the drinking limited primarily to the Kiddush prayer on Shabbat. ;-)

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

November 8, 2013

Cloud Kool-Aid

We've all drunk the Kool-Aid and believe in using the cloud.

And with almost 1 million active apps alone in the Apple Store it is no wonder why.

The cloud can create amazing opportunities for shared services and cost efficiencies.

The problem is that many are using the cloud at the edge.

They are taking the cloud to mean that they in government are simply service brokers, rather than accountable service providers.

In the service broker model, CIOs and leaders look for the best, cost effective service to use.

However, in NOT recognizing that they are the ultimate service providers for their customers, they are trying to outsource accountability and effectiveness.

Take for example, the recent failures of Healthcare.gov, there were at least 55 major contractors involved, but no major end-to-end testing done by HHS.

We can't outsource accountability--even though the cloud and outsourcing is tempting many to do just that.

Secretary Sebelius has said that the buck stops with her, but in the 3 1/2 years leading up to the rollout relied on the big technology cloud in the sky to provide the solution.

Moreover, while Sebelius as the business owner is talking responsibility for the mission failures of the site, isn't it the CIO who should be addressing the technology issues as well?

IT contractors and cloud providers play a vital role in helping the government develop and maintain our technology, but at the end of the day, we in the government are responsible to our mission users.

The relationship is one of partners in problem solving and IT product and service provision, rather than service brokers moving data from one cloud provider to the next, where a buck can simply be saved regardless of whether mission results, stability and security are at risk.

In fact, Bloomberg BusinessWeek outlines the 3 successful principles used in the creation of consumerfinance.gov by the new CFPB, and it includes: "Have in-house strategy, design, and tech"!

Some in government say we cannot attract good IT people.

Maybe true, if we continue to freeze salaries, cut benefits, furlough employees, and take away the zest and responsibility for technology solutions from our own very talented technologists.

Government must be a place where we can attract technology talent, so we can identify requirements with our customers, work with partners on solutions, and tailors COTS, GOTS, open source solutions and cloud services to our mission needs.

When Sebelius was asked on The Hill about whether Healthcare.gov crashed, she said it never crashed, which was technically incorrect as the site was down.

The cloud is great source for IT provision, but the pendulum is swinging too far and fast, and it will by necessity come back towards the center, where it belongs as an opportunity, not a compliance mandate.

Hopefully, this will happen before too many CIOs gut the technology know-how they do have and the accountability they should provide.

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

March 18, 2012

Your Leadership Ticket Is Waiting

A lot of colleagues tell me that they hate office politics, and for many it represents their one-way ticket to ongoing bickering, infighting, and a virtual endless cycle of unsatisfied wants and unhappiness.

Office politics is where the interests of multiple parties either converge or collide--where convergence occurs through feelings of interdependence (i.e. enterprise) and acts of teamwork, while collisions predominate by stressing independence (i.e. isolationism) and head-butting.

This is where good and bad leadership can make a huge difference.

- One one hand, a bad leader sees the world of the office as "us versus them" and fights almost indiscriminately for his/her share of scope, resources, influence, and power.

- On the other hand, a good leader looks out for the good of the organization and its mission, and works to ensure the people have what they need to get their jobs done right, regardless of who is doing it or why.

Thus, good leaders inspire trust and confidence, because they, without doubt, put the mission front and center--and egos are left at door.

Harvard Business Review (January-February 2011) in an article called "Are You A Good Boss--Or A Great One?" identifies a couple of key elements that inherently create opposition and competitiveness within the enterprise:

1) Division of Labor--This is the where we define that I do this and you do that. This has the potential to "create disparate groups with disparate and even conflicting goals and priorities." If this differentiation is not well integrated back as interrelated parts of an overall organizational identity and mission, then feelings of "us versus them" and even arguments over whose jobs and functions are more important and should come first in the pecking order will tear away at the organizational fiber and chances of success.

2) Scarce Resources--This is where limited resources to meet requirements and desirements impact the various parts of the organization, because not everyone's wishes can be pursued at the same time or even necessarily, at all.  Priorities need to be set and tradeoffs made in what will get done and what won't. Again, without a clear sense of unity versus disparity, scarcity can quickly unravel the organization based on people's  feelings of unfairness, dissatisfaction, unrest, and potentially even "mob rule" when people feel potentially threatened.


Hence, a bad leader works the system--seeing it as a win-lose scenario--where his/her goals and objectives are necessarily more important than everyone else, and getting the resources (i.e. having a bigger sandbox or "building an empire") is seen as not only desirable but critical to their personal success--here, their identity and loyalty is to their particular niche silo.

However, a good leader cares for the system--looking to create win-win situations--where no one element is better or more important than another, rather where they all must work together synergistically for the greater good of the organization. In this case, resources go not to who fights dirtier, but to who will most benefit the mission with them--in this case, their allegiance and duty is to the greater enterprise and its mission.

HBR states well that "In a real team [with a real leader], members hold themselves and one another jointly accountable. They share a genuine conviction they will succeed or fail together."

Organizations need not be snake pits with cut throat managers wanting to see others fail and waiting to take what they can for themselves, rather there is another way, and that is to lead with a shared sense of purpose, meaning, and teamwork. 

And this is achieved through creating harmony among organizational elements and not class warfare between them.

This type of leader that creates unity--builds enduring strength--and has the ticket we need to organizational success.

(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

March 7, 2012

The Meaning of CIO Squared

113
An article in CIO Magazine (1 March 2012) describes the term "CIO Squared" as "the combination of chief information officer and chief innovation officer," and goes on to provide examples of CIOs that are both of these. 

While I respect this definition of the term and think innovation is certainly critical to the success of any CIO, and for that matter any organization in our times, I have been writing a column called CIO Squared for a couple of year now in Public CIO magazine and have other thoughts about what this really means. 

Moreover, I think the article in CIO missed the point of what "squared" really implies. 

Like the notion that 1+1=3, CIO Squared is a concept that the CIO is not just multi-faceted and -talented (that would be 1+1=2), but rather that the CIO integrates multiple facets and roles and synergizes these so that they have an impact greater than the sum of the parts (i.e. 1+1=3). 

I see the CIO Squared fulfilling its potential in a couple of major ways:

- Firstly, many organizations have both a Chief Information Officer and a Chief Technology Officer--they break the "Information Technology" concept and responsibility down into its components and make them the responsibility of two different people or different roles in the organization. One is responsible for the information needs of the business and the other brings the technology solutions to bear on this.  

However, I believe that fundamentally, a truly successful CIO needs to be able to bridge both of these functions and wear both hats and to wear them well. The CIO should be able to work with the business to define and moreover envision their future needs to remain competitive and differentiated (that's the innovation piece), but at the same time be able to work towards fulfilling those needs with technology and other solutions. 

Therefore, the role split between the CIO as the "business guy" and the CTO as the "technology whiz" has to merge at some point back into an executive that speaks both languages and can execute on these.  

That does not mean that the CIO is a one-man team--quite the contrary, the CIO has the support and team that can plan and manage to both, but the CIO should remain the leader--the point of the spear--for both.  

Another way to think of this is that CIO Squared is another name for Chief Information Technology Officer (CITO). 

- A second notion of CIO Squared that I had when putting that moniker out there for my column was that the CIO represents two other roles as well--on one hand, he/she is a consummate professional and business person dedicated to the mission and serving it's customer and stakeholders, and on the other hand, the CIO needs to be a "mensch"--a decent human being with integrity, empathy, and caring for others.  

This notion of a CIO or for that matter any CXO--Chief Executive Officer or the "X" representing any C-suite officer (CEO, COO, CFO, CHCO, etc.)--needs to be dual-hatted, where they perform highly for the organization delivering mission results, but simultaneously do so keeping in mind the impact on people and what is ultimately good and righteous.

Therefore, the CIO Squared is one who can encompass both business and technology roles and synthesize these for the strategic benefit of the organization, but also one who is mission-focused and maintains integrity and oneness with his people and G-d above who watches all. 

(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

October 23, 2011

Architecting Crowd Control

Last week (19 October 2011) T3 Motion Inc. in CA launched their all electric Non-Lethal Response Vehicle (NLRV) for "crowd control."

The vehicle is a souped-up three-wheeled Segway equipped two compressed air powered rifles able to shoot 700 non-lethal rounds per minute of pepper, water, dye, or rubber projectiles, and each vehicles can carry 10,000 rounds.

According to Trendhunter, the NLRV also has a "40,000-lumen LED strobe light, a riot shield, a P.A. system, and puncture-proof tires" as well as a video camera.

The notion of a law enforcement officer shooting an automatic (non-lethal, as it may be) to quell a riot does not quite fit in with general first amendment rights for peaceful assembly and typical demonstrations that as far as I know are generally NOT an all heck break loose scenario.

I wonder whether instead of a NLRV for handling riot control, a better idea would be a Lethal Response Vehicle (LRV)--with proper training and precautions--to handle homeland security patrols at major points of entry and around critical infrastructure.

From an architecture perspective, this seems to me to be a clear case of where a "desirement" by somebody out there (gaming, fantasy, or what not) should be channeled into fulfilling a more genuine requirement for people actually protecting our homeland.

The benefits of speed and maneuverability can benefit field officers in the right situations--where real adversaries need to be confronted quickly with the right equipment.

Share/Save/Bookmark

July 4, 2011

Appropriate Technology For All

For July 4th, we headed down to the D.C. Folk Life Festival today on the Washington Mall.

The Peace Corps had a number of exhibits at the festival, including one on what they call "Appropriate Technology."

Appropriate technology is about being user-centric when applying technology to the local needs and realities on the ground around the world.

There are 3 key rules in developing and implementing appropriate technology:

1) Affordable--technology has to be affordable for the people that are going to use it. Even if it saves money in the long-term, it has to be something that can be acquired by people without access to traditional financing in the short-term.

2) Local--the material must be available locally in order to make it accessible to people living in remote and even dangerous parts of the world.

3) Transparent--the design of the technology must be transparent with the assembly instructions available to the local people, so that it can be maintained indigenously.

One company that is helping needy people around the world using appropriate technology is Global Cycle Solutions.

Two products from this company that attach to your bicycle were on display and one was actually being demonstrated:

1) Corn Sheller--For $75 plus shipping this attachment to your bicycle shells corn from the husks in pretty amazing speed. According to the supplier, you "can fill a 90-kg sack of maize in 40 minutes and 10-15 sacks per day...[so the] machine pays for itself within a month." (Pictured you can see the exhibitor from Peace Corps loading the corn into the device and the husk coming out the other end; a little girl is pedaling and powering the device in one, and a little boy is spinning the wheel in the other.)

2) Phone Charger--For $10 plus shipping this bicycle attachment charges your phone as you pedal from place to place or as you spin the wheel in place. According to the website, it "charges as quickly as using a wall outlet." (Pictured is the bike and charger on display.)

Since bicycles are routinely found around the world, these add-on devices that help in food preparation and communications are practical and cost-effective.

Appropriate technology is not a technical term and the concept is not rocket-science, yet if we just keep in mind the people we serve--what their needs are and what constraints they may be living under--we can make solutions that are functional, cost-effective and sensible, and we'll can help a lot of needy people in the world, bells and whistles aside.

(Source Photos: Andy Blumenthal)







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

January 9, 2011

The Center Of Gravity Is Information

Center of Gravity (COG) is a military concept that Dr. Joseph Strange defines as “primary sources of moral or physical strength, power, and resistance.” From a military perspective, this is where we should concentrate when attacking the enemy. As Prussian strategist Carl von Clausewitz states, “that is the point against which all our energies should be directed.”

In “Center of Gravity Analysis” (Military Review, July/August 2004), Army Colonel Dale Eikmeier describes the framework for COG and how an enemy (your threat) attempts to exploit them, as follows:

· Center of Gravity—the organizations that do the work (e.g. the military/industrial complex)

· Critical Capabilities (CC)—the strengths of the organization—its “primary abilities”

· Critical Requirements (CR)—the supplies that a COG use—the inputs that are their opportunities, if leveraged for future plans

· Critical Vulnerabilities (CV)—the vulnerabilities a COG has—e.g. exposed or unguarded critical infrastructure

From an enterprise architecture perspective, I greatly appreciate this analysis of COG as it aligns beautifully with Albert Humphrey’s famous Strenghts, Weaknesses, Opportunities, and Threats (SWOT) Analysis for organizational strategic planning.

Aside from typical SWOT analysis to develop your organization’s strategy, the COG analysis adds greater offensive analysis to SWOT--like the military, organizations using the COG model can disrupt competitors’ advantages by seeking to weaken them where they are most vulnerable.

For example, EA used in this fashion may lead a company to build a sophisticated online sales site that directs customers away from your competitor’s retail location. Similarly, acquiring a major supplier (i.e. vertically integrating) may disrupt a competitors’ supply capability, and so on. The point is that EA becomes a force for attack rather than a mere planning tool or information asset.

It is at this point that I disagree with the assertion in the article that “Information is not power; it is a tool, an enabler. It helps wield military or economic power. By itself, it is simply information.”

Far to the contrary, information is one of the greatest assets that we have. It is the way that an advanced, intellectually based society competes. Of note, our declining performance in Science, Technology, Engineering, and Mathematics (STEM), which is so greatly worrisome to our leadership, is of concern because it is directly a threat to our competitive advantage, both militarily and economically, in the global environment.

Information, as embodied by the Internet, is now the center of our society. With it, we perform critical tasks of information sharing, collaboration and education. Used effectively, our military has developed robust command, control, communications, computers, intelligence, reconnaissance, and surveillance (C4ISR)—all information-based. Similarly, our industry is highly competitive and advanced because of the engineering, innovation, and people behind it.

Enterprise architecture, once a small part of the IT infrastructure, can actually play a far greater role in the information society if we allow it to. We have morphed from the industrial age of the 18th and 19th centuries to a highly advanced information society that creates new sources of critical capability, but also new critical vulnerabilities that must be defended. And we must also leverage the vulnerability of our enemies in order to stay viable. Whether it’s cyber-warfare or economic survival, information is at the heart of everything we are successfully doing today.


Share/Save/Bookmark

September 10, 2009

IT Communications, A Must Have

Being in a technical field like IT, we often see disconnects between the “techies” and the business people—almost like they are speaking foreign languages at each other. The result is that the techies don’t really understand the business requirements and the business people don’t understand the technical solutions. It’s sort of comical to watch, if not for being so sad in terms of the huge number of failed IT projects that result.

One thing we’ve realized is that we need to be able to communicate and communicate well between the business and IT or else we are not going to be very effective at IT service provision and enabling the business to perform at its best.

One solution has been to have IT staff whose job it is to translate between the business and IT units—these people are in roles at times called “business liaisons” or IT-business relationship managers. It is helpful to assign these liaisons to each business unit and give them authority and accountability for managing and nurturing a healthy relationship and unambiguous communication between business units and IT providers. The liaisons “own the customer” and ensure that requirements are captured correctly and understood by IT, that the proposed IT solutions are clearly explained to the business, and that the customer is satisfied with the systems and services they are receiving.

A second solution is hire IT communications specialists who more broadly “market” and communicate IT plans, policies, processes, goals, objectives, initiatives, milestones, and performance. I have found these professionals to be indispensable to “getting the message out there” and enhancing awareness and understanding for IT in the organization. Of course, IT leaders play a critical role in developing and honing the actual message, and in delivering ongoing two-way communications throughout the organization. In essence, they are the ambassadors and communicators par excellence inside and outside the organization with all IT stakeholders.

In short, IT needs to communicate early and often and communicate, communicate, communicate.

ComputerWorld, August 31-September 7, 2009 has a wonderful article affirming the criticality of IT communications in an article entitled: “Marketing IT: An Inside Job” by Mary Brandel.

As Brandel states: “It’s not about hype. It’s about conveying IT’s value.” I would add that it’s not only about conveying IT’s value, but also about creating IT value, by improving the two-way communication between the business and IT and thereby generating more effective solutions.

The article provides a number of useful suggestions for marketing and communicating IT that I’ve adapted, such as customer satisfaction surveys; IT annual reports that communicates accomplishments, alignment to strategic plan, “resources saved, awards won, and conferences at which staff members have spoken;” e-Brochures with “video coverage explaining goals,” services, policies, and plans; and Twitter alerts on service outages.

The key though which Bandel points out is that IT leaders need to “embed a 24/7 marketing mindset throughout the [IT] organization.” While business liaisons and IT communications specialists are focused on and specialize in this, it is still imperative for everyone in the IT organization to understand and be able to market and communicate IT services and processes to customers. All IT personnel are representatives to the business and should present and represent that customer service is our #1 goal.

From my perspective, this means transitioning our IT organizations to be wholly user-centric. This means a clear and ever present awareness that the business is IT’s raison d’être.


Share/Save/Bookmark

August 16, 2009

Vision is not a Business Only Matter

At an enterprise architecture conference a number of weeks ago, the audience was asked how many of you see yourself as technology people—about half raised their hands. And then the audience was asked how many see yourselves more as business people—and about half raised their hands. And of course, there were a handful of people that raised their hands as being “other.”

Then the dialogue with the audience of architects proceeded to regardless of whether you consider yourselves more business-oriented or more technology-oriented, either way, enterprise architects must get the vision from the business people in the organization, so the architects can then help the business people to develop the architecture. It was clear that many people felt that we had to wait for the business to know that their vision was and what they wanted, before we could help them fulfill their requirements. Well, this is not how I see it.

From my experience, many business (and technology) people do not have a “definitive vision” or know concretely what they want, especially when it comes to how technology can shape the business. Yes, of course, they do know they have certain gaps or that they want to improve things. But no, they don’t always know or can envision what the answer looks like. They just know that things either aren’t working “right” or competitor so and so is rolling out something new or upgrading system ABC or “there has just got to be a better way" to something.

If we plan to wait for the business to give us a definitive “this is what I want,” I think in many cases, we’ll be waiting a very long time.

The role of the CIO, CTO, as well as enterprise architects and other IT leaders is to work with the business people, to collaboratively figure out what’s wrong, what can be improved, and then provide solutions on how to get there.

Vision is not a business only matter—it is a broad leadership and planning function. IT leaders should not absolve themselves of visioning, strategy, and planning and rely only on the business for this. To the contrary, IT leaders must be an integral part of forging the business vision and must come up with an enabling “technology vision” for the organization. These days, business is more and more reliant on technology for its success, and a business vision without thought and input from the technology perspective would be superficial at best and dead of center at worst.

Moreover, visioning is not an art or a science, but it is both and not everyone is good at it. That is why open communication and collaboration is critical for developing and shaping the vision for where the organization must go.

Early on in my career, in working with my business counterparts, I asked “What are you looking to do and how can I help you?” And my business partner responded, opening my eyes, and said, “You tell me—what do you think we need to do. You lead us and we will follow.”

Wow! That was powerful.

“You tell me.”

“What do you think we need to do.”

“You lead us and we will follow.”

The lesson is simple. We should not and cannot wait for the business. We, together with our operational counterparts, are “the business”. Technology is not some utility anymore, but rather it is one of the major underpinnings of our information society; it is the driving force behind our innovation, the core of our competitive advantage, and our future.


Share/Save/Bookmark

July 14, 2009

A Call to IT Arms

Recently, I heard a colleague say that we should view IT not as a cost center, but as a resource center—and I really liked that.

In fact, IT is a cost center and a resource center, but these days there is an overemphasis on it being a cost center.

On the negative side, people seem to like to criticize IT and point out the spectacular failures there have been, and in fact, according to Public CIO “a recent study by the Standish Group showed that 82% of all IT project were either failures or were considered challenged.”

This is the dark side of IT that many would like to dwell on.

However, I would argue that while we must constantly improve on IT project delivery, IT failures can be just a point in time on the way to tremendous success and there are many of these IT successes that we benefit from in big and small ways every day.

Moreover, it may take 1000 failures to achieve that one great breakthrough success. That is the nature of innovation and experimentation.

Of course, that does not mean we should do stupid or negligent things that results in failed IT projects—we must do our best to be responsible and professional stewards. But, we should not be afraid to experiment and fail as a healthy part of the creative process.

Thomas Edison said: “I have not failed. I’ve just found 10,000 ways that won’t work.”

So why are we obsessed with IT failures these days?

Before the dot com bust, when technology was all the rave, and we enjoyed the bounty of new technologies like the computer, cell phones, handhelds, electronics galore, the Internet and all the email, productivity software and e-commerce and business applications you could ask for, the mindset was “technology is the engine that drives business.” And in fact, many companies were even changing their names to have “.com” in them to reflect this. The thinking was that if you didn’t realize the power and game-changing nature of technology, you could just as well plan to be out of business in the near future. The technologies that came out of those years were amazing and you and I rely on these every day.

Then after the dot-com burst, the pendulum swung the other way—big time! IT became an over zealous function, that was viewed as unstructured and rampant, with runaway costs that had to be contained. People were disappointed with the perceived broken promises and failed projects that IT caused, and IT people were pejoratively labeled geeks or techies and viewed as being outside the norm—sort of the societal flunkies who started businesses out of home garages. People found IT projects failures were everywhere. The corporate mindset changed to “business drives technology.”

Now, I agree that business drives technology in terms of requirements coming from the business and technology providing solutions to it and enabling it. But technology is also an engine for growth, a value creator, and a competitive advantage!

Further, while some would argue these days that IT is “just a tool”, I would counter that IT is a true strategic asset to those who understand its role in the enterprise. I love IT and I believe we all do and this is supported by the fact that we have become basically insatiable for IT. Forrester predicts U.S. IT budgets in 2009 will be in the vicinity of $750 billion. (http://it.tmcnet.com/topics/it/articles/59200-it-market-us-decline-51-percent-2009-researchers.htm) Think about what you want for the holidays—does it have IT in it?

A recent article in the Wall Street Journal was about how the homeless are so tied to technology that many have a computer with Internet access, even when they don’t have three square meals a day or a proper home to live in.

Another sign of how critical IT has become is that we recently stood up a new Cyber Command to protect our defense IT establishment. We are reliant indeed on our information technology and we had better be prepared to protect and defend it.

The recent White House 2009 Cyberspace Policy Review states: “The globally-interconnected digital information and communications infrastructure known as “cyberspace” underpins almost every facet of modern society and provides critical support for the U.S. economy, civil infrastructure, public safety, and national security.”

It's time for the pendulum to swing back in the other direction and to view IT as the true strategic asset that it is.


Share/Save/Bookmark

May 1, 2009

Customer Service Will Always Be Goal #1

Too many organizations espouse good service, but very few actually excel and deliver on the promise.

However, one company is so good at it that it serves as the role model for just about all others--that company is The Four Seasons.

The Wall Street Journal, 29 April 2009 reviewed the book “Four Seasons” by Isadore Sharp, the luxury hotel’s founder.

Here are some things that I learned about customer service from this:

- Customer Service means reliability—“a policy of consistently high standards.” At Four Seasons, anyone who has visited the chain around the world [83 hotels in 35 countries]…can attest to its reliability. To be reliable, customer service is not just raising and holding the bar high-- having high standards for quality service--but this must be institutionalized through policy and delivered consistently—over and over again. You can’t have a bad day when executing on customer service. Fantastic customer service has to always be there, period!

For The Total CIO, this type of reliability means that we don’t focus on technology per se, but rather on the customer’s mission requirements and how we can consistently deliver on those in a sound, secure, and cost-effective manner. CIO leaders establish high standards for customer service through regular performance plans, measures and service level agreements. Reliable customer service is more than a concept; it’s a way of relating to the customer in every interaction to consistently exceed expectations.

- Customer Service means innovation—“The things we take for granted now during our hotel stays-comfortable beds, fluffy towels, lighted make-up mirrors, fancy toiletries, and hair dryers-made their first appearances at the Four Seasons…likewise for European-style concierge and Japanese-style breakfast menus, in-hotel spas, and the possibility of residence and time-share units.”

For The Total CIO, technology changes so fast, that innovation is basically our middle name. We never rest on our laurels. We are always on the lookout for the next great thing to deliver on the mission, to achieve strategic competitive, to perform more cost effectively and efficiently.  Advantage. Moreover, we reward and recognize customer service excellence and innovation.

- Customer Service means valuing people—“Follow the golden rule. Workers are vital assets who should be treated accordingly…at the Four Seasons, those who might otherwise be considered the most expendable ‘had to come first,’ because they were the ones who could make or break a five-star service reputation.”

For The Total CIO, people are at the center of technology delivery. We plan, design, develop, and deploy technologies with people always in mind—front and center. If a technology is not “user-centric”, we can’t employ it and don’t want it—it’s a waste of time and money and generally speaking a bad IT investment. Moreover, we deliver technology through a highly trained, motivated, empowered and accountable workforce. We establish a culture of customer service and we reward and recognize people for excellence.

- Customer Service means solving problems—“Turning the top-down management philosophy on its head, Mr. Sharp authorized every Four Seasons employee to solve service problems as they arose to remedy failures on the spot.”

For The Total CIO, leadership is fundamental, management is important, and staff execution is vital. It is the frontline staff that knows the customer pain points and can often come up with the best suggestions to solve them. Even more importantly, the IT customer service representatives (help desk, desktop support, application developers, project managers, and so on) need to “own the customer” and see every customer problem through to resolution. Yes, it’s nice to empathize with the customer, but the customers need to have their problems fixed, their issues resolved and their requirements met.

The Total CIO will make these customer service definitions his and his organization’s modus operandi.


Share/Save/Bookmark

October 31, 2008

Weapons or Troops and The Total CIO

Should the CIO focus on day-to-day operational issues or on IT strategic planning and governance issues?

From my experience many are focused on firefighting the day-to-day and putting some new gadget in the hands of the field personnel without regard to what the bigger picture IT plan is or should be.

In many cases, I believe CIOs succumb to this near-term view on things, because they, like the overall corporate marketplace, is driven by short-term results, whether it is quarterly financial results or the annual performance appraisal.

The Wall Street Journal, 30 October 2008, had an article entitled,
“Boots on the Ground or Weapons in the Sky?”—which seemed to tie right into this issue.

The debate is to which kind of war we should be preparing to fight— the current (types of) insurgencies in Iraq and Afghanistan or the next big war, such as potentially that with Russia or China.

Why are we facing this issue now?

“With the economy slowing and the tab for the government’s bailout of the private sector spiraling higher…lawmakers are signaling that Pentagon officials will soon have to choose.”

And there are serious implications to this choice:

“The wrong decision now could imperil U.S. national security down the road.”

The two sides of the debate come down to this:

Secretary Gates “accused some military officials of “next-war-itis,” which shortchanges current needs in favor of advanced weapons that might never be needed.”

In turn, some military officials “chided Mr. Gates for “this-war-itis,” a short-sighted focus on the present that could leave the armed forces dangerously unprepared down the road.”

From war to technology:

Like the military, the CIO faces a similar dilemma. Should the CIO invest and focus on current operational needs, the firefight that is needed today (this-IT-itis) or should they turn their attention to planning and governing to meet the business-IT needs of the future (next-IT-itis).

But can’t the CIO do both?

Yes and no. Just like the defense budget is limited, so too is the time and resources of the CIO. Sure, we can do some of both, but unless we make a conscious decision about where to focus, something bad can happen.

My belief is operations must be stabilized--sound, reliable, and secure—today’s needs, but then the CIO must extricate himself from the day-to-day firefighting to build mission capabilities and meet the needs of the organization for tomorrow.

At some point (and the sooner, the better), this-IT-itis must yield to next-IT-itis!


Share/Save/Bookmark

October 26, 2008

IT Planning, Governance and The Total CIO

CIOs are consumed by day-to-day tactical/operational IT issues and firefighting IT problems, and as a result, there is a lack of focus on IT planning and governance—two of the biggest problems facing CIOs today.

ISACA, an organization serving IT governance professionals, conducted a survey consisting of 695 interviews with CEO/CIO-level executives in 22 countries, and published the results in IT Governance Global Status Report 2006.

Here are some of the amazing findings from this study.

Firefighting predominates: “Organizations are suffering from IT operational problems…only 7% of the respondents experienced no IT problems at all in the previous year…Operational failures and incidents…are mentioned by approximately 40 percent of respondents.”

IT’s alignment with Business is weak: Only 56% of the organizations surveyed “understands and supports the business users’ needs.”

Strategic Planning is underrated by CIOs: “More than 93 percent of business leaders recognize that IT is import for delivering organization strategy…Somewhat paradoxically, general management perceives the importance…slightly higher than does IT management.” In fact, in the public sector, IT was viewed as a commodity versus strategically by 47% of respondents!

IT governance is lagging: “CIOs recognize the need for better governance over IT,” to align IT strategy and manage risks. Yet, “when asked if they intend to do or plan IT governance measures, only 40 percent replied in the affirmative.”

Liza Lowery Massey, who previously served as CIO of Los Angeles, says in Government Technology, 9 July 2007:

“Establishing IT governance up front is the No. 1 thing I would do over in my career. IT governance is crucial to a CIO’s sanity.

Further, Liza wrote in Government Technology, 14 April 2008:

“Now when I help my clients implement IT governance, I see the benefits firsthand. They include shrinking your IT department’s to-do list, achieving IT/business alignment, putting teeth into policies and standards, and focusing departments on business needs rather than technology. My work life would certainly have been smoother had I set up governance to address these issues instead of trying to handle them all myself.”

CIO Magazine, 1 November 2006, has an article by Gary Beach, entitled “Most CIOs Fail to Convince Top Management That IT Can Transform Business.”

In this article, Gary notes that the rate of investment in IT is half the rate of corporate profit growth, and he asks why?

Certainly, the failure to align with business, and effectively plan and govern IT is hindering CIO’s ability to succeed.

The unfortunate result, as Andy McCue reported in Silicon.com on 26 April 2007, is that “CIOs and the IT department are in danger of being relegated to the role of support function because of a lack of vision and technology innovation.”

The answer is clearly for CIOs to “stabilize the patient” and get out of firefighting mode, and allocate sufficient time, attention, and resources to IT planning and governance. Only in this way will CIOs effectively align IT with business requirements, solve genuine business problems, innovate and transform the enterprise, and fulfill the strategic role that the business is looking for from them.


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