A Close Look at Software Goals

Justin Rouch and I have been hard at work on a new platform called Guild Press.

Over the past few months we have been hard at work on establishing goals, creating the business, developing our plans, developing the software and figuring out our feature list. This isn’t an easy undertaking by any means. Especially as I’m looking over our original feature list.

When we first started brainstorming all of the features we wanted to see in Guild Press it became clear that the platform was going to be rather large. The worry wasn’t that we’d over complicate everything but rather that we couldn’t do it all or that we weren’t adding enough value to compete with some of the big players in guild site hosting.

My initial thoughts were that we needed to match feature-for-feature the competition and that we further needed to out-due them.

Here we are a few weeks later and I’m looking at the original feature list we compiled. We’ve added even more items to it and I’m starting to realize today that I am making a mistake that I think many other entrepreneurs are as well. Justin Rouch had some interesting thoughts when we spoke recently that we didn’t want to go all in right at the front of the product.

We are now able to focus on the biggest issue that our customers have told us they want us to tackle and later focus on the other features. This allows us to reduce our initial workload as well as build a new customer loyalty.

By not putting everything in the beginning of our product we are giving ourselves a chance to collect feedback, giving ourselves new features to develop in later revisions and keeping the novelty of what we’ve developed.

When Apple releases a new iPhone they release with a few new features that have been asked for in the past. I owned the iPhone, iPhone 3G and the 3GS. Each time a new iPhone is released a few incremental updates are made. These updates typically produce an applause from the crowd. The iPhone becomes novel again.

Apple likely can and does develop several new features for the iPhone each year but only rolls a few of them out at a time. This keeps the line fresh. This keeps it novel.

This creates loyalty and when you are buying an iPhone you are typically buying in to the promise that it will improve with each version and not just for the particular model you picked up.

This idea of creating the minimum feature set seems so simple yet can be so easily overlooked.

While we know that Guild Press in the early stages won’t meet the needs of every person who stumbles upon it we do know that we will be creating a group of very loyal first users. These are the people who are going to help lead the development cycle we decide to take.

This group of early users will help shape the product, will understand the development cycle and will also understand that many more great things are coming in the future of the product.

It seems risky. It is. We are essentially culling a group of users for the purpose of developing the product. We are allowing them to be in on the ground floor. They will be with us for the first minimum feature set but if we do things correctly and make them aware of what the Guild Press goals are early we understand they will be loyal and that they will help us develop the product.

What are your thoughts on this idea of developing for a small early group?

Related posts:

  1. Keep The Landing Simple
  2. The GPL and WordPress
  3. Share: Invest BEFORE Product/Market Fit, Double-Down AFTER.
 banner ad
You're a moderator for http://rayangel.com Site admin
You're following this conversation Unfollow
Conversation 
Sign in and Post
Ray moderator
Pending approval

Steve, You've hit the nail on the head with our goals. I think you've summed up exactly our thoughts on this matter perfectly.

Approve comment
Ray moderator
Pending approval

Ryan, Thanks for the link. Just read it over and I found it a most excellent read. I think for our approach on Guild Press we are going to be very deliberate on who is in at first and who isn't. We've thrown up some surveys and other actionables on our Facebook page to help us determine who will be our first core group of users. Those who interact with us, email us, take the surveys and offer advice are those likely to be in the very first wave of the product beta. We are going to provide several outlets for providing feedback but I think the best one we can have with the first small group is just direct contact back and forth. The idea being that we can open a direct conversation with these people. We can then listen to what they say and hopefully have a good two way conversation with them as to what the needs are. Thanks for your remarks Ryan. I like the thoughts you've put down here.

Approve comment
Steve Franks moderator
Pending approval

Well, Ray - you can probably guess that I'll agree with you and Justin about getting to market as the number one priority. A few thoughts to clarify what I think you are saying (and with which I agree): 1. Once you are in the market, you will get direct feedback about what features should come next, as opposed to guessing today (and delaying getting to market). 2. Good customers don't want a feature for feature match from a new product (actually that would be mostly a boring undifferentiated product even with a new kicker or two) - they want you do a RADICALLY BETTER job on the features / wants that matter most to them and provide the most value. 3. You will be releasing later versions no matter you launch with. This is not a one-time roll of the dice. Why not save some features to make later versions more valuable. 4. By definition, your early users will "get it" that your vision goes well beyond the minimally viable product. 5. Not trying to do everything by launch lets you focus on a smaller feature set, and increase the odds that you'll nail the launch features - the RADICALLY BETTER ones that set Guild Press apart. Have fun! - Steve

Approve comment
Ryan Imel moderator
Pending approval

Good thoughts, Ray. I like how you guys came back around to a simpler, at least initial, feature set. The focus on one thing, get one thing done really well, reminds me of this piece on Posterous I read earlier in the week http://blog.dustincurtis.com/i-dont-laugh-at-startup-ideas-anymore I like the idea of a small early group, especially for something like Guild Press. How much of organizing an early group is really deliberate, though, and how much will happen one way or another? I would assume anything starting up is going to have a small group of followers, no matter what, for the first year or so. Should the early group be dealt with explicitly -- setting up something where they can provide feedback, in a way that they know only they are being asked? Or is it more of a natural process, where you let them in and listen for the pains over time? I'm not really going anywhere with these thoughts, but thanks for getting me thinking them.

Approve comment