An engineering lead estimates that a release is feasible if a shared service becomes available and two features are deferred. The executive brief retains the delivery date but describes the dependency as manageable. After approval, the lead discovers that the features remain in scope and the shared-service team has not committed capacity.
The lead may have no right to set the commercial priority. They should still have a reliable way to get those conditions considered before the organisation commits, to understand the decision afterwards, and to raise a material change. More invitations to senior meetings would not necessarily provide that access.
Decision access means having an appropriate route into the information and deliberation that determine a choice, with a route back to the people acting on it. It differs from final authority. Good access can improve a decision without giving every contributor a veto, and a clear decision right can remain poorly informed if access is weak.
Identify Which Decision the Accountable Role Needs to Reach
Start with the outcome and trace a consequential choice. For the release, the issue is not simply whether engineering was consulted. It is whether the person assessing feasibility could communicate the assumptions attached to the estimate before approval.
List what the role needs at that point: relevant information, a way to submit evidence, an opportunity to correct a misunderstanding, and a clear escalation route for a material concern. The required form varies with the consequence and timing of the decision.
The lead may provide a written assessment and remain available for questions, while a designated representative attends the meeting. That can work if the representative preserves the conditions, can obtain clarification, and reports the outcome. Attendance alone does not establish any of those properties.
The authority-and-responsibility overview distinguishes decision permission from duties and answerability. Here, the narrower question is whether the information required to fulfil those duties can reach the relevant choice in time.
Preserve Conditions When Information Is Summarised
A decision brief must select information. Expecting senior reviewers to inspect every technical detail would overload the process and obscure what matters. The useful distinction is between omitting detail and removing a condition that changes the meaning of a recommendation.
For the release, the brief should identify that the date depends on a specific service commitment and reduced scope. It can link to the supporting assessment rather than reproduce the entire design. A reviewer should be able to distinguish an agreed fact, an estimate, an assumption, and an unresolved question.
Jensen and Meckling’s analysis of knowledge and organisational structure examines the challenge of bringing decision rights and relevant knowledge together when some information is costly to transfer. It is a conceptual account, not a rule that every decision must move to the most local expert.
Sometimes the better approach is to move authority closer to the information. Sometimes it is to improve the brief or create direct access to a specialist. A portfolio decision can legitimately remain elsewhere because it needs information spanning several teams.
Give the people supplying material evidence a way to check how it is represented. The engineering lead need not approve the commercial decision, but should be able to correct a statement that a dependency has been secured when it has not.
Design Discussion to Surface Information Others Do Not Hold
A meeting can include all the relevant roles and still fail to use their evidence. Familiar points may dominate discussion, while a fact held by one person remains unexamined or appears too detailed to raise.
Stasser and Titus’s research on pooling unshared information investigated this problem in a structured group-decision task. The study supports examining how information is introduced and discussed, rather than assuming that assembling informed people ensures their knowledge is combined. Its findings should not be treated as a diagnosis of every executive meeting.
For a practical review, ask which evidence could change the recommendation and who holds it. Obtain independent assessments before participants converge on a preferred answer where that is useful. During discussion, invite relevant differences rather than asking only whether everyone agrees.
Make factual disagreement visible. Engineering and a platform team may be using different definitions of readiness. The meeting needs to resolve that issue or record what remains uncertain before presenting a consolidated position.
Consultation should also have a consequence. If a concern is not accepted, explain the reason and the conditions under which it would be revisited. Being heard is different from getting one’s preferred option, but an unexplained dismissal gives the contributor little basis for implementing the decision appropriately.
Make Access Useful Before the Commitment Becomes Hard to Change
Information arriving after approval may explain a problem without preventing it. Set the review point according to the actions that follow, such as external communication, procurement, or allocating scarce capacity.
For the lead, submitting the dependency assessment after sales has promised the date creates a different problem from submitting it before the commitment. The process should identify when the estimate and its conditions must be available.
Late information can still matter. Establish who can pause, narrow, or reopen a commitment when a material fact changes. An approval should not turn every earlier assumption into an unchangeable fact.
Avoid fixed response deadlines unrelated to the work. A request affecting an imminent service change may need faster handling than a long-term investment question. The design should specify urgency and a destination able to respond, rather than relying on repeated informal chasing.
The authority-gaps article examines the exposure created while a needed decision remains unresolved. Timely information access and sufficient decision authority need to meet at the same point.
Protect Appropriate Challenge Without Requiring Unlimited Disclosure
Some decision material is confidential or restricted. Meaningful access does not require every participant to see all personal, commercial, or security information. It requires enough relevant information and an appropriate channel for the role to perform its part.
For the release, the engineering lead may need the scope, date, dependency commitment, and operating constraints without seeing every customer negotiation. Where information cannot be shared directly, identify who can examine it and explain the operational implication.
The organisation should also distinguish a challenge to the evidence from a refusal to accept any decision. The lead can identify an unsupported readiness claim without claiming authority over the entire investment. The decision-maker can choose a different course while recording which assessment they relied on.
Aghion and Tirole’s work on formal and real authority offers another theoretical perspective on how information and authority interact. The practical lesson is to inspect the arrangement, not assume that a title reveals whose judgement actually determines the outcome.
When raising a concern has repeatedly led to adverse treatment, a new feedback form is unlikely to resolve the problem alone. Examine how challenges are handled, what protection or escalation routes exist, and whether the people receiving them have authority to act.
Return the Decision and Its Conditions to the People Doing the Work
A useful decision record identifies what was chosen, who authorised it, which conditions apply, and what remains open. The people implementing it should not have to infer the answer from meeting attendance or a changed deadline.
For the lead, the record might confirm a narrower release, name the shared-service commitment, and specify when readiness will be checked. If the decision instead accepts a bounded uncertainty, record who is responsible for monitoring it and what triggers another review.
Identify which version of the assessment informed the choice. A decision made against an earlier scope can otherwise be presented as approval for a later proposal. The implementation team needs to recognise the applicable conditions and know where a change must return. A short version reference and clear owner may be sufficient; the purpose is traceability, not a duplicate archive of every discussion.
Acceptance of risk does not make every action permissible or remove the implementation team’s duties. Clarify the actual scope and any requirements that still apply. A general instruction to proceed should not conceal an unresolved conflict about those boundaries.
The decision-rights guide describes how preparation, advice, approvals, choice, and implementation can be allocated. Decision access makes the communication between those roles usable.
Review the Information Path Alongside the Result
If delivery misses its target, reconstruct the decision with the information available at the time. Compare the original estimate, brief, discussion, approval, and subsequent changes. This can identify where a condition was misunderstood, removed, accepted, or invalidated.
Do not assume that either the senior reviewer or the operating team must be at fault. The lead may have omitted a known issue; the reviewer may have ignored clear evidence; the process may have provided no practical route for clarification. More than one contribution can matter.
Repair the specific break. A better brief, an earlier review, direct specialist access, or a clearer reopening rule may be more useful than changing everyone’s reporting line. Check subsequent decisions to see whether the relevant evidence arrives and remains attached to the commitment.
For the release, meaningful accountability means the team can explain what it knew, how that knowledge reached the choice, and what it did afterwards. Decision access helps make those contributions visible before work is committed and reviewable when the organisation learns what actually happened.
