Skip to main content

Who owns my tractor ???

Pretty stupid question, right? Actually No.

This is the new debate that is going on. For more details read here: Wired article on John Deere

Do the manufacturer own the product because the product has some software that is owned by John Deere or is it owned by customers.

The concept of ownership has been pretty clear for the last century or so, barely going through a debate despite the rise and fall of communism.






What is a Product here

Based on the argument above, the combination of both the hardware and the software is considered a product.

This includes most of the hardware that includes mobile phones, camera equipment, cars or any automobiles.

Why the Confusion


Most of the time in the last 2 decades, we have not had software that could be experienced independent of the hardware.

What this means is that most of the software was proprietary and could not be easily tampered with.

Why do they own our Products

The product being sold here is the bundle of hardware and a license to use the software. How we can use the hardware is going through some changes as the market has been evolving for the  last 2 decades.

Rooting an android device - a TV or a mobile phone - or jail breaking an iphone is no longer considered an offense. However, with some of the other devices need to evolve to become mature.

Implications and Conclusion

Traditional Hardware companies need to mature. Customers should be given freedom to use the hardware the way they want.

This will see the adoption of Internet of Things be faster. This event could be the pivot of how IoT be like in the future. Is it an experience that will be fliexible or just another service that is controlled.
http://madhavanwrites.blogspot.com/2015/04/who-owns-my-tractor.html

Comments

Popular posts from this blog

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile:  http://djrusso.github.io More reading from his paper here:  https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision.  I liked the approach of principles for developing systems that are anti-fragile. It is a very valua

User Personas

User Personas are a very good tool for the product owners, business analysts or product managers to be able to co-create with designers. It is predominantly a product of the user research and should not be an amalgamation of demographic data. It is the best way for us to list all scenarios that a persona would take when they want to attain a goal. It is predominantly used to build empathy with user, focus the team and build consensus in a large diverse stakeholder group. The website I referred to is here:  https://www.smashingmagazine.com/2014/08/a-closer-look-at-personas-part-1/