Josh's StudyWiki

ClassificationSystems-Departmentalization

2 min read

Connection: Classification Systems ↔ Departmentalization

Ch7’s five types of departmentalization (Functional, Product, Process, Customer, Geographic) form a classification system — they are a set of mutually exclusive categories for grouping jobs. PHIL252’s classification rules provide tools to evaluate how well this taxonomy holds up and why some real-world cases are harder to classify than others.

From PHIL 252

A good classification system must be:

  1. Exhaustive — every item must fit into a category
  2. Exclusive — no item should fit two categories simultaneously
  3. Clear — boundaries between categories must be unambiguous
  4. Adequate — categories must be meaningful and useful for the purpose

See ClassificationSystems.

From ADMN 201

Five departmentalization types classify the same thing — how to group jobs — but each uses a different principle of division:

TypePrinciple of Division
FunctionalWhat activity does the job involve?
ProductWhat product does the job support?
ProcessWhat production step does the job perform?
CustomerWhat type of customer does the job serve?
GeographicWhat region does the job cover?

See Departmentalization.

Applying the Classification Rules

graph TD
    A["Five Departmentalization Types\nas a Classification System"]
    A --> B["Exhaustive?\nMostly — covers the major grouping\nprinciples; some hybrids may not fit cleanly"]
    A --> C["Exclusive?\nNot always — a regional sales role\ncould be Product OR Geographic"]
    A --> D["Clear?\nAt the prototype level yes;\nboundary cases require judgment"]
    A --> E["Adequate?\nYes — the five types are\nmeaningful and widely used in practice"]

(diagram saved)

Why This Matters

The PHIL252 insight that classification systems can fail the exclusive test is directly observable in Ch7. A company with a “Western Canada Laptop Sales” team could legitimately classify that department as Geographic or Product or Customer — all three principles apply simultaneously. Real firms often use hybrid departmentalization for exactly this reason, which is why the textbook presents these as types, not rigid rules.

This is the same pattern seen in other Ch7 structures: the Matrix design (see OrganizationalDesigns) explicitly breaks the “one boss = one department” assumption, acknowledging that strict functional classification sometimes fails the adequacy test.

ClassificationSystems, Departmentalization, OrganizationalDesigns

Graph View

Backlinks