Foundation of Business ManagementUnit 513 min read
Organizational Processes & Change: Models, Forces & Implementation
Unit 5 of Foundation of Business Management explores how organizations function through processes (workflow, decision-making, innovation) and manage change (Lewin’s model, Kotter’s 8-step, resistance sources), with real-world applications in Nepali firms like Nabil Bank’s digital transformation and Daraz’s supply chain
TAKEAWAYS:
- Organizational processes are dynamic workflows (e.g., order fulfillment at Daraz) that link inputs (resources) to outputs (products/services) via structured steps, with feedback loops for continuous improvement.
- Change management follows models like Lewin’s Unfreeze-Change-Refreeze or Kotter’s 8-step, where resistance (e.g., employee fear of AI in Ncell) must be addressed via communication, incentives, and pilot testing.
- Process reengineering (e.g., NTC’s digital ticketing system) vs. incremental improvement (e.g., Pathao’s driver app updates) differ in scope, cost, and risk—choose based on urgency and resources.
- Forces of change (technology, competition, regulation) drive shifts like Khalti’s UPI adoption; organizations must scan the environment (PESTEL analysis) to anticipate disruptions.
- Implementation success depends on leadership support, employee engagement, and clear metrics (e.g., Nabil Bank’s 30% digital loan growth post-change).
- Ethical dilemmas arise in change (e.g., layoffs at Himalayan Java during automation); managers must balance efficiency with social responsibility.
1. Organizational Processes: The Engine of Workflow
Organizational processes are structured sequences of activities that transform inputs (resources, information, labor) into outputs (goods, services, decisions). They ensure consistency, efficiency, and alignment with goals. Processes can be:
- Core processes: Directly deliver value (e.g., Daraz’s order-to-delivery pipeline).
- Support processes: Enable core work (e.g., Nabil Bank’s HR training for digital literacy).
- Management processes: Govern the organization (e.g., NTC’s policy review for new services).
How Processes Work: A Step-by-Step Trace
Use the Process Mapping technique to visualize workflows. Example: Pathao’s Ride-Hailing Process:
flowchart TD
A["Customer Request\n(Phone App)"] -->|"Location/Route"| B["Driver Matching\n(Algorithm)"]
B -->|"Assigned"| C["Driver Accepts\n(Notification)"]
C --> D["Real-Time Tracking\n(GPS + App)"]
D -->|"Arrival"| E["Payment Processing\n(Khalti/Nepal Pay)"]
E --> F["Feedback Collection\n(Rating System)"]
F -->|"Loop"| AKey Elements:
- Inputs: Customer request, driver availability, payment method.
- Activities: Matching, tracking, payment.
- Outputs: Ride completion, feedback, data for improvements.
- Feedback: Ratings adjust driver incentives or app features.
Types of Organizational Processes
| Type | Example (Nepal) | Characteristics | Tools/Tech Used |
|---|---|---|---|
| Operational | Daraz order fulfillment | Repetitive, high volume, time-sensitive | ERP (SAP), WMS (Warehouse Mgmt) |
| Managerial | Nabil Bank’s quarterly reviews | Decision-making, resource allocation | Dashboards (Power BI), KPIs |
| Strategic | NTC’s fiber-optic network expansion | Long-term, high impact, cross-departmental | SWOT, Scenario Planning |
Worked Example: Kathmandu Traffic Routes as a Process
- Problem: Congestion on Ring Road during peak hours (7–9 AM).
- Process Analysis:
- Input: Vehicles (private, public transport, delivery vans).
- Bottleneck: Lack of dedicated lanes for buses (like Pathao’s priority lanes).
- Solution: Implement dynamic traffic light control (sensors adjust timings based on flow).
- Output: Reduced travel time by 20% (measured via Google Maps data).
- Change: Requires coordination with KMC, NTC, and private fleets (stakeholder management).
2. Change Management: Navigating the Shift
Change is inevitable—80% of organizational changes fail due to poor execution (McKinsey). Effective change management follows structured models:
A. Lewin’s 3-Stage Model
mindmap
root((Lewin’s Change Model))
Unfreeze["1. Unfreeze\n- Create urgency\n- Disrupt status quo\n- Example: NTC announcing digital ticketing (2023)"]
Change["2. Change\n- Communicate vision\n- Empower action\n- Example: Pilot testing in 3 districts (Kathmandu, Pokhara, Biratnagar)"]
Refreeze["3. Refreeze\n- Reinforce new norms\n- Celebrate wins\n- Example: Full rollout + training for all staff"]Why It Works:
- Unfreeze: Addresses resistance to change (e.g., ticket agents fearing job loss).
- Change: Uses pilot programs to reduce risk (like Daraz testing drone deliveries in rural areas).
- Refreeze: Ensures sustainability (e.g., NTC’s "Digital Ticketing Champion" awards).
B. Kotter’s 8-Step Model (For Large-Scale Change)
| Step | Action | Nepali Example | Risk if Skipped |
|---|---|---|---|
| 1. Create Urgency | Highlight gaps (e.g., slow loan processing) | Nabil Bank: "Customers wait 15 days for loans" | Low engagement from employees |
| 2. Build Coalition | Form a guiding team | CEO + IT + Branch Managers | Lack of cross-departmental buy-in |
| 3. Vision & Strategy | Define "Digital Loan in 30 Days" | Clear timeline + KPIs (e.g., 50% online) | Vague goals lead to failure |
| 4. Communicate | Town halls, emails, app notifications | WhatsApp groups for branch staff | Rumors and misinformation |
| 5. Empower Action | Remove barriers (e.g., train staff) | 2-week digital literacy workshop | Slow adoption |
| 6. Short-Term Wins | Celebrate milestones (e.g., 100 loans online) | Incentives for top performers | Demotivation |
| 7. Sustain Change | Anchor in culture (e.g., new KPIs) | "Digital Loan Officer" title | Reversion to old ways |
| 8. Institutionalize | Document processes, update policies | New SOPs for loan approval | Loss of knowledge when staff leave |
C. Forces Driving Change
Use PESTEL Analysis to identify external forces:
| Force | Example in Nepal | Impact on Organizations |
|---|---|---|
| Political | New FDI policy (2023) | Daraz expands warehouses; Ncell partners with global firms |
| Economic | Inflation (2022–23) | Nabil Bank raises interest rates; Khalti adds BNPL |
| Social | Rise of digital payments (Khalti, eSewa) | Traditional banks must adopt fintech or lose customers |
| Technological | 5G rollout (Ncell) | Pathao uses real-time navigation; NTC upgrades networks |
| Environmental | Air pollution laws (KMC) | Himalayan Java shifts to electric delivery vehicles |
| Legal | Data privacy act (2023) | NTC and banks invest in cybersecurity training |
Worked Example: NTC’s Shift to Digital Ticketing
- Force: Government push for paperless services (aligned with Nepal’s Digital Nepal vision).
- Process:
- Unfreeze: NTC announced phasing out paper tickets by 2025.
- Change:
- Partnered with Khalti for mobile payments.
- Trained 500 agents in 6 months.
- Refreeze: Introduced "Digital Ticketing Ambassador" role to sustain adoption.
- Result: 60% reduction in ticketing errors; 40% cost savings.
3. Overcoming Resistance to Change
Resistance is natural—people fear the unknown. Common sources and solutions:
| Source of Resistance | Example | Mitigation Strategy |
|---|---|---|
| Fear of job loss | NTC agents worried about automation | Retraining programs (e.g., "Ticketing to Tech Support") |
| Lack of trust in leadership | Employees doubt Daraz’s drone delivery safety | CEO town halls + pilot demo in Bhaktapur |
| Inconvenience | Bank staff resist new software (e.g., Nabil’s core banking system) | Phased rollout + IT helpdesk support |
| Peer pressure | "Everyone uses the old way" in Himalayan Java | Incentives for early adopters (e.g., bonuses) |
| Lack of resources | Small businesses can’t afford ERP systems | Government subsidies (e.g., for Daraz sellers) |
4. Implementing Change: Best Practices
A. Process Reengineering vs. Incremental Improvement
| Aspect | Process Reengineering | Incremental Improvement |
|---|---|---|
| Scope | Radical (e.g., NTC’s entire ticketing system) | Small (e.g., Pathao’s app UI tweaks) |
| Cost | High (e.g., $5M for NTC’s digital overhaul) | Low (e.g., $5K for a new Khalti integration) |
| Risk | High (failure = total collapse) | Low (failure = minor setback) |
| Speed | Slow (6–12 months) | Fast (weeks to months) |
| Example | Daraz’s shift from manual to AI-driven inventory | Nabil Bank adding chatbot for customer queries |
Worked Example: Himalayan Java’s Shift to E-Commerce
- Old Process: Wholly offline (retail stores only).
- Change: Launched himalayanjava.com (2022).
- Reengineering Steps:
- Partnered with Daraz for marketplace listing.
- Redesigned supply chain: Direct-to-consumer (D2C) fulfillment.
- Trained staff in digital marketing (Instagram, Facebook Ads).
- Result: 300% increase in orders; 20% cost savings on logistics.
B. Change Implementation Checklist
flowchart TD
A["Start"] --> B["Assess Readiness\n- Survey employees\n- Benchmark competitors"]
B --> C["Choose Model\n- Lewin’s 3-step? Kotter’s 8-step?"]
C --> D["Pilot Test\n- Small-scale trial (e.g., 1 branch for Nabil)"]
D --> E["Train & Communicate\n- Workshops\n- FAQs\n- CEO videos"]
E --> F["Monitor & Adjust\n- Track KPIs (e.g., adoption rate)"]
F --> G["Celebrate & Sustain\n- Rewards\n- Update policies"]5. Ethics in Change Management
Change often raises ethical dilemmas:
- Layoffs: When automating (e.g., Ncell’s customer service bots replacing 100 agents).
- Ethical Approach: Offer retraining (e.g., upskilling for cybersecurity roles).
- Data Privacy: NTC collecting passenger data for digital tickets.
- Solution: Transparent privacy policy + GDPR-like compliance.
- Cultural Sensitivity: Implementing Western-style performance reviews in Nepali firms.
- Fix: Adapt to collectivist values (e.g., team-based bonuses over individual incentives).
Case Study: Chaudhary Group’s Ethical Dilemma
- Change: Introduced biometric attendance in all branches (2023).
- Ethical Issue: Employees feared surveillance and loss of privacy.
- Solution:
- Anonymous feedback channels.
- Clear policy: Data used only for attendance, not performance ratings.
- Outcome: 90% employee satisfaction; no union strikes.
In the Real World
Daraz’s Supply Chain Agility
- Process: Uses just-in-time (JIT) inventory with AI demand forecasting.
- Change: Shifted from manual order processing to automated warehouses (2020–23).
- Impact: Reduced delivery time from 5 days to 24 hours in Kathmandu.
Nabil Bank’s Digital Loan Transformation
- Process: Old system required 15+ steps for loan approval (paperwork, manual checks).
- Change: Implemented KYC automation + blockchain for fraud detection.
- Result: Loan processing time dropped from 15 days to 2 hours.
Pathao’s Driver App Updates
- Process: Early version had no real-time traffic updates, leading to delays.
- Change: Integrated Google Maps API + crowdsourced traffic data.
- Outcome: 30% faster rides during peak hours (7–9 PM).
Exam Tip
This unit is heavily tested in TU/PU exams with:
- Definitions: Know the difference between process reengineering and process improvement.
- Models: Draw Lewin’s 3-step or Kotter’s 8-step and label all stages.
- Case Analysis: Expect short cases (e.g., "How would you implement digital tickets at NTC?"). Use the PESTEL + Kotter’s 8-step framework.
- Ethics: Be ready to critique changes (e.g., "Is Daraz’s layoff ethical? Justify with 3 points").
- Diagrams: Process maps (like Pathao’s ride flow) and force field analysis (forces driving/resisting change) are high-scoring.
Common Mistakes to Avoid:
- Confusing operational vs. strategic processes (e.g., calling customer service a "strategic" process).
- Ignoring stakeholder analysis in change management (e.g., forgetting to engage drivers in Pathao’s app updates).
- Overlooking cultural context (e.g., assuming Western change models work identically in Nepal).
Pro Tip: Memorize one real-world example per concept (e.g., NTC for digital transformation, Daraz for reengineering). Examiners love localized answers!
Based on the TU BIM syllabus for Foundation of Business Management (MGT231), unit 5.
Discussion
Loading…