Showing posts with label Objectives. Show all posts
Showing posts with label Objectives. Show all posts

August 14, 2019

Goals Vs. Tactics

I liked this saying from someone in the IDF. 

Be "flexible in tactics, but stay fixed on the goals!"

There are many ways to accomplish the same thing. 

And different people have their own approaches. 

As in the lyrics: "You take the high road and I'll take the low road."

That's absolutely okay. 

In fact, that's one of the strengths and benefits of diversity.

We bring different ways of looking at the world to the table.

Hence, we can bounce fresh ideas off each other and come to a great way forward. 

The main thing is that we focus on our goals and progress to achieve them. 

Be rigid on goals and flexible in tactics. ;-)

(Credit Photo: Andy Blumenthal)
Share/Save/Bookmark

October 19, 2018

Parking Lot Full of Ideas

So conducting large meetings is not often easy. 

People have their own concepts as to where they'd like the discussion to go.

Yes, agendas help keep the meeting focused. 

And a good facilitator enforces meeting discipline. 

Some people think that any deviation from the agenda is like taken a sudden left turn or driving off the cliff. 

But you don't want to throw away the baby with the bath water. 

It's important to jot down good ideas or follow up questions that come out in the discussion even when they are not immediately relevant. 

That's where the "Parking Lot" comes into play. 

A flip chart or whiteboard to capture the important thoughts for follow up afterwards. 

While parking lots are needed to take certain things off the table immediately in order to focus on accomplishing the meeting's objectives, they are not junk yards for people's input. 

Instead, they are a place to park the stray thoughts and then to actively follow up on these after. 

No question is a dumb one, and no idea isn't worth considering. 

Parking lots can be full of these and they should be parked and then taken for a spin around the neighborhood.  ;-)

(Source Photo: Andy Blumenthal)
Share/Save/Bookmark

July 27, 2018

Calling An ELMO

So this is an interesting meeting facilitation technique. 

Sometimes people get carried away in meetings either as broken records, spinning wheels, naysayers, or ever with verbal attacks.

In these case, either the facilitator or any of the other participants, can have permission to "call an ELMO."

What that stands for is:

Enough,
Let's
Move 
On

When someone at the meeting calls an ELMO the meeting is redirected and focused back to the agenda and meeting objectives.

There are also times, you need a "parking lot" for good ideas that are a little offtrack or for sidebars that you want to come back to later.

At other times, you just need to say, "Let's take it offline."

Focused meetings should generate ideas (brainstorm), exchange points of view, surface problems, discuss issues, and make decisions. 

A good meeting leaves people feeling energized, valued, informed, and productive. ;-)

(Source Photo: Andy Blumenthal)
Share/Save/Bookmark

August 6, 2013

Teamwork, There Is No I

I really love this saying--"There is no I in Team."

A colleague said very astutely, "even though some try to put it in there!"

Teams work best, when everyone does their part and contributes, and no one makes it about their personal agendas, ambitions, and issues. 

A team implies a large degree of selflessness where we do what is best for the team and the mission we serve, and we don't get caught up in personal ego trips. 

When people place themselves above the team--and they try to impose that "I" right on in there, then rather than teamwork, we end up with rivalry and conflict.

From my experience, those who try to take the credit for themselves--typically end up exposed for who they really are and without the honor they chase.

But those who give recognition genuinely and generously to others are in turn respected for their contributions to the mission as well as to the team. 

Selflessly united as a team we can assuredly succeed, but selfishly divided as just a bunch of I's, we will most certainly fail. ;-)

(Source Graphic: Andy Blumenthal)
Share/Save/Bookmark

July 5, 2013

Have You Been Voluntold?

Voluntold, it's a funny word. 

A combination of volunteer and told, to do something. 

I couldn't believe that this word is actually in the dictionary and means:

"When one has been volunteered for something by another person. Often against their wishes and desires." (Reference: Unwords

"The exact opposite of volunteering. Always used in reference to an unpleasant task to which you have been assigned by your boss."(Reference: Urban Dictionary)

I've seen this used when the boss asks for volunteers for a task or special project. If no one volunteers, then the boss volunteers someone--telling them to do it.  They have been voluntold!

One time, I remember a very tense meeting where a boss was presenting his vision for the organization, but at the same time putting down the status quo and everyone in it. 

As one point, he asks for a volunteer to help with driving his vision forward (note: no one had bought into it), and no one volunteers. 

The boss ask for a volunteer once, twice, and three times at the meeting as the tension rises. 

Finally, a hand goes up and someone accepts the task. 

He is the bosses new favorite and is told publicly at the meeting that he will be rewarded for "stepping up."

The truth is he didn't really step up, but rather succumbed to the pressure to do it. 

Another victim of being voluntold. 

In the end, he really didn't perform much of what he volunteered for--not a surprise, since he never bought into it to begin with. 

Sometimes, we do have to ask people to do things, but it shouldn't be by force or undue pressure. 

A leader builds his vision with his team--not for his team--and they move forward together to achieve their unified goals and objectives. 

Telling someone to do something, and pretending that they are really volunteering fools no one and achieves nothing accept maybe calling out some pretend accomplishments to go with the pretend volunteers. ;-)

(Source Photo: here with attribution to Andrew Huff)
Share/Save/Bookmark

June 6, 2013

Charting Your Course


New article here by Andy Blumenthal in Public CIO Magazine called "Using Enterprise and Personal Architecture To Chart Your Course." 

"As a leader, one of your primary jobs is to bring a coherent, rousing vision and strategy to the organization and execute it to keep the organization relevant -- that is enterprise architecture."

Hope you enjoy!

Andy

(Source Photo: Andy Blumenthal)
Share/Save/Bookmark

February 8, 2010

From Planning to Practice

Real planning is hard work. I’m not talking about the traditional—get the management team together, offsite for a few hours or days and spell out a modified mission and vision statement and some basic goals and objectives—this is the typical approach. Rather, I am referring to thinking and planning about the future with a sense of urgency, realism, and genuine impact to the way we do our jobs.

In the traditional approach, the management team is focused on the planning session. They are engaged in the planning for a short duration, but when back in the office, they don’t go back in any meaningful way to either refer to or apply the plan in what they or their employees actually do. The plan in essence defaults to simply a paperwork exercise, an alignment mechanism, a check box for the next audit.

In contrast, in a comprehensive planning approach, the focus is not on the planning session itself, but on the existential threats and opportunities that we can envision that can impact on the organization and what we are going to do about it. We need to look at for example: What are our competitors doing? Are there new product innovations emerging? Are there social and economic trends that will affect how we do business? How is the political and regulatory environment changing? And so on. The important thing is to think through/ work through, the impact analysis and plan accordingly to meet these head-on.

This is similar to a SWOT analysis—where we evaluate our Strength, Weaknesses, Opportunities, and Threats, but it differs in that it extends that analysis portion to story planning (my term), where the results of SWOT are used to imagine and create multifaceted stories or scenarios of what we anticipate will happen and then identify how we will capitalize on the new situation or counter any threats. In other words, we play out the scenario —similar to simulation and modeling—in a safe environment, and evaluate our best course of action, by seeing where the story goes, how the actors behave and react, and introducing new layers of complexity and subtext.

Harvard Business Review (HBR), Jan-Feb 2010, has an article called “Strategy Tools for a Shifting Landscape” by Michael Jacobides that states “in an age when nothing is constant, strategy should be defined by narrative—plots, subplots, and characters---rather than by maps, graphs, and numbers.”

The author proposes the use of “playscripts” (his term), a scenario-based approach for planning, in which—“a narrative that sets out the cast of characters in a business, the way in which they are connected, the rules they observe, the plots and subplots in which they are a part, and how companies create and retain value as the business and the cast changes.

While I too believe in using a qualitative type of planning to help think out and flesh out strategy, I do not agree that we should discard the quantitative and visual analysis—in fact, I think we should embrace it and expand upon it by integrating it into planning itself. This way we optimize the best from both quantitative and qualitative analysis.

While numbers, trends, graphics, and other visuals are important information elements in planning, they are even more potent when added to the “what if” scenarios in a more narrative type of planning. For example, based on recent accident statistics with the car accelerators (a quantifiable and graphical analysis), we may anticipate that a major foreign car company will be conducting a major recall and that the government will be conducting investigations into this company. How will we respond—perhaps, we will we increase our marketing emphasizing our own car safety record and increase production in anticipation of picking up sales from our competitor?

Aside from being robust and plausible, the article recommends that playscripts be:

· Imaginative—“exploring all the opportunities that exist.” I would also extend this to the other relevant element of SWOT and include envisioning possible threats as well.

· Outward-facing—“focus on the links a company has with other entities, the way it connects with them and how others perceive it in the market.” This is critical to take ourselves out of our insular environments and look outside at what is going on and how it will affect us. Of course, we cannot ignore the inner dynamics of our organization, but we must temper it with a realization that we function within a larger eco-system.

To me, the key to planning is to free the employees to explore what is happening in their environment and how they will behave. It is not to regurgitate their functions and what they are working on, but rather to see beyond themselves and their current capabilities and attitudes. Life today is not life tomorrow, and we had better be prepared with open minds, sharpened skills and a broad arsenal to deal with the future that is soon upon us.


Share/Save/Bookmark

September 21, 2009

Leading Through Planning

Recently, I was reminded of two pointers in developing an effective IT strategic plan:
  1. Strategic planning is about leadership and setting direction—There is an interesting saying with respect to this that the manager ensures that you do things right, and the leader ensures that you do the right things. The strategic plan, including the vision, mission, and value statements are about leadership establishing and communicating what the ‘right thing’ is. An effective metaphor for this is that the manager ensures that you climb the ladder, but the leader ensures that the ladder is up against the “right” wall.
  2. Strategic planning goals, objectives, and initiatives have to be aligned and actionable —that means that you need to set the strategic plan elements at an appropriate level of detail and in cascading fashion. One way to do this is to navigate up and down between goal, objectives, and initiatives in the following way: To navigate to a higher elements of the plan hierarchy, ask why. Why do we do XYZ? To navigate to lower levels of detail and specificity, ask how. How do or will we do XYZ.

Together, these two guidelines help to develop an IT strategic plan that is both effective in terms of goal setting and organizational focus as well as at the appropriate levels of detail and alignment to be truly actionable.


Share/Save/Bookmark

April 13, 2008

Strategy and Enterprise Architecture

Enterprise architecture develops the organization’s IT strategic plan and influences its business strategic plan. In order to do this, EA itself must have a strategic roadmap.
Harvard Business Review, April 2008, states that “companies that don’t have a simple and clear statement of strategy are likely to fall into the sorry category of those that have failed to execute their strategy or, worse, those that never had one. In an astonishing number of organizations, executives, frontline employees, and all those in between are frustrated because no clear strategy exists for the company or its lines of business.”
Elements of a strategic plan
What are the elements of a strategic plan?
  1. Mission— “why we exist;” this is the purpose of the organization
  2. Values—“what we believe in and how we will behave”
  3. Vision—“what we want to be
  4. Strategy—“What pour competitive game plan will be; this includes the following: A) Objectives—what we want to achieve: goals and objectives B) Scope—“the domain of the business; the part of the landscape in which the firm will operate.” C) Advantage—the means or initiatives that define how you will achieve your objectives; “what your firm will do differently or better than others,” defines your competitive advantage.
  5. Balanced scorecard—“how we will monitor and implement that plan” A strategic plan for EA
    According to the American Management Association, the mission statement defines what the ultimate purpose of the organization is. It tells who you are, what you are, what you do, who do you serve, and why do you exist.
    The mission statement takes the form of: The [blank] is a [blank] that [produces blank] for [blank] to [help blank].
    For example, the mission statement for enterprise architecture:
    The [enterprise architecture program] is an [office of the CIO] that [develops information products and governance services] for [the employees of ABC organization] to [improve decision-making].
    The values of EA are: driving measurable results, aligning technology with the business, information-sharing and accessibility, service interoperability and component reuse, technology standardization and simplification, and information security.
    The vision of EA is to make information transparent to enable better decision-making.
    The strategy provides the conceptual way you will pursue your mission and vision.
    Defining the objective, scope, and advantage requires trade-offs, which Porter identified as fundamental to strategy.” For example, a growth or market size strategy may obviate profitability, or a lower price strategy may hinder fashion and fit. The point is that an organization cannot be everything to everybody! Something has got to give.
    So for example, in EA, we must trade off the desire to be and do all, with the reality that we must focus on entire enterprise. Therefore, we distinguish ourselves from segment architecture and solutions architecture. In EA, we focus on strategic outcomes and delegate line of business architectures and systems architectures to the lines of business and solution developers.
    Finally, EA implements a balanced scorecard by instituting mechanisms for monitoring and implementing its plans. These include performance metrics for both information products and governance services.
    In sum, to get a meaningful EA plan in place, we have to answer these fundamental elements of strategy for the EA program itself.

Share/Save/Bookmark