Copyright (c) 2013 John L. Jerz

Managing Change (Tuominen, 2000)
Home
A Proposed Heuristic for a Computer Chess Program (John L. Jerz)
Problem Solving and the Gathering of Diagnostic Information (John L. Jerz)
A Concept of Strategy (John L. Jerz)
Books/Articles I am Reading
Quotes from References of Interest
Satire/ Play
Viva La Vida
Quotes on Thinking
Quotes on Planning
Quotes on Strategy
Quotes Concerning Problem Solving
Computer Chess
Chess Analysis
Early Computers/ New Computers
Problem Solving/ Creativity
Game Theory
Favorite Links
About Me
Additional Notes
The Case for Using Probabilistic Knowledge in a Computer Chess Program (John L. Jerz)
Resilience in Man and Machine

Practical Strategies for Competitive Advantage

TuominenMC.jpg

As business operations and competition become more global, companies have to rise to the challenges posed by changes in technology products, and individual competencies. Author Kari Tuominen addresses these issues and provides sound strategies for incorporating change into any organization's management. Businesses must do more than learn from their own experiences. They must also observe others and learn from the competitions experiences. In order to stay competitive, businesses must emphasize the ability to implement plans and objectives faster than others. By keeping abreast of changes as well as learning from past experiences, organizations can adapt, improve, and thrive in today's global marketplace.

p.248 Without an accepted need, there will be no action.
 
p.249 A vision is a final target at which efforts are directed. It avoids the definition of the means.
 
p.272 A person's primary motivator is his or her basic value structure... Without the right value structure, management chokes on guidance and control.
 
p.281 Without a long-term plan, only acute problems are solved.
 
p.282 Use rewards as a means of encouragement. Reward even a good attempt that ends in failure. Rewarding is a sign to the whole organization of the right direction and of the expected mode of action.
 
p.282 In product development projects, often the first person is fired for a crazy idea, the second for poor technical execution, and the third for poor marketing. The fourth person finally succeeds and gets all the credit.

Enter supporting content here