Skip to main content

Why We Must Transcend Silos

Survival - For a service provider to survive in today’s fast-paced delivery environment they will likely need to move away from old ways of doing things. We hear things like; "Terms matter", "Shift your thinking!" or "Shift the focus!" and "CHANGE the CULTURE!".  It is becoming more evident than ever that our organizational structure including silos could be an impediment.

Structure – An organization’s structure impacts how work gets done. Structure influences the actual product and service architecture. Some organizational structures even have siloed within silos. 

Structure matters. Silos can fracture the velocity of delivery and the quality of what is delivered. We can transcend silos! ITIL 4 Foundation or the new DevOps Leader certification classes are a good place to start learning new and better ways for the conversion of demand to value for service providers.

Considerations for Transcending Silos

  • Measurement – High performing IT organizations have an outside-in perspective where the User Experience (UX) is paramount. This infers that the way we measure needs to change. In the past, I have seen functional teams celebrate their own very siloed service or operational targets, while the market share was decreasing due to poor satisfaction. Siloed metrics not tied to the Customer/User Experience (CX/UX) can bring your organization to its knees. Today when you hear the word “VALUE” get out of IT. Value can only be determined and measured from a customer’s perspective.
  • Shared Goals – Cross-functional teams with shared goals and a high level of “trust and transparency”, are replacing siloed teams that have myopic goals that are subjective to their function or silo. Little fiefdoms are giving way to a holistic collaborative approach.
  • Culture – “Culture Eats Strategy”  It is dangerous to continue to do things because “That is the way we have always done it.”, and yet we still hear that coming from staff and managers alike. Peter Drucker often argued that a culture would trump any attempt to create a strategy that was incompatible with its culture. Culture is a DevOps value, but it is often misunderstood. ITSM Academy offers a great whitepaper titled “What is DevOps”. There is a section here talking about a DevOps culture and you can download it for free. Organizations – particularly those undergoing a transformation - fail to recognize its importance. The social and psychological aspects relate to how people interact and feel about their workplace environment. This affects the quality of work, commitment, and loyalty. For teams to be nimble, the old way of thinking (our beliefs), has to change. You may not be able to change a culture, but you can change behavior. Behavior shapes culture and IT BEGINS WITH YOU!

To learn more, please consider the following ITSM Academy certification courses:



Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service Offe

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the