I feel this year I’ve been blessed. I have a client who has been amazing to me. His idea isn’t new, but his approach is fresh and well-conceived. And his attitude towards doing business is total win.
This has made me happy to work for him and continually trying to do a good job. The project is currently ongoing, but we launched it way before it could be classed as finished.
This was an interesting move, but quite necessary from his point of view. And he didn’t put any roadblocks in the way.
Other clients I’ve worked with however seem to find any number of things to put in the way before a launch. And it got me thinking about my own projects… will I have the last-minute jitters and hold off shouting about something because I don’t feel it’s quite “ready”?
I believe something to be ready when it’s usable. This could be late-alpha/beta stage. There are bugs sure. Probably some we haven’t found. And it’s not fully polished. So technically Ready != Finished. A lot of software companies are starting to come around to this view.
It seems that the driving force behind this is that extremely valuable user feedback can be generated, even without users realising how they’re helping. You can start to shout about your app (or whatever) and get some helpful input.
The greatest thing about this is the feeling you can give your users that they have the power to shape the product. They almost make an investment in it, intellectually. This could cause even greater user loyalty than other forms of investment - emotional (attraction) or financial (purchase).
So I’m determined now to get stuff launched! Even if it isn’t “finished.”
Tweet
Finally I’ve got 5 minutes to write about the project I worked on last week! I still can’t reveal what it is yet, but an official relaunch will be happening soon.
I think it’s safe to say though that we succeeded - we rebuilt the thing in a week using CodeIgniter.
Tweet
Challenge: Build a Web App in a week using CodeIgniter
Real challenge: I’ve never used CodeIgniter before
Tweet
Recent comments