Archive for January, 2007

Jan 31 2007

the prosumer developer

I’ve seen a lot of discussion lately around the likes of Coghead and other Do-It-Yourself (DIY) coding apps. To date most of it has been the developer community dismissing the idea that anyone outside the ivory tower could possibly have the mastery skill sets required to create a software application on their own. Well guess what guys, the party’s over.

So far this whole thing has been analyzed from the wrong angle. Developers are thinking that non-programmers are going to set-out and build the next generation killer app. Which, as has been pointed out is simply ridiculous. Even if the software could support it, the average Joe doesn’t understand architecture and design. But this doesn’t mean that we throw the baby out with the bath water.

Let’s step back and look at this from the consumer level-up vs. the developer level-down. Personally, I have been waiting for something that’s a notch above FrontPage but not as developer centric as say Visual Studio.

New technology creates new niches.The advent of affordable, super mega-pixel cameras created a niche for the ”prosumer photographer”. These cameras function right above point-and-shoot, but just below what would be required by a professional that wants to make money at his trade. I don’t recall seeing any headlines that mentioned any Professional Photographers loosing their jobs or their market shrinking due to the entry of the Prosumer. In fact, those that understood the market capitalized on it by offering tutorials, classes and equipment sales to this new class of users.

Another example of this prosumer market entry is Legal Zoom and other DYI law services. A great deal of attorneys view the services offered on that site as low lying fruit that they don’t want to deal with anyway. This frees them up to charge more for higher-end and specialized services.

So back to DIY Coding. Coghead claims 13,000 in their beta program. Certainly not Google-plex beta numbers, but nothing to scoff at either. What it tells me is that they have people’s interest and attention. If they execute this correctly, they could create an entirely new market here.

So, my message here is ”Mr. Developer, tear down this wall!”  Your jobs aren’t going anywhere. But, if I were in your shoes, here’s what I would do:

  • Instead of emphasizing the rules and limitations to what can’t be done with DIY tools, evangelize what CAN be done that would make your day easier (all developers like their day to be easier). 
  • Offer services and consulting around that. Prepackaged, vertical templates will be a hit. You only have to look to Salesforce.com appexchange to see that.

 

What Coghead essentially has done here is create the prosumer developer.

 

One response so far

Jan 10 2007

The Balance Beam

Published by Chris Crosby under Business, Management, Software

Managing a product’s development lifecycle is like constantly walking a balance beam. Fall off the beam, and on one side you get eaten by customers and prospects desiring new features and functionality; the other side your oh-so-precious resources to get it all done and the associated costs.

In a fast paced software company, it can be easy sometimes to get caught-up in customer requests, cool new ideas and the excitement of potential revenue from new-far-off markets. However, it’s critical that before any major decisions are made about your product that you step out of the tornado and evaluate what’s going to keep you propped-up on that balance beam.

Here are a few things to consider when adding new features to your product’s development roadmap:

Impact to customer loyalty and user adoption- New features, especially customer requested ones, usually translate to happier customers and more people using your product. This leads to increased Customer Lifetime Value and more long term revenue from your existing base.

User Interface changes can be a double edge sword. New technologies like AJAX may afford you the ability to do new things in your product different ways, but it can wreck havoc on your existing base if they’re fans of the current interface and aren’t big fans of change. Always, always do a customer “pulse check” and solicit feedback from your current users before making any major overhauls. They’re never shy to give direct input for improvements.

New Revenue from New Features - One of the first questions I ask my Business Development team when we’re discussing new requests is “can we charge for it?”. Whether that be as a separate module or an increase in base price of the product because we’re bringing more value to the table. The sister questions to these are: “Will it win us more deals? Or are we loosing potential customers because we don’t have it and someone else does?” This is almost always where the revenue comes from to help offset the cost of developing the new functionality.

How much is it going to cost, how long will it take, and what are the impacts to other parts of the product?- These are probably the numero uno questions to answer. If a new feature will devour resources to develop and yield no new revenue, don’t do it. Period.

One of the most often overlooked gotchas is the impact of the new functionality to other aspects of the software. If adding Widget A is going to break Widget B or change how users interact with Widget C then you need to do a full impact analysis and include this in your cost and timetable scope.


It’s also a good idea to get representation from all sides of the business in a room together with a white board. Sometimes a developer hearing direct feedback from your sales & marketing team can nip resistance to product changes (hint, developers take a lot pride in their products and often times have difficulty seeing how the product works in real-life for the end user. Stick them with customers and other team members for a few days; they’ll get it). On the converse, it’s good for your Business Development folks to hear the effort and costs tied to developing new functions directly from the people that do it. At times the balance beam just downright becomes a tightrope. Asking these tough questions will help guide you down the path.

-Chris

 

 

 

No responses yet

Jan 09 2007

Little Black Book of Connections - Book Review

Published by Chris Crosby under Books, Management, Marketing

Well I’m a little overdue in my book review of Jeffrey Gitomer’s Little Black Book of Connections: 6.5 Assets for Networking Your Way to Rich Relationships, but I thought since he released his new book today Little Gold Book of YES! Attitude: How to Find, Build and Keep a YES! Attitude for a Lifetime of SUCCESS, I should probably get my thoughts up here before I move on to his newest work of mastery.

First of all, as I’ve mentioned in the past, Jeffrey Gitomer is one of my favorite authors for sales & marketing. His straight forward, easy to follow writing style gives solid advice to anyone in the Business world.

In this edition, Gitomer stays committed to his underlying theme of providing value and establishing yourself as an authority in your discipline. Although the book doesn’t speak to it, what I find interesting is that this is exactly what is happening on the web right now. People have figured out that content = web hits = leads = sales. It’s almost a “build it and they will come” approach to attracting new business.

I can attest, the arch enemy of the sales guy is the “cold call”. This book demonstrates in practical terms how to get your phone to ring vs. the other way around.

-Chris 

 

No responses yet

Jan 09 2007

microsoft is feelin bloggy

This morning I read a review on Intelligent Enterprise by Serdar Yegulalp on Microsoft’s new Live Writer Beta, the newest addition to their “Live” offerings.

This is my first post using the product and I must say I’m pretty impressed. Set-up was amazingly simple. I just punched in the URL to my blog and username/password. It connected and recognized that I have a custom installation of WordPress. It immediately loaded a new post complete with my blog’s theme settings.

Now I know that in a 2.0 world, using thick client applications is considered taboo, but as a non-programmer who gets the very basics of HTML, I often found myself spending a lot of time in FrontPage modifying my posts to get the layout right. This seems to solve that need. I also like the ability to manage my draft posts in an “offline” fashion so that I can write while traveling and post when I come back online without having to copy and paste from a Word doc.

It also has some simple, yet cool features like the ability to add maps and technorati tags. And of course no Microsoft product would be complete without a preview in browser option.

Below is an aerial shot of Latigent International Headquarters using the mapping feature.

 

 

 

This obviously is not a revenue generator for Microsoft, but I think that it sends a signal that they see the need to appeal to the next generation of web users.

In typical Microsoft fashion they entered the ”Live” market with a giant THUD, yet have continued to build on the base and add improvements around the edges. Still a long way to go, but in this case I certainly appreciate the effort. For Microsoft though, I hope that it’s not too little too late.

-Chris 

No responses yet

Jan 07 2007

The Problem with RSS, is RSS…

It’s that time of year again. The ever present New Year technology predictions are sprouting like spring time weeds in my grandfather’s tomato garden. This seems to have sparked a renewed energy around the topic of RSS. I must say, it’s exciting to see a continually growing surge in discussion and awareness around RSS and it’s various real world uses.

So let’s take a deeper look at these crystal ball gazing predictions that “this is the year for RSS“. I appreciate everyone’s optimism, but if this thing is ever going to happen we need to change our product and go-to-market strategies. Obviously the current one isn’t working.

What do I mean? We’ll for starters we’re asking the wrong questions and making the wrong statements. Instead of asking “when is this going to take off?” As leaders in this industry we owe it to ourselves to ask: “Why hasn’t it?” And “what do we need to do to increase end-user adoption?”

About 18 months ago I stuck “Enterprise RSS” functionality into our Business Intelligence product’s development pipeline and declared that Latigent would leverage a first mover advantage in this new emerging market. BlueVue already had a great deal of the required plumbing done, so it was a logical short jump for us. My notion even seemed validated in Dec 2005 when I received a phone call from one of the nation’s top 100 law firms in NYC to demo our product.

I remember stepping out of my cab onto Madison Ave. that cold December afternoon. I looked-up at the big city high rises with stars and dollar signs in my eyes, ready to trail blaze a path into every law office in America. This was an opportunity to set ourselves apart from competitors and define a new market. Or so I thought…

Unfortunately, despite a laborious effort, about the only person in the company that actually understood Enterprise RSS or how to use it was the Head Librarian. And let’s face it, lawyers are not exactly the type to jump on the cutting-edge technology band wagon. Ultimately, the project died.

From that day forward though, I have mentioned Enterprise RSS in every product demo, seminar, and training class I’ve conducted. Today I still get rooms full of silence and blank stares until someone bravely asks, “What’s RSS?”

RSS OldWhat I’ve come to realize is that that little orange icon usually scares the non-developer away. The XML page that pukes out when you click the icon on a website is confusing and sends most people running the other direction. Albeit, there have been major steps by the likes of Feedburner, Google, Firefox and IE7 to alleviate that frustration, my gut says the typical internet user is still in IE6 and a great deal of feeds still don’t route through Feedburner or a similar service.

RSS NewI believe the new feed icon is a little less intimidating, but it’s still not all that clear to a new user what it does, or what exactly a feed is. Some websites post an RSS 101 section on their site, but even those can further convolute things.

The other issue is there are too many formats. Don’t get me wrong, flexible format choices are great for content syndicates but they suck for the content consumer. Johnny internet user doesn’t know the difference between RSS .93 and RSS 2.0 let alone RSS and ATOM. So when a site displays multiple format icons they may appeal to the savvy, but are providing further fear factor for the rest of the world.

On the upside, I do believe the content hurdle is finally being cleared. This provides greater exposure to the technology and peaks the curiosity of Jonny Internet User to take the first step in the RSS self-education process.

Now we’ve taken a look at the why’s behind why RSS hasn’t taken off. Let’s take a look at what we need to do about it. The solution I believe is three fold:

  1. Simplification and accessibility- We need to dumb it down for the average Joe. As I mentioned there are severali-Tunes companies already helping with this. But the real answer lies in “Integrated Readers”. The market for stand alone tools and readers is dead. People don’t want another place to go to get content. They want it in whatever portal they’re using at that moment. Whether it be your Google homepage, or your Company’s ERP system, the content needs to be more accessible and relative. 

    My guess is that if Apple released an i-Feeds reader that was integrated with i-Tunes and the video i-Pod the result would be explosive. Right now some of you are screaming “they already have that for podcasts”. Which is exactly my point. They mask the complexity for the end user.

  2. Content Pizzazz - Let’s face it, straight feeds and static HTML are relatively boring. Some feeds incorporate images, etc.Boring in the HTML. But what we really need is more interactivity with the content. Give people a reason to subscribe. Perhaps RSS Widgets or things similar to the banner ad putt-putt games that put Orbitz on the map. I’ll talk more about these later.
  3. Marketing - As with any product, technology, or service you have to have a good sales and marketing pitch. What we need is an RSS coalition so to speak. An army of advocates educating the masses on what RSS is and how to use it. Perhaps banner ads on MySpace would do the trick :-) 

    I have a couple initiatives brewing in the background for this that I’ll be announcing shortly.

This will be the first in several posts about bringing RSS mainstream, as this starry-eyed guy still has hope that things can take off. So instead of making a New Year’s prediction that this is the year for RSS, I’m making a New Year’s Resolution to do my part in making sure that it is. Who’s with me?

-Chris

[tags]RSS, Integrated Reader, RSS2, Latigent, Chris Crosby, RSS Reader, Software, Technology, 2007 Predictions, New Years Resolutions[/tags]

2 responses so far

Close
E-mail It