You read the question once. Then again. Then a third time, hoping it’ll suddenly make sense.
“Critically evaluate the role of organisational culture in facilitating strategic change.” Cool. Which part? All of it? Forever?
If your brain just tried to cram an entire semester’s worth of theory into one panicked paragraph, you’re not alone and you’re also not actually being asked to do that. A broad question isn’t a demand to know everything. It’s a test of whether you can figure out what actually matters and ignore the rest. That’s the whole game.
Here’s how to play it properly.
Step 1: Read the Question Like a Detective, Not a Student
Before you touch a single source, slow down and interrogate the question itself.
Words like analyse, evaluate, assess, and critically discuss aren’t filler they’re instructions. “Describe” wants a summary. “Evaluate” wants a verdict, backed by evidence. Mixing these up is one of the most common (and most avoidable) ways marks quietly disappear.
Try this: underline the subject, the specific issue, any named organisation, and the command word. Then translate the whole thing into plain English, like you’re explaining it to a mate.
So “critically evaluate the role of organisational culture in facilitating strategic change” becomes: does culture actually help or block change, and what real evidence proves it either way?
Suddenly it’s not a topic. It’s a question you can answer.
Step 2: Don’t Research Until You Know What You’re Looking For
Here’s the trap: you open Google Scholar “just to get a feel for things,” and ninety minutes later you have 30 tabs open, three theories you’d forgotten existed, and no clearer idea of what you’re arguing.
Good research follows the question it doesn’t wander off looking for one. Before saving anything, run it through a quick check: is this source giving me evidence, defining a term, or offering a counterargument? Does it actually help answer my translated question, or is it just interesting? If you can’t answer that, you’re not researching you’re collecting.
Step 3: Pick Theories Like Teammates, Not Trading Cards
There’s a myth that more theories equals more marks. It’s not true, and it usually backfires. Two or three frameworks that genuinely interact will beat seven name-dropped ones every time.
Say you’re exploring employee resistance during a merger. You probably don’t need every change model ever written maybe just one to explain how leadership handled the rollout, and one to explain why staff felt dissatisfied. That’s a paper. The rest is padding. If you’re after genuine management assignment help rather than a longer reading list, this is usually the fix: fewer theories, used properly.
No theory explains everything, either. Pointing out where a model fits your evidence and where it falls short reads as real critical thinking, not just recited theory.
Step 4: Build the Argument Before You Build the Word Count
Sketch your argument in rough notes before writing full paragraphs. It doesn’t need to look impressive, just exist.
If the question asks why a change effort failed, don’t organise around textbook headings organise around competing explanations. Did leadership fail to communicate the vision? Did entrenched culture quietly resist the new process? Were staff just burnt out from workload and uncertainty? That’s something to actually investigate, not just describe.
Step 5: Catch Yourself Before Description Quietly Takes Over
This is where most marks are lost, and it’s subtle. Compare these two lines:
Descriptive: “Transformational leadership focuses on inspiring followers through vision and communication (Bass, 1985).”
Analytical: “Bass’s model explains how vision can inspire change but applied here, that inspiration alone didn’t address the workload issues driving staff burnout, which is a gap the theory doesn’t account for.”
The first line is accurate and completely safe. The second line actually does something it tests the theory against evidence, finds where it holds and where it doesn’t, and pushes your argument forward. That gap between the two is where descriptive writing turns into analysis, and it’s the single biggest quality jump you can make in a single edit pass.
The Unique Bit: Run the 60/40 Check
Here’s a habit that changes how a draft reads almost instantly. For every paragraph, ask two things:
- The Delete Test – if I cut this paragraph entirely, does my argument get weaker? If not, it’s not earning its place.
- The 60/40 Split – roughly 60% of the paragraph should be analysis and application; no more than 40% should be theory setup or definition.
Most weak assignments fail this quietly. They’re 80% theory, 20% “so what.” Flip that ratio and the same content suddenly reads as sharper, more confident, more yours.
One Last Read-Through Before You Submit
Go back to your original translated question not the version you ended up answering somewhere around paragraph six. Read your conclusion straight after it. Does it answer that exact question, or the easier one you gradually drifted toward while researching?
Check the balance too. Too much theory and it reads like a literature review. Too much company description and it reads like a business report. Neither is what’s being marked.
The Real Takeaway
A broad question stops being scary the moment you stop trying to cover everything and start deciding what genuinely matters. Narrow the question. Pick theories that earn their place. Keep pushing past description into what the evidence actually means.
Five theories and fifteen references won’t save an assignment with no argument. One clear argument, tested honestly against the evidence, will carry you further than either ever could.