Business Owner Role
In small IT organizations, staff frequently hold one or more service roles. One exception to this is the Business Owner role, which is typically fulfilled by a single individual. In Enterprise Technology, the Business Owner for enterprise services such as Oracle is frequently a senior level staff not in UIT. In the remainder of the UIT business units, the Business Owner is typically an Executive Director, Associate Vice President or Chief Technology Officer. Note that there are exceptions to these rules.
What does a Business Owner do?
The Business Owner plays a strategic role and is not engaged in the day-to-day activities of managing the service. Rather, they focus on the big picture. They define the vision and roadmap. They have the knowledge and authority to make strategic decisions and clear the path of political and financial obstacles. They communicate to key stakeholders and work closely with the Service Owner, who is responsible for developing a roadmap that aligns with the vision.
What are the general responsibilities of a Business Owner?
- Provides high-level business requirements and works closely with the service owner during the design phase. Prior to launch, they validate that the service meets the expected business outcomes.
- Ensures the service aligns with industry direction, standards, and best practices
- Represents the service in business strategy discussions and provides strategic advice to the service team
- Reviews and approves (if acceptable) identified service risks and mitigations
- Controls and prioritizes all business requests, such as those for feature enhancements, ensuring limited resources (both staff and dollars) are spent on high-value requests
- Reviews and approves communications for key stakeholders and the business during “Major” service incidents
- Owns the service roadmap
What ServiceNow tasks is the Business Owner responsible for?
| Task | Why it matters |
|---|
| You are notified by email and may be required to approve or reject change requests. | Adhering to Change Management best practices minimizes the potential for service disruptions and outages. The Business Owner has the authority to approve change requests at all levels of impact. |
| You are notified by email and by phone of Major (Priority 1) service incidents of significant duration, and may be asked to review and approve communications to key stakeholders and keep the business community informed. | Incident management processes ensure that service issues and outages are handled efficiently. The Business Owner is kept informed of service outages and, in turn, keeps the business informed as needed. |
Key terms
- Change Management: The process responsible for controlling the lifecycle of all changes, enabling beneficial changes to be made with minimum disruption to IT services.
- Incident Management: An incident is an unplanned interruption or reduction in the quality of an IT service. Incident management is the process responsible for managing the lifecycle of all incidents. Incident management ensures that normal service operation is restored as quickly as possible and the business impact is minimized.
- Major Incident: A widespread, serious, major interruption or outage of a critical service that must be resolved with great urgency. They are classified as P1 and P2 incident tickets. The aim of the Major Incident Process is to quickly restore service with any means necessary, including workarounds.
Additional resources
- Glossary of ITIL Terms
- Change and Incident Management Documentation (includes guides)
- What’s the difference between Requests and Incidents?
- Service Owner Role
- Service Manager Role
- Technical Operations Owner Role
- Business Operations Owner Role
