“Meeting” is not a four letter word

At one time or another, we have all opened our email, only to find a meeting invite and think (fill in the bad word of your choice)

Different organizations communicate and collaborate in different ways, depending on the message, decision, or topic at hand. Under certain circumstances, a virtual or physical meeting may be the best vehicle for making a decision or collaborating on a common objective. While most meetings strive to be well-controlled, brief, and focused on facilitating a set of actions, this does not always happen.

Here are some simple and effective ways to ensure that a meeting is a success:

· Establish and communicate a clear agenda in advance. This will allow people to prepare properly and will help the facilitator prevent his or her meeting from being hijacked by one of the attendees.

· Most organizations have a governing set of rules for participation in a meeting. No biting, scratching, spitting, or name-calling is encouraged. Remember everybody has a right to their point of view and all should be heard.

· If some of those points of view or ideas are beyond the scope of the current meeting, they can be documented in the meeting minutes and then put into a “parking lot” so they can be discussed if time allows or they can become the focus of a future meeting.

· The events of the meeting should be recorded. Minutes are taken so that we can keep track of the overall discussion that has taken place and who has been assigned which action items. This is also important so that action items that involve cross-functional groups understand which items each party is accountable for. Deadlines and due dates should be recorded, well documented, and agreed.

Comments

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

Search