Norms at the Interface
Cross-functional norms become visible where work, information, and accountability pass from one role or function to another.
The problem to solve
Telling functions to collaborate does not establish how a request becomes a usable handoff. In the absence of an agreement, teams build local protective norms: copied leaders, duplicate work, informal favors, or silence until the cost is high.
Interface evidence
Bring a recent real handoff into the conversation.
- What request or trigger started the work?
- What input was required and what arrived?
- What did a usable output look like?
- Who could resolve the exception?
- What behavior did leaders reinforce when the handoff broke?
Practical next actions
Test one concise interface agreement for 30 days. Pair the design change with a leadership response that rewards early visibility and end-to-end ownership.
Continue the work
Related resources
Culture / Article
Leaders Make Interface Escalation Visible
Culture shows up at the operating interface: whether people surface a risk early, protect a local boundary, ask for evidence, or escalate every uncomfortable tradeoff upward.
Read resourceDesign / Tool
Review the Interface Before You Redesign the Organization
A useful Organization Blueprint begins with one critical workflow: the outcome, trigger, roles, handoffs, decision rights, evidence, and next test—not an abstract org chart.
Read resource