Ten Excepts From Business Architecture Brainstorming

Monday, August 13, 2012 | comments (1)

From Wickipedia, A business architecture is a part of an enterprise architecture related to corporate business, and the documents and diagrams that describe that architectural structure of business. People who build business architecture are known as Business Architects. Business architecture bridges between the enterprise business model and enterprise strategy on one side and the business functionality of the enterprise on another side.

Below are ten additional insights about BA via LinkedIn Brainstorming: 




  1. Business architecture seeks to represent the architecture of an organization in terms of performance, process, information and capability - either as it exists or as it is intended to be, thereby facilitating the planning and communicating of business change initiatives.

  1. Business Architecture is the requirement set for the Business;  IT architecture may be one of those requirements. Other requirements might include Capabilities, Processes, changes in organizational structure, changes in value chains and systems.

  1. Business Architecture is a series of methods and industry standard practices to describe what you do, why, how, where and whom derives or contributes value of such interactions. It’s about 90% of Why & What, and 10% of How.  This is captured at a high level in a current state ("as is"), an idealized future view ("to be") and a roadmap to take us there.

  1. Business Architecture input can be used into organizational structure, and scope of responsibilities in an alliance type venture; BA input can also be used into where to direct resources and attention to strengthen business capabilities;

  1. BA helps orchestrate the interrelationship between people and process, enterprise as a whole is more about people, process and technology. And EA = EBA + EITA, , BA may focus on strategy maps, organizational structure, business capability analysis, BA can also be taken as an effective communication tool with well-visualized deliverables. 
  
  1. Business architecture need define the following components:
    1) A framework for Business Architecture
    2) A Method (Cookbook)
    3) A set of deliverables
    4) A Meta model
  
  1. BA's Purpose: As an effective communication & governance tool to blueprint future of business, BA is not just for knowledge collection, more about capturing business insight/foresight.

  2. BA's Main Components: Business Value System, Organizational Structure, Business Processes, Business Capability, Business Culture…..

  1. BA's Hierarchy: A significant component of EA, 95% of votes agree EA = EBA + EITA

  1. BA's Users/Customers: Besides enterprise architects and business analysts, management teams from top-down, use BA to help in decision making. 

 The Future of BA Brainstorm:


  • Is there such thing as Agile BA or Social BA—the Blueprint for Social Enterprise or Agile Business.
  • Should Business Culture be included into BA?
  • How to make BA deliverable more visualized to delight users?

Three DIYs at Future of Enterprise

Sunday, August 12, 2012 | comments

Do not go where the path may lead, go instead where there is no path and leave a trail.    -- Ralph Waldo Emerson

Contemporary business becomes more complex than ever, due to the velocity and variety of changes and interdependent business eco-system, there's often a gap between what leadership says it wants and the types of behaviors that their management processes actually encourage. Therefore,  DIY –“Do It Yourself” culture should be promoting and permeating into future of true democratizing enterprise, from self-service leadership, to self-managing team, and self-service data and analytics,  as every leader and her/his organization will be pondering:

  • How can we be small and big at the same time, young and old, brave and wise, deep and broad?
  • How can we move towards a management model which works more with and less against human nature?
  • How can we qualify our thinking process to make decisions with the right data at the right time and at the right level?
  • How can we practice the coherent set of leadership and management principles?

1. Self-Service Leadership


  • Self-Service Leaders Convey Authenticity
 Leaders behavior is shaped by how leaders perceive themselves, by their character, drives and vision. At today’s social era, it’s more effective for leaders to lead via self-reflection or “self service”, such as blog or communicate through multiple social channels,  in order to deliver more cohesive message about authentic self and thought process in key decision making,  to build up unique leadership signature

The self-service leadership will deliver one’s self-concept which is reflected in the choices we make, how to procure the products and service, the criteria when selecting vendors, the value we appreciate, what professions to pursue, and how to exercise leadership., etc.

The good leaders are also good communicators. They have empathy to understand different audiences, and communicate appropriately in the right forms to the right people at the right level; The media may glorify and vilify a leader overnight, the rumors may destroy leaders’ reputation once a while, but a self-service leader will have self-confidence to deliver the vision when they encounter resistance, but also have self-awareness, be cautious about too strong ego which may become arrogant and narcissistic.


  • Consistency is paramount.
Self-service leaders may also lead via consistence, focus and sustainability. They express the cohesive messages about their leadership essentials and styles. DIY-self-service means open leadership, leaders enjoy sharing ideas, be open to new or creative ideas, always consider the other points of view, participate in and support group or team efforts, and work collaboratively with peers.

That said, self-service leaders eager to learn about self and others, willing to learn from feedback via social platform, also be interested in helping others think and experiment, embrace diversity, multiple sources and points of view,  be resilient and flexible about changes and communicate it clearly.

  • Underdog Leaders: Self-service is about using the right language of accountability
 Many underdog talents also face all different kind of career ceilings, self-service is a better practice to use the language of positive self-promotion and accountability, it’s more about promoting fresh concept, updated knowledge, and unique value proposition, to break stereotypical leadership image in 20th century, and standout to be a strong influencer & thought leaders who can make the dent in the universe and advance humanity.

Self-service underdog leaders can build up reputation via open mindset, and relying on healthy discussion & facts and collective wisdom to point the way toward the right conclusion or decision, also become advocate of diversified viewpoint and cultivate more high-potential underdogs. 


2. Self-Organizing Team, Self-Regulated Organization


  • Self-Organizing Team Nurtures Creativity:
 In 20th century’s command-control working environment, majority of employees are doing what they’ve been told, compliance is the key to survive; that’s why two third of employees do not feel engaged at work. Now,  the business becomes more dynamic, innovation is the only light every organization is pursuing now, at 21st century, nobody comes to work for being managed reactively, what maters now is creativity, the talents desire to work at the environment where they feel fulfilled and successful. And all talents intend to be self-determining and autonomous.

  • Agile –Self-Organizing Team Best Practice
 Self-Organizing team such as Agile/Scrum engineering team focuses on delivering work via culture of “PULL”, such a team well suited to adapt to the rapidly changes and complex business dynamic base on the interconnected actions of competitors, customers, users, and follow three I principles: Incremental, Iterative and Improving, it’s more focus on outside-in, customer viewpoint, instead of traditional top-down, inside-out business hierarchy.

Self-organizing team does not mean chaos, it means to build the cornerstone of self-regulating business, it should encourage transparency, and it won’t happen in darkness, there’s approval needed in big changes, the team secures flexibility and room to act and perform, the practice need reflect the fairness of the holistic performance evaluation, where changes in assumptions can be taken into account.


3. Self-Service Data & Analytics



  • Self-Service Data:
 We are not only embracing DIY culture enhanced by the latest technology trends such as CoIT-Consumerization of IT, and Social computing tools, now, we also live at the era of Big Data. The next level of self-service is self service on the data, both for internal and external use. It is about opening data and mastering the data, in order to gain business insight about customers, employees and products/services.

It will be an imperative to be able to do self-service on the data, because modern enterprises need to be much more permeable than they are accustomed to be. Business functions can self-service the data to analyze and capture the means for improving business. Protecting the data appropriately is essential while allowing self-service. So IT will focus on security, availability, and reliability increasingly.

  • Self-Service BI and Analytics
 With self-service data, non-technical users with easy-to-use analytics tools can be empowered to generate insights found that proactively responding to constantly changing business need, which is also the predominant reason organizations are sharpening self-service capabilities.

From a macro perspective, it’s easy to identify the biggest long-term trend in business intelligence, the self-service analytics tools are providing more professionals with the better interface, visual capabilities to access, analyze, and share data on their own. Such light-weight analytics tools will encompass a smart business with culture of DIY & analytics. 

DIY, is no long just a acronym or buzzword, it’s the mainstream culture in the future of business. 

Five Criterias How CIOs Evaluate Vendors

Thursday, August 9, 2012 | comments


Customer-vendor relationship at modern business is both art and science, complex also critical, but it’s worth the effort to craft such a good long term relationship, especially for IT vendors, how to delight customers takes both aptitude and attitude, how modern CIOs evaluate vendors also takes fair judgement and deep knowledge, here are some collective wisdoms from one of LinkIn discussions, and there're learning lessons for both CIOs and vendors:

1. Golden Rule:

Treat customers' problems as your own, do the best to take care of it;

·       Vendors should share the same vision and direction together with their clients.
       A successful relationship will still be as vibrant in 5 - 10 years as it was during the buying/selling cycle if all parties collaborate and share what they are really trying  At the end of the day,  all parties are trying to achieve the same thing - delivering business value based on their model. These can be mutually beneficial not mutually exclusive. 

·       Solve Customer-Vendor Conflict: The "Silver Bullet Foundation" is full of people who thought they were buying something that was going to fix everything. The "Vendor Presidents Clubs" are filled with many who have achieved selling the silver bullet promise. The people typically foisted with the blame are those charged with the change management and implementation.

·       Two-Way Communication: The successful customer-vendor relationship is for the customer and vendor to understand the problems need be solved via well described methodology and the effective communication vocabulary,  as the speed of change is accelerated, business need well define the requirement and specification clearly, but business dynamic may not allow them to get anything they need when they have them; vendors should make continuous communication & improvement with client;  

·       Knowing how to put together a complete solution that works in the best interest of all related constituencies in the business. Often understanding the dynamic change and growing complexities in supplier agreements comes secondary. First is understanding what is truly needed internally across business, IT, finance, procurement, supplier and contract management, legal, etc.

 2. Best Possible Solution – if it’s not Complete Solution

Everybody talks about customer experience these days, IT vendors are no exception, how to design, not necessary "complete solution", but customer-tailored, best possible solutions, help customers overcome real business obstacles or add value via well-defined KPIs, that's the key to build up win-win situation.

Both Customers & Software vendors have to walk into any major transformation projects with their eyes wide open, fully expecting to apply changes as they move forward - this flexibility has to be part of the transformation strategy

    1. The buyer's long term goals are accurately represented internally at the seller.
    2.  The seller's capabilities to fulfill said goals are also accurately stated.
    3. Other expectations are managed successfully.
    4.  The appropriate resources can be quickly marshaled on both sides in the event that something occurs requiring remediation
    5. A good IT vendor focus on processes, and there's always opportunity for improvement.
    6. "grade" or "range" solutions. by offering a range of solutions, each with different results and budgets and risk profile, vendor can actually help clients surface and resolve their internal conflicts, which can give you a leg up in the selection process 
    7. Being a Trust Advisor: The real win-win to this is when you couple the above with the ability to not only understand IT strategy at the buyer but also synthesize that with information gathered elsewhere to identify gaps in the strategy that were overlooked by the client.

 3. Attitude: Under-promise, Over-delivery:

Certainly some vendors will offer best possible solutions if complete solution impossible; It takes the great attitude, the product itself, the professional services to tailor the product to the client’s specific needs, and training to ensure the client and their team have the necessary skills to maintain/enhance the solution as they move forward. Do all vendors do this? Certainly not. Many are simply focused on providing a product they call a solution and then walking away. Some popular symptoms:

·       Over-Selling:  in order to sell, vendors are often presented with a solution which is so to speak "aligned" with customer’s problem. When in fact it wouldn't be. 

·       Under-Delivering: there are too many wants that are unfulfilled - either oversold at the point where they bought the software -- or missing or broken code that should have been there in the first place. Business needs keep evolving, and what we need today may no longer be valid a short time later.

·       Fear: The third problem is the fear, to make a mistake for the customer. Vendors are aware of costs and the risks. And it gets worse when you have a time pressure. And the fear not to be able to sell for the vendor

·       Not Coach Customer Well: Solutions continue to evolve (more releases) but the customer does not get couched in dynamic environments. New customer process changes, technology impacts, economic, and political policy trigger changes in the customers’ environment thus changing the need. At least this is how new releases should be pursued - ever improving upon the value delivered to the customer, and customers need be coached accordingly.

4. Play Trilogy Fairly

The relationship between the vendor and IT is echoed often, it's not always just the IT and vendor that are working towards a solution. The business is usually involved if it is a business application. Thus, its not just the customer-supplier engagement model that impacts but business-IT engagement model. Hence the unholy trilogy tends to be business-IT-vendor,  and quite often the vendor gets away with deal when they have a better alignment to the business than IT. However, that is usually when governance becomes the ultimate critical issue as scope management leads to budget blow out and then ultimately its becomes a $ driven project, it’s the root cause for shadow IT cropping up.

The trilogy also often happens after someone got an approved budget (estimated internally) which then is expected to cover the cost of the vendors’ deliverables. That is something that needs enhancement and requires serious gathering of requirements up front between business and IT for sending out RFQs before going through budget approvals. 

As Vendor, how to manage customer relationship properly, to help smoothen business-IT-vendor trilogy, not the other way around? Strategically speaking, what businesses expect from IT is also about what IT expects from the vendors, it's more about the speed, the scale, the value and the choices; is vendor up to the speed and delivers the values both parties agree on, does vendor provide choices for customers to fulfill the goals; is vendor both accountable when having problems or flexible enough to solve the issues.

5. No Negative Surprise

 With today's mega-integrated solutions and product catalogs, customers encounter holes and gaps of missing, untested, buggy workarounds or are 'stranded' because of requirements for this and that enhancement pack or maintenance upgrade that is additive to the original implementation. Sometime vendor-customer relationship becomes a 'captive' model, due to enormous customer investment and integration, suppliers are focused on acquisitions and integrating them within their product lines and never seem to be able to get the job 'done' before the next one. 

Customers’ other primary concern is the lag between the promise and the delivery. Or "its in the next release" syndrome is just a symptom of unmanaged expectations. Releases need to exist if not just for the sake of innovation and continuous improvement of the software.

Therefore, at today’s business dynamic, implementing new software requires companies to steer away from traditional contracting and focus on digging deep into how leveraging optimization and negotiation processes/methodologies can provide flexibility and protections to ensure that the software meets changing business requirements over the life of the investment.

Do not show customers too many such "surprises"--charging further without notice, increasing pricing without reason, or getting next release without improvement.

Instead of "complete solution", most of businesses will more appreciate Agile solutions, innovative vendors, with good attitude, not just treating customers as cash cow, but as long term partners, help solve business problems more radically, the value proposition between sellers and buyers is in balance. These are the right ways for mature vendors to delight CIO and customers.




CIO as Producer, API as Lego Blocks

Tuesday, August 7, 2012 | comments

Today’s CIO has many roles, from business strategist to innovative intrepreneur, from technology visionary to talent master, now, we may need add a new one: a producer, not for TV show, but for digital business services, as IT turns to be a platform for co-creation and digital engagement via an agile IT architecture with speed. A recent released API business value report from PWC may help CIOs gain some insight on being a successful producer:


1. Architecture with Speed

 API is the acronym for application programming interface, a technology term that means the specifications for how software programs are able to exchange information with each other even if designed and run by different organizations.

First of all, CIOs should understand that using APIs is an architectural choice, not a technology choice, second, a relatively new style of APIs, called representational state transfer (RESTful) APIs, which is pull-centric, not the traditional push model,  inspires the new architecture and platform thinking, the goal is to architect a collaborative environment for co-creation, it need be part of IT strategy, as it’s high level architectural change, and it takes audacious IT leadership. 

The new architectural principle and programming model based on RESTful APIs reduces integration cost and complexity, so integrations can scale for many internal as well as external uses. Statistics suggests that using [RESTful] APIs reduces development time by 50 to 75 percent. As SOA has largely remained internally focused, RESTful APIs, sharply reduce the cost and complexity of integrations, deliver a scalable approach for both internal and external use, also accumulate less technical debt for every new piece of functionality created.

From a few user case studies, RESTful API interfaces build up the modular capabilities,  create a level of simplicity that didn’t exist previously, and simplicity speeds things up, making integrations cost-effective.

2. Running IT as Software Company

 IT has to adapt to faster business tempo today, CIO leadership must keep a balance in this evolution and manage IT assets in new ways. The advice to CIOs is to approach the evolution in five dimensions:

  • Business Strategy & Purpose: Framing a customer-centric enterprise via  digitization is a significant transformation facing many organizations today, from IT perspective, most IT organizations spend way too much time building applications and not focusing on the customers, to quote Drucker: “ the purpose of business is to create a customer”.

  • Business Capability Orchestration:  Loosely coupled modular capabilities: means the use of open software interfaces on modular capabilities to allow easy digital connections with other capabilities, internal capabilities and processes are broken into modular service components that have standard open interfaces. Business capabilities and assets inside the enterprise are easily combined with assets and capabilities outside the enterprise.  Loose coupling makes it possible to change the components without affecting the system, as long as the interface is kept stable.

  • Developer community management: The ability to co-create in a digital ecosystem—A co-creation strategy treats customers, channel partners, suppliers, and industry ecosystem participants as active agents who have permission to combine the modular capabilities exposed in a platform to create new experiences. Sophisticated enterprises are starting to think more like a software company—as a platform and an ecosystem. This increase in APIs has led to the need for tools and services that help companies create, publish, manage, operate, and analyze APIs.

  • CIO as Producer: not producing movies or TV shows, but for producing digital services;  IT don’t have to do all the coding anymore. The key role for IT is to be the owner, producer, and platform of the services. Business units, even third parties, can use the services to develop a new capability. The CIO organization therefore will become an orchestrator of services—across vendor capabilities, published services, and consumed services—a role that the new architecture will need to acknowledge and enable.

  • Analytics and reporting:  Analytics helps companies understand and improve the value of their APIs. Value driven analytics gauge API adoption by measuring traffic, purchases, and registrations. With API traffic control tools, companies can define and enforce levels of partner access to data consumption. API analytics tools can also help diagnose performance and scalability issues associated with API platform growth.

 3. SMAC Embraces RESTful APIs

Today’s business leaders are capitalizing and operating on digital ecosystems that are expanding due to the confluence of social networks, mobile computing, analytics, and cloud computing (SMAC). SMAC also provides unprecedented opportunities for enterprises to take advantage of the innovative disruptions.

SMAC represents an acceleration of change that is overwhelming to the current IT approach of owning the end-to-end experience. Today’s methods do not scale to address the challenges that SMAC presents: too many variations in use cases and too many endpoints. In addition to understanding and having strategies for these individual SMAC
technologies, enterprises should look at abstractions that bring together these technologies where they intersect. RESTful APIs have been used as key enabler of such digital connector, creates significant new opportunities for enterprises to transform internally to a digital operating model and to engage externally with the evolving digital ecosystems.

The APIs bring up the reality that there are just too many niches solutions that customers need to be served. No business will be able to do all of the scenarios. In a digital world, an API is a good interface to enable many distribution channels. The best designed APIs are designed for a public audience, in order to get value among the long tail of developers

In conclusion, CIO need craft a good strategy on how the businesses participate in digital channels via taking advantage of APIs, CIOs have many things to experiment these days, they need to know how to integrate services in the cloud. They’ll need to understand how to deploy using APIs, they also need use social/mobile platform to engage customers and employees, analyze Big Data to capture business insight, hopefully APIs are such lego blocks to help shape an Agile social Enterprise.

Long Live Curiosity: Three Lessons from The Olympic Champion on Mars

| comments

Nasa reported the Curiosity had landed on Mars “wheels down” at 10:31 PST August 5, 2012, it’s not only the leapfrog progress for Rocket Science, but also a celebrated advancement for humanity, as some declared, is era of imagination really coming?

What can we learn from curiosity’s landing and her adventure on Mars:


1.    “The Seven Minutes of Terror” to “Seven Minutes of Triumph”

“A Seven minutes of terror” means – once Curiosity hit the Martian atmosphere, it completed a complicated set of maneuvers – including hanging from a rocket-powered “backpack” – successfully in only seven minutes time. A 14-minute communications delay meant it all had to be programmed in advance, with no room for error. Had anything gone even slightly wrong, Curiosity would have smashed into the planet and the $2.5 billion mission would have been a complete failure.

No wonder, rocket science is still one of the most complicated, advance & adventurous disciplines, well combination of hard science with deep courage, to turn around “seven minutes of terror” to “Seven minutes of triumph”.


2.    “Lucky Peanut” –Rocket Scientists’ humbleness and humor

As bright as rocket scientists, when watching the video, we saw them to share peanut for good luck during the landing controlling hour, we perceived the humbleness and humor: Opportunity brings risk, a success takes 99% of perspiration, but still need add 1% of luck, to accomplish such a curiosity’s journey, as human, we may just need dream big, but feel humbled at the same time.

Risk taking is required, as is pursuing curiosity. Respecting and exploring nature will take both ambition and humility, discipline and adventure should go hand in hand,


3. Life Signs on Mars –Discover Humanity in Universe

Because the Gale crater exposes several layers of Martian strata to the surface, part of Curiosity‘s mission is to look for signs of that microbial life either exists or once existed on Mars. Curiosity will go up to different outcrops and different soil types and sample them. Dig in, pick something up and analyze it. And the instruments themselves are much more sophisticated than previous examples.


That said, Curiosity is fulfilling all of our curiosities, to discover humanity in universe. 

It takes collective wisdom and collaborate effort to explore space, and demystify many puzzles facing universal humanity today.

Welcome to the era of Imagination! Good Luck & Long Live, Curiosity!

Three Big Insights from Big Data

Sunday, August 5, 2012 | comments

Modern businesses all need learn how to swim at the sea of big data, to ride the wave, or avoid obstacles, after being through 5 Ws + 1H Big Data Navigation, some Olympic level data champions may gain the insights others can not perceive: 

 1. Customer Insight




  • Know What Customers Need Before They know Themselves

Big Data allows businesses to see customers’ behavior pattern they have never seen before, it also uncovers the interdependence and connections that will lead to a new way of doing business, or engaging customers’ feedback, do sentimental analysis or research on knowing what customers need before they even know themselves, and develop next generation of product, service or business model accordingly.


  • Optimize Customer Experience Life Cycle

Big Data also lets us see the “real-time” cause and effect of business’s actions and customers’ responses, Organizations that do so will be able to monitor customer behaviors and market conditions with greater certainty, and react with speed and effectiveness to differentiate from their competition. It will lead service innovation which can optimize customer experience life cycle based on personalization, targeted interactions & preferences and 360 degree view of customers, ultimately increasing customer loyalty by following 3 “I”s: Insight, Interaction, and improvement. 


2. Decision Making Insight

  
  • Operational Excellence: Businesses explore the power of big or small data to drive business decisions to create transparency in organizational activities that can be used to increase efficiency. Big Data analytics also improves the quality of business decision-making requiring organizations to adopt new and more effective methods to obtain the most meaningful results from the data that generate value.

  • Business Governance & Risk Management: Big Data can also help business to predict or detect fraud or bad behavior, breakdown functional silos to manage data more holistically, to converge IT governance with business governance, and enforce GRC discipline.

3. Talent Insight


  • Make sure the right talent at the Bus: It will always take  long term journey for identifying, attracting, developing and retaining the right people with the right capabilities at the right position,  via Big Data, talent manager can recognize thought leaders, social influencers or domain expert more easily; data analysis of employee and talent performances also allow experiments and feedbacks, make sure right talent at the bus at the right time;

  • From Talent Controller to Talent Multiplier: Talent managers start using data not just to monitor employees’ behavior, but to ask& answer some hard questions that are at the heart of how employees contribute to business performance, predict employee preferences and behaviors and tailor next practices to attract and retain talent. Develop predictive models and identify leading indicators to forecast business requirements and staffing requirements, track skills and performance, and maximize human capital investment.
  
Big Data is Big part of “the Internet of Things”, human and machine analysis of large data sets will also provide big insight beyond commercial value, it will have broad touch including social, political and economic intelligence, and has huge positive impact for society at many perspectives in the futre.



Insourcing vs. Outsourcing: Five Principles to Define IT Sourcing Strategy

Tuesday, July 31, 2012 | comments (43)

One of LinkedIn CIO discussions about the survey: "outsourcing takes big turn back in last two years and insourcing increased 35%. What are you seeing?” spur many quality comments about IT sourcing strategy, the other IT survey also shows: now most of customers, large or small, prefer to have more flexibility, do not like to tie into multi-year contract, on the other side, vendors may attract customers to mega-deal via pricing discount., etc. 

The world becomes more complex, change is accelerated, the present shift to insourcing those functions once again is an indicator that organizations are realizing they need greater flexibility and agility, which is a little more difficult to achieve when functions are outsourced.. Bsiness and IT also have more sourcing choices than ever, insourcing, outsourcing, on shore, near shore, off shore, and public/hybrid/private cloud sourcing, with all these, how to craft a good IT sourcing strategy?

1. IT Sourcing is Critical Element of Business/IT Strategy

IT sourcing is crucial for IT strategy –to decide what kind of IT organization you need become and climb IT maturity,  IT strategy is integral part of business strategy, that’s why IT sourcing will directly impact business’s strategy, innovation and vendor relationship for long term:

  • Business/IT Strategy: Business strategy is about diagnosing business problems, making a set of choices, following the guideline to take actions in order to compete for the future. IT as business enablers, is the means to the end, not the end, the end should be business agility, elasticity, flexibility and resilience. Many of times, business can’t articulate what they need, so centralized IT should collaborate with business to become value center. IT also need categorize its services into competitive necessities and competitive uniqueness, differentiate core from chore, focus on value delivery, taking continuous journey on consolidation, rationalization, integration, modernization and optimization via leveraging effective IT sourcing solutions.

  • Culture of Innovation:  Fully outsourcing IT services may present a challenge to creating a culture of innovation, achieving speed to market, and providing superior customer service/quality for companies in a dynamic and competitive market within the context of emerging mobile, social, and cloud computing technologies.

  • Vendor Evaluation/ Relationship Management: Sourcing can no long just consider cost, it's also about evaluating vendor's innovation capability, leverage expertise, add alternative brainpower & talent pool, and appreciate "take extra mile" attitude, to build up solid partner relationship for long term. First of all, business & IT need understand how to create value proposition in innovative service/products, customer experience and operational excellence, in which internal IT can do great job to orchestrate business capabilities; then IT may leverage vendors' strength, to complement the skills and strength. Also take consideration of vendor's soft competency such as take extra miles attitude, innovation capability and niche point, etc
         

2. You Can’t Outsourcing What you Don’t Understand

 Outsourcing and offshoring were never silver bullets for process inefficiencies or bad organizational design. There was too much of "my mess for less". Add in the cultural and communication issues,  the turnover and cost inflation in available resource pools, there was always going to be a point at which the reality overcame the theory.  The business also should no longer talk about outsource jobs to take political pressure, they are looking at both technical value and BUSINESS value a provider can put on the table of long term strategy.

That said,  first, business may still need "shoot the tangle, in order to see from different angle" internally, then make systematic decisions on your sourcing strategy/solutions, both methods have their place. Organizations need to take a hard look at what they are trying to achieve and determine which method works best, as insourcing vs.outsourcing vs. offshoring success depends on objective why it is done and what is required to be:

  • Insourcing is better for critical Domain Knowledge centric activities; business innovation driven project, to create competitive uniqueness for business growth.
  • Outsourcing is better if niche knowledge requirement for specific duration, repeatable transaction based, freeing internal resources for more value added area, and flexibility of Ramp-up and Ramp-down; 
         
  • Nearshoring/Offshoring: could be where there is a large knowledge pool available,  budgets are very tight while a demand for services remains high, follow the sun model, taking advantage of 24 hour clock and lower cost as added benefit,  tap into a global talent pool or the right "local" partners to expand.
  • Cloud Sourcing: The latest trend provides business more choices via vary of flavors : public, private and hybrid Cloud, SAAS/PAAS/IAAS/BPAAS,  to help customer leverage IT value, running IT as business, Cloud also provides better agility and elasticity via faster provisioning, Opex service model. 

3. SLA & KPIs Driven Hybrid Model

After being through decade long of outsourcing, it reaches the point where the private and public sectors are finally realizing that outsourcing is not as "simple" as they originally thought. When done right, yes, it can have benefits, but it requires hard work to manage and ensure that it is done correctly. You can’t manage what you don’t measure. 

The environment has become so competitive that SLAs/KPIs are continuously being driven up, thus, driving the costs higher that, in many cases, the cost-saving potentials are being watered down and questioned. And it still makes sense to find a sourcing partner for the necessary activities of a business that are not core to how you go to market and make money, no matter where you choose to have the work done. Balancing cost, quality and location in a 24 x 7 world isn't easy - we need all the sourcing strategies and options we can find to make this work effectively, especially with the quality going down and costs going up in the outsourcing model.

The outsourcing pitfall may also include miscommunication: the companies give lip service to "yes, we'll support increased communication and increased touch points", but most of the time they don't adjust project timelines and they treat their offshore counterparts as if they were just down the street. Then, they can't understand why the project is behind

The other problem is most companies swing to one extreme or another. There should be an optimum multi-sourcing strategy that is based on TCO and the total value.

 4.  Don’t Forget Hidden Cost or Shade of Grey 

A valid analysis lies in examining the motives and objectives that drove the outsourcing strategies of those companies in the first place.

  • Pay Cost later without careful analysis: Some companies follow the trend to offshore, without fully consideration about service levels, support, customer service and focus solely on the cost, until they realize that the hidden cost is that all of those things you give up, cost you time, efficiency, agility, frustration, retention.

  • Investigate beyond the Surface: The other angle to evaluate vendor and sourcing strategy is about investigating "hidden cost" or grey area, some reasonable, some not, and customers surely dislike to see such surprise too frequently, that said, selecting vendors or solutions, not only look at the surface, dig through and understand the pros and cons more objectively

 

5. Cloud Sourcing –Emerging Trend

Though outsourcing training is slowing, businesses now have more choices to fly in the cloud, the emergence of Cloud computing also provides business more choices to manage IT, particularly, as cloud has vary of flavors : public, private and hybrid to help customer leverage IT value, running IT as business, and focus on innovation & core activity, with the ability of IT department leadership to inspire the work force and increase the quality of the final product or service, Cloud also provide alternatives for faster provision, transform CapEx to Opex, to improve business’s cash flow.  

Flexibility and the ability to be drive radical business changes in pursuit of competitive advantage will define successful businesses in the future. The constant shift in corporate preference for sourcing models merely indicates that few have the right blend, and perhaps more importantly, the technology provision is increasingly perceived as a constraint to growth.

Companies need become more creative with their sourcing models and not committing 100% to outsourcing or insourcing. Outsourcing, whose effectiveness is predicated on operational excellence to provide the low costs, is the antithesis of agile changes and unique approaches required to keep up with the IT implications of business innovation.

Three Trends of Future of Leadership

Saturday, July 28, 2012 | comments

Leadership is both art and science, there’re numerous great books and articles every year to decode it, but nobody can completely solve leadership puzzle yet, though we brainstorm the seven ingredients for future of leadership, it seems always have some missing ingredients there, as leadership is also dynamic,  some prestigious management gurus articulate: the real leadership is about transforming the system now, could it be a missing ingredient? How to create it, what could be the future trends of leadership?

 1. Wisdom –Strategic Imperative

The fittest may survive; the wisest may lead; and the most innovative business may thrive;

Modern leadership puts some emphasis on leaders’ three types of intelligence:
Business intelligence to analyze and breakdown the problem, frame process to execute it; Social Intelligence: know the power bridge to lift up career; or Emotional Intelligence: act properly under pressure; it's necessary but not sufficient to lead at today's business dynamic: more mechanic than innovative, homogeneous than heterogeneous, even we expand them into ten intelligences for leadership innovation which are crucial for today’s leaders, still, there’s something missing,  at today’s super-complex, hyper-connected and interdependent business dynamic, walking through all sorts of intelligence, we may just need reach the next,  transformational level: wisdom:  

·  Wisdom is Highest Level of Intelligence:
Common sense in an uncommon degree is what the world calls wisdom. 

Intelligence may still divide the thoughts, wisdom will unify the cognizance, encircle the world; leadership wisdom is multi-dimensional pursuit of collective thinking, embrace full spectrum of diversity, culture and change management

·      Wisdom speaks of nature:

It’s reflection, or self-awareness; at pre-social age, we may know political or business leaders via media, as public face for their organizations,  but culture or media seems regard leadership as entertainment sometimes: glorify or vilify one promptly, appreciate & amplify the story such as: today's PR face of company is working for the competitor at the 2nd day, to blur the essential with style, to confuse trend with fad, or despise leadership value to reward opposite;

At today’s social era, it’s more effective for leaders to lead via self-reflection or “self service”, such as blogging or communicate through other social channels in order to deliver more cohesive message about authentic self and thought process,  to figure out unique leadership signature, put simply, leadership need present wisdom, not just put a show.
         
Leadership is influence, influence is from wisdom, wisdom speaks of nature, here is five nature views of leadership.

2. Three “C”s of Leadership Essential


Modern society may also blur leadership with management, there’s intersection between two disciplines, but leadership is more about effectiveness-doing right things, and management is more about efficiency –dong things right; Will three Cs here make leadership transformational –to hunt for such a missing ingredient?

<·     Character

 Character means many things, it’s the human's blueprint, the combination of values, attitude and the integrity,  also like a seed, with its own uniqueness & color theme, the nurturing environment may help sprout it up; The character of great leaders may also like diamond, solid, but not tedious; shining but not flamboyant, perfect balance of Ying & Yang, it can be polished for better!

Character may cascade more crucial Cs in leadership essentials:
--Courage: to overcome barrier, breakdown ceilings or correct bias;
--Confidence: Character is from heart, confidence is about heart feelings.
--Consistence: the characters may help develop habits to strengthen skills.

Character means the abstract level of human recognition: you may see something in common between a 10-year-old cute boy and Mother Teresa, like integrity/commitment; or a teen-age witty girl have same traits with Winston Churchill, such as tenacity and optimism.

Not only for leaders, at every level of talent recruiting and development, being a good judge of character… that's where the real skill gets tested, the value get rooted, and the performance get achieved, make a tough choice for your talent strategy to add the missing ingredient for business transforation.

·      Creativity

If wisdom is leadership’s strategic imperative, then innovation is business’s imperative today,  it's requirement for all leaders; not just entrepreneur; creative leaders may have nature curiosity to dig through; creative leadership will champion the culture of innovation, walk the talk, enjoy divergent thinking and new ideas; tolerate failure or reward the one who thinks differently.

To quote Colonel Scott Krawczyk, one of educators: “From the very earliest days of this country, the model for our officers, which was built on the model of the citizenry and reflective of democratic ideals, was to be different. They were to be possessed of a democratic spirit marked by independent judgment, the freedom to measure action and to express disagreement, and the crucial responsibility never to tolerate tyranny.”

·     Capability

1) Thinking Out Louder: Thinking Capability

Future of leaders need think creatively, independently reflectively and flexibly. As say going: you can send kids to college, you can not teach one how to think; Some high educated people may not know how to think at all; Thinking capability will be directly link to one’s wisdom, and leadership influence. As author of Solitude and Leadership well put: “Solitude, the ability to be alone with your thoughts. is one of the most important necessities of true leadership.”

2) Being Solutonary: Problem Solving Capability

The future of education is to produce solutionary, today and future of leaders need exemplify to be such a solutionary, that said, leadership is not about power play or just public face for business, it needs design, develop and deploy new ways of thinking (big ideas) that crafts good strategy, and inspire people to take action..  

3) Being Learning Agile: Learning Capability

Future of leaders need be coach, also “stay foolish stay Hungary” at the same time, leaders need continue to learn and influence not only the team, but also cross the team, work within the system and on the system, to make positive influence on culture and education.
  
Future of leaders need think big, deep and long, practice innovation, decision and action,

3. Leadership Convergence

 The missing ingredient of leadership may also be hunted through leadership convergence, leadership transformation need bother divergent thinking and convergent understanding.

 Leadership wisdom embrace inclusion: recognizing, respecting, managing and leveraging similarities and differences to achieve superior business results worldwide.

Leadership convergence also means all sorts of leaders: no matter you are leaders in public service or private sector; community or religion, entrepreneurs or enterprise executives cross-geographic boundary, can find common ground, appreciate same value, unify opinions, and make humanity progress, through universal wisdom. 

Leadership takes raw talent, but more about persistence, dedication, and some personal sacrifice, more importantly, the change is accelerated and the world is more connected, future of leaders need wisdoms, global mindset, and three C essentials: character, creativity, capability to shape up transformational leadership and embrace leadership convergence. 

DevOps: The New Muscles in Business’s Agile Wings

| comments

Modern business now embraces Big 4 technologies: cloud, mobile, social and big data, like winds at full-blow mode, business need grow agile wings to balance wind power, to become more flexible and elastic. 

Agile software development practices iterative & incremental methodology, where requirement and solutions are based on collaboration between selft-organizing, cross-functional teams, it intends to keep software project with its practical business goals;

Agile also continues shaping new muscles such as DevOps, which is a deployment pipeline that stresses communication, collaboration and integration between software developers and information Technology (IT) professionals.

 1. Agile & DevOps: The Solid Wings to Lift IT to Cloud

 The emerging Agile software development practices, is a less-risky model of what can happen when the product changes with frequent user feedback and minimal waste. Agile has already created a greater sense of collaboration within development teams, and cloud computing initiatives also serve as the catalyst for bringing development and IT ops together, because the cloud model demands a new mindset about how applications are developed, deployed, managed and measured.

That said,  Agile also means Agile Mindset. As Agile need for speed, traditional IT operation is risk reverse, prefer stability, the bottlenecks occurs. Therefore, DevOps grows into the new muscle, response to the interdependence of software development and IT operations. It aims to help an organization rapidly produce software products and services, produce leaner and more responsive team to deliver business value back to the client.

There’s also a pressing need for IT ops to collaborate more effectively with development teams—so that developers think about manageability requirements before the application rolls out to operations. It’s also about Agile culture and Agile governance.


2. Some Pitfalls to Pull Down Agile/DevOps Wings


  • Complexity: That could be a pitfall for agile developments if iterations and increments were to be associated with an exponential growth of complexity.

  • Short-term Inertia: Other potential pitfalls for Agile/DevOps,  such as defect increase, chaos occurs when just start adopting it, due to change management, culture inertia, lost focus, ineffective measurement or performance incentives. 

  • Other tensions between development and operations. Software often is developed in one environment, then run in another; Agile tends to focus on testing to confirm that the desired business functionality has been produced but can overlook difficult-to-test attributes,

  • Macro-challenges on the enterprise level such as the rate of change to bring up operations and compliance issues.

  • The complications of integrating agile development and IT operations also vary with different project, company, and industry. 

The potential solution may include partitioning a large project into sub-projects, in each sub-projects, Agile still be used to perform sub-task independently, it is being said, the hybrid model to combine Waterfall’s structure with Agile’s agility, some call it WaterScrum Fall model. At DevOps environment, the challenge also include re-educate people and making sure that they understand the operational indication when developing applications.


3. KPIs for DveOps 

DevOps encompasses key governance processes, such as configuration, change and release management to Agile method. The KPIs include:

  • Time to Configuration
  • Time for change Cycle  
  • Quantity of deployments weekly or monthly
  • Mean time to resolution

Some also call the next stage of DevOps as NoOps-the team automate the process of realeasing application into dev/test environment or production. Seem "No" here is next level of "Yes".

DevOps is enhanced “muscles” for Agile methodology:  from architectural perspective, it's about how to design/operate more holistically in order to reduce unproductive complexity; from strategic perspective, it's about where to streamline software deployment pipeline, expedite decision making and how to optimize business process; tactically, it's about cross-functional collaboration and iterative project management; methodologically, cloud & social computing platform make it more as reality than hype.

Five Reasons CIO Falls into Scapegoat

Thursday, July 26, 2012 | comments

Enterprise CIOs, like shepherds, take care of their business’s technology/information assets, however, many pitfalls ahead may make a dedicated, responsible CIO a falling scapegoat. There are many WHYs need be asked, many Hows need be experimented, in order for enterprise to focus on problem solving, than finger-pointing; to make fair judgment in leadership and talent management and to optimize business governance & discipline. 

Why is the CIO the "fall guy" when a company has data security leaks, business systems go down, critical applications crash, project failure or a technology vendor provides a surprise $10M price increase. 

There are five key reasons CIO falls into a scapegoat:

 1.    Ineffective Leadership & Business Culture

Generally, the causes lie in the camp of the board, C-Level, senior executives and presidents themselves. As risks enumerated above can be thought of as business risks, they are generally managed through a CIO's risk management business plan. CIO is the most visible person managing such risks. However, it should be the whole leadership failure:  

  • Board Responsibility: Board Members are still not setting top-level policies and reviews of security budgets to help protect against breaches and mitigate financial losses. Boards and senior executives still don’t understand that security and IT risks are part of enterprise risk management

  • Statistical Data: from cross-industry survey, 58% of the respondents said their board did not review the company’s insurance coverage for security-related risks; Only about one-third of company boards are focusing on activities that would help protect against reputable or financial losses; Organizations show that they do not have full-time senior level personnel in place to properly manage security risks. Less than two-thirds of the companies have a security management practice that is consistent with internationally accepted best practices and standards.
.
  • Business Culture: A lot also depends on the organizational culture: finger pointing or supportive? Problem solving or political play? The "spirit" of top may directly impact business culture as a whole.  Finding the guilty guy, then the CIO is (more or less) the right one to fall. If the organization has more like  ‘what did we learn from it' “how to solve the problem’ attitude,  then there is a chance that risk management of IT related themes can be shared with the board and other CxO executive. organizations may need cultivate the culture to share the credit when thing's fine, and co-take responsibility when things turn bad and focus on digging root cause & solving the problem radically. 

The culture of trust and transparency are needed, and business/IT governance need be converged and further enforced, it's not only senior leader team's responsibility, but also one of top agendas for corporate board.


2.    Look at Symptom, Not Root Cause


Sometimes seems the "plumbing" issues maybe caused by construction problems., etc
That said, when accident happened, the organization may need trace from top-down level, not only just symptom, but also underlying root cause:

  • Does board and senior leadership team put business continuity & governance at top priority, well support IT via resources & investment;
  • Does IT & business work seamlessly to build up the effective process to prevent risk?
  • Do employees not "abuse" the trust from management, not follow through the guideline & corporate policy? 
  • Is accident very isolated one, couldn't particularly blame any single party, or each party need share the responsibility?
  • Does business's governance, risk management, compliance, and security function be interactive enough to bring up more systematic and structural solution for business as whole? 
Statistics: As you may know 20 percent of IT problems are caused by technologies, 40 percent are caused by people and 40 percent of them are caused by processes. CIO is responsible for the management of IT processes and IT staff and almost can't affect technologies. It means that CIO is not "fall guy' if the root cause of critical applications crash is software bug recognized by manufacturer. And he/she may need take fair share of responsibility if the root reason of critical applications crash is wrong change management process or low-skilled developer engineer. 
    Additionally, because of the revolving doors with people coming and going more frequently, the accountability for bad decisions has often left the building. Consequently the person now in control of IT becomes the scapegoat.

    How to fix it: Organizations would have an enterprise-wide active risk management and/or business continuity plan. When thing's OK, all cross-functional teams can share the credit, when bad thing's happened, each party may also share their piece of responsibility. Senior leadership team need take initiative to build up more solid GRC framework and discipline. The CIO has the responsibility to review and mitigate the technology risk to the firm. This is done in the form of Vendor contracts, Business Resumption planning, communication of policy and procedures to the firm.


    3. Poor / insufficient investments for managing risks 

    The business usually makes the decision on how much resources are allocated to address the risks, and if the resources are simply inadequate, then there's a dual accountability to be addressed. 

    Statistics: On average, CISOs are allocated a consistent 2 percent of their organizations’ IT budgets for security spending. If IT budgets are dropping, then we can conclude that associated security budgets may be dropping as well, in real dollars. The gap between afford-ability and actual needed, could be one of root causes to keep system down or lead other unhappy surprise, it may also reflect the ineffectiveness of today's annual IT budget scenario, it's not distributed by real need, but by static formula

    Tradeoff (Cost saving / higher risk) can be taken and then need to be managed jointly in case of challenges. The blame game quickly starts if the execs are a team only on paper but there are hidden aspirations / power games.

    Solution: The CIO has justified the need for increased resources to address vulnerabilities, but the resources are simply not available. So it becomes a managed risk, by and with the business. As long as there's awareness and acceptance of the plan for addressing those risks (or not), then there should be no "blame game"


    4. Ineffective Decision Making Scenario

    If an IT project or IT initiative fails, business seems never be held accountable for their role in contributing to the failure. Even though they may have been the catalyst or cause for failure due to poor pre-implementation business planning, flimsy C-level IT investment decision making or abdicating their responsibilities to IT. More specifically:

    • First, because often the business executives lack visibility of critical business architecture information and business intelligence upon which to base vital project planning decisions.

    • And secondly, the strategic decisions to invest in IT systems are always made at the top level of an organization, but without CIO participation. For example: due to CEO or CFO alliances with certain Vendors or systems implementers, or based upon the cheapest solution, often the CEO or CFO may choose based upon their own selection criteria.

    Solutions:

    • Who makes Decisions: The CIO needs co-make investment decision or at least point out in a documented way to the decision makers that if they don't spend the money to follow good security practice, there will be specific bad consequences.

    • How to Make Key Decisions?  What's the formal IT investment decision making process flow/document management, how to build an effective framework to enforce more fact-base decision management scenario? 

    • How to get further Advice: Besides leadership team, does business have specialized talent such as EA or analyst to act as business Quality professional to verify business/IT investment. Does business process management office help oversee the decision making process, and make suggestion on optimizing business capabilities. 

    • Monitor: communicate the risks to the rest of the Executive staff, and lock down what you can, monitor what you can't lock down, and also collaborate with Legal to  make sure policy covers the things you can't lock down or monitor so you'll have legal recourse if all else fails


    5. Innovation Experiment Takes Risks
     

    • Taking this scenario, the company has a proper risk management process in place and potential risks have been weighted on the cost vs. potential risk /loss of revenue, reputation, customers.
    • Risk vs. Innovation: If a CIO is strictly following corporate rules for data security, best practices for IT operations etc. she or he becomes “no no” leader for new ideas, In essence, CIO is expected to become Chief Innovation Officer. With a desire to eliminate all risk you also kill all the opportunities. A balance is needed between
      - risk appetite / innovation (early adopting of a new technology)
      - cost containment (requiring a solid state-of-the-art operations)
      - optimizing customer satisfaction 
      
    Moreover, when the risks were fully explored, understood, and then taken around the 'C' table. The 'blame' rests with the management team, although it still might have been a reasonable choice. So WHY take out the CIO? Convenience and easily explained outside of the executive chambers. And as the saying goes, “A good scapegoat is nearly as welcome as a solution to the problem.". 

    The ENTIRE NOTION of “taking the fall” is wrong headed. 

    Learning Lessons for CIO:  Today's CIO has to be an excellent salesman, a visionary, a fantastic motivator/manager to collaborate with “C” level to get the resources required to do this work and inform them of the risk and to be politically adept in managing crisis which will occur during their watch also At the same time the CIO has to keep track with the rapidly changing landscape of IT developments.
     
    Support : Creating Website | Johny Template | Mas Template
    Copyright © 2011. Personal Inspiration - All Rights Reserved
    Template Created by Creating Website Published by Mas Template
    Proudly powered by Blogger