As a manager-in-training in the engineering department of a large-scale
sugar mill, I initially held the view that organisational design was a corporate
topic reserved for HR or executive retreats. However, this lecture
fundamentally changed my perspective, revealing that the structure of our
mill is as critical to our success as it is to achieving targets.
The core principle that structure follows strategy is immediately visible in
our operations. At Ubombo sugar mill, the strategy is almost always cost
minimisation rather than high-end innovation; we succeed by being
the most efficient producer of high-volume sugar. Consequently, our
structure is designed for tight cost controls and to avoid unnecessary
expenses. This explains why our engineering budget is so strictly formalised
—the structure is built to support an extreme-efficiency strategy.
The lecture highlights that routine tasks, those that are automated and
standardised, are typically associated with taller, more departmentalised
structures. A sugar mill is the definition of routine technology: the process of
crushing, boiling, and centrifugal separation is a continuous, standardised
flow. This necessitates a bureaucratic organisation characterised by
highly routine operating tasks, formalised rules, and a clear chain of
command.
Early in my training as a manager, I found the strict adherence to "Standard
Operating Procedures" (SOPs) and the rigid hierarchy frustrating. However,
the lecture clarifies that in a high-complexity, routine environment, this
formalisation ensures safety and quality. In a factory where a single valve
error can cause a catastrophic explosion, decision-making must follow the
chain of command to ensure accountability and specialised expertise.
One of the most practical insights for my career is the challenge of
departmentalisation. We operate under a functional structure that separates
Engineering, Production, and Laboratory functions. While this allows for deep
technical specialisation, I have experienced the silos that the prof mentioned
firsthand. For instance, the engineering team may focus on a long-term
maintenance project (optimising our assets), while the production team
focuses solely on immediate throughput (meeting the daily "crush"). Often,
these departmental objectives create conflicts within the departments.
Henry Mintzberg’s warning that reporting lines are less important than
business processes is a vital lesson for me. To be an effective manager, I
cannot stay within the "Engineering" box on the org chart; I must understand
the end-to-end business process for sugar production to reduce the ‘us and
them’ mentality that often leads to blaming cultures between shifts.
As I move into more senior roles, I will face the paradox of centralization vs
decentralization. In a mill, we often struggle with this: should a shift
supervisor have the autonomy to shut down a mill if they sense a mechanical
issue (decentralised), or must they wait for the Factory Manager’s approval
(centralised)? The lecture taught me that there is no single right answer and
that these decisions are interdependent. The fear of "getting stuck" at one
extreme sets up failure; instead, I must learn to manage the tension between
the need for corporate control and the need for operational agility on the
factory floor.
For an engineer, it is easy to become "mesmerised with management" and
org charts rather than focusing on how work gets done. These lectures have
taught me that my career will not just be about fixing machines; it will be
about designing and navigating the human systems that allow those
machines to run. Moving forward, I will be more conscious of the
environmental forces, like market volatility or technology changes, that
influence our mill's structure, ensuring that as I grow, I help the organisation
adapt rather than just "rearranging the deck chairs"