Dasar-Dasar Manajemen dalam Dunia Profesional

Main ideas, concepts, and lessons

1. Management is centered on goals

   • The core substance of management is always tied to organizational goals.
   • Management is described as processes made of behavioral actions that help achieve those goals.

2. Management only matters when there is an organization

   • Management exists because there is an organization made from agreements: members enter because they align with the organization’s goals.
   • A key consequence: members should contribute (not merely “work and get paid”).

3. Contribution and roles must be understood

   • Each member must understand their role in the organizational structure.
   • Roles are tied to business processes: people are grouped by roles so they can contribute effectively.
   • The emphasized attitude: differences in how people act are acceptable, but the goal must remain shared (not politics/opposition).

4. Modern corporate “goal” framing

   • In many companies, profit is discussed, but the argument here is:
     • Profit is a requirement for sustainability, not the ultimate goal.
     • The real goal is social contribution—providing solutions to societal problems.
   • Financial figures (including profit) are treated as intermediate outcomes that enable continued contribution.

5. Profit is achieved through managing sales and costs

   • Simple model:
     • Profit = Sales value − Costs
   • Management actions (in practice):
     • Increase revenue (sales)
     • Reduce costs (efficiency)

6. Business-process thinking: “next process is our customer”

   • The organization is viewed as internal customers across a chain of processes.
   • Sales is only one part of the process chain; failure anywhere can cause delivery failure.
   • Example:
     • Purchasing → production: purchasing must supply materials.
     • If purchasing fails, production quality/quantity—and then sales delivery—can fail.
   • Therefore: define
     • your role
     • who your customer is
     • what their needs are

7. Delivery is not negotiable; timelines must be strict

   • Avoid open-ended waiting and “we’ll do it when we can.”
   • Delivery depends on schedules and customer needs; customers don’t want to wait.
   • Leadership emphasis: set deadlines and plan around when things must be finished.

8. Management cycle using POLC: Plan–Organize–Lead–Control

   • Control is crucial to prevent common “we’ll do it later” failures.
   • The discussion prefers going in depth on leading/directing and control.

---

Methodology / step-by-step instructions (detailed bullet format)

A. What to do in “planning” (before actions)

• Step 1: Define the goal first
  • If there is no goal, there is no need for action.
• Step 2: Break the big goal into smaller goals
  • A plan is not merely a schedule; it is a goal breakdown.
• Step 3: Convert goals into indicators/benchmarks
  • For each sub-goal, define a measurable indicator so progress can be verified.
  • Planning must include how you know a goal has been achieved.
• Step 4: Collect complete facts/data before deciding actions
  • Data completeness is stressed.
  • Use “mutually exclusive, collectively exhaustive” logic (no overlap, no missing categories).
  • Planning fails if based on guesses or incomplete data.
• Step 5: Ensure correlation between actions and goals
  • Don’t create actions that don’t logically lead to the defined objectives.
• Step 6: Align timelines correctly
  • Don’t mix timelines for separate activities.
  • Example: measurement time and design time are different activities and need separate timing.
• Step 7: Make the plan a “guide for work,” not just a document
  • The plan must be used during execution.
  • Avoid “plans only exist on paper.”

B. Leading / directing: how to communicate correctly

• Step 1: Direct based on goals, not personal will
  • Avoid ordering as a display of power, bullying, or personal taste.
• Step 2: Direct as a communication process
  • Communication should include:
    1. Goal
    2. What actions must achieve that goal
    3. Details of what will be done
    4. Any additional clarification
• Step 3: Use standards
  • Directing should drive standardized behavior (not ad-hoc improvisation).
• Step 4: Differentiate planning types
  • Single-use plan (project ends)
  • Standing plan / standard (repeatable work, e.g., manufacturing routines)
• Step 5: Don’t “order like a combat commander”
  • If communication ignores standards/goals, workers get driven by circumstances and immediate needs.
• Step 6: If people can’t perform, it indicates a leadership teaching failure
  • Don’t complain that subordinates “can’t work.”
  • Instead, teach:
    • Job skills through job instruction
    • Train until people can perform according to standard
  • Toyota framing: a leader is someone who knows how to do the job—and can teach it.

C. Control: how to monitor and solve gaps

• Step 1: Define standards (or benchmarks) first
  • Without standards, you cannot control.
• Step 2: Compare actual vs ideal
  • Control means comparing:
    • what was planned / standardized
    • versus what is actually happening (facts/data)
• Step 3: Detect gaps (deltas) and deviations
  • Identify where reality deviates (plus/minus differences).
• Step 4: Use control data to identify problems
  • Problem definition: the gap between actual and ideal conditions.
• Step 5: Solve the problems
  • Leadership/management must have the will to close the gap.
• Step 6: Perform continuous improvement
  • If still below standard:
    • solve, then reassess
    • raise standards/adjust approaches through problem-solving, not empty promises

D. Core logic linking the whole system

• Planning (and standards) helps anticipate failure modes.
• Leading ensures people behave according to standards (and are trained to do so).
• Control finds deviations via data and drives problem-solving.
• Best problem-solving prevents issues before they become problems.

---

Speakers / sources featured

• Hasanuddin Abdurrahman — main speaker/lecturer (host of the video content)
• Mr. Umar Kayam — referenced for a fried rice waiting-times anecdote (“fried rice for only 10 [minutes]”)
• Stephen Covey (misheard as “Stephen Copy”) — referenced conceptually (“plan is mental creation” / simulate first)
• “New Horizons” spacecraft — referenced for planning, data, gravity assist, and mission timing to Pluto
• Toyota — referenced for leadership/teaching via job instruction and standardized work context

Japan manufacturing concepts referenced

• Heijunka (leveling / flat output concept)
• Muda (waste)
• Muri (overburden/overcapacity forcing)
• (Also mentions “muda/muri/cheat” with some subtitle errors; core idea is waste, overcapacity, and fluctuation)

Javanese proverb/phrases referenced

• “Weruh sak durunge winarah” (know before the lesson)

• “Jentreke kabeh” (complete/exhaustive)

• “God decides / humans plan” — referenced proverb/theme (no specific named source in the subtitles)

Other individuals mentioned (anecdotal)

• An Indonesian student in Japan (friend; anonymous)
• A Mexican part-time supplier worker in Hiroshima (anonymous)
• Startup advisor speaker’s own prior experience (speaker’s own, not a named external source)