A design studio has no conventional team managers. Project groups form around client work, members discuss priorities together, and experienced designers contribute advice across the studio. Employees value the access to one another and the opportunity to shape their work.
A new recruit nevertheless finds that some proposals advance much more easily than others. One colleague maintains the project allocation board. Another has long relationships with the founders and knows which commitments are flexible. A third is routinely asked whether a design is ready for the client. These responsibilities affect decisions even though they are not reporting relationships.
There is nothing inherently wrong with that influence. Expertise and trusted relationships help organisations function. The difficulty arises when people cannot tell which advice is optional, which decisions are binding, or how to question an arrangement that affects them. A flat organisation needs an understandable account of authority just as a more layered one does.
Flatness Describes Only Part of the Structure
The word flat can describe fewer management layers, wide reporting spans, self-managing teams, or an ambition to distribute participation. These arrangements are not interchangeable. A company might remove a reporting layer while retaining central control of spending. Another might delegate substantial decisions to teams while keeping formal people-management roles.
Start by specifying what the studio has actually changed. Who can commit money, accept client work, determine project membership, and address an employment concern? Which choices belong to the whole group? These questions reveal more about the working structure than the absence of boxes on a chart.
Jo Freeman’s The Tyranny of Structurelessness examined informal power in women’s liberation groups. She argued for explicit, accountable delegation rather than assuming that rejecting formal structure removed influence. Her essay is relevant to the problem of unacknowledged authority, but its movement context is not evidence that all flat companies develop the same problems or should adopt a conventional hierarchy.
A useful lesson is to investigate the structure people actually use. In the studio, the allocation board, client relationships, and design review practices already organise work. Making them explicit can preserve distributed working while reducing the need for newcomers to discover the rules through private conversations.
Separate Expertise From Permission to Decide
The experienced designer may know why a client previously rejected an approach. Their advice deserves attention because it contains relevant knowledge. That does not automatically mean they should approve every design, control staffing, or determine another employee’s development opportunities.
Clarify the scope of the responsibility. A project might designate a design lead to decide whether work meets the agreed brief, while a separate person agrees changes to the client commitment. The design lead should explain the criteria and make relevant evidence available. Team members can then distinguish professional judgement from a preference they are free to discuss.
Authority can also be collective. The studio might reserve major expenditure for a group decision and delegate ordinary project expenses within a budget. The important details include who participates, how a decision closes, and what happens when someone is absent. A group label alone does not make authority clear.
Some decisions remain constrained by professional, contractual, or organisational obligations. A project group cannot make those constraints disappear through consensus. It needs access to the relevant advice and an established route for resolving uncertain interpretations. Local discretion becomes more useful when people can identify the boundaries within which it applies.
The article on decision rights examines how this specificity can support action without giving one person unlimited control.
Examine Control of Access and Coordination
Maintaining the allocation board might look administrative, but it can affect which projects receive attention and who gets desirable work. That influence may be entirely legitimate. The person maintaining it might simply implement choices made openly by the studio. Alternatively, important prioritisation decisions may be occurring through edits that nobody else understands.
Trace a few allocations. Who proposed them, what constraints were considered, and where could someone raise a concern? Check whether the board records a decision or silently makes it. The remedy depends on the answer: clearer recording may suffice in one case, while another needs an explicit allocation mandate and review route.
Meeting facilitation has similar limits. A facilitator can help participants hear evidence and reach a decision without possessing authority to choose the result. If the role includes deciding which proposals receive discussion, state the criteria. Invite a way to raise omitted issues rather than relying on the facilitator to anticipate everything.
Information access also matters. A founder’s regular contact may know a client deadline that others do not. Record information that materially affects shared commitments, subject to appropriate confidentiality. Equal access to every conversation is neither realistic nor necessary, but participants need enough context to understand decisions that affect their work.
Make Disagreement and Sensitive Concerns Addressable
Consensus can be valuable where a decision requires sustained cooperation. It can also leave people uncertain about whether an objection needs to be resolved, acknowledged, or accepted as a reason not to proceed. Define the rule before a consequential disagreement rather than choosing it to favour the preferred answer.
The studio could seek a shared recommendation and then use a designated decision-maker for unresolved questions within the project mandate. It could reserve specified choices for a collective vote or another agreed procedure. Different methods have different consequences. There is no need to describe every compromise as consensus when some participants remain unconvinced.
People also need a route for concerns they cannot safely resolve in the group. A dispute about allocation, a complaint about influential behaviour, and a confidential employment issue require different handling. Identify appropriate responsibilities, confidentiality boundaries, and an alternative when the usual contact is implicated. Calling everyone peers does not provide that arrangement.
Formal roles alone do not guarantee fairness or a meaningful appeal. A conventional manager can be difficult to challenge too. The test is whether people can understand the decision, obtain a response, and use an appropriate review route in practice. Ask newer and less connected members about their experience, since established employees may find an informal arrangement easy to navigate.
Reserved powers also need acknowledgement. The studio’s founders may retain decisions about investment, ownership, or entering a new market while inviting broad participation in project work. That can be a coherent arrangement. Presenting every decision as collective when a founder can ultimately override it makes participation harder to interpret.
State which matters are delegated and which remain reserved. If an override is used, explain its effect on existing commitments and the reason that can appropriately be shared. People should be able to distinguish advice that informed a decision from authority to make it. Participation does not require everyone to hold the same powers, but it does require an honest account of the powers they do hold.
A practical onboarding check can expose ambiguity. Ask a newer employee how they would propose a project, challenge an allocation, or obtain help with a concern. Compare the route they describe with the intended arrangement. If success depends on knowing whom to approach privately, investigate what the published route lacks. The aim is to make useful access repeatable rather than depend on a newcomer quickly acquiring influential relationships.
Revisit delegated mandates periodically with the people affected. A coordinator might be making sensible decisions under an agreement that nobody remembers accepting. Restating the scope, hearing concerns, and confirming or changing the appointment gives the responsibility a current basis without requiring every operational choice to return to the whole studio.
Distribute the Work Without Hiding Its Cost
Coordination roles can rotate, remain specialist responsibilities, or be divided among several people. Choose according to the work. Rotating a meeting chair may spread participation. Rotating a sensitive support responsibility too quickly may undermine continuity and require repeated training.
Allow time for the responsibility and recognise it in workload discussions. A designer maintaining project allocations should not have to do that work invisibly on top of an unchanged client workload. Conversely, a useful coordination role need not become a permanent full-time management position merely because its contribution is acknowledged.
Build continuity where important knowledge sits with one person. A second member could learn how to maintain the allocation record, and decisions could retain enough rationale for someone else to interpret them. This reduces dependence without pretending that expertise can be transferred instantly through documentation.
There is no universal headcount at which this design stops working. Coordination demands depend on interdependence, distribution, turnover, the nature of the work, and the information available. Growth may expose limitations, but a small studio can also have opaque power. A larger organisation can maintain substantial local autonomy through explicit structures.
Review the arrangement when the work changes or people struggle to use it. If newcomers repeatedly need private permission to access opportunities, investigate the actual route. If shared decisions take too long, examine the mandate, information, and decision method before adding another layer. The companion article on removing management layers considers the wider accounting of responsibilities and effort.
The studio can retain fewer layers and a participatory culture while acknowledging that some roles carry particular authority. Making those responsibilities visible gives people a basis for contribution, challenge, and review. It also allows the organisation to preserve useful influence without treating familiarity, confidence, or access as an unexplained right to decide.





