CLEP Principles of Management Quick Review

Frederick Taylor's scientific management sought to replace rule-of-thumb work methods with time-and-motion studies and a standardized "one best way" to maximize efficiency at the task level.

Taylor's core principles: (1) develop a science for each element of work, (2) scientifically select, train, and develop workers, (3) cooperate with workers to ensure the methods are followed, (4) divide work and responsibility between management and workers. Associated with time-and-motion studies, piece-rate pay, and the Gilbreths' motion studies.

Scientific management (Taylor) targets the efficiency of individual tasks and workers on the shop floor; administrative/classical theory (Fayol) targets principles for managing the organization as a whole.

Answer choices may attribute Taylor's "one best way" and time-and-motion studies to Fayol or Weber -- match the theorist to the specific technique, not just the general era.

Taylor $arrow$ scientific management $arrow$ time-and-motion studies $arrow$ "one best way."

Henri Fayol identified five functions of management (planning, organizing, commanding, coordinating, controlling) and 14 principles of management applicable to the organization as a whole.

Fayol's 14 principles include division of labor, authority and responsibility, unity of command, unity of direction, scalar chain, centralization, esprit de corps, equity, and order. Fayol is considered the father of administrative/classical management theory.

Unity of command (each employee reports to only one supervisor) vs. unity of direction (one plan and one head for a group of activities sharing the same objective) -- both are Fayol principles but describe different things.

Students often swap "unity of command" and "unity of direction" -- the exam tests the exact definition of each term, not just recognition that it is "a Fayol principle."

Fayol $arrow$ 14 principles $arrow$ administrative/classical management $arrow$ organization-wide view.

The Hawthorne studies (Elton Mayo, Western Electric plant) showed that social and psychological factors -- attention, group norms, morale -- affect worker productivity as much as physical working conditions.

The "Hawthorne effect" is the tendency for people to change their behavior because they know they are being observed or studied. The findings launched the human relations movement, shifting emphasis from purely physical/economic incentives toward social needs and supervision style.

Hawthorne effect (behavior changes because of being observed) vs. halo effect (one positive trait colors the overall judgment of a person) -- these are different psychological phenomena.

A study describing output that rose regardless of whether lighting was increased or decreased is the classic signature of the Hawthorne effect -- do not assume the physical change itself caused the result.

Mayo $arrow$ Hawthorne studies $arrow$ human relations movement $arrow$ social factors matter.

The systems approach views an organization as an open system of interrelated inputs, transformation processes, and outputs interacting with its environment; the contingency approach holds that there is no single "best way" to manage -- the right approach depends on the situation.

Open systems exchange inputs and outputs with the environment and rely on feedback; closed systems do not. Contingency variables include organization size, technology, environmental uncertainty, and individual differences.

Systems approach (organization as interacting subsystems) vs. contingency approach (best management practice depends on the situation) -- systems theory describes structure; contingency theory prescribes situational choice.

"It depends" scenario questions (e.g., "the best leadership style depends on the situation") signal contingency theory -- do not select systems theory merely because the question mentions interrelated parts.

Systems $arrow$ inputs/transformation/outputs/feedback; Contingency $arrow$ "it depends" on the situation.

Organizational structure formalizes how tasks are divided, grouped, and coordinated; departmentalization is the basis on which jobs are grouped together.

Common departmentalization bases: functional, product/divisional, geographic, customer, and matrix (dual reporting lines). Chain of command is the unbroken line of authority from top to bottom; span of control is the number of subordinates a manager directly supervises.

Functional departmentalization (grouping by specialty, e.g., marketing, finance) vs. divisional/product departmentalization (grouping by product line, region, or customer segment, each division largely self-contained).

A matrix structure is often mistaken for a simple functional structure -- watch for language about employees reporting to two managers simultaneously (a project manager AND a functional manager), which signals matrix.

Departmentalize $arrow$ functional / divisional / matrix / customer / geographic.

HRM encompasses the staffing process (recruitment, selection, training, appraisal, compensation) plus compliance with employment law.

Staffing sequence: HR planning $arrow$ recruitment $arrow$ selection $arrow$ orientation $arrow$ training/development $arrow$ performance appraisal $arrow$ compensation/benefits. Key U.S. legal framework: Title VII of the Civil Rights Act (bars discrimination based on race, color, religion, sex, national origin), the Americans with Disabilities Act (ADA), and the Age Discrimination in Employment Act (ADEA).

Recruitment (attracting a pool of qualified applicants) vs. selection (choosing which applicant to hire from that pool) -- recruitment casts a wide net first; selection narrows it down.

A question describing "gathering many qualified applicants" tests recruitment; a question about "interviews, tests, and background checks to pick a candidate" tests selection -- don't conflate the two stages.

HR process $arrow$ plan $arrow$ recruit $arrow$ select $arrow$ train $arrow$ appraise $arrow$ compensate.

Content theories of motivation explain WHAT internal needs drive behavior; Maslow and Herzberg are the two most heavily tested content theories.

Maslow's hierarchy (bottom to top): physiological, safety, social/belongingness, esteem, self-actualization -- lower needs must be largely satisfied before higher needs motivate. Herzberg's two-factor theory: hygiene factors (pay, working conditions, company policy) prevent dissatisfaction but do not motivate; motivators (achievement, recognition, growth, the work itself) create satisfaction and drive performance.

Hygiene factors (must be present to avoid dissatisfaction, e.g., salary, job security) vs. motivators (create true job satisfaction, e.g., recognition, responsibility) -- raising pay (hygiene) will not, by itself, boost motivation.

Exam distractors often list a hygiene factor (e.g., "improved cafeteria") as the answer to "which factor increases motivation" -- hygiene factors only prevent dissatisfaction, they do not motivate.

Maslow $arrow$ 5-level pyramid; Herzberg $arrow$ hygiene (no dissatisfaction) vs. motivators (satisfaction).

McGregor's Theory X/Y describes managerial assumptions about workers, while Vroom's expectancy theory and Adams' equity theory are process theories explaining HOW motivation happens.

Theory X = workers are lazy and must be coerced/controlled; Theory Y = workers are self-motivated and seek responsibility. Vroom's expectancy theory: Motivation = Expectancy $×$ Instrumentality $×$ Valence (effort leads to performance, performance leads to reward, reward is valued). Adams' equity theory: employees compare their outcome/input ratio to others' and are demotivated by perceived inequity.

Expectancy theory (motivation depends on the perceived link between effort, performance, and reward) vs. equity theory (motivation depends on perceived fairness relative to others) -- expectancy is about an individual's own effort-reward chain; equity is about social comparison.

A scenario about an employee who stops trying because "raises never seem to follow good performance" tests expectancy theory (a broken effort-performance-reward link), not equity theory, which requires a comparison to another person.

Theory X/Y $arrow$ managerial assumptions; Vroom $arrow$ E$×$I$×$V; Adams $arrow$ fairness vs. others.

Leadership theory evolved from trait theories (leaders are born) to behavioral theories (leadership is a set of learnable behaviors) to contingency/situational theories (the best style depends on the situation).

Lewin's three leadership styles: autocratic (leader decides alone), democratic/participative (group involved in decisions), laissez-faire (hands-off, group decides). Fiedler's contingency model matches leader style (task- vs. relationship-oriented) to situational favorableness. Hersey-Blanchard's situational leadership adjusts style based on follower "readiness"/maturity.

Leadership (influencing and inspiring people toward a vision, focused on change) vs. management (planning, organizing, and controlling resources to meet established goals, focused on stability) -- a person can be a manager without being a leader, and vice versa.

A leader described as "adapting style based on how ready/skilled the follower is" is Hersey-Blanchard situational leadership, not Fiedler's contingency model, which matches a relatively fixed leader style to the situation.

Lewin $arrow$ autocratic/democratic/laissez-faire; Fiedler $arrow$ match style to situation; Hersey-Blanchard $arrow$ match style to follower readiness.

Organizations function through informal as well as formal elements -- group dynamics, shared culture, communication networks, and ethical norms all shape performance.

Formal groups are created by organizational authority (command/task groups); informal groups arise spontaneously from social needs (interest/friendship groups). Organizational culture is the shared values, beliefs, and norms that guide behavior, often transmitted through stories, rituals, and symbols. Communication flows downward, upward, horizontally, or through the informal "grapevine." Business ethics and corporate social responsibility involve balancing profit with obligations to stakeholders.

Groupthink (a cohesive group suppresses dissent to preserve harmony, leading to poor decisions) vs. group cohesiveness (the degree members are attracted to and want to remain in a group) -- high cohesiveness raises the risk of groupthink but is not the same concept.

A scenario where "no one voiced concerns about a flawed plan because they didn't want to disrupt team harmony" is testing groupthink -- don't mistake it for simple conformity or generic teamwork.

Formal vs. informal groups $arrow$ culture = shared values $arrow$ grapevine = informal communication $arrow$ groupthink = suppressed dissent.

Effective managerial decision-making follows a systematic process rather than snap judgment, moving from problem identification through implementation and follow-up.

Classic rational decision-making steps: (1) identify the problem, (2) identify decision criteria, (3) weight the criteria, (4) generate alternatives, (5) evaluate alternatives, (6) select the best alternative, (7) implement the decision, (8) evaluate decision effectiveness.

Programmed decisions (routine, repetitive, handled via established rules/procedures) vs. non-programmed decisions (unique, unstructured, requiring judgment) -- routine inventory reordering is programmed; entering a new international market is non-programmed.

The exam may test whether a decision "handled the same way every time using a standard procedure" is programmed -- do not select "non-programmed" just because a human is technically making the choice.

Decision steps $arrow$ identify problem $arrow$ criteria $arrow$ alternatives $arrow$ choose $arrow$ implement $arrow$ evaluate.

Herbert Simon argued that real managers cannot achieve the rational model's ideal of perfect information and an optimal choice, so they operate under bounded rationality.

The rational model assumes complete information and selection of the optimal solution. Bounded rationality (Simon) recognizes managers have limited information, time, and cognitive capacity, so they "satisfice" -- choose the first acceptable/good-enough solution rather than the theoretically best one.

Satisficing (accepting a good-enough alternative that meets a minimum threshold) vs. optimizing (searching for the single best possible alternative) -- bounded rationality leads to satisficing, not optimizing.

A manager who "picks the first option that meets an acceptable standard rather than the best possible one" is satisficing under bounded rationality -- don't mistakenly label this the rational/classical model.

Simon $arrow$ bounded rationality $arrow$ satisfice (good enough), not optimize (the best).

Operations management concerns the systems and processes an organization uses to convert inputs into finished goods and services efficiently.

Productivity = outputs $/$ inputs. Key operations concepts: capacity planning, inventory management, just-in-time (JIT) inventory (minimizing inventory by receiving goods only as needed), and process/layout design.

Efficiency (doing things right -- minimizing resource waste/cost for a given output) vs. effectiveness (doing the right things -- achieving stated goals) -- a manager can be efficient without being effective, and vice versa.

An item describing an organization that "hit its sales targets but spent well over budget" is testing effectiveness without efficiency -- do not assume high output alone means both were achieved.

Productivity $arrow$ outputs/inputs; Efficiency $arrow$ doing things right; Effectiveness $arrow$ doing the right things.

Total Quality Management (TQM), associated with W. Edwards Deming, is a management philosophy centered on continuous improvement and meeting customer expectations through the efforts of everyone in the organization.

Key TQM principles: intense customer focus, concern for continuous improvement (kaizen), process-focused (not just outcome-focused) management, and employee empowerment in quality. Deming is closely associated with statistical quality control and the Plan-Do-Check-Act (PDCA) cycle.

TQM (an ongoing, organization-wide philosophy of continuous, incremental quality improvement) vs. quality control/inspection (checking finished output for defects after production) -- TQM tries to build quality in throughout the process, not just catch defects at the end.

The exam may present "inspecting products at the end of the line to catch defects" as TQM -- that describes traditional quality control, which TQM is meant to reduce reliance on.

TQM $arrow$ Deming $arrow$ continuous improvement $arrow$ customer focus $arrow$ PDCA cycle.

Management information systems (MIS) collect, process, and deliver information to support managerial decision-making at all organizational levels.

Useful information should be timely, accurate, relevant, and complete. Different levels of management need different types of information: operational managers need detailed, real-time data; top managers need summarized, strategic information.

Data (raw, unprocessed facts) vs. information (data that has been processed/organized to be meaningful for decision-making) -- a spreadsheet of raw sales numbers is data; a summarized quarterly sales-trend report is information.

A question may describe "a large volume of unorganized numbers" and ask whether this is "information" -- raw, unprocessed facts remain data until they are processed into a useful form.

MIS $arrow$ data (raw) $arrow$ processed $arrow$ information (useful) $arrow$ supports decisions.

Most modern management texts organize the manager's job into four core functions -- planning, organizing, leading, and controlling (P-O-L-C) -- performed continuously and often simultaneously.

Planning = setting goals and deciding how to achieve them. Organizing = arranging resources and tasks (structure, staffing) to implement the plan. Leading = directing and motivating people toward goals. Controlling = monitoring performance and correcting deviations from the plan.

Planning (deciding what to do and how) vs. controlling (checking whether it was actually done and correcting course) -- planning happens before action; controlling happens during/after, comparing actual results to the plan.

A manager "comparing actual sales to the sales goal and adjusting the sales plan" is exercising controlling, even though the word "plan" appears -- don't default to "planning" on keyword alone.

P-O-L-C $arrow$ Plan (set goals) $arrow$ Organize (arrange resources) $arrow$ Lead (direct people) $arrow$ Control (monitor/correct).

Plans exist on a hierarchy that cascades from broad, long-range strategic plans down to narrow, short-range operational plans.

Strategic plans (top management, long-term, broad, organization-wide) $arrow$ tactical plans (middle management, medium-term, department-level, implement strategy) $arrow$ operational plans (first-line/supervisory management, short-term, specific day-to-day procedures).

Strategic planning (top management sets overall long-term direction) vs. tactical planning (middle management translates strategy into department-level action) -- "expand internationally within 5 years" is strategic; "open the European regional office this year" is tactical.

A short-term, department-specific plan (e.g., "this week's production schedule") is often mislabeled "strategic" simply because it is a plan -- match the time horizon and organizational level, not just the presence of a goal.

Strategic (top, long-term) $arrow$ Tactical (middle, medium-term) $arrow$ Operational (first-line, short-term).

Strategic planning starts with defining organizational purpose (mission) and aspiration (vision), then assessing internal and external conditions before setting goals.

Mission statement = the organization's core purpose/reason for existing. Vision statement = what the organization aspires to become. SWOT analysis examines internal Strengths and Weaknesses and external Opportunities and Threats to inform strategy.

Strengths/Weaknesses (internal factors the organization controls, e.g., skilled workforce, outdated equipment) vs. Opportunities/Threats (external factors the organization does not control, e.g., a new market, a new competitor) -- correctly classifying internal vs. external is the key skill.

A new competitor entering the market is a Threat (external), not a Weakness (internal) -- exam distractors frequently swap internal and external factors within SWOT scenarios.

SWOT $arrow$ Strengths/Weaknesses = internal; Opportunities/Threats = external.

Management by Objectives (Peter Drucker) is a planning and motivation technique in which managers and employees jointly set specific, measurable goals and periodically review progress toward them.

MBO process: set organization-wide objectives $arrow$ cascade goals to divisions/departments/individuals $arrow$ managers and subordinates jointly set specific individual objectives $arrow$ develop action plans $arrow$ periodically review progress $arrow$ appraise performance against the objectives.

MBO (goals set jointly/collaboratively between manager and subordinate) vs. top-down goal-setting (goals imposed unilaterally by management) -- MBO's defining feature is participative, mutual goal-setting.

Goals "handed down from upper management without employee input" are not true MBO, even if specific and measurable -- participation is the essential ingredient the exam checks for.

MBO $arrow$ Drucker $arrow$ jointly set specific goals $arrow$ review progress $arrow$ appraise results.

Organizing translates plans into a structure of authority and responsibility, including decisions about how many people a manager can effectively supervise.

Authority = the formal right to direct others and make decisions. Responsibility = the obligation to perform assigned duties. Accountability = being answerable for outcomes. Span of control = the number of subordinates a manager directly supervises; a wide span produces a flatter structure, a narrow span produces a taller structure.

Authority (the right to direct, which flows downward and can be delegated) vs. responsibility (the obligation to perform, which is assumed) -- a manager can delegate authority but cannot fully delegate away ultimate accountability for the outcome.

Delegating authority does not free the manager of all accountability -- responsibility for the overall outcome still rests with the delegating manager even after authority is delegated.

Wide span $arrow$ flat structure; Narrow span $arrow$ tall structure. Authority delegated $$ accountability erased.

Centralization and decentralization describe where decision-making authority is concentrated within the organizational hierarchy.

Centralization = decision-making authority concentrated at upper management levels. Decentralization = decision-making authority pushed down to lower levels/local managers closer to the problem. Fast local decisions and employee development favor decentralization; the need for uniform policy favors centralization.

Decentralization (authority is distributed to lower levels as an organization-wide philosophy) vs. delegation (a manager assigns a specific task/authority to a specific subordinate) -- decentralization is structural; delegation is an individual act.

A single manager assigning one task to one employee illustrates delegation, not "decentralization" -- decentralization describes an organization-wide policy, not one individual assignment.

Centralized $arrow$ authority at the top; Decentralized $arrow$ authority pushed down/out.

Organizations distinguish between line positions, which have direct authority to achieve organizational goals, and staff positions, which support and advise line managers.

Line authority = direct chain-of-command authority to give orders and achieve core objectives (e.g., production, sales managers). Staff authority = advisory/support authority (e.g., HR, legal, quality control) that assists line managers but generally cannot give direct orders to line employees.

Line functions (directly involved in producing/selling the organization's core product or service) vs. staff functions (support/advise line functions but are not directly responsible for core output, e.g., legal counsel, HR).

An HR manager described as "recommending" and "advising," but not directly commanding production employees, is exercising staff authority -- don't mistake advisory influence for line command authority just because of a management title.

Line $arrow$ direct command, core mission; Staff $arrow$ advise/support, no direct command.

Delegation is the process of assigning authority and responsibility for specific tasks to subordinates, enabling managers to focus on higher-level work.

Effective delegation requires assigning duties, granting authority to carry them out, and creating accountability for results. Empowerment goes further, giving employees genuine discretion and decision-making power over their own work.

Delegation (a manager assigns a specific task and the authority to complete it, while retaining ultimate responsibility) vs. abdication (a manager simply walks away from a responsibility without providing support/authority/follow-up).

A manager who assigns a task but provides no authority, resources, or follow-up is a classic example of poor/failed delegation -- true delegation requires granting commensurate authority, not just handing off work.

Delegate $arrow$ assign task + authority + retain accountability; Empower $arrow$ give real decision-making discretion.

French and Raven's five bases of power describe the distinct sources from which a manager's ability to influence others can come.

The five power bases: legitimate (formal position), reward (control over rewards), coercive (control over punishment), expert (specialized knowledge/skill), and referent (personal charisma/likability that inspires identification).

Legitimate power (comes from one's formal organizational position/title) vs. expert power (comes from one's knowledge/skill, independent of title) -- a junior employee with rare technical expertise can hold expert power over senior colleagues.

A well-liked, charismatic team member who influences peers despite having no formal authority is exercising referent power, not legitimate power -- match the source of influence, not the person's rank.

Power bases $arrow$ legitimate, reward, coercive (position-based); expert, referent (person-based).

Early behavioral leadership research (e.g., the Ohio State and Michigan studies) found that leader behavior clusters into two broad dimensions: concern for people and concern for task/production.

Consideration/employee-oriented behavior focuses on relationships, trust, and employee welfare. Initiating structure/task-oriented behavior focuses on defining roles, structuring work, and meeting production goals. Effective leaders often blend both dimensions.

Employee-oriented (relationship/people-focused) leadership vs. task-oriented (production/structure-focused) leadership -- these are two independent dimensions of behavior, not opposite ends of one scale.

The exam may imply a leader must choose EITHER people-focus OR task-focus -- behavioral research treats these as independent dimensions a leader can exhibit simultaneously (e.g., high-high leaders).

Consideration $arrow$ people; Initiating structure $arrow$ task; both are independent dimensions.

Leading translates motivation theory into the day-to-day practice of directing, coaching, and inspiring employees toward organizational goals.

Job enrichment = adding more responsibility, autonomy, and meaningful work to a job (vertical loading) to increase intrinsic motivation. Job enlargement = adding more tasks of similar skill level to a job (horizontal loading) to reduce monotony, without necessarily increasing responsibility.

Job enlargement (more tasks at the same level -- "horizontal" expansion) vs. job enrichment (more responsibility/autonomy/meaningful work -- "vertical" expansion) -- enrichment is linked to Herzberg's motivators; enlargement mainly varies routine.

An assembly worker simply given two more repetitive tasks at the same skill/responsibility level illustrates job enlargement, not job enrichment, even if the exam phrases it as "increasing the job."

Enlargement $arrow$ more tasks, same level (horizontal); Enrichment $arrow$ more responsibility/autonomy (vertical).

Controlling is the ongoing management function of comparing actual performance to planned standards and taking corrective action when needed.

Basic control process: (1) establish standards/goals, (2) measure actual performance, (3) compare performance to standards, (4) take corrective action if there is a significant deviation. Standards should be specific and measurable.

Control (comparing actual results against pre-set standards and correcting deviations) vs. planning (the initial process of setting the goals/standards themselves) -- controlling presumes a standard already exists from planning.

A manager "setting next year's sales target" is planning; a manager "comparing this year's actual sales to last year's target and taking action" is controlling -- watch for whether a standard is being set or measured against.

Control process $arrow$ set standards $arrow$ measure $arrow$ compare $arrow$ correct.

Controls can be timed to occur before, during, or after an activity, each catching problems at a different stage of the process.

Feedforward control occurs before the activity begins, preventing problems (e.g., inspecting raw materials before production). Concurrent control occurs while the activity is happening, catching problems in real time (e.g., direct supervision on the line). Feedback control occurs after the activity is complete, using results to improve future performance.

Feedforward control (proactive, before the process starts) vs. feedback control (reactive, after the process is finished) -- feedforward tries to prevent problems before they occur; feedback catches and learns from problems only after output is complete.

"Inspecting raw materials before production begins" is feedforward control, but the exam may mislabel it feedback control simply because "inspection" sounds like a check on output -- focus on WHEN in the process the control occurs.

Feedforward $arrow$ before; Concurrent $arrow$ during; Feedback $arrow$ after.

Budgets translate plans into quantitative, financial terms and serve as a key control tool for monitoring whether the organization is operating within its planned resources.

A budget is a numerical plan for allocating resources to specific activities over a set period. Variance analysis compares budgeted (planned) figures to actual figures; a favorable variance means actual results were better than budgeted, an unfavorable variance means worse than budgeted.

Favorable variance (actual results better than the budgeted standard) vs. unfavorable variance (actual results worse than the budgeted standard) -- these describe the direction of deviation from budget, not simply whether a number went up or down.

Actual costs coming in higher than budgeted is unfavorable, but actual revenue coming in higher than budgeted is favorable -- the same direction ("higher than planned") can be favorable or unfavorable depending on whether it is a cost or a revenue line item.

Budget $arrow$ planned figures; Variance $arrow$ actual vs. budget; Favorable = better than planned.

Some management frameworks treat staffing -- filling and keeping organizational positions filled with qualified people -- as a distinct function tightly linked to organizing and leading.

Staffing includes workforce planning, recruiting, selecting, orienting, training, appraising, compensating, and promoting or separating employees as needed. Succession planning identifies and develops future candidates for key positions in advance.

Staffing (the ongoing management function of ensuring the organization has the right people in the right positions) vs. the Human Resources department (the specialized unit that executes many staffing policies organization-wide) -- staffing is a function every manager performs.

The exam may treat "staffing" and "the HR department" as interchangeable -- staffing is a function performed by managers at every level (e.g., a sales manager staffing their own team), not exclusively an HR task.

Staffing $arrow$ fill positions with the right people $arrow$ recruit, select, train, appraise, retain.

As organizations expand across borders, managers must adapt strategy and structure to operate effectively in multiple countries and cultures.

A multinational corporation (MNC) maintains significant operations in more than one country. Global-entry strategies range from lowest to highest commitment/risk: exporting, licensing/franchising, joint ventures, and wholly owned foreign subsidiaries.

Licensing (granting a foreign firm the right to use your trademark/technology for a fee, low investment/control) vs. joint venture (a jointly owned entity created with a foreign partner, sharing investment, control, and risk) -- licensing involves minimal direct investment abroad.

A "jointly owned foreign operation with a local partner" is a joint venture, not licensing -- shared ownership and shared control are the signal for a joint venture.

Global entry $arrow$ export $arrow$ license/franchise $arrow$ joint venture $arrow$ wholly owned subsidiary (rising commitment/risk).

Geert Hofstede's research identified dimensions on which national cultures systematically differ, helping managers anticipate how management practices may need to adapt across countries.

Key dimensions: power distance (acceptance of unequal power distribution), individualism vs. collectivism (personal achievement vs. group loyalty), uncertainty avoidance (tolerance for ambiguity/risk), and masculinity vs. femininity (assertiveness/achievement vs. cooperation/quality of life).

High power distance (a culture that accepts and expects hierarchical, unequal authority) vs. low power distance (a culture favoring more equal, participative relationships between superiors and subordinates) -- informal, first-name-basis interaction with the boss reflects low power distance.

Employees who "rarely question or challenge a manager's decision, even when they disagree" illustrate high power distance -- do not mislabel this high uncertainty avoidance, which instead concerns comfort with ambiguity/risk.

Hofstede $arrow$ power distance, individualism/collectivism, uncertainty avoidance, masculinity/femininity.

Workforce diversity management involves recognizing and leveraging differences among employees (demographic, cultural, cognitive) as an organizational asset, supported by inclusive policies.

Diversity management goes beyond legal compliance to actively fostering an inclusive culture where differences are valued. Common initiatives include diversity training, mentoring programs, and inclusive recruitment/promotion practices.

Equal Employment Opportunity compliance (the legal floor -- not discriminating based on protected characteristics) vs. diversity management (a broader, proactive strategic effort to attract, develop, and leverage a diverse workforce) -- compliance is the legal minimum.

The exam may treat "avoiding discrimination lawsuits" and "managing diversity" as the same concept -- diversity management is proactive and strategic, going beyond merely avoiding legal liability.

EEO compliance $arrow$ legal minimum; Diversity management $arrow$ proactive strategic advantage.

Because environments are dynamic, managers must plan and lead organizational change; Kurt Lewin's three-step model remains the foundational change framework.

Lewin's three-step change model: unfreezing (creating motivation/readiness to change, reducing resistance), changing/moving (implementing the actual change, new behaviors/processes), refreezing (stabilizing and reinforcing the new state so it sticks). Common sources of resistance include fear of the unknown, habit, and self-interest.

Unfreezing (preparing people for change, breaking down the status quo) vs. refreezing (locking in/stabilizing the new way of doing things after the change) -- unfreezing happens first, refreezing happens last.

A company that implements a change but never reinforces or institutionalizes the new process often sees employees "revert to old ways" -- this failure is due to skipping the refreezing stage, not the unfreezing or changing stages.

Lewin $arrow$ unfreeze $arrow$ change $arrow$ refreeze.

Contemporary management must address entrepreneurship, sustainability, and rapidly evolving technology as ongoing strategic concerns alongside the traditional management functions.

Entrepreneurship = the process of starting and growing a new business venture, involving innovation and risk-bearing in pursuit of opportunity; intrapreneurship applies the same mindset by employees inside an existing large organization. CSR and environmental sustainability (the "triple bottom line" -- people, planet, profit) are increasingly treated as strategic management concerns, not just ethical add-ons.

Entrepreneurship (creating a new, independent venture) vs. intrapreneurship (innovating and taking entrepreneurial risks from within an existing organization, using its resources) -- an employee developing a new internal product line within their current employer is an intrapreneur, not an entrepreneur.

An employee who develops a new product line "using company resources, while still employed by the company" is practicing intrapreneurship, not entrepreneurship, even though the language of "starting something new" is present.

Entrepreneur $arrow$ starts own new venture; Intrapreneur $arrow$ innovates from within an existing firm.

100 questions/90 minutes $arrow$ 4 functions (POLC) $arrow$ 5 needs (Maslow) $arrow$ 14 principles (Fayol).

Efficiency = right way; Effectiveness = right goal; Delegation = individual act; Decentralization = org-wide policy.

Taylor = tasks; Fayol = principles; Mayo = people; Maslow/Herzberg/McGregor = motivation; Simon = bounded rationality; Deming = quality.

No fixed textbook -- match content to the official CLEP knowledge and skills outline.

Actor $arrow$ level/horizon $arrow$ internal/external $arrow$ match exact theory $arrow$ eliminate near-miss choices.

$$100 questions/90 minutes, all MCQ; Functional Aspects (P-O-L-C) is roughly half the exam.

Mission/Vision $arrow$ SWOT scan $arrow$ formulate strategy $arrow$ implement $arrow$ control/evaluate.

Problem $arrow$ criteria $arrow$ weight $arrow$ alternatives $arrow$ choose $arrow$ implement $arrow$ evaluate.

When in doubt: match the exact theorist/definition -- a surface topic match is not enough.

This is the whole exam in 29 lines -- if a term above is fuzzy, revisit that numbered topic box.