His name was Jørn Utzon, and in January 1957 he was a 38-year-old Danish architect with few completed buildings. That month, in Sydney, it was announced that his design had won the international competition for the city’s new opera house, out of 233 entries from 32 countries. A peninsula in the harbor, a stone platform and, on top of it, white shells that nobody yet quite knew how to build.
Construction began in 1959. For the next few years, Utzon ran the project and decided what got built, from the foundations to the shells.
In 1965 the state government changed. The new Minister for Public Works, Davis Hughes, began to question Utzon’s competence, his drawings, his schedules and his cost estimates. He refused to pay the project’s running costs and withheld funds to the point where the architect could not pay his own team. Utzon wanted to deal directly with the suppliers he had chosen for the interiors, such as the plywood manufacturer Ralph Symonds. The government demanded tenders.
On February 28, 1966, Utzon left the project. The main structure was done. The interiors were still to come.
In March, the minister offered him a role as “design architect,” reporting to a panel of executive architects and with no power to supervise construction. Utzon said no.
The interiors went to another architect, Peter Hall, appointed that April. The opera house opened on October 20, 1973, ten years later than planned, inaugurated by Queen Elizabeth II. Utzon was invited and chose not to go. He died in 2008 without ever returning to Australia to see the finished building.
The Role They Offered Him
The most useful detail in this story is the role the minister offered him. “Design architect.” His name would stay attached to the building, the authorship would remain intact, the title even sounded good. What changed was who decided: the money, the suppliers, the schedule, the sign-off on every step. All of that moved somewhere else.
Utzon read the offer for what it was. He would be responsible for a building over which he no longer had the final say.
Responsibility and authority almost always travel together, which makes it easy to forget they are two separate things. Responsibility says who answers for the outcome. Authority says who decides how to get there. As long as they sit with the same person or the same team, nobody needs to tell them apart. When they come apart, whoever kept only the first is usually the last to notice.
Components Have Owners Too
In an earlier piece, “The Design System as a Decision-Making System, Not a Visual Prison,” I argued that a design system exists mainly to make decisions: it stores choices already made so every team can reuse them without making them again. One question was left out, and it now feels unavoidable. If the system is a decision machine, who decides about the machine itself?
In most organizations, the formal answer is simple. The design system team owns the components, the patterns, the documentation. It maintains them, fixes them, and answers when something breaks in a product. Its name is on the system, the way Utzon’s stayed on the building.
The thing is, a design system is shaped by rules that rarely originate inside it. Brand decides the palette and the tone. Product decides priorities and deadlines. Engineering decides what is feasible and when. A new leadership role can decide that every team will now follow a set of cross-cutting principles. Each of these decisions is legitimate. Added together, they can shift authority over the system without anyone announcing it.
The team still owns the components. The rules about how those components should evolve, though, are now being written in another room.
How You Lose the Final Say Without Losing the Title
The Sydney story shows three paths authority can leave by, and none of them requires taking anyone’s title away.
The first is money and time. Hughes questioned the drawings, but the tool he used was the budget: he decided what got paid for and when. In a design system, the equivalent is the roadmap. Whoever decides what capacity exists, and for what, decides in practice what the system will be a year from now.
The second is process. The government required tenders for suppliers, a process rule, and with it took away the architect’s choice of who would build the interiors. In a system, contribution rules, acceptance criteria, who approves a new variant and who can grant an exception are process rules with the same effect. Whoever writes them decides more than it seems.
The third is hierarchy. The “design architect” offer placed Utzon below a panel. He would keep designing, and every drawing would go through whoever held the power of supervision. In many design system teams this happens quietly: proposals still come out of the team, but they now get validated by a function that didn’t exist before, or that didn’t have that say.
Each of these paths can have good reasons behind it, and the damage almost always comes from them opening without anyone saying so. The team is still held accountable as the owner, answering for inconsistencies, delays and adoption, and discovers at the first conflict that the decision it needed already belonged to someone else.
The cost shows up first in people. A team held accountable for decisions it can no longer make wears out fast, and starts defending the system against everyone, which only confirms, in the eyes of those who decide, that it’s better to decide without it.
A Separation That Can Work
Cricket has an interesting solution to this. The Laws of the game have belonged since 1788 to the Marylebone Cricket Club, a private club that holds the copyright and remains the only body that can change them. Governance of world cricket, however, passed to the International Cricket Council, which sets the “playing conditions” for international matches, and those conditions can differ from the Laws. The club owns the code. The ICC decides how it applies where it matters most. And the arrangement holds because the separation is written down and each side knows where its say ends.
Negotiate Before You Need To
Separating responsibility and authority can be healthy, as long as the separation is spoken and written down. The right time to write it is before the conflict, because after it every conversation about who decides gets colored by the specific decision that triggered it.
In 2015, Nathan Curtis described three team models for scaling a design system: solitary, where one team builds the system mainly for its own needs; centralized, where a dedicated team runs it for the whole organization; and federated, where several teams contribute to it and maintain it together. The models say who does the work. When the organization changes, they are missing a layer: who decides about which part of the system.
A practical way to build that layer is a simple decision rights map, drawn up with whoever starts setting cross-cutting rules, every time the organization changes. Four questions are enough to start:
- Which decisions about the system belong to the team that maintains it, with no one else’s approval?
- Which decisions require consultation, and with whom?
- Which rules come from outside and enter the system as constraints?
- When two outside rules contradict each other, who breaks the tie?
The last one is the one usually missing. Brand and product can both be right about a component and ask for incompatible things. If nobody knows who breaks the tie, it gets broken by whoever speaks loudest or last, and the system team is left responsible for the outcome of a decision it didn’t make.
There’s a reason this conversation rarely happens in time: while owner and decision-maker are the same, nobody misses it. In an organization that keeps changing, that overlap rarely lasts, and it’s worth treating it as temporary.
What Utzon Left in Writing
The Sydney story has a second act, and it holds the most useful clue.
In 1999, more than thirty years after he left, Utzon was appointed design consultant by the Sydney Opera House Trust. He would never return to Australia. What he did, from Mallorca, with his son Jan and the architect Richard Johnson, was write. In May 2002 a document called the Utzon Design Principles was completed. It walks through the building and explains the principles behind the decisions that produced it. The document states its own purpose: to be a permanent reference, to guide any proposed change, and to clarify the original design intent. From then on, every proposal would be assessed by its impact on those principles.
In a letter to the Trust’s chairman in August 2000, reproduced in the document, Utzon wrote:
“As time passes and needs change, it is natural to modify the building to suit the needs and technique of the day. The changes, however, should be such that the original character of the building is maintained.”
Utzon lost his authority in 1966 for good. More than thirty years later, he found another form of influence: making his criteria explicit, so that whoever came after could decide with them. He accepted change and wrote down its conditions.
For a design system team, the lesson has two parts. The first is to negotiate decision rights before you need to. The second is to write the system’s principles in a way that outlasts whoever decides. Documenting a component with the reasons behind its decisions forces anyone who wants to change it to argue with those reasons. It’s a form of authority that survives changes to the org chart.
Whoever loses the final say over a system can keep influencing it, if they left its reasons in writing.
The Room That Bears His Name
In 2004 the first room in the building rebuilt to a Utzon design opened, and it was named after him: the Utzon Room. In 2007 the Sydney Opera House was added to the UNESCO World Heritage List. Utzon died on November 29, 2008, without having seen any of it with his own eyes.
His name was always on the building. He lost the final say over it in February 1966, and only got it back, in part, when he put it in writing.
Anyone who owns a design system would do well to ask, today and calmly, who has the final say over it. And, whatever the answer, to leave the system’s reasons in writing, so whoever comes to decide later can read them.
Sources
- Sydney Opera House. Wikipedia
- Jørn Utzon. Wikipedia
- Pritzker Prize, Jørn Utzon, 2003 Laureate, Biography. pritzkerprize.com
- Utzon Design Principles, Sydney Opera House, May 2002. sydneyoperahouse.com
- Laws of Cricket. Wikipedia
- Nathan Curtis, Team Models for Scaling a Design System, September 17, 2015. centercentre.com
- Bruno Mota, The Design System as a Decision-Making System, Not a Visual Prison, May 2026. uxdesignmanager.com
