University College London · FACULTY OF MANAGEMENT

GBSH0049 Chap.1 Organisations and Systems

- one subject, every graph, every model, every mark
6 Chapters4-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 1 of 10 · GBSH0049

Organisations and Systems

Organisations and Systems introduces the module's basic unit of analysis: people coordinating work toward a common purpose. The chapter compares functional structures, open systems and networks because each reveals a different part of managerial reality. Functions show specialised responsibility, systems show exchanges with the environment, and networks show dependencies that formal reporting lines can hide.

The practical skill is boundary choice. A diagnosis must include enough actors, information and workflow to contain the likely cause without becoming so broad that no decision remains possible. Purpose then provides the comparison point for evaluating whether local activity creates wider value or merely shifts cost and work elsewhere.

In this chapter

What this chapter covers

  • 01

    Common purpose and coordinated work

  • 02

    Functional structures and specialised roles

  • 03

    Open-system inputs, outputs and feedback

  • 04

    Networks and organisational dependencies

  • 05

    Boundary choice for managerial diagnosis

  • 06

    Symptoms, causes and system consequences

Worked example · free

Diagnose an incomplete appointment pathway

Q [6 marks]. A clinic adds online triage, but incomplete requests and duplicate phone work increase. Explain the organisational mechanism and recommend a first test. The marks shown here are not an official university marking scheme.
The open-system loop shows resources entering coordinated organisational work, producing outcomes, and returning evidence that changes later choices.The open-system loop shows resources entering coordinated organisational work, producing outcomes, and returning evidence that changes later choices.Inputspeople, evidenceOrganisationcoordinationOutputscare, valuefeedback changes the next cycle
The open-system loop shows resources entering coordinated organisational work, producing outcomes, and returning evidence that changes later choices.
  • 1Set the boundary around patients, intake, administration and clinical review.
  • 2Identify the broken handoff: a digital-only assumption creates incomplete information and rework.
  • 2Recommend assisted intake and track completion, repeat contact and allocation time.
  • 1State that the practice marks are an original learning aid, not a published UCL allocation.
The problem is not technology use alone but a workflow that assumes access and complete data. A supported route and linked measures test whether the redesigned handoff reduces rework without excluding patients.
Sia tip — Draw the smallest system that still contains the likely cause.
Glossary

Key terms

Organisation
A coordinated collection of people working toward a common purpose.
Open system
An organisation understood through its exchanges with an environment.
Boundary
The chosen limit of actors and processes included in an analysis.
FAQ

Organisations and Systems FAQ

Why use several views of an organisation?

A structure chart clarifies formal responsibility, an open-system view reveals environmental exchanges, and a network view exposes interdependence. Managers choose the view that explains the focal decision instead of assuming one picture can answer every organisational question.

How do I choose an analytic boundary?

Include the actors, information and dependencies needed to explain the problem and support a decision. State what remains outside. If the likely cause sits beyond the line, widen it; if every social condition enters, narrow it.

What turns a system map into analysis?

Arrows must express testable relationships, such as a missing handoff producing rework or a measure changing behaviour. The map should generate competing explanations and direct evidence collection rather than serve as a decorative summary.

How should I test an organisational explanation?

Write at least one rival mechanism and identify evidence that would support or weaken each account. Compare intended work in policy, recorded work in process data and enacted work in observation or stakeholder experience. Keep the claim at the correct level, because one person's mistake does not establish a team norm and one department does not automatically represent the whole system.

Choose a reversible first response when uncertainty remains, state the safeguard for possible harm and schedule a review that can change the original map. This method shows that the recommendation is a testable managerial judgement rather than a diagram converted into certainty.

Study strategy

Assessment move

Rebuild one organisational problem in three ways. First draw the functional structure and mark formal accountability. Next draw inputs, transformation, outputs and feedback. Finally show the network of information and resource dependencies. Compare what each view reveals and conceals. Practise writing a causal chain with an observed condition, a coordination mechanism and an outcome.

Challenge every symptom label by asking what process could create it and what evidence would distinguish that explanation from an alternative. For coursework, keep the boundary explicit and revisit purpose at the conclusion. Check whether a local improvement shifts burden to patients, another department or a partner.

End practice answers with the next piece of evidence required, because responsible managerial diagnosis remains open to revision when the system behaves differently from the model. Build a weekly evidence exercise around one ordinary event, such as a delayed decision, repeated data entry or a meeting that fails to settle responsibility. Write the factual observation without explanation first.

Generate three mechanisms involving structure, information and incentives. For each mechanism, identify an observation, record or stakeholder account that could support it and one that could weaken it. This prevents the first plausible story from becoming the conclusion. Redraw the boundary twice, once too narrowly and once too broadly. Explain what the narrow map misses and what the broad map makes impossible to manage.

The useful version should contain the decision, relevant dependencies and affected outcomes. Practise moving between levels without mixing them. An individual mistake is not automatically a team norm, and a department pattern is not automatically a whole-system property. State the level of every claim. When reading cases, highlight policy as intended work, process records as recorded work and observation as enacted work.

Differences among them often reveal the management problem. Add one counterfactual pathway: what would happen if the organisation did nothing or used a different boundary? Compare the likely information and coordination effects. Finish by writing a reversible first action, a safeguard and a review condition. Explain how the result would update the original map.

This habit keeps system thinking practical because the map directs evidence, evidence supports a proportionate response, and the response tests whether the map was accurate.

Working through Organisations and Systems in GBSH0049? Sia is AskSia’s AI Management tutor — ask any GBSH0049 Organisations and Systems question and get a clear, step-by-step explanation grounded in how GBSH0049 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 32 of your subjects at University College London, plus 1,000+ more Bibles across the AskSia library.
Sia - your GBSH0049 tutor, unlimited, worked the way the exam marks it
The full 4-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works