Technology Evangelist— Internet futurist, Web 2.0 lyricist, and a Web 1.0 veteran.

Tuesday, July 25, 2006

Who is Mike Johnston?

My name is Mike Johnston, a Technology Evangelist— Internet futurist, Web 2.0 lyricist, and a Web 1.0 veteran.

Do you know how many companies create a website hoping to increase sales or generate leads but end up with little or no return on their investment?

Well, I help companies create compelling and profitable online user experiences using “outside the box” strategies and tactics. Fortunately, these strategies help a large percentage of my clients increase their site traffic by more than 200% and improve their conversion rates by more than half.

However, it's about more than just traffic and conversion. My clients begin to understand that a compelling online user experience will give meaning and value to their products and services. Not only does this benefit my clients but their customers as well.

How can I help you start thinking differently about your website? Contact me today for your free consultation: learnmore[at]mikejsolutions.com


Tags: ,

Are we qualified to call ourselves Web 2.0 experts?

At MikeJSolutions, we consider ourselves experts at web architecture and user interface design. We've been doing it for almost 20 years. Over that time span Mike Johnston has produced successful projects for clients such as Turner Broadcasting, Web.com, AT&T, CSX Railways, Hartsfield/Jackson Airport and Lucent Technologies just to highlight a few. In terms of programming and innovation we pioneered "drag n' drop" using asynchronous Javascript [AJAX] via a web browser in 1999 (Soholaunch). This is not new technology, as some would lead you to believe. It has simply been embraced by the standards community and is referred to by a cool new acronym. So, are we experts? If 20 years worth of experience and millions of dollars in revenue generation (with no VC money) doesn't do it then your definition of expert lacks clarity.

Ruby on Rails, while a fantastic time saver and truly unique technology, simply makes it easier for lesser programmers to create complex database interactions more rapidly. The next time you engage a "Ruby" expert ask them to supply you with a documented database design for your application. When building a web application you need to engage a company that understands relational and normalized database design. They should be able to document that design appropriately prior to building the application not simply make it up as they go. This is after all the "meat" of your application.

In reality, Web 2.0 is a philosophy that combines a specific design trend, asynchronous Javascript [AJAX] and programming short-cuts like "Ruby on Rails" to promote itself as something bigger than the Web of 1999. It has been made real to many in the industry because other browser technology has simply caught up to Microsoft (the truth hurts young coders; Microsoft embraced the DOM model in 1997). As most VC's will tell you, it is in fact a great time to be in the internet business but you still need a revenue model. The problem with Web 2.0 as a "group" is that it's simply a new generation of users (young and inexperienced in 90% of the cases) who believe they can create web applications and services without a revenue model to support it.

There will always be rock stars like 37 Signals. I love Jason Fried and what he and his group are doing. The fact of the matter is that a good idea for which people are willing to pay money for will always be successful. That's not Web 2.0- that's business. I think Jason would agree.

God forbid anyone take advice from a Web 1.0 veteran. From the new generation's point of view, all we talk about is ROI and revenue when clearly the answer to building a successful Web 2.0 company is to dismiss all planning and build something for the sake of building it. I suppose "if you build it they will come" is a new Web 2.0 ideal that has never been thought of until now. Holly shiitake why didn't we think of that?

For MikeJSolutions, we look forward to a continued tradition of providing our clients with online success by focusing on building properly architected, usable and elegant web sites that generate a positive return on their investment- regardless of the technology in use. For all others seeking to be the next 37 Signals we sincerely wish you luck and good fortune. Just shut up and do something because talk is cheap.

Wednesday, May 17, 2006

Featured as Design Meltdown Example Site

The MikeJSolutions Version 1.0 web site has been featured as an example of excellent web design at the design inspiration web site Design Meltdown. The site design has since been archived and we are not using it but we are still very proud of this honor. You can view the website design at http://www.mikejsolutions.com/stripes.php and see the featured page at Design Meltdown's Stripes Example Section.

Autopsy of an Overcooked Product

In late 1999 I founded a startup called Soholaunch. Fresh off of the dot-com success of that time period the vision of the company was to make it easy for the common person to create and manage a website. To this end I single handedly built what is, still to this day, arguably the most feature rich and comprehensive online web site development and management tool around. But I bet most of you reading this have never heard of it. It covers the gambit in features, capabilities and scalability. Soholaunch is still alive and well today and being run by my former partner, Mr. Jim Buckler. We are still very good friends and speak quite frequently. I walked away from Soholaunch after four years conceding that it was a failure (I really hope Jim proves me wrong). What did I learn? I learned there are three critical things that must happen for a web application to be successful (Jim this could be helpful).

1. Focus on doing one thing really well.

The Soholaunch product has so many features that it is just impossible for the company to be an "expert" in all of these areas. It's an overcooked product. The "Swiss army knife web site builder" is one of its greatest marketing assets and one of its biggest operational weaknesses. Do you know how long it takes for a sales rep to describe what Soholaunch does? An average pitch meeting or demo could be two hours long. Forget trying to educate consumers on how to use the damn thing.

You should be able to describe your product in less than two minutes from top to bottom. If not, it's probably not focused enough. Based on this description users should have a 98% ability to use the product without any education or assistance.

2. Stay true to your vision.

When we first started Soholaunch it was a hosted application. Every indication showed that thin-client computing or web-based applications were clearly the future. The problem came in mid-2000 when the dot-bomb happened. Suddenly there was a mass exodus from the Internet. The question of the day was, "what if you guys go out of business tomorrow?" This prompted us to change our development strategy. Soholaunch became (and is to this day) a product that you can download and install on any php/mysql-hosting environment. This increased support costs; increased development costs and complexity; but most of all de-valued the intellectual property. It also changed the business model, target market and vision. At that point we had to sell to developers who could install php code and manage mysql databases. The vision was changed overnight and by default impacted the entire business model.

Be flexible with your development and business model but stay true to your original vision. If you do not know where you are going then you will certainly have no idea how to get there.

3. Sell to the end user.

Using reseller channels and distributors to sell and market your web application will be a disaster. These channels will never support your product properly and you will almost never hear feedback from the end users. With Soholaunch we spent many hours modifying source code for provisioning into hosting companies. We were suddenly in the business of building custom provisioning systems for hosting companies and not being paid for the effort. This was a fatal mistake. We spent months enabling the product to be put in front of thousands of consumers and it would fail to sell. The end-user experience was awful and the hosting company had no clue how to support a web application.

Sell and market your application directly to the people who will actually consume the product. Use their direct feedback to improve your product and enhance the user experience.