Four Dimensions of Product and Service Management
Overview
The four dimensions ensure a holistic approach when designing, managing, and improving products and services. Every product and service should be considered from all four dimensions to remain effective.
The Four Dimensions
1. Organizations and People
This dimension focuses on organizational structure, culture, and people involved in the service. The effectiveness of an organization cannot be assured by formal structure alone -- it also needs a culture supporting its objectives and workforce capacity/competency.
Culture and Safety Culture
Organizations should foster cultures encouraging contribution, learning, trust, and recognition. A safety culture represents "a set of shared beliefs, perceptions, and values in relation to risks, where people feel trusted and valued."
Safety culture promotion requires senior management commitment to psychological safety, realistic risk-handling practices, continual organizational learning, and workforce risk awareness.
Leadership
Effective leaders at all levels:
- Engage, inspire, and motivate people with integrity
- Focus on value through priority adjustment
- Create healthy cultures by following organizational values
- Communicate clear vision
- Demonstrate commitment to knowledge and continual learning
Conscious leadership balances global good with individual self-interest, speaking with integrity, leading authentically, and holding themselves accountable.
Organizational Structure and Conway's Law
Organizations structure by geography, governance drivers, or work scope.
Conway's Law: "Digital product architecture often reflects how the teams involved in product development are organized and communicate."
Impact includes product design mirroring organizational design, and product work speed constrained by team communication complexity/number.
The reverse Conway approach involves designing team structures to enable target product architecture, typically moving from large, centralized solutions to smaller, independently evolving solutions with standard interfaces, supported by multi-disciplinary product teams (up to 10 members).
Skills and Competencies
Organizations should identify, acquire, develop, and continually improve competencies across categories:
| Skill Category | Examples |
|---|---|
| Technical | Domain expertise, platform knowledge, AI/ML skills |
| Problem-solving | Analysis, logical reasoning, brainstorming, creative thinking |
| Communication | Verbal and written communication, active listening, negotiation |
| Collaboration | Teamwork, conflict management, respecting diverse opinions |
| Leadership | Motivating others, delegating, mentoring, decision-making |
| Adaptability | Embracing change, self-management, continuous learning |
| Emotional intelligence | Self-awareness, empathy, relationship management |
Industry-specific models like e-CF and SFIA support professional competency planning.
Organizations, People, and AI
AI offers opportunities but requires risks management. Organizations should balance adoption speed with effective governance. AI supports humans in:
- Information processing (vast data amounts)
- Pattern recognition (subtle patterns in large datasets)
- Reducing cognitive bias (objective decision-making)
AI increasingly becomes a collaborative partner enhancing human capabilities, taking repetitive, data-intensive tasks, enabling people to focus on strategic activities: stakeholder engagement, relationship building, and continual improvement.
Key questions:
- Does the organization have people with right skills?
- Does culture support collaboration and continual improvement?
- Are roles and responsibilities clear?
- Does culture promote psychological safety?
2. Information and Technology
This dimension addresses data, information, and technologies used in digital products and services, and organization management systems.
Technology in Product and Service Management
Technologies include workflow management systems, knowledge bases, inventory systems, communication tools, and analytical tools. AI, machine learning, mobile platforms, cloud solutions, remote collaboration tools, and automated testing/deployment are now common practice.
The ITIL AI Capability Model (6C Model)
ITIL v5 introduces the 6C Model -- a functional AI solution classification helping understand possible applications. It enhances AI governance by helping organizations tailor risk profiles, controls, and countermeasures to specific AI functions.
Data, Information, and Knowledge
The amount of data organizations generate/process grows daily. The data-information-knowledge categorization is contextual: the same information belongs to different categories depending on situation and the categorizing person.
Information value is determined by outcomes it enables for stakeholders. Information is only valuable when enabling desired outcomes.
Data Governance
Data governance ensures data quality, security, usability, and availability throughout its lifecycle. Key principles:
- Strategic alignment: governance supports overall strategy
- Accountability and ownership: clear data asset responsibility
- Defined policies: documented classification, quality, security, and disposal standards
- Transparency and auditability: practices are clear and traceable
- Integrity: honesty about governance challenges and decisions
- Adaptability: evolves with changing needs and regulations
AI data quality challenge: "AI tools are as good as the data they are trained on. Many organizations find their accumulated product and service management records are not complete, accurate, or consistent enough for AI purposes."
ITIL Car Rental: Information and Technology
Max: "The information and technology dimension of ITIL Car Rental represents information created and managed by teams. It also includes technologies that support and enable our services. Applications and databases, such as our booking app and financial system, are part of this dimension as well."
Sam: "We take data protection very seriously. Whether it is for car sharing or car rental, we collect personal data: ID, driving license, and so on. That is why we already have a solid data management system in place, that undergoes regular audits. So, when we introduced our new service, driverless cars, we were confident that there were no additional challenges around processing personal data. We were ready."
Max: "That is true when we talk about user data. But we have new challenges now. We actively use AI and are highly concerned with AI governance: specifically, how we control its use. AI plays a critical role in vehicle navigation. While we do not manage the core navigation systems ourselves, we still hold responsibility for our customers' safety and that impacts our reputation. That is why we are asking our vehicle manufacturer to formally confirm they have an AI governance system in place, which provides the level of control and assurance we need."
Key questions:
- What information is needed to manage the service?
- Which technology best supports the service?
- Is information adequately protected?
- Is data quality sufficient for AI and analytics?
3. Partners and Suppliers
This dimension focuses on relationships with external organizations contributing to service delivery.
Includes:
- Outsourcing and sourcing strategy
- Contract and SLA management with suppliers
- Strategic partnerships
- Supply chain risk management
- Service integration across multiple suppliers
In ITIL v5:
- Broader ecosystem management models
- Clearer definition of product vendor and service provider roles
- Guidance for multi-vendor environments
Key questions:
- Should work be done in-house or outsourced?
- How can multiple suppliers be managed effectively?
- Which strategic partnerships are needed?
4. Value Streams and Processes
This dimension covers how the organization performs work to create value. It addresses organizational and cross-organizational workflows, focusing on activities undertaken and their organization.
Workflows in ITIL
ITIL describes workflows at several levels:
| Level | Description |
|---|---|
| Management practice level | Each practice includes several processes (detailed in Practice Guides) |
| Value chain level | Eight lifecycle activities, each with high-level workflow |
| Value stream level | Real-life activity combinations as actually performed |
Unlike processes and value chain models describing "workflows as designed," value streams represent "actual sequence" of activities "as performed." Mapping and analysis of value streams is a continual activity, not a one-off project.
Optimizing Workflows for Complexity
Organizations often develop detailed procedures for activities. Such procedures may be effective in predictable, stable situations, but can be less effective, useless, or even harmful in different contexts. Different situations require different strategies.
Navigation analogy: When a driver uses a navigation system, the route resembles a pre-defined process. But even with updated data, the driver still needs to maneuver, change speed, and sometimes deviate responding to live conditions. Similarly, strictly pre-defined business processes are increasingly inapplicable to growing work scenario variety. The solution involves designing processes as high-level courses of action and allowing people to make decisions within them. Detailed procedures should be limited to repeatable, standardized activities.
ITIL Car Rental: Value Streams and Processes
Anna: "We identified bottlenecks, some related to digital products, some to work processes, and managed to significantly improve the workflow. More importantly, value stream mapping helped us improve our services for customers! By understanding how work and information flow through multiple teams, we have made our services better. It came as a surprise to me: I used to think that value stream mapping was only about efficiency, but it actually helps to create value, not just eliminate waste!"
Key questions:
- Which value streams create value for the customer?
- Are processes optimized and automated enough?
- Are there bottlenecks or waste to remove?
- Are workflows designed for the right complexity context?
Complexity Context
ITIL v5 recognizes organizations operate in different complexity contexts, and management approach should vary accordingly:
| Context | Characteristics | Best Approach |
|---|---|---|
| Ordered | Clear cause and effect; known/knowable patterns | Standard processes, best practices, automation |
| Complex | Cause and effect only perceived retrospectively; emergent patterns | Experimentation, sensing, adapting; no single "right answer" |
| Chaotic | No clear cause and effect; urgent action needed | Act first to stabilize, then sense and respond; crisis management |
| Confused | Unknown which context applies; assessment needed first | Gather information, assess situation, then select appropriate approach |
Why complexity matters for practitioners: Many IT organizations default to "ordered" approaches (detailed procedures, expert analysis) even when their environment is actually "complex" (rapidly changing, emergent). In complex contexts, rigid procedures can prevent adaptation. ITIL v5 encourages organizations to recognize their context and adjust their approach: use best practices for ordered environments, experimentation for complex ones, and novel action for chaotic ones.
External Factors: PESTLE
All four dimensions are influenced by external factors beyond organizational control. ITIL uses the PESTLE model to analyze these factors:
| Factor | Examples | Impact on Services |
|---|---|---|
| Political | Government technology/digitalization policy | May require changes to data handling, reporting, or service location |
| Economic | IT budgets, cloud costs, economic conditions | Affects investment decisions, sourcing strategy, and service pricing |
| Social | User expectations, remote work, digital literacy | Shapes service design, channel strategy, and employee experience |
| Technological | AI, cloud, IoT, blockchain, quantum computing | Creates opportunities and risks; changes what is possible |
| Legal | GDPR, AI Act, data sovereignty, compliance | Mandates specific controls, reporting, and security measures |
| Environmental | Green IT, sustainability, carbon footprint | Drives sustainable design, energy efficiency, and ESG reporting |
Organizations should regularly scan their PESTLE environment and feed insights into product and service portfolio decisions, particularly during the Discover stage of the lifecycle.
Balancing the Four Dimensions
Important principle: No dimension is more important than another. Imbalance across the four dimensions leads to ineffective services.
Examples:
- Strong technology but not enough people -> Operations cannot run well
- Skilled people but outdated technology -> Low productivity
- Perfect processes but weak suppliers -> Unstable quality
- Everything strong but chaotic value streams -> Customers are dissatisfied
Related Pages
- Key Concepts (foundational definitions)
- Strategic Analysis (PESTLE) (external factors affecting dimensions)
- Operating Model Design (Organizations and People dimension)
- Case Study: IT Merger (Four Dimensions analysis in practice)
- Case Study: Cloud Outage (failure across all dimensions)