How do you pivot? How do you change? Do you change? Business leaders, those forecasting and driving strategy, those dubbed “change agents” inside an enterprise have an increasingly tough task. Often they are handed the reigns to steer a company in some new direction, but they battle a mine-field of internal opposition that makes the act of change, very, very difficult. A simple but effective graphic – one that was actually featured in the social media focused post The Social Media Minefield: 5 Factors Blocking Your Success - does a nice job of showcasing common roadblocks that get in the way of you getting to your desired state.
With the understanding that in a traditional enterprise it is far easier to keep things the same, we’d like to turn your focus to a very recent article from GigaOm that highlights the inevitability that is change.
For any programmer or project manager we encourage you to read the entire article here. Beyond this being an intriguing new language full of promise and purpose it remains of course unknown if Halide will get the kind of uptake needed for enterprises to take notice. But that doesn’t really matter because this is just an example of what is consistently taking place in the greater landscape of technology. Every single day, in fact every single moment of every single day, there are programmers from across the globe tinkering, refining, re-inventing and producing iterations, and sometimes all together brand new software languages. The entire industry is in a constant state of continuous innovation. Few will hit, most will miss, and some new advances will even change the world. But where should your focus be as the leader or aspiring leader of an enterprise? Should you chase these new technology languages? How would you chase them if you could?
Utilizing Your Community to Shepherd Change
What’s New to You, is Not to Them
We have found, through practice, experimentation, failure and successes, that often the skills needed to innovate on top of a new software language or framework already exist within our community. When this is the case – and most often it is – the focus completely shifts from “chasing” the talent needed for success and instead keys-in on shaping a highly defined challenge or problem in such a way that effectively communicates how the new language will be utilized. In short, the talent in that specific language already exists, it was only a matter of drawing it out properly.
Ramping-Up the True New, Faster
Not New, Just Out of Bandwidth
The GigaOm article which triggered this post matters. How you as an enterprise pivot matters! That GigaOm story is not uncommon. In fact, it is the norm in technology and software. When considering Open Innovation and the utilization of a community, think of the flexibility this approach can provide your enterprise. Whether you’d like to experiment with a new framework or simply need to address a traditional bandwidth concern in a specific language, development via community can at least be part of your solution.
No comments:
Post a Comment