Question 3 (a)
Matrix organisation: meaning, where it suits, merits and demerits
8 marks
- Time to write
- About 16 minutes
From an older CBCS paper
Question
Question 3 (a) · 8 marksWhat is Matrix Organization ? For what types of organization is it suitable ? Explain its merits and demerits.
Reworded from the university paper; the task is the same. The original paper belongs to the University of Delhi. See DU's question bank.
Before you write
Read off the question and its marks
Read from the question
- What…?Explain…3 questions in all: answer every one.
Write it in this order
- Read; underline the asks; jot your points 1 min
- 1 Meaning and features of a matrix organisation 2 marks 4 min
- 2 Organisations for which it is suitable 1½ marks 3 min
- 3 Merits 2 marks 3 min
- 4 Demerits 2 marks 3 min
- 5 Conclusion ½ mark 1 min
- Check: every ask answered, key terms underlined 1 min
Easy marks
- Step 1 opens with the meaning: a one-line definition, the quickest mark in it.
Short on time? Trim steps 1–4 evenly rather than skip one: each is capped at its own marks. End with step 5 in a line or two.
Try it first. About 16 minutes for 8 marks. Write it out, then open the solution.
Solution
Hover or tap a marked figure, like 72,000, to see how it is made and where else it appears.
A matrix organisation, also called a grid organisation, lays a project structure on top of the permanent functional structure of an enterprise. The functional departments stay in place and keep authority over the running of their units; they form the vertical lines of command. Project teams, set up when a particular project needs a high degree of technical skill for a limited period, form the horizontal lines. Where the two cross, a grid is formed.
1Drawn from every department, the project team huddles over one drawing.
Project organisationThe team answers to the project manager rather than to the functional heads.
2Ajay at his desk, a file arriving from each side: the project boss and the department boss.
Matrix organisationThey therefore have two bosses.
Its working features follow from this design:
- It is built around a specific project, and the project manager has authority to finish it within the time and cost limits set by top management.
- Its staff are drawn from the functional departments and go back to them for reassignment when the project ends.
- The two kinds of manager play different roles: the project manager takes a general management view of the project, while each functional manager protects the standards of his own function.
- Each member of a project team therefore has two bosses, the functional head and the project head, and the extent of each one's authority has to be marked out clearly.
It is not the same as a pure project organisation. There the project manager has full authority over the project's resources; in a matrix he shares them with the functional managers.
Organisations for which it is suitable
The matrix form was developed for large and complex undertakings that need a structure more flexible and more technically oriented than the line and staff or functional forms. It suits an organisation that:
- runs several projects at the same time, rather than one or two very large ones;
- needs specialists from different disciplines to work together on each project for a limited period, while their functional departments continue the regular work.
A Pune automobile-components maker developing an electric-vehicle motor is an example. Design, production, purchase and finance staff join one project team under a project manager for the development period, and still report to their own department heads.
- Flexibility. More projects can be taken up simply by forming more project teams, as the environment and the organisation's needs demand.
- Development of skills. People learn new skills by working on many projects, so the matrix serves as a training ground for a range of professional abilities.
- Attention to each project. Each project gets its own attention and resources, which makes planning and control easier and helps it finish on time.
- Motivation, communication and coordination. Team members are motivated because they work directly towards one project's completion; direct contact improves communication across ranks; and the project manager integrates people from different disciplines, which reduces coordination problems.
- Conflict within the team. Members come temporarily from different departments and may clash, and the project manager has no line authority over them, so coordination and control suffer.
- Dual command. Its most serious weakness: a team member is never sure whose order, the functional head's or the project head's, to obey first, so unity of command is broken.
- No clear hierarchy. Project and functional managers do not stand in a scalar relationship, so working relationships are unclear.
- Higher cost and paper work. Communication flows both vertically and horizontally all the time; paper work grows, and conflicting instructions make projects slower and costlier.
- Difficult appraisal. When staff move from project to project, functional heads find it hard to judge their performance, and some staff find it hard to adjust to each new project.
- Complex relationships. Informal relationships operate alongside the formal ones and make coordination harder.
The matrix organisation trades the simplicity of a single line of command for flexibility and expertise. It suits large, technically demanding enterprises that run several projects at once, provided the authority of the functional and the project heads is clearly divided.
Where the 8 marks sit
| # | Component | Marks |
|---|---|---|
| 1 | Meaning and features of a matrix organisation | 2 |
| 2 | Organisations for which it is suitable | 1.5 |
| 3 | Merits | 2 |
| 4 | Demerits | 2 |
| 5 | Conclusion | 0.5 |
| Total | 8 |
Report a problemopens an email to admin@getkunji.com with the question ID7765-Q3aalready filled in.