Showing posts with label ved sen. Show all posts
Showing posts with label ved sen. Show all posts

Real-Time Mobile Infrastructure and Digital Transformation Discussion with Expert Ved Sen

In this Google+ Hangout OnAir, I have the privilege of discussing the findings of my recent report, Real-Time Mobile Infrastructure, with UK based mobile and digital transformation expert Ved Sen. We discuss the challenges identified and possible solutions.  Enjoy!

Real-Time Mobile Infrastructure Report, Introduction
Real-Time Mobile Infrastructure Report, Part 1
Real-Time Mobile Infrastructure Report, Part 2
Real-Time Mobile Infrastructure Report, Part 3

Video Link: https://youtu.be/IMYHORGxMYY?list=UUGizQCw2Zbs3eTLwp7icoqw


************************************************************************
Kevin Benedict
Writer, Speaker, Senior Analyst
Digital Transformation, EBA, Center for the Future of Work Cognizant
View my profile on LinkedIn
Learn about mobile strategies at MobileEnterpriseStrategies.com
Follow me on Twitter @krbenedict
Subscribe to Kevin'sYouTube Channel
Join the Linkedin Group Strategic Enterprise Mobility
Join the Google+ Community Mobile Enterprise Strategies

***Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and digital transformation analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Kevin Benedict Interviews Digital Transformation Expert Ved Sen

This week I am in Orlando, Florida meeting many of the smartest folks in Cognizant and planning our 2015. While at this event I am taking the time to interview some of our global experts on digital trends and strategies.  This interview is with Ved Sen, Global Head, Advisory Services, Social, Mobile and Sensors at Cognizant.  Enjoy!

Video Link: http://youtu.be/1u5gzIQN-us?list=UUGizQCw2Zbs3eTLwp7icoqw


************************************************************************
Kevin Benedict
Writer, Speaker, Senior Analyst
Digital Transformation, EBA, Center for the Future of Work Cognizant
View my profile on LinkedIn
Learn about mobile strategies at MobileEnterpriseStrategies.com
Follow me on Twitter @krbenedict
Subscribe to Kevin'sYouTube Channel
Join the Linkedin Group Strategic Enterprise Mobility
Join the Google+ Community Mobile Enterprise Strategies
***Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and digital transformation analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

The Internet of My Things and How It Works

IoT MyThings
In this article, my ever brilliant friend and colleague, Ved Sen, shares what the IoT (Internet of Things) is really about and the processes, technologies, systems and strategies behind it.
***

So there’s been all this talk about the Internet of Things. What the heck is it? You may well be cautious. Especially since it’s currently perched at the peak of the Gartner Hype curve for 2014.

So I started thinking about this by listing all the ‘things’ I interact with. From my house & home to the trains I take and from the clothes I wear to the hotel room I might live in on my travel. Obviously you can get many levels in the hierarchy. The home is a complex construct, and comprises many sub-things. Example – rooms, walls, plumbing. Some of these, such as ‘heating’ may have further sub-components – radiators, boilers, etc.  The resultant picture looks something like this, at a very high level. Of course, this is hugely inadequate for detail, but you get the conceptual model.

Then I started thinking about an appropriately benign and traditionally less intelligent ‘thing’ – like a window. Everybody has windows at home and they affect our everyday lives.  They have states (open/ shut), based on the environment and conditions. For example we associate safety, air-conditioning and sunlight with windows being open or closed, and based on the weather, time of day, etc.  So I drew this table of the different emotions and feelings we derive, the specific benefits they deliver, the activity or state associated with this and the conditions under which these states need to be enabled.

IoT State and Benefits
At this point, I came to an important realisation. Products can be smart and controllable, they can even react to the environment, all without the help of the internet. For example, we have some Velux(TM) windows on the skylights. These windows come with a remote control, they can be opened and closed and they can also react to weather conditions and close if left open when it starts to rain. So they are actually smart, in some way, and possess the capability to communicate. They’re just not on the internet. The challenge of this model is that my ability to control these outcomes is limited to the pre-set automations and my being in close proximity – i.e. at home. (Disclaimer: I’m obviously referring to the specific models we have installed. Velux does not have any IOT proclamations on it’s website, but this is not to say that they don’t have or are planning to launch models that come with their own smartphone apps, which allow control of windows from anywhere.)

This excellent article by Michael Porter & James Heppelman posits that all products in future should have:
  1. Mechanical/ electrical components
  2. Software components
  3. Communication components 
These three collectively make products smarter and ultimately evolve to product systems (e.g. home security) and then to a ‘system of systems’ model (e.g. connected homes) – which spans an entire problem domain, according to the authors.

The kind of activities that we can perform on smart products evolves from monitoring, to control, optimisation and then to autonomy. Ultimately this leads, according to the authors, to improved competitive performance via operational efficiencies and strategic positioning choices. Often, forcing the question ‘What business are we in?’

So for example the Velux windows we have installed, have a rain sensor, which allows them to automatically close if it starts to rain, they don’t have a sun-sensor, which allows them to re-open when the sun comes out again. Of course, I may not want them to open just because the sun is out. So it needs my intervention. I can only do this from home, currently, which is a constraint. Putting the Velux windows to one side, for all my windows, I would also like to be reminded if ground floor windows are left open at night or when I’m away. If I had pollen allergies, I would probably like to be alerted if the pollen count is too high, or have the windows close. I would like to be able to open all multiple windows or close them, even if I’m not at home, based on weather conditions.

So you see, we have a need for state information (monitoring) as well as control. I might even have settings for ‘sunny day’ which applies a set of commands to all windows. This is the optimisation that the article above refers to. These control should extend to blinds (effectively these are a part of my window settings). This is where we consider windows as a product system, whereas currently, we tend to have completely different suppliers for these 2 products (windows and curtains/blinds). Any maker of smart windows must therefore consider blinds and curtains as a part of their product system.
Now, considering any smart and connected product, we could argue that they have sensors, which generate data, which are used by apps, which enable access and control of the product, and provide additional functions that ultimately deliver a benefit. The sensors are obviously on-board the device/ product. But the data generated could be anywhere, typically on a cloud, so that the apps and the access can take place through any connected control point (such as a mobile phone).
IoT Data Access Function Layers

This is where the internet of things really kicks in. In my previous example of the Velux window models which we have installed, the data, access, applications and controls all sit within a closed system involving the window and the remote control. You could argue therefore that a true IoT model requires a cloud based data and access model and an ability to use the data and control/ monitor the product from any device and application that is authorised.

Of course, everybody looking at the Internet of things should bear in mind Bruce Sterling’s SPIME model (derived from space + time). According to Sterling, the SPIME object has 6 facets:
  1. identification
  2. location
  3. data mining
  4. computer aided design & construction
  5. prototyping
  6. lifecycle management
Using these, we can track the history of any object from concept to grave.

Stepping back a bit, the Internet of Things seems like a catch-all neologism to encapsulate a number of related concepts. It involves:
  • smart and connected products
  • multiple types of open and closed networks
  • robotics
  • cloud based access
  • decision analytics
  • functions ranging from monitoring, control and optimisation
It can also involve single products or groups of products. Many smart products today are autonomously capable of performing advanced functions which have nothing to do with the internet of anything. The Roomba vacuum cleaner is a great example of an exceptional product that doesn’t really need to connect to the Internet.

Most individual products also tend to ignore or be indifferent to the network effect, which kicks in when we consider multiple elements in the same network. For example, my windows may be rain-sensitive, but I might have other devices, products and appliances at home which may be influenced by the occurrence of rain. Does each product need to have it’s own rain sensor? In my IOT wish list, my smart windows can communicate to other appliances at home. So for example, the washing machine can run an extra spin cycle when it rains, so clothes dry in the same time, and conversely when it’s sunny, it can reduce the spin cycle to conserve energy. For this to happen, I need a network standard for my connected home network that multiple devices can connect to (i.e. my window can ‘talk’ to my washing machine). A problem that the DLNA among many others, has been seeking to solve for years.

The true value of the IoT thus seems to become clearer when we step into the details and away from buzzwords. Much like anything else really!  And the winners as always will be those businesses which are able to truly focus on:
  • design thinking
  • benefits
  • elegance of use
  • great experiences
  • excellent engineering
Companies who will be bold enough to rethink their business models and honestly answer the question ‘what business are we in?’ – allowing them to move from selling a product to delivering a composite service which may include a physical product. It might even mean changing the commercial model where the product is only ‘leased’ to the consumer who actually buys the service rather than acquires an asset.

Meanwhile I will dream about smart, connected windows which can deliver safety, sunshine, comfort to my home. As far as consumers are concerned, the I in IoT should really stand for ‘invisible technology’.

************************************************************************
Kevin Benedict
Writer, Speaker, Senior Analyst
Digital Transformation, EBA, Center for the Future of Work Cognizant
View my profile on LinkedIn
Learn about mobile strategies at MobileEnterpriseStrategies.com
Follow me on Twitter @krbenedict
Subscribe to Kevin'sYouTube Channel
Join the Linkedin Group Strategic Enterprise Mobility
Join the Google+ Community Mobile Enterprise Strategies
***Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and digital transformation analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Digital: Big Vision, Small Action

In my experience with digital tools & projects, nobody’s really an expert – everybody has gaps in their understanding. ~ Ved Sen
Ved Sen
Global Head Advisory Services
Social, Mobile and Sensors
My friend and colleague Ved Sen shares his insights from working in the trenches on digital transformation projects.  This is an important piece, as he is sharing real world advice on project management, scope and change management - not hypotheticals.
***

I've been a part of scores of discussions and projects around digital transformation, strategy and innovation. I've also been in the trenches trying to make some of this stuff actually happen. Over the years I've developed a strong olfactory sense of ideas that aren't going well and those where there’s clearly a smell of success.

I've spent many moments reflecting on these experiences. Sometimes at airport lounges by myself after day long meetings, nursing a glass of wine. At other times, in heated discussions with colleagues, locked in the deadly embrace of entrenched opinions.

In a nutshell, in my experience, it boils down to a simple credo – big vision, small action. This is a viewpoint you will see reflected in a lot of contemporary writing and thinking around lean and agile models, but somehow, while thinking big comes naturally, it’s very hard for big companies to act small. But every day I see signs that the smartest companies are recognizing the value of lean teams, working on small outcomes, which create momentum and the building blocks of great change. For most others, fail-fast is something they like to talk about but it stays on the slides rather than finding its way into the program.

Don't get me wrong, big ideas are critical. They underscore the vision and direction in which we need to move. The big idea is the north star of our journey. But you cannot negotiate even half a mile of unfriendly terrain with your eyes fixed on the north star. And all too often we fall into the trap of big idea & big action.

A typical idea of a big action is when a large company goes – ‘we are going to completely re-engineer the way we sell our widgets to our customers, across our 16 divisions and migrate from a direct to indirect sales network whilst improving our net promoter score and digitise our entire sales process while we're about it’. You've all been there I'm sure.

I’d like to highlight five very specific benefits of small action – those agile, lean projects which we love to quote but seem reticent to undertake. And why, especially in the world of digital change and transformation, they are even less useful than a hippopotamus at a barbecue.

The first challenge is politics and alignment. If you want to make a big change, in large organisations, you are expecting to get the buy in of a dozen or more senior people, who may well have contradictory expectations and competing ambitions. The time taking process of consensus building is the anathema of change, and often the end product of a consensus is an unwieldy compromise which no longer has the ability to deliver the benefits anticipated. In contrast, the small action looks at creating the smallest viable version of this change, may be in one division and one product line of a less prominent business unit. But however insignificant it is, you can never argue with success or with data, and small change grows quickly on the back of data and proven success. The power of digital is that it IS possible to create successes and gather effective data on a small scale.

Speed is an immediate victim of the big change process. Likely timelines for getting alignment with senior teams can take months. It can even take months just to get the right people into the room, to discuss the key issues. In fact, the small change approach can deliver large transformations faster because once it gathers speed, the change rate is exponential. A few years ago, I was working on a large complex program with half a dozen workstreams, which had gone on for over a year with almost zero success. People were demotivated and change resistant. One of the little things we tried was to take one of the workstreams and just focus on making that work over an 8 week timeframe. In two months, we had a success story, and suddenly everybody wanted to be in on the journey. The entire program was completed in under 8 months.

The actual implementation of a large scale program can be exponentially complex in terms of detail. This is not to say it can't be done. If you were building a new airport terminal, you would have to take on and manage the complexity, but in the digital world the number of unknowns is also very high. It may sound simple to say “we'll combine our CRM data with our transaction system, to create better views of customer history” but in one company where we tried it, we stumbled on firewall access, data structures, speed of response, security issues and user interface design. You can gloss over those challenges in a powerpoint presentation but not in the actual implementation. Will your grand plan survive it’s first brush with reality? In a small action approach, you can break up complexity into much more manageable chunks and solve them one at a time. Whatsapp recently announced that it had added the much awaited blue ticks for message delivery. The service has grown a lot both in features and popularity, but the first version of Whatsapp was launched in 3 months with 4 developers working. Evernote still releases a new version every other week.

You see, it boils down to learning. In the large change programs, we spend a lot of time discussing with ‘experts’ and owners of expertise areas. We seek advice and inputs and then we expect armed with all that planning, that things will go as per schedule. Small change makes no such assumptions. Small action learns ‘on the job’ and consequently it learns in real time. One is a learning by talking, the other is learning by doing. I think we all know which is more effective. In my experience with digital tools & projects, nobody’s really an expert – everybody has gaps in their understanding. So learning from expertise is immediately limited.

Finally, the digital landscape itself is changing. From regulatory stances on privacy (Google) or entering new markets (think Uber), to new platforms, tools, models and disruptive players, there is a high change environment in which you need to operate. Given this, the danger of the big change approach is obvious, with it’s slow and complex  approach, it may be outdated by the time the implementation has actually started. And often the fear of going back and re-negotiating the same issues, means that the program just gets shelved. This is probably the single most common outcome of large change programs in the digital environment. It gets put on the shelf and people just stop talking about it. Ultimately, it becomes a symbol in the organisation of project failure. People go ‘remember project Orion?’ (nudge! nudge!). The only way to address this is through the calculus of small change. Stick to small agile action which can help to absorb directional change brought about by the environment, and you never have to jettison a very large amount of work, so the risk is never too high.

A couple of years ago, we were pitching some new and exciting technology led change program to a client who are a well known Utility company. Our approach involved running programs of change, integrating complex back end systems and creating an aggressive 6 month program of work. One of the senior most execs in the room from the client organisation started the meeting by telling us how he along with a couple of his engineers had just spent the weekend ‘playing around’ with a new location based open source utility which they found to be quite interesting and had built a pilot for replacing their existing clunky routing application and were planning to roll out the change to a small set of service teams within the next 7 days. It suddenly made our 6 month change program look very glacial.

Think of a snowball that you start rolling down a snowy hillside, and how it gathers pace and bulk as it moves. This is how small change works. Now think of repairing a car by a committee of people with specialised and disparate skills taking the entire car apart, and then putting it back together again. This is how big change works. In the digital world, only one of these approaches is effective.

So the next time you encounter a digital transformation initiative, remember: politics, speed, learning, scaling and environmental change are the 5 reasons why it makes sense to commit to big vision but small action.
************************************************************************
Kevin Benedict
Writer, Speaker, Senior Analyst
Digital Transformation, EBA, Center for the Future of Work Cognizant
View my profile on LinkedIn
Learn about mobile strategies at MobileEnterpriseStrategies.com
Follow me on Twitter @krbenedict
Subscribe to Kevin'sYouTube Channel
Join the Linkedin Group Strategic Enterprise Mobility
Join the Google+ Community Mobile Enterprise Strategies
***Full Disclosure: These are my personal opinions. No company is silly enough to claim them. I am a mobility and digital transformation analyst, consultant and writer. I work with and have worked with many of the companies mentioned in my articles.

Interviews with Kevin Benedict