Intranet governance: who belongs on your steering group and why

A new intranet can stall when everyone has a say but no one owns the decision. HR needs policy visibility, internal communications wants room for announcements, and IT needs clear access rules. Without effective intranet governance, these legitimate needs turn into repeated meetings and delayed decisions.
The answer is not a bigger committee. It is a steering group with a clear mandate, balanced representation, and defined decision rights. Here is how to assemble that group, separate oversight from everyday work, and give employees a meaningful voice.
In this article:
- What should your intranet steering group decide?
- Which functions need a voice on the steering group?
- How do the product owner, content owners, and governance board differ?
- How can you balance IT and business voices?
- How should end users participate without becoming token representatives?
- Which decision rules prevent committee gridlock?
- What should your steering group charter include?
What should your intranet steering group decide?
Your steering group is the governance board responsible for cross-functional direction and decisions beyond the product owner’s authority. Its purpose is to resolve shared questions, not approve every page or backlog item.
The group should own decisions such as:
- Which employee needs take priority when departments compete for limited resources.
- Which publishing, ownership, and review rules apply across the organization.
- Who becomes accountable when content or services cross departmental boundaries.
- Whether a request justifies an exception to an agreed policy.
- Which conflicts require an executive decision about funding or staff time.
Routine work should stay elsewhere. A content owner should not need board approval to correct an outdated policy link. A product owner should not need a committee vote to reorder work within agreed priorities.
Give the group a written mandate from the executive sponsor. That mandate should state which decisions are binding across departments, what the group may delegate, and where its authority ends.
Without that backing, members may agree in a meeting but return to departments that feel free to ignore the outcome.
This article focuses on those people and authority boundaries. Detailed implementation planning, platform selection, and launch tactics belong in separate workstreams.
Which functions need a voice on the steering group?
Include the functions that own employee needs, resources, content, and risk. Representation does not mean everyone must attend every meeting. Use standing seats for recurring decisions and invite specialists when their input is required.
| Function | Why it belongs | Expected contribution |
|---|---|---|
| Executive sponsor | Gives the group authority across departments. | Authorizes the mandate, resolves conflicts beyond the group’s remit, and secures resource decisions. |
| Product owner or intranet lead | Connects governance decisions to everyday work. | Brings recommendations, maintains priorities, and turns decisions into assigned actions. |
| Internal communications | Represents organization-wide communication needs. | Defines publishing responsibilities, coordinates announcements, and identifies competing messages. |
| HR | Represents employee services and workforce policies. | Explains needs across recruitment, onboarding, employment changes, and departure. |
| IT | Makes technical responsibilities and constraints visible. | Explains feasibility, access controls, integration dependencies, and ongoing support obligations. |
| Legal, privacy, and security | Identifies obligations that cannot be treated as preferences. | Defines required reviews, approval gates, and risk escalation routes. |
| Marketing or brand | Keeps internal identity and messaging consistent. | Provides brand guidance without allowing visual preferences to outweigh employee tasks. |
| Business unit representatives | Connects central decisions to operational work. | Brings departmental priorities and commits the department to agreed actions. |
| End-user representatives | Shows how decisions affect everyday work. | Challenges assumptions with examples from employees, including those outside headquarters. |
In a smaller organization, one person may represent more than one function. Record those responsibilities explicitly rather than assuming they are covered.
The sponsor does not necessarily need to attend every session, but must remain available for escalations. Similarly, legal or privacy specialists may join only when a proposal triggers their review. Their absence from routine meetings must not remove a required approval.
Business unit representatives need more than knowledge of their department. They also need authority to agree to actions, such as assigning a content owner or allocating review time. Otherwise, every decision becomes another round of consultation.
How do the product owner, content owners, and governance board differ?
Clear role boundaries reduce waiting time. People can act without asking the committee to confirm decisions they already have authority to make.
Use this matrix as a starting point:
| Role | Accountability | Decisions owned | Escalation route |
|---|---|---|---|
| Product owner | Keeps intranet priorities aligned with agreed employee and business goals. | Day-to-day prioritization and acceptance of work within approved scope, budget, and policy limits. | Governance board for cross-department conflicts or exceptions beyond those limits. |
| Content owner | Keeps assigned content accurate, approved, current, and ready for retirement when no longer needed. | Content changes, review timing, and archiving within shared rules and required approval processes. | Product owner for coordination; board for unresolved ownership or policy conflicts. |
| Governance board | Maintains shared direction and resolves cross-functional trade-offs. | Shared policy, competing departmental priorities, and exceptions within its mandate. | Executive sponsor for unresolved strategic or resource conflicts. |
| Executive sponsor | Ensures the intranet has organizational authority and support. | Strategic direction, resource commitments, and disputes beyond the board’s remit, subject to organizational controls. | Relevant executive, financial, or risk authority when required. |
Accountability is not the same as execution. An HR content owner can delegate editing to an author while retaining responsibility for factual accuracy and approval.
Likewise, the product owner coordinates the intranet but does not automatically become the owner of every page. Each content area needs a named accountable person, a review expectation, and a route for resolving overdue work.
Decide these boundaries before assigning tasks. “HR owns this” is less useful than naming the role responsible, the person currently holding it, and the deputy who can act during an absence.
How can you balance IT and business voices?
Balanced governance prevents two common problems: an intranet driven by feature requests with no regard for ongoing support, and an intranet driven by technical constraints with too little attention to employee work.
Select members for their decision authority and relevant knowledge, not seniority alone. Then give business and technical representatives complementary responsibilities.
Business representatives should describe the employee problem before requesting a feature. Ask them to explain:
- Who is affected?
- What task is difficult today?
- What happens if nothing changes?
- What observable benefit would justify the work?
“Employees cannot identify the current leave policy” is a clearer starting point than “HR needs another homepage tile.”
IT should explain constraints alongside feasible alternatives. Instead of reporting only that a request creates an access risk, explain who could gain unintended access, which rule applies, and what alternatives would avoid that risk.
Separate mandatory approval gates from advisory input. For example, a proposal involving employee personal data may require a privacy review under your organization’s rules. A preference about page layout usually does not carry the same authority.
Document those distinctions before disagreements arise. Required legal or security approval cannot be replaced by a simple majority vote.
Finally, appoint a chair to keep discussion focused on the decision needed. Name a deputy for every role whose absence could block a decision, and specify whether that deputy has the same approval rights.
How should end users participate without becoming token representatives?
An employee seat is useful only if that person can influence the outcome.
Choose representatives whose working conditions reflect meaningful differences in your workforce. Depending on your organization, that may include desk-based employees, frontline workers, remote staff, regional teams, and people with accessibility needs.
Do not assume department heads or enthusiastic early adopters speak for everyone. An employee who uses the intranet throughout the day may miss barriers faced by someone who has limited device access.
Make participation workable:
- Define their authority. State whether employee representatives are decision-making members or advisors.
- Provide paid time to participate. Include time to read proposals, consult peers, and attend meetings.
- Use accessible decision briefs. Explain the employee impact without requiring technical knowledge.
- Give them a challenge route. Let them flag an unsupported assumption, request evidence, or ask for a concern to be recorded.
- Close the feedback loop. Explain what changed because of their input and why other requests were not accepted.
If permanent seats cannot reflect the workforce, support them with a rotating employee panel. Keep enough continuity for representatives to understand earlier decisions, and provide a handover when membership changes.
For example, a frontline representative might show that a proposed policy acknowledgment process assumes daily computer access. Record whether that evidence changed the requirement, triggered further consultation, or led to another approach. Attendance alone is not evidence of influence.
Which decision rules prevent committee gridlock?
A committee does not need unanimous agreement on every question. It needs a predictable process that distinguishes consultation, approval, and final authority.
Start by assigning one accountable decision-maker to each decision type. For board decisions, name the chair as responsible for completing the agreed decision process and recording the result. That does not allow the chair to bypass voting rules or mandatory approvals.
A practical model is:
- Routine prioritization: The product owner decides within documented limits.
- Departmental content: The content owner decides within shared policy and required review processes.
- Cross-functional policy and major trade-offs: The board decides under its agreed decision rule.
- Strategic or resource conflicts beyond the board’s authority: The sponsor resolves or escalates them.
- Mandatory legal, privacy, or security gates: The designated authority approves before the affected action proceeds.
Define quorum by both attendance and necessary representation. A meeting may have enough people present but still lack a required approver.
For decisions within the board’s remit, the charter could require a majority of voting members, representation from both business and IT, and relevant approvals. Seek consensus first, then use the documented voting rule if agreement is not reached. Escalate ties or unresolved conflicts to the sponsor. A vote cannot authorize an action that lacks mandatory approval.
Before each decision, circulate a short brief containing:
- The problem and affected employees.
- The realistic options.
- The recommended option and expected benefit.
- Constraints, risks, and required approvals.
- The decision-maker and response deadline.
Time-box consultation. State what happens when someone does not respond. Silence may close an advisory comment period, but it should never count as mandatory legal or security approval.
Keep a decision log with the outcome, rationale, accountable owner, follow-up actions, and conditions for revisiting the decision. This prevents settled questions from returning simply because someone missed a meeting.
Example: HR and internal communications both want homepage space
HR wants to highlight an enrollment deadline. Internal communications wants to promote a leadership update.
The product owner applies agreed criteria, such as urgency, audience, required employee action, and available alternatives. If homepage scheduling falls within delegated authority, the product owner decides and records the reason. The board does not need to approve the placement.
Escalation is appropriate if the request would change the shared homepage policy or exceed another documented limit. Disagreement alone is not a reason to send routine work to the committee.
What should your steering group charter include?
A short charter makes intranet governance usable. Start with one page, linking to a role matrix or approval policy where more detail is needed.
Include this checklist:
- Purpose and scope: What the group decides and what remains outside its remit.
- Mandate and sponsor: Who authorizes the group and backs its decisions.
- Membership: Standing members, employee representatives, and invited specialists.
- Chair and deputies: Who runs the process and who can act during absences.
- Member contributions: Each role’s responsibilities, decision rights, and expected preparation.
- Delegated authority: What the product owner and content owners can decide independently.
- Decision rules: Quorum, voting or consensus rules, and the fallback when agreement fails.
- Mandatory approvals: Which proposals trigger legal, privacy, security, or other required reviews.
- Escalation routes: Where unresolved issues go and when a response is expected.
- Decision records: Where briefs, outcomes, rationale, and actions are stored.
- Meeting cadence: How often the group meets and which decisions can happen asynchronously.
- Ongoing ownership: Which roles continue after launch and when membership is reviewed.
Match meetings to decisions needed. A new intranet may require frequent steering decisions early on, while an established intranet may need fewer scheduled meetings. Use asynchronous approvals for routine matters where the same authority, quorum, and recordkeeping rules can still be met.
Governance should not disappear at launch. Product ownership, content ownership, policy oversight, and risk review remain necessary. Revisit membership when departments reorganize or responsibilities change.
Before adopting the charter, test it against a sample departmental disagreement. Can everyone identify who decides, who must contribute, which approvals are required, and where an unresolved conflict goes? If not, clarify the charter before relying on it.
Ready to start?
Draft a one-page steering group charter before your next planning workshop. Name the sponsor, product owner, core representatives, and content ownership expectations, then confirm decision rights with your sponsor.
Test it with one realistic conflict, such as competing homepage requests. A clear answer to “Who decides this?” will save more meeting time than adding another committee seat.


