VCE Business Management common mistakes
VCE Business Management · Understand the traps and how to avoid them.
Defining a sole trader, partnership or company only by restating the term ("a sole trader is a business owned by one person") without naming the legal features the question rewards: unlimited versus limited liability, separate legal entity, continuity of existence, and number of owners.
Students memorise a one-line label per structure and stop there, because that is enough to recognise the word in a multiple-choice stem; they never build the feature comparison that extended-response markers use as a checklist.
What to do instead
Build a four-column comparison table (liability, separate legal entity, continuity, owners) for sole trader, partnership, private company and public company, and practise answering structure questions by explicitly naming at least three features and applying each to the scenario business rather than listing them in the abstract.
Describing the difference between a private and a public company only as "private is smaller" or "public is listed", instead of explaining proprietary versus public status, share offers to the general public, ASX listing and disclosure obligations.
Everyday usage of 'private' and 'public' pulls answers toward size and ownership stereotypes, and students rarely rehearse the legal distinctions because they seem like trivia rather than analysis.
What to do instead
Write a one-sentence definition of each type that contains the words 'proprietary', 'limited', 'share offer to the public' and 'ASX', then answer two practice questions where you must justify which type suits a stated expansion plan.
Naming a management style (autocratic, persuasive, consultative, participative, laissez-faire) without describing the decision-making behaviour that defines it, or mislabelling a scenario because the manager 'asked for opinions' once.
Style names are short and memorable, so students answer with the label and assume the marker will infer the meaning; scenario questions then punish them because the label alone earns no application marks.
What to do instead
For each style, memorise one sentence beginning 'The manager decides...' plus who is consulted and how communication flows; then practise classifying short scenarios by asking who actually makes the final decision and how much input employees had.
Treating the operations system as a list of three separate stages (inputs, processes, outputs) rather than showing how they connect, and omitting the specific input types (materials, capital equipment, labour, information, time) in the case.
Textbook diagrams show the stages side by side, so students reproduce the diagram in words and never demonstrate the flow of value or the transformation that the question is testing.
What to do instead
Practise writing one paragraph that follows a single product through all three stages using the case business, naming at least three input types and stating what changes at each stage; check that every sentence links one stage to the next.
Confusing efficiency with effectiveness, or using them interchangeably, when asked to evaluate an operations decision.
Both words appear in the same study design section and both sound positive, so students default to whichever comes first to mind rather than to the distinct ideas of resource use versus goal achievement.
What to do instead
Adopt a fixed test: efficiency is about resources used per unit of output (waste, cost, time); effectiveness is about how well the output meets the objective or customer need. Apply the test to three practice scenarios and write one sentence on each concept for the same business.
Describing technological or operational change as 'it makes things faster and better' without naming the specific strategy (automation, computer-aided design, computer-aided manufacturing, lean production, quality management) or its effect on the business's operations.
Students know the change happened but not the vocabulary for it, so they generalise; the generalisation feels safe but earns no marks because it cannot be tied to the case.
What to do instead
Keep a glossary of change strategies, each with a definition, one benefit and one limitation, and practise answering by naming the strategy first, then explaining its effect on a named input, process or output in the case.
Answering a 'discuss' or 'evaluate' question with a single-sided list of benefits and no weighing, so the response never reaches the higher mark bands.
Students equate length with quality and add more points on the same side rather than adding the counter-argument and a judgement, because they have not been taught what the command word demands.
What to do instead
Use a fixed skeleton for evaluative questions: two benefits, two costs or limitations, then a concluding sentence that states a position and the condition under which it holds ('this is likely to succeed provided that...'). Rehearse it on past-style questions until it becomes automatic.
Writing generic answers that could apply to any business, with no use of the case facts, names, figures or industry context provided in the question.
Under time pressure students reach for memorised content because it feels efficient, and they assume mentioning the business name once counts as application.
What to do instead
Before writing, underline three case facts and force each body paragraph to include at least one of them; finish by checking that swapping in a different business name would make the answer wrong, which proves genuine application.
Explaining the motivation for transformation (globalisation, technology, innovation, change in markets) without linking it to a specific driving force or to the effect on the business's operations and objectives.
These drivers are abstract and overlap, so students list them as a set and move on rather than tracing a causal chain from driver to business response.
What to do instead
Practise writing causal chains of the form 'driver, therefore pressure on the business, therefore response, therefore effect on an objective', using a different driver each time, and check that each link names something concrete.
Describing change management as 'communicating with staff' without naming a recognised approach (for example the low-risk, high-risk or Lewin-style approaches) or explaining how it reduces resistance.
Communication is the most familiar idea and students stop at the first plausible answer; they have not practised distinguishing the approaches or explaining the mechanism by which each reduces resistance.
What to do instead
For each approach, write one line on when it suits a business and one line on how it lowers resistance, then answer a scenario question that requires choosing an approach and justifying it against a named source of resistance such as fear of job loss.