Organizational Behaviour and Human Resource ManagementUnit 516 min read
Organizational Structure & Culture: Types, Designs & Impact
Unit 5 of Organizational Behaviour and Human Resource Management explores how organizations structure themselves (hierarchies, teams, networks) and how culture shapes behavior, performance, and change—with real-world examples from Nepali companies like Nabil Bank and Daraz, plus exam-focused comparisons and case studie
TAKEAWAYS:
- Organizational structure determines who reports to whom, how decisions flow, and who does what—affecting efficiency, innovation, and employee morale.
- Culture is the "invisible glue" that binds employees through shared values, norms, and rituals, directly influencing productivity and customer trust.
- Contingency theory proves there’s no "one-size-fits-all" structure; the best design depends on the organization’s strategy, size, and environment.
- Organizational culture can be measured using frameworks like Competing Values Framework (CVF) or Schein’s Three Levels, and changed through OD interventions.
- Flat structures (e.g., startups) vs. tall hierarchies (e.g., NTC) trade off speed vs. control, while matrix structures (e.g., Daraz) balance specialization and collaboration.
- Cultural misalignment (e.g., NEPSE’s risk-averse culture clashing with tech startups) can derail growth—diagnosis and intervention are critical.
1. Organizational Structure: Definitions and Types
Organizational structure is the framework that defines:
- Roles and responsibilities (who does what).
- Authority and reporting lines (who answers to whom).
- Coordination mechanisms (how work flows).
It shapes decision-making speed, innovation, and employee satisfaction. Without a clear structure, chaos reigns—imagine Pathao’s dispatch system if drivers didn’t know who assigned rides!
Key Elements of Structure
Common Structural Types
| Type | Description | Example (Nepal) | Pros | Cons |
|---|---|---|---|---|
| Functional | Groups by expertise (HR, Finance, Marketing). | Nabil Bank | Efficiency, specialization | Silos, slow cross-department work |
| Divisional | Groups by product/region (e.g., Electronics, South Asia). | Daraz | Flexibility, customer focus | Duplication of roles |
| Matrix | Combines functional + divisional (e.g., dual reporting). | Himalayan Java (Product + Region) | Innovation, resource sharing | Complexity, conflict |
| Flat (Horizontal) | Few hierarchy levels, wide spans of control. | Pathao (driver app) | Fast decisions, employee autonomy | Overworked managers |
| Tall (Vertical) | Many hierarchy levels, narrow spans of control. | NTC | Clear chain of command | Slow decisions, bureaucracy |
| Network | Outsources core functions (e.g., contractors). | Freelance designers for Daraz | Cost savings | Loss of control |
2. How Structure Affects Performance: A Real-World Trace
Let’s trace how Nabil Bank’s structure impacts its loan approval process:
- Functional Structure: Loans → Credit Risk → Processing → Disbursement.
- Pros: Specialists ensure accuracy (e.g., risk analysts use data models).
- Cons: Slow for small businesses (e.g., a tailor waiting 30 days for a ₹500K loan).
- Decentralized Decision-Making: Branch managers can approve loans <₹1M.
- Impact: Faster service but higher risk of errors.
- Matrix Overlay: Some branches use cross-functional teams (loan officer + business advisor) for SMEs.
- Result: 40% faster approvals for startups (source: Nabil Bank 2022 Report).
Why it matters: Nabil Bank’s hybrid structure balances speed and risk, but requires strong training to avoid confusion.
3. Organizational Culture: Definitions and Levels
Culture is the "way we do things around here"—it’s invisible but powerful. Edgar Schein identified three levels:
Measuring Culture: The Competing Values Framework (CVF)
CVF classifies culture into four quadrants, each with trade-offs:
| Culture Type | Focus | Example (Nepal) | Best For | Risks |
|---|---|---|---|---|
| Clan | Collaboration, family | Himalayan Java | Startups, creative industries | Slow decision-making |
| Adhocracy | Innovation, risk-taking | Daraz, Khalti | Tech, fast-changing markets | High turnover |
| Market | Competition, results | NEPSE, NTC | High-pressure sales, utilities | Employee burnout |
| Hierarchy | Stability, control | Nabil Bank (traditional) | Regulated industries (banks, NTC) | Resistance to change |
4. How Culture Shapes Behavior: Case Study
Case: NEPSE’s Risk-Averse Culture vs. Tech Startups
- NEPSE’s Culture:
- Hierarchy: Strict approval chains for trades.
- Rules: Heavy compliance (e.g., KYC for investors).
- Assumption: "Slow but safe" (e.g., 2015 market crash led to stricter controls).
- Tech Startups (e.g., Khalti):
- Adhocracy: "Move fast, break things" (e.g., rapid app updates).
- Trust: Employees work remotely with minimal oversight.
- Conflict: When Khalti listed on NEPSE, it faced cultural clashes:
- NEPSE’s slow approval process delayed Khalti’s IPO.
- Khalti’s flat structure clashed with NEPSE’s hierarchical audits.
Lesson: Culture eats strategy for breakfast. Even the best-laid plans fail if the values don’t align.
5. Designing Structure and Culture: Contingency Approach
There’s no perfect structure—it depends on:
- Strategy: Cost leadership (tall hierarchy) vs. innovation (flat).
- Environment: Stable (bureaucracy) vs. dynamic (matrix).
- Technology: Routine tasks (centralized) vs. creative (decentralized).
- Size: Small (flat) vs. large (divisional).
Example: Daraz’s Evolution
- 2015 (Startup): Flat structure, adhocratic culture ("Do whatever it takes").
- 2020 (Growth): Added divisional structure (e.g., Grocery, Electronics) + matrix teams for logistics.
- 2023 (Scaling): Introduced stronger HR policies (e.g., remote work rules) to manage 10,000+ employees.
6. Changing Structure and Culture: OD Interventions
Organizations must adapt to survive. Organizational Development (OD) uses tools like:
| Intervention | When to Use | Example (Nepal) | Outcome |
|---|---|---|---|
| Team Building | Improve collaboration | Nabil Bank’s cross-functional loan teams | Faster approvals, 20% higher satisfaction |
| Survey Feedback | Diagnose culture issues | NTC’s employee engagement survey | Identified "bureaucracy fatigue" |
| Process Redesign | Streamline workflows | Daraz’s "same-day delivery" pilot | 30% faster orders |
| Cultural Training | Shift values (e.g., from hierarchy to trust) | Khalti’s "innovation workshops" | Higher risk-taking in product teams |
| Merger Integration | Combine two cultures (e.g., acquisitions) | Nabil Bank + Global IME merger | Unified IT systems, reduced silos |
Real-World Example: NTC’s Digital Transformation
- Problem: Slow, paper-based processes (e.g., license renewals took 2 months).
- OD Intervention:
- Diagnosis: Survey revealed employees feared tech would replace jobs.
- Intervention: Pilot project in Kathmandu zone + training on new systems.
- Culture Shift: Introduced "digital champions" (employees who advocated for change).
- Result: Online license renewal now takes 15 minutes (vs. 60 days).
7. Structure vs. Culture: Which Matters More?
| Factor | Structure | Culture |
|---|---|---|
| Visible? | Yes (org charts, job descriptions) | Mostly invisible (values, norms) |
| Changes Fast? | Slow (requires redesign) | Can shift quickly (e.g., new CEO) |
| Impact on Performance | Affects efficiency, coordination | Affects motivation, innovation |
| Example | NTC’s tall hierarchy → slow decisions | Daraz’s "fail fast" culture → rapid innovation |
Key Insight: Culture is the "operating system"—structure is the hardware. You can change the hardware (restructure), but if the OS (culture) is outdated, the system will still fail.
## In the Real World
eSewa’s Flat Structure and Trust Culture
- Idea: Decentralized decision-making (regional teams manage payments).
- How: Employees use discretion to approve small transactions (e.g., ₹500 top-ups), reducing fraud risk while speeding up service.
- Result: 90% of transactions are processed in <30 seconds (vs. bank transfers taking hours).
Khalti’s Adhocratic Culture and Innovation
- Idea: "Move fast, iterate faster" (startup culture).
- How: Engineers deploy code updates daily (vs. banks’ quarterly releases). Example: During COVID-19, Khalti added QR code payments in 3 weeks.
- Impact: Became Nepal’s #1 fintech by 2021, processing ₹50B/month.
NTC’s Hierarchical Culture and Bureaucracy
- Idea: Centralized control for safety-critical operations (e.g., traffic management).
- Problem: Slow approvals delay projects (e.g., a new bus route took 2 years due to paperwork).
- Lesson: While hierarchy ensures consistency, it can strangle innovation.
## Exam Tip: How to Score Full Marks
This unit is conceptual but applied—examiners love real-world ties and comparisons. Here’s how to ace it:
1. Define Clearly, Then Apply
- Weak: "Organizational culture is important."
- Strong:
"Organizational culture consists of shared values, norms, and artifacts that guide employee behavior (Schein, 1985). For example, Nabil Bank’s ‘customer-first’ culture is reinforced by its ‘Banker of the Year’ awards, which motivate staff to prioritize service quality over internal politics. This aligns with the Clan culture type in the Competing Values Framework, fostering collaboration but potentially slowing decision-making in crises."
2. Use the "So What?" Technique
For every point, ask: "How does this affect performance, employees, or customers?"
- Example:
"Daraz’s matrix structure combines functional expertise (e.g., logistics) with divisional focus (e.g., Electronics team). So what? This reduces duplication (e.g., shared warehouses) but increases conflict when a product manager and regional head disagree on inventory levels. Solution: Daraz uses cross-functional training to align goals."
3. Compare Structures/Cultures in Tables
Examiners love structured comparisons. Use this template:
| Aspect | Functional Structure (Nabil Bank) | Matrix Structure (Daraz) | Impact on Innovation |
|---|---|---|---|
| Decision Speed | Slow (multiple approvals) | Fast (dual reporting) | ⬆️ (Daraz) |
| Employee Skills | Deep expertise (e.g., loan officers) | Broad skills (e.g., product + sales) | ⬆️ (Daraz) |
| Conflict Risk | Low | High (e.g., budget disputes) | ⬇️ (Nabil Bank) |
4. Link to OD Interventions
If asked about change, always mention:
- Diagnosis (e.g., survey, focus groups).
- Intervention (e.g., team building, process redesign).
- Evaluation (e.g., metrics like "time to approval").
Example Answer:
*"To address NTC’s bureaucratic culture, an OD intervention could involve:
- Diagnosis: Conduct an employee survey to identify pain points (e.g., ‘license approvals take too long’).
- Intervention: Implement a pilot digital workflow in one zone (e.g., Kathmandu) with mandatory training on the new system.
- Evaluation: Measure processing time reduction (e.g., from 60 days to 15 days) and employee satisfaction scores. Result: If successful, roll out company-wide with ‘digital champions’ to sustain the change."*
5. Avoid Common Pitfalls
- ❌ "Culture is just about perks" → Wrong. Culture is about values, not ping-pong tables.
- ❌ "Flat structures are always better" → Context matters. A startup (Pathao) thrives with flat structures, but NTC needs hierarchy for safety.
- ❌ Ignoring trade-offs → Always mention pros and cons (e.g., matrix structures increase innovation but add complexity).
## Quick Revision Checklist
Before the exam, ask yourself:
- Can I draw and label the 5 types of organizational structures?
- Can I explain Schein’s 3 levels of culture with a Nepali example?
- Can I compare 2 structures (e.g., functional vs. matrix) using a table?
- Can I describe 2 OD interventions and their outcomes?
- Can I link culture to performance (e.g., "NEPSE’s risk-averse culture delays IPOs")?
If yes, you’re ready for 15/15!
Based on the TU BBS syllabus for Organizational Behaviour and Human Resource Management (MGT223), unit 5.
Discussion
Loading…