Skip to main content

Death by Meetings

So I assume everyone has heard the phrase “death by meetings”, that fear that you are going to be in a series of meetings and that no matter how hard everyone tries, you seem to come out of these meetings with the same to do list or a larger one.  I know your all shaking your head yes or saying “been there done that and have the tee shirt to prove it”. 

We at ITSM Academy recently had our yearly strategic meetings and I want to say up front, Best Strategic Meetings in the eight years I have been with the organization. Now that it is not to say that we haven’t had great Strategic Meetings in the past, because we have.  And that is not to say that I wasn’t heading into these meetings with a bit of trepidation, as I think most of us do. I recently read an article called Managing Yourself, Learn to Love Networking*. It defined four strategies that you can engage to help you network with other people even if you really don't enjoy it.  I thought, why can’t I take these 4 approaches and use them to help me be the best I can be and contribute effectively to the goals of the organization?

Step number one ‘Focus on learning”.  Most people have a dominant motivational focus – promotion or prevention (1).  Promotion is focusing on the growth, advancement and accomplishment, while the perspective is excitement, curiosity and an open mind, something hard to do for grumpy cats. Prevention on the other hand is the view of I’m obliged to do this and take part for only professional reasons, which to me really limits your ability to listen and engage with people.

Step number two “Identify Common Interests”. (2)  Take time to think about how your interests and goals align with those individuals that you are meeting and hopefully brainstorming with.  What pain-points do we have in common and how can we work together to eliminate them to all our benefits? What is working well and how can we continue to mature it over time with coordinated efforts?  If you are not sure of what the people you work with do on a daily basis, ask them to tell you and find those areas of where your common interests lie.

Step number three “Think Broadly about what you can give”. (3)  Don’t be afraid to share your experiences and knowledge.  You would be surprised at how much you have to offer and what value you bring to the table, especially if you can look at things with a different set of eyes and a unique perspective.

Step number four “Find a Higher purpose”. (4)  Enter the meeting with a higher goal, focus on the collective benefit of engaging with others to move your organization forward.  Think about how you can contribute to making your organization more efficient and effective and what the results will look like for your customers.

*Managing Yourself, Learning to Love Networking - https://hbr.org/2016/05/learn-to-love-networking

Tiziana Casciaro, Fancesca Gino and Maryam Kouchaki. (1, 2, 3, 4)

Comments

Popular posts from this blog

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…