Talk:Strategy map

Untitled

Other than the introduction, this article has nothing to do with 'strategy maps'. The remainder of the article goes into a variety of different concepts introduced by Kaplan and Norton, and does not discuss how any of these concepts are related to strategy maps, what a strategy maps looks like, etc. It is suggested that either the remainder of the article be deleted, or the concepts that are described are explicitly described in terms of their connections to strategy maps.—Preceding unsigned comment added by 170.3.8.253 (talk) 18:48, 27 December 2006 (UTC)

For what it's worth, the previous statement (unsigned) is interesting, but it makes me wonder if the person making this statement is familiar with what a strategy map is. Personally, I find very little wrong with the description of the material in the article. Nickmalik (talk) 07:51, 12 May 2008 (UTC)

I agree with the assessment of the (unsigned) first paragraph. This article should not be a place to write about mission, vision, perspectives etc. These belong in the balanced scorecard article, not here. User:Parveson —Preceding undated comment added 15:57, 23 July 2009 (UTC).

I have made substantial changes to the article to focus it more closely on the topic, and reduce the focus on proprietary methods / ideas.--Glawrie (talk) 20:02, 2 July 2010 (UTC)

citations

I added a tag requesting citations for the IBM lock-in statement where some detail was provided. Another statement was made that Microsoft 'had been accused of lock in' with no further citation or reference. I have no problem with these statements if a citation is given to the context of the accusation (assuming the intent was to refer to a court case). However, the fact of an accusation is not salient. EVERY company has been accused of things, most unfounded.

I do not consider an accusation to be particularly notable or even useful, without some references to the facts of the case. The IBM reference provided some detail, so I didn't delete it outright, yet. Unless valid citations are made, I'll remove the IBM reference as well.--Nickmalik (talk) 07:45, 12 May 2008 (UTC)

lock in strategy

The lock-in strategy is commonly found in the public sector: for exemple passport deivery or court jugments are coercive monopoly, which nobody finds particularily unethical. They correspond clearly to the internal process persective of social and regulatory process.

They are also frequent in non-profit organisation, like UNO, WHO, ILO,... where the service output is precisely social and and regulatory processes or rules.

In private sector, you find locked customer at each pump station on a high-way: the customer stops to buy gaz, but often ends up with a impulse buy for a newspaper or a drink. The internal process is built upon a physical regulation.

And, noy that I am saying it, isn't whole purpose of advetrising campaign to incease customer lock in, sorry to incease customer loyalty ? Again a social process. AlainD (talk) 16:05, 4 June 2009 (UTC)

Suggestion

In the Operation management process you suggest that Effort should be made to reduce lead times as experienced by the customer between placing the order and delivery at the doorstep, and not just to reduce the time taken in the factory.

I aggree so much. Why not mentioning that : Effort should be made to focus on the user not the customer, for exemple GM's user and automobile drivers, while GM's customers are car dealers. AlainD (talk) 16:11, 4 June 2009 (UTC)

Example?

Could someone add an example of a strategy map? It's a graphical thingy, but describing it in words doesn't make it easy to understand. A picture would really say more than a 1000 words here. RonaldKunenborg (talk) 19:55, 26 September 2011 (UTC)

Royal Trouble Strategy Map

Is it possible to "steal" a strategy map from Runescape Wiki to illustrate how the concept works in detail, even if the example is "less than serious", there are

• quest requirements,including
  • skill requirements
  • previous quests required, including
    • their own quest requirements
    • all their skill requirements

et cetera, AND a set of guides on how to train the skills, complete the quests, etc.

Royal Trouble quest

The actual form and layout of this material would depend more on mastery of the page-subject, but the material itself would be readily adaptable to whatever is required to properly illustrate the subject. Thanks! -- TheLastWordSword (talk) 14:08, 24 October 2012 (UTC)

Agile Strategy Maps

Removed the section on Agile Strategy Maps. The only reference I could find to the concept that Agile developers would create a unique diagram, also called a strategy map, was from the a blog post. There needs to be reliable third party sources referencing this method and referencing the results of using it, before it can be included in Wikipedia. I am not challenging that (a) these things exist, or (b) that they provide value. I'm simply stating that including them, at this time, violates Wikipedia policy. See the policies on no original research and notability.Nickmalik (talk) 19:58, 20 June 2014 (UTC)

Merge this page with Balanced Scorecard

Strategy Maps are a standard element of the strategic performance management framework called Balanced Scorecard, and are discussed there (see this section - https://wiki.riteme.site/wiki/Balanced_scorecard#Second_generation). The information about the history of the idea is incrementally useful over that on the Balanced Scorecard page, but the information on Perspectives and on links to the strategy development process is covered in more detail on the other page.

Remove strategy map from "Strategy" navigation device

Currently both Balanced Scorecard and Strategy Maps appear as separate items in the Strategy Navigator that is included on this page. Given that Strategy Maps are simply an component of a Balanced Scorecard there would appear to be no value in having these two elements separately in the navigator (or, to be consistent, you would need to add many other components - such as performance measures, targets, destination statements etc.). — Preceding unsigned comment added by Glawrie (talk • contribs) 13:19, 13 July 2017 (UTC)

Strategy maps are a valuable strategy tool

Reading the comments "Merge this page with Balanced Scorecard" and "Remove strategy map from "Strategy" navigation device", it may seem logical from an academic point of view. Strategy practitioners would respectfully disagree. A simple "strategy map" search on Google, and Google --> images would prove the usefulness and popularity, even though the BSC has declined in popularity.