IT245 Business Information Systems

Business Information SystemsUnit 211 min read

IS, Organizations & Strategy: Models, Structures & Alignment

Unit 2 of Business Information Systems explores how information systems (IS) shape organizational structures, strategies, and competitive advantage. It covers organizational theories (classical, neoclassical, contingency), IS roles in strategy (support, transformation, factory), Porter’s Five Forces, SWOT analysis, and

Core Concepts: Organizations and Information Systems

1. Organizational Theories and IS

Organizations evolve through different theories that influence how IS is designed and used. Three key theories:

A. Classical Theory

  • Focus: Efficiency, hierarchy, and standardization.
  • Key Figures: Frederick Taylor (scientific management), Max Weber (bureaucracy).
  • IS Role: Supports rigid structures (e.g., centralized databases, batch processing).
  • Example: A government office (e.g., Nepal’s Revenue Department) uses legacy systems for tax filings due to strict hierarchical approvals.

B. Neoclassical Theory

  • Focus: Human behavior, communication, and flexibility.
  • Key Figures: Chester Barnard (acceptance theory), Herbert Simon (decision-making).
  • IS Role: Enables collaboration (e.g., eSewa for citizen-government interactions, Khalti for peer-to-peer payments).
  • Example: Pathao uses real-time driver-passenger matching (neoclassical IS) to reduce wait times.

C. Contingency Theory

  • Focus: "One size does not fit all"—IS must adapt to organizational context.
  • Key Factors:
    • Environment: Stable vs. dynamic (e.g., NEPSE vs. Daraz).
    • Technology: Routine vs. non-routine tasks.
    • Strategy: Cost leadership vs. differentiation.
  • Example: Nabil Bank uses AI for fraud detection (dynamic environment) but legacy core banking for routine transactions (stable).

Taylor: Scientific ManagementWeber: BureaucracyIS Role: Centralized, rigid systems (e.g., legacy ERP)ClassicalBarnard: Acceptance TheorySimon: Decision-MakingIS Role: Collaborative tools (e.g., eSewa)NeoclassicalRoutine tasks → Legacy systems (e.g., Nabil Bank core bankinNon-routine tasks → AI/Adaptive systems (e.g., Nabil Bank frEnvironment: Stable/DynamicCost leadership → Standardized IS (e.g., NTC billing)Differentiation → Custom IS (e.g., Daraz AI)Strategy: Cost/DifferentiationContingencyOrganizational Theories
Hierarchical comparison of organizational theories with IS applications (Nepali examples)

In the Real World

  1. eSewa (Nepal):

    • Idea: Neoclassical IS (communication-focused).
    • How: Simplifies citizen-government interactions (e.g., bill payments, license renewals) by replacing bureaucratic paperwork with a mobile app. Uses decision support systems (DSS) to route requests efficiently.
  2. Daraz (Alibaba Group):

    • Idea: Contingency Theory (dynamic environment).
    • How: Uses real-time inventory management IS (sensors + AI) for fast-moving consumer goods (FMCG) but relies on legacy ERP for supplier contracts in stable regions. During sales (e.g., 11.11), it scales cloud infrastructure dynamically.
  3. NTC (Nepal Telecom):

    • Idea: Classical + Contingency Hybrid.
    • How: Maintains a hierarchical billing system (classical) for fixed-line customers but uses AI chatbots (contingency) to handle dynamic customer complaints on mobile networks.

2. Organizational Structures and IS

IS must align with organizational structure. Three common structures:

Structure Description IS Support Nepali Example
Functional Departments by function (HR, Finance). Departmental databases (e.g., SAP HR module). Nabil Bank: Separate systems for loans, deposits.
Divisional Groups by product/region (e.g., Daraz Nepal vs. Daraz India). Decentralized IS (e.g., regional CRM). Chaudhary Group: Separate ERP for cement vs. retail.
Matrix Employees report to multiple bosses (e.g., project teams). Collaborative tools (e.g., Slack, Trello). Himalayan Java: Cross-functional teams for export vs. local sales.

How IS Shapes Structure

  • Centralization vs. Decentralization:
    • Centralized IS (e.g., NTC’s billing system): Single database for all regions → Pros: Uniformity, cost savings. Cons: Slow adaptation.
    • Decentralized IS (e.g., Daraz’s regional warehouses): Local inventory systems → Pros: Faster response. Cons: Data silos.
  • Workflow Automation:
    • Example: Khalti’s payment workflow automates fund transfers between banks, merchants, and users, reducing manual checks (classical → neoclassical shift).

flowchart TD
    A["Organizational Structure"] --> B["Functional"]
    A --> C["Divisional"]
    A --> D["Matrix"]
    B --> E["Departmental IS<br/>(e.g., SAP HR)"]
    C --> F["Decentralized IS<br/>(e.g., Daraz CRM)"]
    D --> G["Collaborative Tools<br/>(e.g., Slack)"]
    E --> H["Pros: Uniformity<br/>Cons: Slow"]
    F --> I["Pros: Speed<br/>Cons: Silos"]

3. Information Systems and Strategy

IS can support, transform, or act as a strategic factory for organizations.

A. Levels of Strategic IS

Level Role of IS Example
Operational Supports daily tasks (e.g., transactions). Ncell’s billing system.
Managerial Provides reports for decision-making. Daraz’s sales analytics dashboard.
Strategic Shapes long-term competitive advantage. Google’s AI search algorithm.

B. Strategic Roles of IS (Michael Porter)

  1. Support Existing Strategy:
    • Example: NEPSE uses IS to track stock prices in real-time, supporting investors’ decision-making.
  2. Transform the Business:
    • Example: Pathao disrupted traditional taxi services by using GPS + dynamic pricing IS.
  3. Create New Products/Services:
    • Example: Khalti introduced QR-based payments, a first in Nepal.

C. Porter’s Five Forces and IS

IS can influence competitive forces by:

  • Reducing supplier power: Daraz’s supplier portal automates orders, reducing dependency on wholesalers.
  • Increasing buyer power: Price comparison tools (e.g., SanoSano) give customers more options.
  • Lowering barriers to entry: Shopify (used by Nepali e-commerce stores) lets small businesses compete with giants.
  • Reducing rivalry: NTC’s fiber-optic network reduces competition from mobile data providers.
Market Entry BarriersProfit PotentialOIndustry DemandShopify's Low-Cost EntryMarket Entry PointQP
How Shopify reduces entry barriers for Nepali e-commerce (demand shift)

mindmap
  root((Porter's Five Forces))
    Threat of New Entrants
      IS Role: Lower barriers (e.g., Shopify)
    Bargaining Power of Suppliers
      IS Role: Automate orders (e.g., Daraz)
    Bargaining Power of Buyers
      IS Role: Price tools (e.g., SanoSano)
    Threat of Substitutes
      IS Role: Differentiation (e.g., Pathao’s app)
    Competitive Rivalry
      IS Role: Reduce rivalry (e.g., NTC’s infrastructure)

4. SWOT Analysis and IS

IS can be a strength, weakness, opportunity, or threat in a SWOT framework.

SWOT Factor IS Example (Nepal) Impact
Strength eSewa’s mobile integration Reduces corruption, improves service.
Weakness Legacy banking systems (e.g., NMB) Slow digital transactions.
Opportunity AI in NTC’s network optimization Reduces downtime, improves service.
Threat Cyberattacks on Khalti Erosion of customer trust.

5. Strategic Alignment Models

Two key models explain how IS aligns with business strategy:

A. Henderson-Toward Model

Aligns business strategy, IS strategy, and organizational infrastructure.

  • Example: Nabil Bank’s digital transformation:
    • Business Strategy: Expand mobile banking.
    • IS Strategy: Develop a mobile app + API integrations.
    • Infrastructure: Train staff, upgrade servers.

B. McFarlan’s Strategic Grid

Classifies IS projects by strategic impact and environmental uncertainty.

Grid Quadrant Description Nepali Example
Factory High impact, low uncertainty. NTC’s billing system.
Turnaround High impact, high uncertainty. Daraz’s AI recommendation engine.
Support Low impact, low uncertainty. Office email (e.g., @ncell.com).
Strategic Low impact, high uncertainty. NEPSE’s blockchain pilot.

flowchart TD
    A["McFarlan's Strategic Grid"] --> B["Factory<br/>High Impact, Low Uncertainty"]
    A --> C["Turnaround<br/>High Impact, High Uncertainty"]
    A --> D["Support<br/>Low Impact, Low Uncertainty"]
    A --> E["Strategic<br/>Low Impact, High Uncertainty"]
    B --> F["NTC Billing System"]
    C --> G["Daraz AI"]
    D --> H["Corporate Email"]
    E --> I["NEPSE Blockchain"]

Case Study: Chaudhary Group’s IS Strategy

Challenge: A diversified conglomerate (cement, retail, FMCG) needed unified IS. Solution:

  1. ERP Implementation (SAP):
    • Factory Role: Standardized accounting across subsidiaries.
    • Turnaround: Integrated Chaudhary Retail’s POS with cement plant logistics.
  2. Digital Transformation:
    • Opportunity: Launched e-commerce for cement (B2B portal).
    • Threat Mitigation: Invested in cybersecurity for online orders. Outcome:
  • 20% cost reduction in supply chain.
  • 30% increase in retail sales via digital channels.
2010 BSLegacy ERPimplementation (centra2020 BSCloud migration(decentralized)2023 BSAI-driven supplychain (strategic align
Chaudhary Group's IS evolution timeline

Exam Tip

  1. Definitions:
    • Know the difference between classical, neoclassical, and contingency theories.
    • Memorize Porter’s Five Forces and how IS affects each.
  2. Applications:
    • Compare functional vs. divisional structures with Nepali examples (e.g., Nabil Bank vs. Daraz).
    • Link SWOT to real firms (e.g., Khalti’s strength in mobile payments vs. weakness in rural reach).
  3. Diagrams:
    • Draw Henderson-Toward or McFarlan’s grid for any case study.
    • Label organizational structures (functional/divisional/matrix) clearly.
  4. Critical Thinking:
    • Evaluate: Why did NTC centralize billing but Daraz decentralize inventory?
    • Predict: How might AI IS change NEPSE’s threat of substitutes?
  5. Common Pitfalls:
    • Don’t confuse operational IS (e.g., Ncell billing) with strategic IS (e.g., Pathao’s app).
    • Avoid vague answers—always tie theory to a Nepali/global example.

Key Formula to Remember:

  • Strategic Alignment Score (simplified): (Example: Nabil Bank’s mobile app scores high for digital strategy alignment.)

Based on the TU BIM syllabus for Business Information Systems (IT245), unit 2.

Discussion

Loading…