Information is widely available, empowering lower-level employees with decision-making authority.
CEO
|
-----------------
| | |
EMP --- EMP --- EMP
(with data access)
Result: Fewer middle managers are needed, leading to a "flatter," more agile organization.
🎬 Zappos: Cutting Management Layers
Zappos.com, "A Little Bit About Holacracy" (0:00 to 0:42)
🏢 Simulation: Org Structure Flattening
👔 CEO
📊 VP Operations
🗂 Director A
🗂 Director B
👤 Mgr 1
👤 Mgr 2
👤 Mgr 3
💼 Staff
💼 Staff
💼 Staff
💼 Staff
Levels: 5 | Middle layers removed: 0 | Like CG Group Nepal before ERP
🧮 Worked Example: Counting the Layers
A company has 625 frontline staff. How many managers does it need?
Each manager supervises 5 people
CEO → 5 → 25 → 125 managers → 625 staff
156 managers in 4 management layers
With good IS, each manager supervises 25
CEO → 25 managers → 625 staff
26 managers in 2 management layers
That's 130 fewer manager posts and 2 fewer layers.
A message from the front line to the CEO now passes through 1 manager instead of 3.
Information systems let one manager track many more people, through dashboards, reports and shared data. That's what makes a flatter structure possible.
Effect 2: Streamlining Business Processes
Making work faster, cheaper, and more accurate.
Example: Enterprise Resource Planning (ERP) Systems
Before ERP, departments worked in silos with separate systems:
Sales System 🧱 Finance System 🧱 Warehouse System
After ERP, a single integrated system connects the entire organization:
Sales ↔️ Finance ↔️ Warehouse ↔️ HR
This automation and integration makes processes like "order-to-cash" incredibly efficient.
⚡ Before vs. After: Manual vs. ERP Process
🛍️ Sales
--✗--
💰 Finance
--✗--
📦 Warehouse
--✗--
👥 HR
--✗--
🚚 Shipping
--✗--
📞 Support
⚠️ Siloed systems — no real-time data sharing (like Bhatbhateni pre-ERP)
ERP Core
📌 State: Before ERP — departments unable to share data
⚠️ When IS Meets People: Resistance to Change
Why people resist
Fear of losing their job
Fear of losing power, when information they used to control becomes shared
Having to learn a new system while doing their normal work
Not being told why the change is happening
How good managers respond
Involve users early in designing the system
Train people properly before go-live
Pick respected staff as "champions"
Roll out in phases, not all at once
Many IS projects that fail have working technology. They fail because the people and processes were not ready.
🍫 Case Study: The ERP That Ruined Halloween
In 1999, chocolate maker Hershey spent about $112 million on a new ERP and supply-chain system.
To finish fast, it cut the planned timetable and switched everything on at once, in July, just before its busiest season: Halloween.
Orders went into the system but did not come out properly. Warehouses were full, yet stores did not receive their sweets. Around $100 million of orders could not be delivered on time.
That quarter, Hershey's profits fell by about 19%, and its share price dropped sharply.
Discuss: Using Leavitt's diamond, which parts besides technology did Hershey not prepare? What would you have done differently?
Hershey's factory, Pennsylvania (1976 photo)
Effect 3: Enabling New Business Models
IT as the foundation for digital disruption.
Many of today's largest companies would be impossible without sophisticated information systems.
E-Commerce
Global marketplace, recommendation engines, logistics networks.
Sharing Economy
Real-time matching of supply (drivers) and demand (riders).
Uber, "How Uber Matches Riders and Drivers | What Moves Us" (0:10 to 1:17)
🎬 Netflix, 2010: Why Streaming Beats DVD
CNN Business, "Netflix: DVDs dead, streaming lives" (0:20 to 1:07), Reed Hastings in 2010
🇳🇵 Which IS Made This Possible? Nepal Quiz
Select the IS type that made each Nepal service possible, then check your answers:
Practical Application: The Nepali Context
How IS is transforming business in Nepal.
🔍 Case Study: Digital Transformation in Nepal
Digital Payments (eSewa, Khalti)
Enabled a new business model for cashless transactions, utility payments, and mobile top-ups, changing how people and businesses handle money.
Ride-Sharing (Pathao, inDrive)
Created a new "sharing economy" model for transportation, using GPS and matching algorithms to connect riders and drivers efficiently.
These companies did not just introduce new technology; they introduced entirely new ways of operating that reshaped their respective industries in Nepal.
🌍 Global Case: M-Pesa, a New Business Model in Kenya
In 2007, the Kenyan mobile operator Safaricom launched M-Pesa, which lets people send and store money by text message, even on basic phones and with no bank account.
Thousands of small shops became agents, where customers turn cash into mobile money and back.
It is now used by tens of millions of people across several African countries.
A 2016 study in the journal Science estimated that mobile money lifted about 2% of Kenyan households out of extreme poverty.
Compare: How is M-Pesa similar to eSewa and Khalti in Nepal, and how is it different? Who gains, and who loses, when a phone company starts acting like a bank?
M-Pesa agent shop, Nairobi
Summary & Key Takeaways
Remember the two-way relationship.
Information systems and organizations mutually influence each other. One does not exist in a vacuum.
An organization's strategy, culture, and people will dictate the kind of systems it builds and how they are used.
In turn, information systems can flatten organizational structures, streamline core processes, and reduce costs.
Most importantly, IT is a powerful enabler of new, disruptive business models that can redefine entire industries.
Discussion Questions
How might the information systems at a creative advertising agency differ from those at a large accounting firm? (Think culture and strategy).
Explain in your own words what is meant by IT "flattening" an organization. What is the role of middle managers in this new structure?
Can a company successfully implement a new information system (like an ERP) without changing its business processes? Why or why not?
Image Credits
Leavitt's diamond diagram: made for this course — /blog/assets/images/slides/it231/leavitt-diamond.png