Showing posts with label User Needs. Show all posts
Showing posts with label User Needs. Show all posts

January 25, 2016

Stack Theory Doesn't Stack Up

Christopher Mims' article in the Wall Street Journal today on why big companies get disrupted by others doesn't make a lot of sense to me. 

He discusses the "Stack Fallacy" of Anshu Sharma a venture capitalist that it "is the mistaken belief that it is trivial to build the layers above yours."

Mims explains that the stack is like a "layer cake of technology"--where one layer is built on another.

Similar to the OSI technology model where there are architecture layers for physical, data, network, application and so on. 

Basically, Mims explains that tech companies can only invent at a single layer of technology (or below). 

But when companies try to invent up the stack, they fail.

Here's why...

Mims says that companies despite their size and resources can't innovate up the stack because they don't understand the users there. 

But this doesn't stack up to me. 

Companies can and do use their resources to study and understand what users want up the food chain and what they can't easily build, they can acquire. 

Apple successfully went from a iPod and iTunes music player and song store to producing a highly sophisticated and integrated iPhone and Apps store where music is just an afterthought.

Similarly, IBM went from being primarily a mainframe and desktop company to being a top-tier consulting firm with expertise in cloud, mobile, social, artificial intelligence, and analytics computing. 

But it isn't easy for a company to change. 

And to me, it's not because they can't understand what users want and need. 

Rather, it is because of something we've all heard of called specialization. 

Like human beings, even extraordinary ones, companies are specialized and good at what they are good at, but they aren't good at everything. 

A great example of this was when NBA superstar, Michael Jordan, tried to take his basketball talents and apply it to baseball...he was "bobbling easy flies and swatting at bad pitches" in the minor leagues. 

As even kindergarteners are taught that "Everyone is good at something, but no one is good at everything."

Companies have a specific culture, a specific niche, a specific specialization and expertise.

And to go beyond that is very, very difficult...as IBM learned, it requires nothing less than a transformation of epic proportions. 

So I think Mims is wrong that companies can't understand what users want in areas up the innovation stack, but rather it's a monumental change management challenge for companies that are specialized in one thing and not another. 

So welcome to the world of Apple after Steve Jobs and his iPhone and to the the recent 25% decline in their stock price with investors and customers anxiously waiting for the possible but not certain next move up the technology stack. ;-)

(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

December 12, 2009

EA Can Do It

A number of weeks ago, I was at a CTO Event in DC and got to hear from colleagues about their thoughts on various technologies and IT trends. Overall the exchange was great, and as always, I was deeply impressed with the wisdom and experience of these IT leaders.

However, one particular set of comments set me back in my chair a little. And that was on the topic of Enterprise Architecture. Apparently, a number of CTOs (from a relatively small number of agencies) had not had great success in their organizations with EA and were practically questioning it’s very existence in our IT universe. Yikes!

I believe some of the comments were to the effect (and this is not verbatim—I will put it euphemistically) that these individuals had never seen anything valuable from enterprise architecture—EVER—and that as far as they were concerned, it should be discontinued in their organizations, altogether.

In thinking about the stinging comments from some of the IT leaders, I actually felt bad for them that they had had negative experiences with a discipline like EA, which is such a powerful and transformative planning and governance framework when implemented correctly—with the value proposition of improving IT decision making and the end-user as the focal point for delivering valuable and actionable EA information and governance services—generally what I call User-centric Enterprise Architecture.

Right away after the negative comments, there were a number of CTOs that jumped up to defend EA, including me. My response was partially that just because some EA programs had not been successful (i.e. they were poorly implemented), did not mean that EA was not valuable when it was done right—and that there was indeed a way to build an organizations enterprise architecture as a true beacon for the organization to modernize, transform, and show continuous improvement. So please hold off from dismembering EA from our organizations.

Recently, I was further reassured that some organizations were getting EA, and getting it right, when I read a blog by Linda Cureton, the new CIO of NASA who wrote: NASA CIO: How to Rule the World of IT through Enterprise Architecture.

In the blog, Ms. Cureton first offers up a very nice, straightforward definition of EA:

“Let me step back a bit and offer a simple definition for Enterprise Architecture that is not spoken in the dribble of IT jargon. In simplest terms, it is a planning framework that describes how the technology assets of an organization connect and operate. It also describes what the organization needs from the technology. And finally, it describes the set of activities required to meet the organizational needs. Oh, and I should also say it operates in a context of a process for setting priorities, making decisions, informing those decisions, and delivering results called - IT Governance.”

Further, Ms. Cureton draws some parallels from a book titled How to Rule the World: Handbook for an Aspiring Dictator, by Andre de Gaillaume, as follows:

It is possible to manage IT as an Enterprise.

· You can use the Enterprise Architecture to plan and manage the kinder, safer, more cost effective IT world.

· Transformational projects will successful and deliver desired results.

· IT can be a key strategic enabler of NASA's [and other organizations] goals.”

Wow, this was great--an IT leader who really understands EA and sees it as the tool that it genuinely is for--to more effectively plan and govern IT and to move from day-to-day organizational firefighting to instead more strategic formulation and execution for tangible mission and end-user results.

While, I haven’t read the dictators handbook and do not aspire to draw any conclusions from it in terms of ruling the world, I do earnestly believe that no organization will be successful with their IT without EA. You cannot have an effective IT organization without a clear vision and plan as well as the mechanism to drive informed decision making from the plan and then being able to execute on it.

Success doesn't just happen, it is the result of brilliant planning and nurtured execution from dedicated and hardworking people.

Reading about NASA’s direction now, they may indeed be looking to the stars, but now, they also have their eyes focused on their EA.


Share/Save/Bookmark

May 21, 2008

Ask the User and Enterprise Architecture

The best way to find out what the end-user wants is to ask them.

The Wall Street Journal, 25 January 2008 reports on Ask.com that “Ask Searches for Answer to Luring New Users.”

Since 2006, Ask.com spent $140 million to Google’s $34 million on advertising between Jan. 2006 and September 2007, yet Google’s market share of the internet search business stands at 58.4% to Ask’s 4.3%, and “Ask’s market share hasn’t grown in the past couple of years, while Google’s…has seen its dominance increase.

Google is beating Ask based on “superior technology and word of mouth,” so the advertising is a moot point.

Jim Safka, the new head of Ask says that to understand the discrepancy, “the first step is figuring out who uses Ask today and what they use it for. We are not going to take wild swings.”

Apparently, Ask took some wild swings in the past without asking their users and ended up getting rid of the “Jeeves” from their original name Ask Jeeves.Com and getting rid of the “friendly butler designed to answer any question user posed him.”

Ask also goofed on a number of marketing campaigns which didn’t resonate with end-users, like “one campaign named ‘Use Tools, Feel Human’ [that] featured a primate [who] evolves into a human by using Ask.com.”

While “Ask’s market share continues to weaken,” Mr. Safka says that “Consumes are smart. If you look at the data and listen to them, the answer ends up being obvious.”

From a User-centric EA perspective, it is critical to ask the user what they want and understand their needs. One of the principles of User-centric EA is that we are focused on developing useful and usable products and services for the end-user; we do not build any information products that do not have a clear end-user and use. In contrast, traditional EA is often user blind and as a result develops “artifacts” that are difficult to understand and apply. Like Ask.com is learning, if you don’t understand your user’s needs, you end up with a lot of shelfware—whether it’s EA or search engines.


Share/Save/Bookmark

March 1, 2008

IT Project Engineering and Enterprise Architecture

Architecture and Governance Magazine, Volume 4, Issue 1, has an article called “The Secrets of IT Success: Transforming Companies” that identifies three critical architectural elements necessary for successful IT project execution, or as I see it, project initiation.

These critical IT project elements are as follows:

  • Community Analysis—“It must understand the needs of the customers, the supply chain, and the transactions necessary for the day-to-day running of the business…generate understanding on both the business and IT sides of the equation, to capture organizational goals comprehensively, and to enable effective training and buy-in, IT analysts and engineers must identify with and embrace the community to be transformed.”
  • Operations Analysis—“A deep understanding of the operational activities, capabilities, and business processes…Here work activities are identified, captured, and catalogued so that information flows, technologies, roles, and other processes and elements can be accurately mapped. The analytical results from this phase give a clear perspective to move from the business’s needs to the requirements of the new technology that will need to be implemented.
  • Technology Analysis—“technical needs are defined and blueprinted, and their intersections with business rules are specified…A multidimensional analytical view encompassing user workflow, technologies, data, security, business rules, and interfaces can greatly enhance the pure IT view of transformation.”

To me this translates in simple terms to the following:

  • Business needs
  • Functional and technical requirements
  • Technology solutions

While these IT project elements factor into the development of the enterprise architecture, they are more the domain of segment and solutions architecture that work toward business and operational outcomes, rather than strategic-level outcomes.

The article also calls for the use of visual tools to aid in IT project analysis:

  • In all three phases, a key ingredient is supplying a visual tool as part of the universal language that will be used throughout the project to facilitate clear communications between members of the community affected by it. Consistent and unambiguous visual expressions of the operational need and intent immeasurably enhance the likelihood of a successful IT implementation.”

This call for the use of visual tools is similar to and supportive of the use of information visualization in User-centric EA, where information visualization is especially helpful in the high-level, strategic profile views of the architecture as well as in modeling business, data, and systems. In all areas of User-centric EA, the principles of communication and design are critical for developing useful and usable information products and governance services for the end-user.


Share/Save/Bookmark