Chuyển đến nội dung chính

Data to dollars: Supporting top management with next-generation executive information systems

The ability to transform data into insights to help manage a company is the domain of corporate business intelligence, which consists of the processes, applications, and practices that support executive decision making. With such knowledge at a premium, chief information officers have moved to center stage. By connecting the right parties across their companies, CIOs are making their role—helping organizations to mediate between business requirements and IT capabilities—more critical than ever.
It’s a challenging mission because for all the data flowing through companies, executives often struggle to find the information they need to make sound decisions. Potentially valuable content is frequently trapped in organizational silos, lost in transit from one system to another, bypassed by inadequately tuned data collection systems, or presented in user-unfriendly formats. Although wired with layers of information-gathering technology, organizations still find it difficult to deliver the right data to the right people.
At the heart of these difficulties are inadequate executive information systems, supposedly designed to help top management easily access pertinent internal and external data for managing a company. Our research suggests that a set of common problems plagues these systems, which have existed for some time. Some forward-looking companies have therefore given CIOs a mandate to redesign them and to restore their importance in corporate decision making.
A failure to deliver
When information systems are dysfunctional, performance suffers. The executives of a large chemical company, for example, found that only about half of the data generated from its executive information system was relevant to corporate decision making. Executives needed precise numbers for each strategic business unit, product, and operating business, but nonuniform data made apples-to-apples revenue and cost comparisons difficult.
A rigid design architecture, based solely on financial-accounting rules, restricted the system’s output to a limited number of reporting formats. Custom analyses, such as inventory turnover by product and region, were nearly impossible to generate. A cluttered front-end interface compounded the problem. Executives intent on reviewing key performance indicators (KPIs) had to sort through a jumble of onscreen data, so the CIO needed to take several IT analysts offline every month to comb through the figures and create the desired analyses. Frustrated, the company’s board pressed the CIO to explain why group reporting costs were climbing upward and so much IT support was necessary.
As the chief information officer, the CIO should play a more central role in designing next-generation executive information systems that can help a company’s top managers extract value from the data that surrounds them. Three major factors often hinder success.
Inconsistent and unreliable content
Different semantics and inconsistencies in the way information is structured from one unit to another hobble many executive information systems. Data, gathered through a multitude of sources, often with different labels, tags, and uses, can be hard to aggregate accurately for decision-making purposes. Group management accounting may roll up figures one way, operational management another—inconsistencies that can make executives question the reliability of the underlying data. At times, data sets lack contextual links that could provide perspective needed for executive analysis. Even if the system’s interface seems to be convenient, when executives doubt that the numbers are vetted, current, and accurate, they may be disinclined to use it.
Poor oversight and system handling
Too often, disjointed communication between businesses and IT can lead to flaws in an executive information system’s design. Creating reports may be complex. Sometimes IT logic rather than business analysis drives the navigation system. Tensions may arise as divisions, accustomed to seeing their numbers presented a certain way, vie to retain control over preferred reporting formats. Clear ownership is central to governance, but fiefdom issues are often a problem. As one executive told us, “Data ownership can get personal. The notion ‘I want my data my way’ can be pervasive.”
Inflexible business/IT architecture
Because business needs are dynamic, corporate business intelligence must be as well. Yet many executive information systems have static design architectures that limit the capture, organization, and accessibility of data. New demands—say, regulatory changes, the adoption of International Financial Reporting Standards, or requests from the field for performance data—often require time-consuming adjustments. Older systems are largely ill-equipped to handle these updates, so the IT staff must create manual links to Excel spreadsheets and other data tables, and this can cause confusion. Since design limitations prevent the new data from being integrated into the system, parallel data structures crop up across the IT landscape. A well-functioning executive information system should deliver varying levels of detail, yet many dashboards offer only a top-line view of the business; navigation facilities to pierce through layers of reporting data overcharge current IT capabilities.
From information to intelligence
One global corporation decided that the best way to tackle these problems was a wholly redesigned IT blueprint to support top management. The company, a multibillion-dollar global logistics organization prized for its ability to transport goods from one corner of the globe to another, was having a tough time getting its internal executive information system in order. While it could track cargo along any given point of its delivery network, it had little visibility into its own data streams. Years of rapid growth and decentralized, somewhat laissez-faire information management had created an untidy patchwork of reporting processes across its divisions. Management lacked a single viewpoint into the company’s core performance data and, as a result, couldn’t know for sure which products made money.

Knowing that something had to be done, the CIO formed a task force, with members from both the business side and IT, which quickly found that relations between them were in some ways dysfunctional. Executives from headquarters, the business units, and the divisional and central IT functions all documented performance in their own way, tapping into different data sources to tally their results. These figures were rolled up into a series of group reports, but variances in the underlying data and the lack of a uniform taxonomy made it difficult for managers to know which set of numbers to trust. The management interface, designed to present key performance data, was jammed with so many different and, in some cases, conflicting KPIs as to be largely unusable. A non-user-friendly front end compounded the problem. Executives therefore asked for a new executive information system to gauge the company’s performance at varying levels of detail (exhibit). This new corporate navigator would have to incorporate major improvements in design and functionality (see sidebar, “One company’s blueprint for a next-generation executive information system”).


Standardize data and new information structures
To bring order, the CIO had to deal with a number of core issues. Standardizing the underlying data to tackle inconsistencies was the first of them. Under the CIO’s leadership, the task force agreed to a set of groupwide KPI definitions, factoring in what the business side saw as the most important KPIs—such as inventory turns, cycle times, and margins—on a product-by-product basis. Then he created a company-wide taxonomy table to smooth the translation from one unit to another. The relationships between key pieces of information were redefined for the most important KPIs needed to manage the company. New IT bridges resolved the problem of manual data transitions from one system to another.
Designing a business intelligence architecture
To improve the system’s responsiveness, the CIO redefined the technical blueprint, creating centralized business intelligence data storage to house, tag, and order different data streams. A new architecture based on business domains or groupings rather than IT capabilities allowed data to flow more fluidly. The design included flexible tools for accessing and transforming data—tools that connected the group’s system to various upstream databases, such as those for financial and management accounting. Revised business applications created a common set of monthly and quarterly reporting formats, as well as analyses that executives without deep IT knowledge and experience could use to delve deeper into such things as share-holder value, budgeting, and capital planning. Last, a redesigned and improved interface allowed managers to move easily between these views to get the information they desired in a format they could handle. Features such as color coding, for example, created more intuitive groupings, guiding users through different types of reporting data.
Streamlining the reporting hierarchy
As the CIO resolved these IT issues, he worked in parallel to help business leaders gain a greater degree of visibility into the company’s core operations. In a series of meetings, he asked the leaders to identify their most important KPIs and reports in order to streamline and prioritize them. Stronger logic and better-informed, more disciplined reports and metrics help leaders set better targets, raise questions when performance diverges from them, and monitor progress more efficiently. The dynamic business-based architecture makes it easier to change reports—eliminating the costly ad hoc analyses that had bogged down the process—so fewer IT resources are needed to maintain the system. Because the underlying data are now far more reliable, the CFO, for example, can use the redesigned interface as a presentation device during analyst calls and when he speaks before the board.
Organizational flux, rising competitive pressures, and the expanding global reach of many organizations now place a premium on information that helps executives manage a company. New demands for transparency from stakeholders and regulators magnify the need for better (and often more timely) information. Transforming data into useful insights is critical to creating value and, ultimately, to a company’s competitive advantage. As the leading conduits between business requirements and IT capabilities, CIOs have an opportunity to expand their influence while supporting the goals of their companies.

Nhận xét

Bài đăng phổ biến từ blog này

Các nguyên tắc của COBIT 5

Nguyên tắc thứ 1: Đáp ứng nhu cầu các bên liên quan (Meeting stakeholder needs) Doanh nghiệp tạo ra giá trị cho các bên liên quan bằng việc duy trì cân bằng giữa lợi ích, rủi ro và nguồn lực.  COBIT 5 cung cấp các quy trình cần thiết và các điều kiện cần thiết (enabler) nhằm hỗ trợ việc tạo ra các giá trị kinh doanh thông qua việc sử dụng công nghệ thông tin. Mỗi doanh nghiệp khác nhau sẽ có các mục tiêu khác nhau nên một doanh nghiệp có thể tùy biến COBIT 5 để phù hợp với bối cảnh của doanh nghiệp thông qua mục tiêu kinh doanh, biến đổi từ mục tiêu kinh doanh chung thành các mục tiêu chi tiết mà có thể quản lý được, có các đặc tả chi tiết và ánh xạ các mục tiêu đó vào các quy trình, các thực hành của mục tiêu CNTT. Các tầng mục tiêu (goals cascade) đạt được thông qua bốn bước: Bước 1: Định hướng của các bên liên quan ảnh hưởng đến nhu cầu của các bên liên quan. Bước 2: Nhu cầu của các bên liên quan tác động vào mục tiêu của doanh nghiệp.   Nhu cầu của các bên liên

Quản trị công nghệ thông tin

"Theo định nghĩa của OCED, quản trị doanh nghiệp (corporate governance) bao gồm các quy trình để định hướng, kiểm soát và lãnh đạo tổ chức. Quản trị doanh nghiệp bao gồm thẩm quyền, trách nhiệm, quản lý, lãnh đạo và kiểm soát trong tổ chức." Theo Principles of Corporate Governance,  OCED. "Quản trị công nghệ thông tin (IT Governance - ITG) là trách nhiệm của Ban Giám Đốc và các nhà quản lý. Quản trị công nghệ thông tin là một phần của quản trị doanh nghiệp và bao gồm cấu trúc lãnh đạo, cấu trúc tổ chức và các quy trình để đảm bảo công nghệ thông tin của tổ chức được duy trì và mở rộng theo các định hướng chiến lược và mục tiêu của tổ chức'' Theo Board Briefing on IT Governance, 2 nd  Edition,  IT Governance Institute Thông tin là một nguồn lực quan trọng của tất cả các doanh nghiệp và công nghệ giữ một vai trò cũng quan trọng từ khi thông tin được hình thành đến khi thông tin bị phá hủy.  Công nghệ thông tin ngày càng phát triển và trở nên phổ biến hơn

MỤC 2.1: TẠO GIÁ TRỊ (CREATING VALUE)

Các dự án tồn tại trong một hệ thống lớn hơn, chẳng hạn như một cơ quan chính phủ, tổ chức hoặc thỏa thuận hợp đồng. Để ngắn gọn, tiêu chuẩn này sử dụng thuật ngữ tổ chức (organization) khi đề cập đến các cơ quan chính phủ, doanh nghiệp, các thỏa thuận hợp đồng, liên doanh và các thỏa thuận khác. Tổ chức tạo ra giá trị cho các bên liên quan. Ví dụ về các cách mà các dự án tạo ra giá trị bao gồm, nhưng không giới hạn ở: Tạo sản phẩm, dịch vụ hoặc kết quả mới đáp ứng nhu cầu của khách hàng hoặc người dùng cuối; Tạo ra những đóng góp tích cực cho xã hội hoặc môi trường; Cải thiện hiệu quả, năng suất, hiệu quả hoặc khả năng đáp ứng; Thực hiện các thay đổi cần thiết để tạo điều kiện thuận lợi cho việc chuyển đổi tổ chức sang trạng thái mong muốn trong tương lai; và Duy trì các lợi ích được kích hoạt bởi các chương trình, dự án hoặc hoạt động kinh doanh trước đó. 2.1.1 CÁC THÀNH PHẦN CUNG CẤP GIÁ TRỊ (VALUE DELIVERY) Có nhiều thành phần khác nhau, chẳng hạn như danh mục đầu tư, chương trình,