Friday, December 12, 2008

Customer loyalty vs product features....


My good friend Bill Self, in his thinkinglikeacustomer.com blog has a great article on the difference between product focus and customer focus. I recently had a brainstorming session with my long-time customer Knowledge Athletes. We were trying to look further out than the next funding round so we could prioritize scope and determine what things to concentrate on after completing the scope we'd already committed to. We also wanted to be sure we weren't looking at the trees and forgetting about the forest.


We started with an hour or so on mission statement. KA has a GREAT mission statement to start with, but it's useful to periodically review your mission statement to be sure that as you develop new ideas your mission doesn't change. By publicly declaring the mission statement we also gave ourselves a measurement to determine if each presented idea fit within that statement. This stayed on a whiteboard during the entire session.

Our next step was a brainstorming session to get down ideas for the product. Ideas were contributed by the business folks, educational leader, programmers, advertising, customers, sales and marketing. The rules were as follows:

  • There are no bad ideas - we're putting them ALL up there, and we'll judge them later.
  • We're not evaluating ideas - no judgements on how hard they are to implement, whether they complicate or simplify the user interface, or whether they add value or not. Just get the idea on paper (or in this case spreadsheet). We'll evaluate later.
  • View the feature from the customer's point of view - at this stage, since we're looking at features (rather than infrastructure) we're suggesting features only from the point of view of the customer. "If I were a customer I'd love it if the product can do X (and define X)." This is the part that relates to Bill's article.
  • Don't dig too deep - while we're capturing input on the ideas, don't start speccing the whole idea out - we just need to get the gist of the idea to prioritize and evaluate it. We can dive into the nitty-gritty of what the feature does and how it does it later. This requires a moderator to call "time out" if the topic strays.
  • Use end-user input data - During the brainstorming phase we extensively used the vast amount of research data KA collected during our initial proof-of-concept phases. What did users stumble over? What did they have a hard time learning (IE not intuitive)? Where did the product complexity not solve their problem or issue? What suggestions did THEY have for improvements

After we concluded our brainstorming session we had over 70 new features to evaluate. Note I didn't say add - we still needed to look at what is more important, what is easy or hard to do, and whether the addition of a feature adds or removes user complexity and capability. Obviously the budget doesn't support all these new features so we also have to prioritize them. I'll address how we went about that process in my next post. In the meantime be sure to check out thinkinglikeacustomer.com - it's an awesome blog.

Friday, December 5, 2008

What does it really cost....

One of the most frequent enquiries we get from web and software entrepreneurs is "how much would it take to build something just like X". Leaving aside the implication that you could penetrate a market someone else has already occupied with a "me-too" product, in most cases the would-be entrepreneur can answer this question themselves! It's actually really easy in today's world. Let's say you wanted to build a product just like the popular restaurant reservation system Opentable.com. (Or just like it with some difference or tweak you think will make it better). Here's how you find out what kind of investment you'd need to make to build it:

  • Fire up Google.
  • Now put the following phrase into the search box: Opentable venture funding. You can also try Opentable angel funding.
  • The first article that comes up is a press release from Open Table indicating that they received in 2000 a $10M venture capital infusion, after a $2M initial angel and VC round.
  • The $2M was probably pretty close to the cost to build out their initial demo/proof of concept and implement it in a small controllable beta (probably by region), and some portion of the $10M was used to make that scalable, fully featured, and to build the sales, marketing and business arm of the company to make it huge. There was probably an additional initial investment in Friends, Families and Acquaintances dollars (typically under $1M).

You can use this same methodology to find out the initial venture funding of most of the companies out there that have received venture dollars in the past. Sometimes you have to dig a little deeper, or you might have to go through a few articles to find either the actual or estimated dollar amount (except for public companies they're not required to report it). Alternatively you could look at other similarly scaled apps and check their funding.


The mix of how they spent their venture might be a little trickier, but most start-ups are spending the bulk of their initial cash on initially building software, and the bulk of their second round on infrastructure, scalability, marketing and sales. A me-too product would probably have to spend even more money on marketing and sales to be successful, since they'd have to fight off competition the first company into the space didn't have.


So what does that mean for the would-be entrepreneur? It means you'd better have something so interesting, new and revolutionary that no one else has thought of it if you expect to get funded and bring the product to fruition. Google took over the search market from Yahoo by presenting a simple semantic search interface instead of yahoo's structured/categorized search. It changed the world, but most of the success stories today are for new ideas no one ever thought of before.


Assuming you do have that revolutionary idea, be prepared to invest some serious dollars into making the thing a world-wide success. Treat the development effort and the business model development as the serious task that it is. Do some due diligence, market research, business planning, and specifications work before you jump into the development process feet first. Be sure you're prepared to stay the course and hear NO a lot before you dive into the Venture and Angel Capital fray - there are a very few applications that get funded, and the better prepared you are the more likely you'll be to be one of them.

Wednesday, November 26, 2008

DotNetNuke Corporation gets Series A financing

According to CMS Reports DotNetNuke Corporation whose principals are the progenitors of DotNetNuke, the open source platform that OS-Cubed does much of it's customer facing web development on, has acquired Series A Financing from August Capital and Sierra Ventures. Sierra originally invested in companies such as Symantec, Cisco, and Barnes and Nobles. August has invested in more recent start-ups such as Splunk and eBates.



"This initial funding comes at a key juncture for DotNetNuke Corporation, as the use of DotNetNuke continues to accelerate and we must scale to meet the needs of our rapidly growing community and ecosystem," said Shaun Walker, Chief Architect of DotNetNuke Corporation and original creator of DotNetNuke. "With an impressive track record of growing early stage companies into market leaders, August Capital and Sierra Ventures represent valuable partners and resources for DotNetNuke Corporation. We look forward to working closely with these firms to build on our past success and strengthen our position in the Microsoft ecosystem."



At the same time DotNetNuke Corporation announced that they will be releasing a "professional edition" of DNN 4.9 which will come with technical support and official bug-release level backing of the company. In keeping with the spirit of the open source development model, the core elements of the commercial distribution will continue to be licensed under the permissive BSD open source license and the company will work continuously to provide new innovation and increased value in the free, open source core product.



OS-Cubed looks forward to exploring just what this means for the future of DotNetNuke, and are excited to see the product move into the professional arena. We congratulate Shaun and the other DNN inventors on their success, and hope that same success extends to our clients who continue to use and create awesome software on the DNN platform.

As an amusing sidenote, the blogger suggestion for correcting the spelling of DotNetNuke is "Detonating" :)

Thursday, November 20, 2008

Do you remember this?



This month in 1977 the Cray 1 supercomputer was released.
It was 6.5' tall, and almost as wide
It cost 8.8 Million dollars
It did 80 million floating point operations per second



The PS3 pictured above cost $399
It is barely 1' tall and 4" wide
It does 218 BILLION floating point operations per second


So the next time you complain your computer is slow...... think about it.

Saturday, November 15, 2008

What to write on next....

I've gotten some interesting requests for topics to write about. I thought I'd put it up to my readers for comments about what items they are most interested in hearing about:

Some great ideas from Sharon Flank:

  • How do you be sure your entrepreneurial site is secure and can't be used for illegal purposes?
  • Should you partner with an outsource firm that retains some ownership in the final product?
  • Outside reviews of scope to help control scope creep
  • Reserving development dollars to implement ideas from user testing
  • Software documentation do's and don'ts

Other ideas:

  • What makes a great programming team?
  • Version Control: protecting your assets and maintaining a development audit trail
  • FFF funding - opportunity and challenges
  • Why use the Microsoft platform
  • Mixing open source and proprietary software

What are your ideas? What would you like to hear about next?

Wednesday, November 12, 2008

An agile programmer team room

I've been reading and admiring the quick article on http://www.scissor.com/ about building an Agile Programming team room. While we have many of the same elements in our development environment there are many ideas here that I'd love to steal er borrow :)

I was surprised by how much their offices look like ours. We also have an open floor plan, tons of natural light, dual monitors at every workdesk, lots of available whiteboard space. One of the things I loved about their space is the overall storyboard with colored cards, and the weekly iteration rollover plan. Very nicely laid out.

Agile or XP is a methodology frequently used in early stage (and some late state) startups to rollout product effectively, iteratively, and with stable solid builds. The idea is to rollout stable usable versions of the application almost weekly. OS-Cubed's methodology definitely adopts many of the great ideas of XP, but we're always learning new things about how best to develop software.

I'm going to challenge my programming team to take a look at this and see what elements they feel might help them keep on track and develop better software. Thanks to scissors.com William Pietri for revealing some of their "inner geek"...

Followers