… And This is Why Flexible Products Matter

The Devil We Know

On the heels of introducing “Productonomics“, I figured I should go ahead and post something relevant, and this article caught my eye a few weeks ago from Silicon Alley Insider: Facebook Has Zynga By The Short Hairs — But It Needs To Be Careful. Yes, of course I appreciate any business article that can refer to pubic hair, but it speaks directly to the kinds of “broad spectrum” econ-based concepts that we all need to be thinking about as we build products.  I have always felt that when developing products, you aren’t JUST dealing with the current marketplace and what you think users want… you are mightily constrained by “what you have to work with”, and many times those constraints matter more than we think.

Its easy to examine at our “product arsenal” and determine the following:  “I have X many designers, developers, and project managers, and I have these tools and technology providers – ok, go”. The problem with that line of thinking is that, in a sense, we are creating an experimental environment that is doomed to provide a false reading of our reality… a  reality that is a complex system with lots of moving parts. We really need to think about the business and competitive environment that our company exists  in, and in many sectors, the business development and legal efforts may have more impact on your decision-making than anything else (just ask anyone building digital media products).

The article discusses the buyer-supplier hold up problem, and in my mind, its an insightful view into the relationship of Zynga and Facebook – – or any app developer to platform provider relationship (iPhone and Android App developers, take note – – – same situation).  A Product Manager, looking at their options from a pure “user advocate” position, might opt to say “well, our users love our game on Facebook, and it works well on Facebook, and we can develop many more features if we stick to one platform, and overall, the product will be better”.  That actually might be a true statement, but past the short-run, if the the party that provides the platform has too much leverage, the product can suffer severely from restrictions that you didn’t bargain for – – or more likely, the profits of your company suffer severely from leverage that you gave up (and then the product suffers from lack of resources).

So what conclusions can a Product Manager draw from this lesson? Perhaps another micro-economic principal is helpful to throw in to understand their situation: Interdependence.  A popular buzz-word thrown around these days to describe the positive side of interdependence is “ecosystem”, but its the same idea. We don’t live in a vacuum with our users, and our companies don’t operate in a static world.  We need to think ahead, and plan for “scale” and all that — but relying on your intuition to make the right guess is pretty damned risky – – I think the lesson learned is for us product people is that we are advocates of users, yes, but also advocates of flexibility.  The real value of Farmville is the game itself, and Zynga might lose some short-term market-share by building in some “flexibility”, but in the mid to long-run, they will be better off with a healthy if not slightly competitive relationship with Facebook and a product that can evolve regardless of the platform or distribution environment.  That discussion will will probably manifest itself in a “we need to give up short-term feature-improvements for longer term flexibility” discussion… not the easiest one to have. Clearly, though, its the conclusion that Zynga drew: http://www.technewsworld.com/story/70086.html.

Introducing: Productonomics

When it comes to my blog and thinking and writing about things of interest to me (and hopefully others), I obscenely violate of the best practices that I enthusiastically promote to all those I work with – “generate ideas, quickly share them, iterate, optimize, repeat”.  Well, I’ve decided to stop violating this practice and share an idea that I’ve had rattling around in my head for quite a while: Productonomics. The idea is not especially revolutionary or even very original (the title may make some of you cringe – it even does me sometimes, but hey – it’s catchy). It may be that I am just collecting a sub-set of ideas or putting a slant on concepts that have permeated my industry for a long time, but I think that my approach narrow and unique enough to add some insight and value.  Most importantly, I have found this way of thinking to be very useful and productive in a very practical day to day kind of way. I strongly believe that that all companies and “product people” can benefit from taking a step back and looking at problems through different lenses, and the lense that micro-economics provides is very powerful and insightful for those of us who need to make decisions on a daily basis about “what people want and how we build it”.

I got so excited when I started to pull together these ideas that I went out and registered the domain and had all these delusions of grandeur of having the “Productonomics” blog taking off and getting me a book deal or something… well – for now, I still own the domain, but I’ll just post here on quiet little timjmitchell.com and set the categories of those posts to “Productonomics”.

Mobile App Stores

Above is a presentation given by Distimo Blog about mobile app stores, pricing, revenue, market size, etc.  There are a lot of interesting tidbits in there, but here were the pieces I found interesting:
  • Android has the highest % of free apps.  My conclusion here is that Android is a lot easier to develop to and
    the space isn’t as crowded yet, so developers are jumping in because they see the risk-reward to be a lot lower than iPhone.
  • Blackberry (RIM) and Microsoft app prices are almost twice as high.  I actually don’t get this at all, and as a Blackberry user, it annoys me that apps are so expensive for the Blackberry.  Sometimes the price differential between iPhone and Blackberry is over $20!
  • They predict that prices are going to level out and go down.  This, of course, makes sense, since competition and increased transparency will force developers to increase the quality and reduce the prices.  As developers get more adept at creating apps, they’ll get more efficient.

Suffice it to say, I’m moving to Android as soon as I can.  A $30 Skype app for my Blackberry is ridiculous when its $4.99 on the iPhone.

Mind Blown

Those of us who work in technology can often become jaded perhaps “unimpressable” by new technologies or applications of technology. After all, innovations are usually iterative and built upon an existing bedrock of technology that may not seem very impressive anymore. There are time, though, when your mind gets totally blown, and you start thinking that maybe you will get that jet-pack before you die. This video from TED is utterly amazing, and my mind was fully blown. Privacy issues? Whatever.

Time Management Thoughts (from the past!)

Recently, I started consulting on a regular basis, and I am now feeling all of my time management skills put to the test.  I have always prided myself on good time management and good organizational skills, and I’m constantly tweaking my tools and process to optimize efficiency (yes, I am a self-repairing robot).  I am, in fact, an unapologetic “devotee” of David Allen and the “Getting Things Done” way of organizing and working. (Yes – it does look like a self help book, and yes, he does talk about reducing stress in your life, but it is extremely practical… I digress).  While working through a whole new set of processes for my consulting business, I ran across an old Powerpoint Deck that I put together a couple years ago for some time management training for my team.  Some of it is “loosely” based on GTD, and in order to get a glimpse of the “GTD way” you can take a look at the GTD Workflow Chart to understand a bit.I was managing a medium sized team, and it was a mix of a lot of different backgrounds — some music industry, some technology, some a little of both, some with a lot of experience, some not so much – you get the idea. The biggest productivity problems we had seemed, in many cases, to stem from some very core prioritization and work-flow issues.

Experience had taught me that as management, you simply can’t force people into “your way” of organization — especially in a rapid moving tech start-up environment.  People have to adapt to their own style and their own natural rhythm.  So, what I tried to do was formulate some really simple, non-preachy,  ideas around every day decisions that, in aggregate, eventually add up to all of the work we do.   There is definitely a good amount of “GTD” influence in here, but I tried to keep it light, simple, and more of a “guiding principle” kind of methodology instead of a “system”. You’ll even notice a fair amount of tongue in cheek in there — I was poking fun at myself for teaching “productivity”. Let me know what you think!  I’ll be posting some other interesting stuff about my experience with GTD soon.