Business administration Study Guide
Study Guide
📖 Core Concepts
Business Administration – The administration (or management) of a commercial enterprise; involves overseeing operations, making decisions, and organizing people & resources toward shared goals.
Scope of Administration – Encompasses finance, personnel, and management‑information systems; tasks are usually internal, routine, and reactive.
Fayol’s Five Functions – Planning, Organizing, Commanding/Leading, Coordinating, Controlling. These are the universal steps managers perform.
Key Managerial Skills – Strategic thinking, leadership, problem‑solving, communication, and the ability to work with diverse stakeholders.
Corporate Culture – The shared values, beliefs, and behaviors that shape how an organization operates.
Fail Fast Principle – Test ideas quickly so failures surface early and can be addressed before large investments.
Kanban System – A visual workflow tool that limits work‑in‑progress (WIP) to boost efficiency and transparency.
Sunk Cost – Past expenditures that cannot be recovered; they should not influence future decisions.
---
📌 Must Remember
Business administration = “business management” – the internal coordination of people, resources, and processes.
Fayol’s five elements: Plan → Organize → Command/Lead → Coordinate → Control.
Managerial skill set: Strategic thinking, Leadership, Problem‑solving, Communication, Diversity management.
Corporate culture = shared values & behaviors; it drives everyday actions.
Fail fast = rapid prototyping → early detection of flaws.
Kanban = visual board + WIP limits → work only when capacity exists.
Sunk cost = ignore when deciding whether to continue a project.
---
🔄 Key Processes
Management Cycle (Fayol)
Planning: Set objectives & decide actions.
Organizing: Allocate resources & assign tasks.
Command/Lead: Direct & motivate staff.
Coordinating: Align inter‑departmental activities.
Controlling: Monitor outcomes, compare to standards, adjust.
Kanban Workflow
Create a visual board (To‑Do, Doing, Done).
Set WIP limits for each column.
Pull work into “Doing” only when capacity is available.
Review flow daily; remove bottlenecks.
Fail‑Fast Testing Loop
Ideate → Prototype → Test quickly → Capture failures → Iterate.
---
🔍 Key Comparisons
Administration vs. Management – Administration is the broader function (includes finance, HR, MIS); Management is the action of planning, organizing, leading, controlling.
Planning vs. Organizing – Planning decides what to do; Organizing decides how to allocate resources to do it.
Commanding vs. Leading – Commanding = giving orders; Leading = inspiring & motivating.
Kanban vs. Traditional Gantt – Kanban is pull‑based, visual, WIP‑limited; Gantt is push‑based, schedule‑driven.
---
⚠️ Common Misunderstandings
“Sunk costs matter.” → They are irrelevant for future choices; only incremental costs/counts.
“Administrative tasks are proactive.” → By definition they are usually reactive and routine.
“Corporate culture is just perks.” → It’s the deep‑rooted values & behaviors that guide decisions.
“Fail fast means accept failure.” → It means detect failure early, not celebrate it.
“Kanban works only in factories.” → It applies to any knowledge‑work process needing flow control.
---
🧠 Mental Models / Intuition
Management Loop: Think of a feedback loop – set a target, act, measure, adjust, repeat.
Kanban as a Traffic Light: Green = pull new work, Yellow = limit, Red = stop until capacity frees.
Sunk Cost = “Sunken Ship”: Once the ship is underwater, you can’t raise it – don’t let it dictate future routes.
---
🚩 Exceptions & Edge Cases
Hybrid Tasks: Some admin activities (e.g., strategic budgeting) can be proactive.
Sunk Cost Accounting: For tax or reporting purposes, sunk costs are still recorded; just ignore them in decision analysis.
Kanban Adaptation: In highly regulated environments, WIP limits may be relaxed to meet compliance deadlines.
---
📍 When to Use Which
Fayol’s functions – Use whenever you need a complete managerial framework (any industry).
Kanban – Ideal for repeatable, flow‑based work (software dev, support tickets) where visual status and WIP limits improve throughput.
Fail Fast – Apply in innovation, product development, or any high‑uncertainty project where early feedback saves resources.
Sunk‑Cost Rule – Use when evaluating continuation of a project, investment, or initiative; ask “What will we gain now if we proceed?”
---
👀 Patterns to Recognize
“Goal → Resource → Process → Feedback” appears in planning, Kanban boards, and controlling steps.
Early testing signals (quick prototypes, A/B tests) indicate a fail‑fast scenario.
WIP limit breaches on a Kanban board flag bottlenecks needing coordination.
References to “values, beliefs, behaviors” signal a question about corporate culture.
---
🗂️ Exam Traps
Distractor: “Sunk costs should be added to future budgeting.” → Wrong; sunk costs are irrelevant for future decisions.
Distractor: “Kanban eliminates the need for any performance metrics.” → Incorrect; metrics (cycle time, lead time) are still essential.
Distractor: “Fail fast means abandoning projects after any negative result.” → Misleading; it means learning from early failures, not giving up immediately.
Distractor: “Commanding is the same as leading.” → They differ: commanding = issuing orders; leading = motivating and guiding.
---
or
Or, immediately create your own study flashcards:
Upload a PDF.
Master Study Materials.
Master Study Materials.
Start learning in seconds
Drop your PDFs here or
or