Skip to main content

Strategic Thinking

What is strategic thinking? This question often crosses my mind and those of my students, especially when I am teaching the ITIL Lifecycle classes. Just as often as the question arises, a variety of answers are put forth as well.

One definition of strategic thinking holds that “the role of strategic thinking is ‘to seek innovation and imagine new and very different futures that may lead the company to redefine its core strategies and even its industry’ ". This implies that the definition and use of strategic thinking are related but different from strategic planning—putting into action or executing the ideas developed using strategic thinking. Strategic thinking is just that—postulating or thinking about what the future holds and what the future looks like. Strategic planning is action based. A good organization recognizes they need both.

As a Professor who attempts to provide learners with theory-driven practical data, information, knowledge and wisdom, I particularly like the difference in definition between strategic thinking and strategic planning. But how do you learn to use the two approaches differently yet in a related manner? I think one key is in the deliverables.

The key deliverables of strategic thinking should be a vision, a mission statement and a values statement. In this context a vision is a mental picture of what you would like the future to be for yourself, your company and your industry. A mission is a basic statement on how you would like to go about achieving that picture of the future. The mission then becomes a key input to strategic planning, which develops action steps from the mission. The values statement identifies the core beliefs and convictions you will stand by as you move forward towards your vision.

The key deliverables of strategic planning are your objectives, goals, strategies, plans, and critical success factors that serve as a roadmap and toolkit for achieving your vision. Since the vision is a picture of a broad horizon, strategic planning helps you lay out the details, milestones, vehicles, elements and conditions required to achieve success.

Once you have used strategic thinking and strategic planning to layout your future, you will have completed top-down design of what success looks like for your customers and your organization. You will need to follow up the top-down design by building your capabilities from the bottom up as a validation of design. You will need to identify the processes, roles, key performance indicators, measures, metrics and tool sets that will enable you to reach your vision.

Remember that you need to do the top-down design before you do the bottom-up build. Otherwise you risk putting the proverbial cart before the horse. Taking too operational a perspective on how to serve your customers can take you away from the benefits of strategic thinking and planning and place you into a “just do it” mentality that can often lead you in directions you did not intend.

You will continue to go in this strategic thinking/planning and capabilities cycle using Continual Improvement as a guide towards quality. Each cycle will help you refine your vision and improve your roadmap and toolkit until you are moving along the journey to success as a well-oiled machine.

So do not hesitate: start thinking and planning strategically today!


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…