How to build a useful working relationship with your chair

Build a useful chair-CEO relationship through an explicit working agreement about information, contact, and issues that require early attention. Confirm formal roles rather than infer authority from a close relationship. Keep the board’s decision process distinct from management and obtain qualified governance advice where needed.

Role ambiguity is uncertainty about the responsibilities and behaviors expected of a position, including unclear boundaries over decisions, priorities, and coordination with other people. This definition follows APA Dictionary of Psychology: role ambiguity (American Psychological Association (2018), defining publisher entry; no single inventor claimed). Role conflict involves incompatible expectations rather than unclear expectations. The working agreement clarifies ordinary contact within the company’s actual governance arrangements, rather than creating authority through a close personal relationship.

A private moment that makes the issue visible

Composite scenario, not a client case: You answer a chair’s message during dinner and are unsure whether it is advice, a request for information, or a direction. You value the access, but the operating team receives another instruction before anyone has clarified its authority.

State the decision before discussing personalities

The working agreement should make contact more useful without turning a personal exchange into an undocumented governance arrangement. Role ambiguity identifies the uncertainty to address, not the actual legal division of authority.

Proposed method: chair-CEO contact-and-boundary agreement

Confirm formal responsibilities. Review governing arrangements and advice from counsel. Distinguish chair, board, and management decisions. Keep the formal position and practical contact plan in separate records. Obtain qualified advice where authority is disputed. Do not infer a governance right from familiarity, availability, or a past informal exception.
Agree on information needs. Specify the recurring operating account and the matters that need earlier contact. Avoid assuming availability resolves reporting expectations. Choose recurring information that serves an identifiable question. State the period and limitations. A commitment to share everything leaves both parties without a usable standard for what requires attention.
Set contact and surprise thresholds. Name who contacts whom and under what conditions. Include a backup route and appropriate confidentiality limits. Use examples of developments needing early contact and confirm the relevant duties. Identify a backup through the authorized route. Confidential information should not move to a wider audience merely because the primary person is unavailable.
Clarify advice and decisions. State when a discussion is exploratory and where a formal decision must occur. Do not give inconsistent private assurances. Ask whether the exchange is advice, a request for information, or a decision needing formal treatment. Clarify the next route before management receives a new instruction based on an ambiguous private conversation.
Review a real interaction. Use a recent issue to test the agreement. Correct role overlap or missing information through the proper process. Compare what each person understood with the record of the interaction. Correct a concrete ambiguity rather than make a general judgment about trust. Share an authorized operating change with the people who must perform it.

Begin with two records rather than one broad relationship promise

Keep the formal governance position separate from the proposed working agreement. The first comes from the company’s actual governing arrangements and qualified advice. The second describes how the chair and CEO intend to exchange information within those boundaries. A useful personal relationship can support the work without becoming evidence that the chair, board, or management has acquired a different authority. Ask the appropriate adviser to resolve an actual dispute about the formal position.

Use APA’s role-ambiguity definition to frame the operational question: which expectations are unclear in this interaction? Identify the specific request rather than describe either person as interfering or inaccessible. Ask whether the message seeks information, advice, a recommendation, or a decision. These categories are proposed prompts, not legal classifications. Confirm what follows from the actual request through the proper company process.

Write an early-contact note that preserves uncertainty

Prepare a short format for a consequential development. Include the confirmed fact, unresolved question, action already authorized, and help or decision requested. State the period the information covers. The chair should be able to tell whether management is reporting an event or offering an interpretation. Avoid postponing necessary contact until a polished explanation exists, while keeping an unverified concern clearly labeled as a concern.

For a hypothetical resource problem, the CEO reports that a delivery dependency changed and identifies the current operating response. The chair offers a possible line of inquiry. The CEO confirms whether that is advice or a request requiring a formal route. Management then supplies its recommendation through the appropriate process. The example illustrates clarification; it does not establish a universal rule about the chair’s legal powers.

Reconcile accounts before arguing about contribution

Ross and Sicoly’s 1979 experiments found biases in the availability and attribution of contributions to shared work. Their finding is a reason to inspect records when participants recall who did what differently. It does not prove that the chair or CEO is exaggerating. Review the actual request, information supplied, and subsequent decision before characterizing a disagreement as a failure of commitment or respect.

Invite correction of the account through a suitable audience. If a matter concerns other directors, confidential personnel information, or formal board action, do not treat an informal two-person conversation as the complete record. Ask which account belongs in the authorized forum and who may receive it. Familiarity should make clarification easier, rather than replace the confidentiality and governance checks the situation requires.

Review the agreement through actual interactions

Choose a recent contact that was useful and another that caused confusion. Ask what information arrived, how the recipient understood it, and what instruction followed. Check whether the agreed distinction between advice and authority held in practice. Update the working examples when a new kind of request appears. Do not expand the agreement into an expectation that either person remains continuously available for every operating question.

Edmondson’s 1999 study defines psychological safety at the work-team level and examines learning behavior in that setting. It does not validate a chair-CEO agreement. Its limited relevance is to preserving a route for questions or corrections without treating them as disloyalty. A candid exchange still needs accurate information and the formal decision process. Comfortable conversation alone is not evidence that an appropriate company decision occurred.

Close the review with the specific change each participant will use. It might concern the opening information, the backup route, or how a request is labeled. Confirm that affected management owners receive any authorized instruction they need. Keep the relationship agreement as a support for the company’s work, with a visible way to revise expectations when actual interactions show that a boundary remains unclear.

Put the boundary into words

I want our contact to support the work without making authority unclear. Let us agree what needs early attention, what information you need regularly, and which matters must go to the board’s formal process.

Work through a bounded example

Hypothetical application: A chair offers advice about a resource issue. The CEO confirms its advisory status, develops a recommendation with management, and routes the required decision through the proper forum. The team does not receive an informal conversation as a new directive.

Define what counts as useful early contact

Choose examples rather than a promise to keep the chair informed of everything. A verified threat to an important commitment, a material change in an assumption, or an issue requiring a board decision may need a different route from an ordinary operating update. Have the appropriate governance and legal owners determine actual duties. The working agreement should make those requirements usable without inventing thresholds from the relationship alone.

State what the first contact should contain. A brief account can identify the confirmed development, what remains unknown, the action already authorized, and the decision or advice requested. Do not wait for a polished explanation when the fact itself needs attention. Equally, do not convert every unverified concern into a formal conclusion. Mark the state of evidence so the chair can interpret the contact accurately.

Confirm a backup route. A dependable arrangement cannot require either person to be perpetually reachable. Identify how an urgent matter reaches the appropriate authority when one person is unavailable. Protect sensitive information in that route. Do not widen the audience solely because a convenient channel is available.

Keep a close relationship compatible with clear roles

Use explicit language when a conversation changes purpose. An exchange can begin as advice and reveal a matter requiring a formal decision. Name that transition and route it appropriately. Do not let the familiarity of the participants make the required review feel unnecessary. The same applies when the chair shares a concern attributed to other directors: clarify what is being conveyed and which process will establish the board’s actual view.

Keep management accountable for its own recommendation. A CEO can seek useful challenge without making the chair the hidden owner of every operating choice. Record the evidence and reasoning that management will present. If the chair’s advice is not adopted, explain the business basis through the appropriate relationship and forum rather than avoid the conversation.

Prepare for a boundary disagreement before it becomes personal. Identify the specific decision, the source of authority, and the information each person used. Obtain qualified advice where the formal position is disputed. A general conversation about trust may be worthwhile, but it cannot settle an unclear governance right.

At a periodic review, examine an interaction that worked and one that created confusion. Ask whether the information arrived in a useful form and whether anyone treated advice as a binding instruction. Update the agreement with concrete examples. The relationship can remain candid and supportive while preserving the processes through which the company is actually governed.

Check the failure mode before scaling

Do not treat this framework as a statement of legal governance rights. Avoid selective disclosure or a private substitute for board deliberation. Qualified counsel should resolve actual authority and confidentiality questions.

Review the work, then revise the arrangement

Review whether contact prevents avoidable surprises and whether formal roles remain clear. Record changes to the working agreement instead of allowing exceptions to become custom silently.