Business models, operations and the decisions behind them.

A Matrix Organisation Needs Clear Decisions Alongside Its Reporting Lines

Three colleagues discussing a simple organisational chart with intersecting reporting lines on a whiteboard.
AI-generated photographic illustration; not documentary photography.

An employee belongs to the finance function but works on a product team’s project. Two managers appear on the organisation chart. The diagram may describe a matrix arrangement, but it does not by itself explain what happens when both managers need the same person’s time.

Atlassian’s guide to organisational charts describes matrix structures and different reporting relationships. The useful next step is to connect those lines to actual decision responsibilities.

Ask what each line means in practice

Who sets professional standards? Who assigns day-to-day project work? Who approves leave, reviews performance or agrees a change in priorities? Organisations distribute these responsibilities differently, so the words solid line and dotted line should be explained locally.

Consider a fictional analyst supporting a product launch while also preparing a monthly finance report. The product lead owns the launch deadline; the functional manager owns reporting quality and capacity. If both tasks become urgent, the analyst needs an agreed escalation route rather than being expected to satisfy incompatible instructions silently.

Make conflicts visible early

A shared view of commitments can reveal when a person is allocated beyond their available time. Record the work, deadline and responsible decision-maker. This is more useful than asking the employee to negotiate every clash informally with whoever speaks most forcefully.

Separate consultation from approval. Several managers may need to contribute expertise, but that does not necessarily mean all of them have the same authority to approve a decision. Unclear approval rights can turn a matrix into repeated rounds of permission seeking.

When studying a company, use the chart as a starting map. Ask for one real workflow and follow how a decision travels through it. A chart that looks complicated may work well if responsibilities are clear; a tidy chart may conceal confusion.

The structure is not automatically better or worse than a single reporting hierarchy. Its effectiveness depends on how the organisation coordinates priorities, authority and accountability. The most informative question is often simple: when the two lines disagree, who helps resolve the conflict and how quickly?