Engineering ManagementUnit 110 min read
Management Basics: Definitions, Functions, Levels & Evolution
Unit 1 of Engineering Management explores the core concepts of management—its definition, evolution, functions, levels, and importance in engineering organizations—with real-world examples from Nepali tech firms and global corporations.
TAKEAWAYS:
- Management is the process of planning, organizing, leading, and controlling resources to achieve organizational goals efficiently.
- The three levels of management (top, middle, operational) each have distinct roles and responsibilities.
- Scientific Management (Taylor) and Human Relations (Mayo) represent key historical approaches to improving productivity.
- Engineering management applies technical expertise to solve organizational problems, especially in tech-driven firms like eSewa and Ncell.
- Management principles (e.g., unity of command, division of work) ensure smooth operations in projects and teams.
- Global vs. Nepali contexts: Multinational firms (e.g., Google) use data-driven management, while Nepali firms (e.g., Nabil Bank) rely on traditional hierarchies.
1. Definition of Management
Management is the art and science of coordinating resources (human, financial, material, and information) to achieve predefined goals efficiently and effectively.
Key Characteristics of Management
mindmap
root((Management))
Characteristics
Goal-Oriented: Achieves organizational objectives
Pervasive: Applies to all levels (top to operational)
Multi-Dimensional: Involves planning, organizing, leading, controlling
Continuous Process: Dynamic and ongoing
Group Activity: Requires teamwork
Dynamic Function: Adapts to changes (e.g., tech disruptions)Difference Between Management and Administration
| Management | Administration |
|---|---|
| Focuses on achieving goals | Focuses on maintaining systems |
| Dynamic and future-oriented | Static and present-oriented |
| Example: eSewa’s app development team planning a new feature | Example: NTC’s billing department processing invoices |
Worked Example:
- Nepal Rastra Bank (NRB) manages monetary policy (goal-oriented), while its records department administers compliance reports (system-oriented).
2. Evolution of Management Thought
Management theories evolved from classical to modern approaches, shaped by industrial revolutions and technological advancements.
Major Schools of Management Thought
flowchart LR A["Classical School"] --> B["Scientific Management<br/>(Taylor, Gilbreth)"] A --> C["Administrative Theory<br/>(Fayol, Weber)"] D["Neo-Classical School"] --> E["Human Relations<br/>(Mayo, Maslow)"] D --> F["Behavioral Science<br/>(Hertzberg, McGregor)"] G["Modern School"] --> H["Systems Theory<br/>(Kast & Rosenweig)"] G --> I["Contingency Theory<br/>(Fiedler, Lawrence & Lorsch)"]
Key Theorists and Their Contributions
| Theorist | Theory | Key Idea | Real-World Example |
|---|---|---|---|
| Frederick Taylor | Scientific Management | Standardize work methods to improve efficiency | Daraz’s warehouse sorting (optimized picking routes) |
| Henri Fayol | Administrative Theory | 14 principles (e.g., unity of command, division of work) | Nabil Bank’s branch hierarchy |
| Max Weber | Bureaucratic Model | Formalized rules, hierarchy, and impersonality | NTC’s regulatory framework |
| Elton Mayo | Human Relations | Worker morale > efficiency (Hawthorne Effect) | Pathao’s driver incentives (bonuses for high ratings) |
| Peter Drucker | Management by Objectives | Align employee goals with organizational objectives | Google’s OKRs (Objectives & Key Results) |
Worked Example:
- Khalti’s fraud detection team uses contingency theory—they adapt rules based on whether fraud is high (strict checks) or low (relaxed verification).
3. Functions of Management
The 4 primary functions (POLC) are interdependent and cyclical.
flowchart TD A["Planning"] --> B["Organizing"] B --> C["Leading"] C --> D["Controlling"] D -->|"Feedback"| A
A. Planning
- Definition: Setting goals and deciding actions to achieve them.
- Types:
- Strategic (long-term, e.g., Nepal’s IT policy 2076)
- Tactical (medium-term, e.g., Daraz’s Q4 sales targets)
- Operational (short-term, e.g., daily traffic routing for Pathao drivers)
Worked Example:
- Nepal Electricity Authority (NEA) plans 10-year power expansion (strategic) but also daily load shedding schedules (operational).
B. Organizing
- Definition: Arranging resources (human, financial, physical) to implement plans.
- Key Elements:
- Departmentalization (by function, product, geography)
- Span of Control (how many subordinates report to one manager)
- Authority & Responsibility (e.g., project leads in engineering firms)
Comparison: Functional vs. Divisional Structures
| Feature | Functional Structure | Divisional Structure |
|---|---|---|
| Basis of Division | Jobs/functions (e.g., HR, IT, Finance) | Products/regions (e.g., Daraz Nepal vs. Daraz India) |
| Communication | Vertical (slow for cross-department work) | Horizontal (faster for product teams) |
| Example | Ncell’s IT and customer service teams | Himalayan Java’s regional branches |
C. Leading (Directing)
- Definition: Influencing employees to achieve goals.
- Tools:
- Leadership styles (autocratic, democratic, laissez-faire)
- Motivation theories (Maslow’s hierarchy, Herzberg’s two-factor theory)
Worked Example:
- Toyota’s "The Toyota Way" uses democratic leadership—team members suggest improvements (e.g., Kaizen).
D. Controlling
- Definition: Ensuring actual performance matches plans.
- Steps:
- Set standards (e.g., NEPSE’s daily trading volume targets)
- Measure performance (e.g., Khalti’s transaction success rate)
- Compare & take corrective action (e.g., NTC’s internet speed audits)
4. Levels of Management
Organizations have three hierarchical levels, each with distinct roles.
classDiagram
class TopLevel {
+Long-term planning
+Strategic decisions
+Example: CEO of Nabil Bank
}
class MiddleLevel {
+Tactical planning
+Supervisory role
+Example: Branch manager at Ncell
}
class OperationalLevel {
+Daily operations
+Directly supervises workers
+Example: Call center agent at eSewa
}
TopLevel --> MiddleLevel : delegates to
MiddleLevel --> OperationalLevel : overseesRoles by Level
| Level | Key Responsibilities | Example in Nepal |
|---|---|---|
| Top Level | Vision, policies, external relations | CEO of Chaudhary Group |
| Middle Level | Implement strategies, coordinate departments | Project manager at Mahindra Nepal |
| Operational | Execute tasks, solve daily issues | Warehouse supervisor at Daraz |
Worked Example:
- Nepal’s Ministry of Science & Technology (top level) sets IT policies, while PU’s exam committee (middle level) designs syllabi, and lab assistants (operational) conduct practical exams.
5. Importance of Management in Engineering
Engineering management bridges technical expertise and business acumen, critical for:
- Project execution (e.g., Melamchi Water Project)
- Innovation (e.g., Nepal’s electric vehicle pilot programs)
- Risk management (e.g., NTC’s power grid stability)
Case Study: eSewa’s Growth
- Technical: Built a secure payment gateway (engineering).
- Management: Used agile methodologies to iterate features (management).
- Result: Processed 10M+ transactions/month (2023).
In the Real World
eSewa’s Queue System
- Idea Used: Controlling function (managing transaction queues).
- How: During peak hours (e.g., Dashain bonus payments), eSewa limits transactions per user to prevent server crashes. This is operational controlling in action.
Pathao’s Driver Motivation
- Idea Used: Human Relations Theory (Mayo).
- How: Pathao offers bonuses for 5-star ratings and referral incentives, proving that social recognition (not just money) boosts performance.
Nabil Bank’s Loan Approval
- Idea Used: Scientific Management (Taylor).
- How: The bank uses standardized loan assessment checklists (e.g., credit score >600, income proof) to reduce processing time from weeks to days.
Exam Tip
- Definitions Matter: Memorize key terms like:
- "Management is the process of getting things done through people."
- "Fayol’s 14 principles of management include ‘unity of command.’"
- Compare Theories: Questions often ask to contrast Taylor vs. Mayo or functional vs. divisional structures. Use tables in answers.
- Real-World Links: Always relate theories to Nepali examples (e.g., NTC’s bureaucracy = Weber’s model).
- Diagrams = Marks: Draw POLC cycle or organizational charts in exams—they fetch extra points.
- Case Study Questions: Expect short cases (e.g., "How would you apply Maslow’s hierarchy to motivate Daraz delivery boys?"). Structure answers as:
- Problem (e.g., low morale → high turnover).
- Theory (e.g., Maslow’s self-actualization needs).
- Solution (e.g., training programs for career growth).
Final Note: Management is not just theory—it’s how every company, from Ncell to Google, turns ideas into success. Master the frameworks, but always think: "How would this work at a Nepali firm?"
Based on the PU BE Computer (PU) syllabus for Engineering Management (MGT320), unit 1.
Discussion
Loading…