Skip to main content

Porter's outside-in and Hammel - Prahald's Inside-out


Over the years inspiration and motivation to out do something which creates spark in the
genre of concurrent times is always been challenge for all of us, to make things happen requires a plan, an out of the box solution to rationalize its existence.

More often than not inspiration are unknown to us, which may leads to different scenarios of multiple ways of looking at things differently and indifferently also, anyways there are always n-1 degrees of freedom to think differently for n+1 different ways looking at things.

Inspired by a spiral which is coincidentally a galaxy in our spatial system gives us views like --if one start from a point from outer end to reach at center, will reach from outside-in and if one starts from the center and circle outwards move than that will be inside-out thinking. So again its up to individuals, which way move. Traveling by we see stars and other objects binding each other with gravitational forces.

Galaxy

One of the many management strategy framework, Porter has given a outside-in approach for the organization strategy framework working towards corporates success or may be applicable to many scenarios. In which he suggest about forces influencing from outside and to investigate those scenario.

On the other side Prahalad and Hamel has proposed theory of inside-out approach gives us a core competences of the organization to utilize and plan many outcomes.

Taking a balance view of the approach gives us the suitability of the application for best fit solution. While in modern times we have techniques like six thinking hats by Dr. De Bono suggest us to wear different strategy hats for different scenario to make decisions, formulating strategy.

Enhanced by Zemanta

Comments

Popular posts from this blog

Usecase Scenario development and User Stories

A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this: Typical Software Development Life-cycle explained Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the  the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development. "A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives. " Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a s...

Games People Play in context to Projects

Games People Play in context to Projects: Contextually life and projects full of games, work on  dynamics of human relationships by   Dr. Eric Berne guides us not only in many social but relationship situations in corporate world also. In Todays concurrent world where we are living in a global village with Orkut, Facebook, Linkedin, Twitter and other social media leads to discounts of information in social network, where more of transactional games played knowingly(conscious) or unknowingly(unconscious). Precede to this let us understand game, A game full of transactions played with different roles by players changing their roles for a outcome in different ego states like Parent, Adult and Child ego states that will payoff.  Continuing with Payoff, specifically in context to Project teams where transactions happen at concrete or transformational levels where people not necessarily behaving rationally and motivat...

Constructive Blame storming and using Devils Advocate in problem solving and competency development

Cover of Six Thinking Hats Discussions leads to solutions , mistakes leads to innovations, As part of innovation , solution approaches, models quite often used technique in healthy discussions on day to day basis is Brain Storming , mischievously known as blame storming. To the extent organizations build competency around subjects of real time situations, till it takes to materialized very few of them make it to the concrete implementations. Take for example Google revolutionized the way we use internet with countable team, that storm sustained and now second wave coming from Facebook, Linked etc. Questions asked about their revenue models but skepticism will always there, social networks are strong tools not only for marketing but of communication, collaboration, and increased productivity and realized intangible benefits. Discussions are full of Arguments, counter arguments, statements, facts, thesis, anti thesis etc. Contextually the term devil's advocate can be dis...