Org Structures, Culture & KM: How Knowledge Flows

TAKEAWAYS:

• Organizations are knowledge ecosystems: their structure (hierarchy, networks) determines how knowledge is created, stored, and shared.
• Organizational culture (values, norms, trust) is the biggest KM enabler or barrier—e.g., Google’s "20% time" policy vs. rigid Nepali bureaucracy.
• Flat vs. hierarchical structures impact KM differently: flat structures (e.g., startups) foster collaboration, while hierarchies (e.g., NTC) require formal KM systems.
• Knowledge silos (isolated teams/departments) kill innovation—tools like intranets or cross-functional teams break them.
• Case studies (e.g., Daraz’s supplier networks, Nabil Bank’s loan approvals) show KM in action with measurable outcomes.
• Exam focus: Define terms (e.g., "knowledge silo," "communities of practice"), compare structures, and link KM strategies to real orgs.

1. Organizational Structures and Knowledge Management

Organizations are not just hierarchies—they are knowledge networks where structure directly affects how knowledge flows. The three primary structures (hierarchical, flat, and matrix) each have unique KM implications.

A. Types of Organizational Structures

graph TD
    A["Organizational Structures"] --> B["1. Hierarchical (Functional)"]
    A --> C["2. Flat (Horizontal)"]
    A --> D["3. Matrix"]
    A --> E["4. Networked"]
    B --> B1["KM: Top-down, formal processes\nExample: NTC, Ncell"]
    C --> C1["KM: Informal, collaborative\nExample: Startups, Daraz"]
    D --> D1["KM: Cross-functional teams\nExample: Toyota’s lean manufacturing"]
    E --> E1["KM: External partnerships\nExample: Chaudhary Group’s supply chains"]

Key Idea:

• Hierarchical (Functional): Knowledge flows vertically (e.g., CEO → managers → employees). Pros: Clear roles, standardized processes. Cons: Slow innovation, silos. Example: NTC’s network planning relies on top-down engineering knowledge, but field technicians often lack access to updated designs.
• Flat (Horizontal): Minimal layers; employees collaborate directly. Pros: Faster decision-making, innovation. Cons: Overload, lack of expertise. Example: Daraz’s customer service teams use Slack to share real-time order issues, reducing response time.
• Matrix: Employees report to multiple bosses (e.g., project + functional managers). Pros: Cross-pollination of ideas. Cons: Conflict, ambiguity. Example: Toyota’s engineers and assembly workers co-design improvements under the "Toyota Production System."
• Networked: Outsourced or partner-based (e.g., freelancers, suppliers). Pros: Access to diverse expertise. Cons: Security risks, coordination challenges. Example: Chaudhary Group’s agribusiness relies on farmer knowledge networks for crop advice.

Worked Example: Nabil Bank’s Loan Approval Nabil Bank uses a hybrid hierarchical-flat structure for loan processing:

1. Hierarchical: Branch managers submit loan applications to a central risk committee (top-down).
2. Flat: Loan officers use a shared CRM (Salesforce) to flag high-risk applicants, enabling peer reviews.
3. Outcome: Faster approvals (reduced from 15 to 5 days) by breaking silos between underwriting and credit teams.

2. Organizational Culture and Knowledge Sharing

Culture is the "invisible KM system"—norms, trust, and leadership styles either encourage or suppress knowledge flow.

A. Dimensions of Organizational Culture (Schein’s Model)

mindmap
  root((Organizational Culture))
    Artifacts["Visible: Dress codes, rituals, stories"]
    Espoused Values["Stated goals, e.g., 'Innovation at Google'"]
    Basic Assumptions["Unconscious: 'Trust your team' vs. 'Hoard info'"]

Key Idea:

• High-trust cultures (e.g., Google, Pathao) encourage knowledge sharing via:
  • Open-door policies (e.g., Google’s "20% time" for side projects).
  • Reward systems (e.g., Pathao’s driver bonuses for sharing route tips).
• Low-trust cultures (e.g., traditional Nepali banks) rely on:
  • Hierarchical secrecy (e.g., senior managers hoarding client lists).
  • Punitive policies (e.g., firing whistleblowers).

Comparison Table: KM-Friendly vs. KM-Hostile Cultures

B. Communities of Practice (CoPs): The Glue for Knowledge

CoPs are informal groups where employees share expertise. They thrive in flat cultures but can exist anywhere.

graph LR
    A["Community of Practice"] --> B["Domain: Shared expertise\nExample: NTC’s telecom engineers"]
    A --> C["Community: Shared context\nExample: Daraz’s logistics drivers"]
    A --> D["Practice: Shared problem-solving\nExample: Nabil Bank’s fraud detection team"]
    B --> E["Outcome: Best practices documented"]
    C --> F["Outcome: Reduced onboarding time"]
    D --> G["Outcome: Faster innovation"]

Real-World Example: NTC’s Telecom Engineers

• Problem: Field technicians struggled with outdated wiring diagrams.
• Solution: NTC created a CoP where engineers shared troubleshooting videos on an internal YouTube channel.
• Result: 30% faster fault resolution (measured via NTC’s internal KM dashboard).

Worked Example: Kathmandu Traffic Routes Imagine Kathmandu’s traffic police as a networked CoP:

• Hierarchical: Senior officers issue orders (top-down).
• CoP: Junior officers share real-time route updates via WhatsApp groups (bottom-up).
• Outcome: During Dashain, traffic flow improves by 20% because ground-level knowledge (e.g., "Laxmi Chowk is blocked") reaches dispatchers faster.

3. Knowledge Silos: The Enemy of KM

Silos = departments/teams that hoard knowledge, leading to duplication, errors, and wasted resources.

graph TD
    A["Knowledge Silo"] --> B["Cause 1: Functional Departments\nExample: NTC’s IT vs. Operations"]
    A --> C["Cause 2: Lack of Trust\nExample: Nepali banks’ loan vs. risk teams"]
    A --> D["Cause 3: Poor Tools\nExample: Excel spreadsheets instead of shared databases"]
    B --> E["Effect: Redundant work\nExample: Two NTC teams designing the same tower"]
    C --> F["Effect: Poor decisions\nExample: Nabil Bank rejecting viable loans due to siloed data"]
    D --> G["Effect: Knowledge loss\nExample: Retired engineer’s expertise dies with them"]

How to Break Silos:

1. Cross-functional teams (e.g., Daraz’s product + logistics teams co-design packaging).
2. KM tools:
   • Intranets (e.g., Nabil Bank’s internal wiki for loan templates).
   • AI chatbots (e.g., NTC’s virtual assistant for technician queries).
3. Leadership mandates (e.g., Google’s "Psychological Safety" workshops).

Case Study: Daraz’s Supplier Network

• Problem: Suppliers in remote areas (e.g., Pokhara) lacked access to Daraz’s demand forecasts, leading to stockouts.
• Solution: Daraz implemented a shared dashboard (powered by SAP) where suppliers see real-time sales data.
• Result: 40% reduction in overstocking and 15% faster order fulfillment.

4. Organizational Learning and KM

Organizational learning = the ability to create, acquire, and transfer knowledge to improve performance (Argyris & Schön’s model).

flowchart TD
    A["Single-Loop Learning"] --> B["Fixes errors without questioning\nExample: NTC patches a network failure"]
    A --> C["Outcome: Short-term fix, no systemic change"]
    D["Double-Loop Learning"] --> E["Questions assumptions\nExample: NTC rethinks its rural connectivity model"]
    D --> F["Outcome: Long-term innovation"]

Real-World Example: NEPSE’s Market Data

• Single-loop: NEPSE fixes a website crash by upgrading servers (temporary fix).
• Double-loop: NEPSE analyzes why traders rely on unofficial WhatsApp groups → launches a real-time API for institutional investors.
• Impact: 25% increase in transparent trading data.

Worked Example: Pathao’s Driver Onboarding Pathao uses double-loop learning to improve driver training:

1. Single-loop: Fixes app bugs reported by drivers.
2. Double-loop: Surveys drivers to find they lack route knowledge → partners with local taxi unions to create a driver CoP.

5. Case Study: Chaudhary Group’s Agribusiness KM Strategy

Challenge: Chaudhary Group’s 100,000+ farmers in Nepal lacked access to modern farming techniques. Solution: A multi-layered KM approach:

graph LR
    A["Chaudhary Group KM Strategy"] --> B["1. Farmer CoPs\nExample: WhatsApp groups for pest control tips"]
    A --> C["2. Mobile Apps\nExample: ‘Chaudhary Krishi’ for weather alerts"]
    A --> D["3. University Partnerships\nExample: IAAS collaboration on soil data"]
    A --> E["4. Incentives\nExample: Bonuses for sharing high-yield techniques"]
    B --> F["Outcome: 20% yield increase in maize"]
    C --> G["Outcome: 30% reduction in crop losses"]

Key Takeaway: Chaudhary’s success shows that KM isn’t just about technology—it’s about culture, trust, and local adaptation.

In the Real World

1. eSewa’s Payment Fraud Prevention

   • KM Idea: Cross-functional CoPs
   • How: eSewa’s fraud detection team (IT + customer service) shares real-time scam patterns via a Slack channel. When a new phishing tactic emerges in Kathmandu, the team updates its internal wiki within hours.
   • Impact: 45% drop in fraudulent transactions in 2023.

2. Nabil Bank’s Loan Approval AI

   • KM Idea: Breaking silos with data integration
   • How: Nabil Bank’s loan officers previously relied on separate systems for credit scores and customer history. By integrating these into a single AI dashboard, officers now see a holistic risk profile in one view.
   • Impact: Loan approval time cut from 10 to 3 days; rejection rate dropped by 12%.

3. Daraz’s Logistics Optimization

   • KM Idea: Networked knowledge + real-time data
   • How: Daraz’s warehouse managers in Kathmandu and Pokhara use a shared inventory dashboard to predict demand spikes (e.g., during Dashain). Drivers in remote areas contribute route data via a mobile app.
   • Impact: 22% reduction in delivery delays during peak seasons.

Exam Tip

This unit is conceptual but applied—expect:

1. Definitions: Be ready to define:
   • Knowledge silo
   • Community of practice (CoP)
   • Single-loop vs. double-loop learning
   • Hierarchical vs. flat organizational structures
2. Comparisons: Tables (like the culture comparison above) are high-value. Practice drawing them from scratch.
3. Case Analysis: Given a scenario (e.g., "NTC struggles with rural network upgrades"), you must:
   • Identify the KM problem (e.g., silos between IT and field teams).
   • Propose a solution (e.g., cross-functional CoPs + mobile tools).
   • Justify with real-world examples (e.g., "Like Daraz’s supplier dashboard").
4. Diagrams: Always sketch a structure diagram (hierarchical/flat) or flowchart (e.g., how knowledge moves in a bank loan process). Examiners reward visual clarity.
5. Nepali Context: Relate answers to local firms (e.g., "Nabil Bank could adopt Pathao’s driver CoP model for loan officers").

Common Pitfalls:

• Vague answers: Avoid "KM is important" without linking to structure/culture.
• Ignoring trade-offs: If you say "flat structures are best," explain when hierarchy works (e.g., crisis management at NTC).
• No examples: Always tie theory to one Nepali or global company.

Final Visual: KM in Action at Nabil Bank

flowchart TD
    A["Customer Applies for Loan"] --> B["Branch Officer\nUses CRM to check credit score"]
    B --> C["Risk Team\nReviews AI flagged risks"]
    C --> D["CoP Forum\nPeers discuss edge cases"]
    D --> E["Approval Committee\nMakes decision"]
    E --> F["Customer Notified\nKnowledge updated in wiki"]
    G["Retired Officer\nShares expertise via mentorship"]
    G --> F