News Flash

Dev Tip: When using jQuery on your site, link to the source at http://code.google.com/apis/ajaxlibs so your site loads faster

Tagged: start-up

28 January 2009

So you’re a skilled developer or design freelancer who has established a handful of customers who pay your bills and provide you with an income. That’s great. You may wish to keep things just the way they are or you might want to build on this and build up your own small business. If you’re opting for the later then here are a few tips to help you ride the bumpy road from freelancer to fully-fledged small business.

1) Move Out of Your Back Bedroom
If you are moving from freelancing to running a company then you need to show your potential customers that you are 100 per cent committed to the business, thus allaying their fears that you won’t be around in a few months time. If you can, move from your home workspace to a dedicated office. This doesn’t necessarily mean huge expense but it can instill a great deal of confidence in you from potential clients. Depending on where you are, office space can cost from as little as £130/month ($190) and should also help with your work-life balance. An additional benefit is that it will give you a postal address that you can publish on your stationery and website without revealing your home location.

2) Dress for Business
Now that you’re running a business (for better or worse) you will need to take a look at your appearance. Many may disagree, but personally I think nothing says business more than smart dress. Of course, it’s up to you how you dress but think about it this way. If you want the conversation to centre around your professional skills, don’t wear anything that will steal the conversation away from this. A T-shirt with a witty slogan on it may be just the thing for a night out with your mates, but a lunch with a potential client? Maybe not. Why do anything to stack the odds against your company winning the project?

I am happy to accept that this is a controversial subject and would be very interested to hear your thoughts about this. What works for you? Do customers react to you differently when you are wearing smart dress as opposed to casual?

3) Centralize your Data
When you are a freelancer working on your own it’s fine to store information about your work processes in your own head, or contact e-mail addresses in your personal AddressBook. But the moment someone else is involved in your business then this isn’t good enough anymore. You may start to find that you spend a lot of time imparting knowledge to others. You will need to move that knowledge somewhere where it can be easily shared. For example, Highrise (www.highrisehq.com) is great for keeping a database of your customers and tracking conversations/activity with them.

As much non-skill related information should be documented as possible, this will assist you in building business processes to ease any future expansion that you may have planned. You should encourage others working with you to do the same and attempt to cultivate a culture of ‘centralised knowledge.’

4) Be the Person Your Customers Like
Building good relationships is key to running a successful business. There are thousands of web development/design studios in the country and there’s nothing to stop your customers moving to your competition if they feel they are not getting value from you. People rarely choose based entirely on price. They buy from people they like and whom they think will support them in the best way. It’s this support that will win you a customer for life (even if your services are more expensive than your competitor’s). As a general rule you should try the following:

5) Reply to Emails Promptly.
Even if you cannot compile a meaningful response/resolution immediately then acknowledging the message with a reply will let the customer know that you are on the case.

6) Always Return Voicemail Messages.
This is really important. If a customer knows that based on your history that you always call them back after leaving a voicemail then they will not feel the need to keep calling you or bombarding you with email. This can help alleviate stress in busy periods when you deem answering the telephone of secondary importance.

7) Maintain a Verbal/Email Relationship.
You should contact the customer on a regular basis (every 3 months if the job is over) to inquire how things are going. This will help to make the customer feel important and that you are still interested in their business even though the project is finished. It will also help to keep you in their mind for future projects. Try to avoid a sales push with every contact else this goodwill will be broken and they will dread your calls.

8) Express Interest in your Client’s Business Sector.
Keeping up with trends in your customer’s industry can be invaluable in generating recurring revenue from existing streams. Tracking changes in their business will allow you to suggest improvements or additions to their application or website. This can be as simple as following their RSS feed and needn’t take up much of your time.

9) Welcome Customer Complaints.
Complaints are great! Complaints allow you to fine-tune your business so that future customers don’t suffer from the same irritations. You must handle every complaint about your business seriously and be prepared to make good on any deal that a customer doesn’t feel you’ve delivered on.

10) Don’t be Afraid to Pass
Many people believe that you should never turn down work. I disagree. If a potential customer is looking for services that you know in, your heart, are not your speciality then don’t be afraid to pass the work on to another trusted freelancer or business. Although not earning you revenue immediately it will benefit you in two ways:

Firstly, you will earn the customer’s respect for passing them on to a
3rd party. This will show them that you are looking after their needs rather than taking the money and delivering a poor job. You will be surprised how quickly you become a ‘trusted advisor’. And Always send a follow-up email to the customer a few weeks into the project inquiring about how things are progressing with the 3rd party and ask them to keep in touch.

Secondly, forging strong relationships with other companies and freelancers can pay dividends in the long run. Approaching a 3rd party with a business lead will buy you a great deal of goodwill and allow you to introduce yourself and services to that person with a view to working together in the future. Networking is the way that you might get your next big job.

11) Work on your Sales Technique
Working on improving your sales technique with prospective clients should be something that continually evolves throughout your career. There are no strict rules for selling; you just need to be better than your competition! You can be the best programmer in the world but unless your potential customer likes you and is confident that you can do a great job then your skills and experience will count for zero. Here are a few ideas to get you started:

12) Build ’stock’ proposals.
Especially, for common projects such as content management and ecommerce. This will save you time when pitching for a job and allow you to reply to an enquiry within a day or two of your meeting with them. The longer it is left silent between you and the customer the smaller your chance of winning the project.

13) Always be On Time.
But be aware that arriving early can be as disruptive as arriving late.

14) Learn About Personality Types.
Learn how to spot them and how to deal with different people and groups.

15) Use a Notepad to Take Notes.
If a customer sees you taking notes then they are much more likely to tell you more information about what they need.

If sales is an area that worries you then there is a wealth of great information on how to sell effectively by Warren Greshes (www.greshes.net).

Good luck with your new venture!

Thanks to www.flickr.com/photos/tanfacedprairieboy for use of the main image

Continue reading 168
Future of Web Design London May 17-19 2010

2 October 2007

welovelocal.com is a UK based social local search website which helps people find the best businesses in their area by reading reviews and recommendations from people they can trust. Three months ago we launched in London and we’re now gearing up for nationwide launch. A soft launch was a great way to get things right before we hit the rest of the country, here’s some of the other lessons we’ve learned so far:

1. Keep it simple. Stay Focussed

We knew from our initial brainstorming sessions that welovelocal.com could quickly become a local portal website covering everything from local listings to local news. Great ideas are only great if they fit a purpose, as such it is important to be clear from the outset what your site’s core user proposition is.

Once you have defined the principle rationale for your site, use this as your reference point for all future decisions. With welovelocal.com we want to help people find the best businesses in their local area, so every development decision sprung from here. Of course, when preparing the wireframes we let our imagination run-away with us, including a plethora of weird and wonderful features; but by returning to the central rationale for the site, we were confident enough to strip away any superfluous additions before development began.

2. Do Your Homework Properly

welovelocal.com was originally set to be called Local Insider. Four weeks prior to the launch of welovelocal.com and we received advise from our legal team that if we proceeded with the name, we would run the risk of a legal challenge from a major UK Newspaper Group, who owned Insider.co.uk, a business publication trading within an overlapping trademark category.

In retrospect, we were super-naive to get so far without getting the final approval. We had initiated a precursory trademark search when we first finalized the name with our web designer, however, as always, legal matters tend to take longer than you could possible envisage, hence why we began work using the Local Insider name. My advice, sign off any legal concerns prior to starting any branding in relation to your site. It may not be fun, but put legal advice to the top of your list of things to do.

3. Make it Sociable

Thanks to feedback from lonely users, we realized very quickly, that a site with a community element is no fun if you’ve got no mates. Indeed, we were kind of blown away by the popularity of the limited social networking features we had implemented. Our goal was never to become a full-blown social network, but rather to leverage the ecosystem of a social network to help people find businesses recommended by like-minded people. We had already made a big effort in the site design and functionality to encourage new users to invite friends and family adding regular prompts where appropriate and import contacts functionality from major email clients, however we learned that people were eager to find new local friends on welovelocal.com

In response, we moved quickly to introduce ‘Locals’, enabling members to automatically access recent reviews local to where they live and check out the profile of other individuals regularly reviewing nearby. Following further feedback, we have since also launched Groups, enabling people to discuss more openly on a range of issue.

4. It’s the Community, Stupid

With a soft launch we anticipated a small amount of correspondence with some of our die hard members, but overall expected just a small percentage of our members to stay in regular contact. In reality, we’ve been blown away by the passion of our members and the incredible value they have added to the development of welovelocal.com.

What we’ve learned is that members deserve a lot of attention, and the need to plan for dedicated support for site members is essential. With a site heavily dependent on user generated content, you’re effectively nothing without your community; they’re your greatest asset and your strongest marketing tool, indeed, there are countless articles on Vitamin and beyond that support this. Our approach has been to quickly reward our community with surprise gifts and other thank yous, as well as adopting a mantra to always respond to any query as fast as humanly possible.

5. Listen to Feedback

Prior to launch we had tested the site with a range of strangers and friends, and feedback, give or take a few curve-ball suggestions, has been as expected. For our business users, we recently organized a local meet-up of small business owners to get their feedback on how we hope to develop the welovelocal Business Centre.

Getting to know our business users was a real eye opener. The message was clear: Time is money, and welovelocal.com can have all the widgets, APIs and add-on features you like, but ultimately, as far as welovelocal.com is concerned their overbearing concern was how much traffic and how many customers the site could deliver. Of course, we knew this was the case, but it certainly underlined and reiterated the need to be 100% clear what your motivation is for any site developments. As we begin work on updating the Business Centre, providing clear stats to demonstrate leads we have generated for business users will be our priority.

6. Get Sticky

It may sound a little defeatist but no matter how excited and passionate you get about your site, you’re just another URL in an ever expanding Web universe, so plan to work with this.

Very few sites demand everyday/regular use, so working out how to improve the ‘stickiness’ of your site is vital. Notably, how can your site complement, or better still enhance, a user’s existing Web habits while reinforcing the core rationale for your site in a meaningful way.

Building a Facebook application quickly was a top priority, enabling users to share their reviews with other their Facebook friends and let people know where they are thinking of checking out next. While we ask for people to share their experiences with us, we don’t expect to be the defining reference point of their digital identity, as such, we are now working on a range of tools and widgets to complement our user’s existing Web habits. With the ever increasing widgetization of the Web, being flexible with your site content and the manner you collect user generated content should be fundamental to way your site engages new users. We really don’t care whether our members interface with welovelocal.com, from an iGoogle homepage, Facebook application or whatever widgets we plan for the future, the key is they are using our content to find the best local businesses.

7. People expect you to be as good as Google. Deal with it

The Web has got a lot better over the last few years, and people’s expectations have followed suit. One of the biggest ongoing challenges we’re now facing is improving our search functionality. Inevitably people expect Google quality results, which is no mean feat. We’ve made a lot of refinements to our search algorithm and mined a lot of our data, but we’re still not Google; nonetheless, we’ve learned that local knowledge can go a long way.

What’s interesting with local search, notably geo-data, particularly in the UK is that very little standardization exists and colloquialisms confuse matters even more. By looking at search habits and utilizing local knowledge, we are able to apply a far greater depth of local understanding to way we sort our search data, than Google can hope to achieve, simply because we have local knowhow. Moving forward, we are investing heavily in leveraging local knowledge across the UK to do refine our search and importantly turn a potential weakness into a major strength.

So in conclusion, if you’re anything like us you won’t get everything right the first time. I think it is fair to say that some of the best sites out there have been shaped by their members and I hope with each update and improvement we will too. We’re now preparing for national launch, and just starting to build out the Business Centre for our business users, so I’m sure you’ll see more changes to the site over the coming months.

Prepare to be agile and expect your site to evolve. It’s easy to work up to a launch date in the hope that you’ll get everything right first time. Notably, through all the self-doubt, peer feedback and community response, be 100% clear what your site’s core proposition is, and always return that as your reference point for future decisions.

Continue reading 2

25 September 2007

The idea for ImThere was born in July ‘05 out of necessity—it was a chore finding fun stuff to do around town. Fifteen months and many pots of tea later, we launched a service that we had hardly even tried to use. Soon after, we began questioning if it was what we even wanted.

Last June we finally launched the ImThere we had envisioned over two years ago. We are now finally able to find stuff to do that we wouldn’t have known about otherwise.

And So it Began…

Development of ImThere seemed clear-cut. The functionality was outlined and broken up into the site’s distinct pages. We let our designer and two developers figure out how best to design and architect the site. Once we prioritized the functionality to be developed and the pages to be designed, we created a weekly schedule providing a roadmap to launch. We appeared to be off to a smooth start.

What Our Team Began With
What Our Team Began With

Our first glimpse of ImThere came three weeks later, when our designer uploaded his first pass at the main page. It looked great. That, combined with our excitement seeing ImThere for the first time, resulted in joyous expletives. Once we calmed down and compiled actual feedback, we had a list of items like:

  • “The green arrow submit buttons are too bright and distract a little”
  • “Let’s change Weekly to Daily on the featured venue/artist”
  • “It looks like the View More links for Important Events and Hot Events have different font weights”

Valid feedback, but completely focused on aesthetics and nitpick-y details.

Revisions of the Main Page
Revisions of the Main Page

As the design progressed, the developers were hard at work on the back-end. From content targeting to popularity algorithms to exotic data handling, we had very lofty goals—all to be included in version 1.0. Even seemingly simple things turned into intricate projects requiring custom code, rather than using what Ruby on Rails, the ImThere platform of choice, provided.

With three months of the back-end work complete, designs began to be applied to the website. Despite the immense back-end functionality, the front-end appeared extremely basic. The event, venue, artist, and user pages were pulling data from the database, and data could be entered through crude forms. But it was a start, and we were thrilled to finally have the developers working on something we could see. However, given the back-end functionality still needed for the launch, the front-end work moved sluggishly.

Logged In Users Saw a Different Main Page
Logged In Users Saw a Different Main Page

Another three months later, even though the website was shaping up, our position was similar. Entering data was a chore, and there were too few ways to interact with the website. Even so, we felt the time had come to release something. We rushed to flesh out the remaining pages and smooth things out as well as we could. As time ran short, we began cutting the visual elements that were not yet coded. Finally, after a 30-hour marathon coding session, we launched.

Kicking it Out the Door

When a launch finally arrives, an indefinable feeling runs through everyone involved. It’s a mix of excitement, relief, and anxiety over what happens next. In our case, the anxiety turned to eerie silence as we saw people leaving the website soon after arriving. Truthfully, we couldn’t blame them. Since many of the planned interactive features were scrapped to get ImThere out the door, there wasn’t actually much to do. And since we couldn’t add content until right before the launch, there wasn’t much to see either. Our team even struggled to use it and found little value or enjoyment.

Warning Users About What They Were Getting Into
Warning Users About What They Were Getting Into

Over the next two months we slaved over the code to add missing features, develop new ideas, and fix up the remaining bugs. The website became unquestionably better, but people still weren’t latching on. Not only that, we were even still forcing ourselves to use it. It was a bad situation; no one was falling in love with it no matter what we tried.

There comes a time when you have to accept things just aren’t working, and you need to take a step back to figure out what’s really wrong. After just a few months, we had reached that point.

Taking a Step Back

At first, we were confused as to what the problem was. We had successfully implemented the functionality we had originally defined, and the few remaining missing elements couldn’t explain the state we were in. The website looked great, so that couldn’t be the problem either. After dragging ourselves away from development for the first time in nearly nine months, it dawned on us what had happened—we had taken a feature list and developed it into a website.

What we built had very little flow to it and felt forced. Each page seemed so disparate from the others that users couldn’t get the big picture, let alone find reasons to use it. It felt like a bunch of random features bundled into the form of a social event-themed service. The problem became even more apparent when we struggled to recall what the original vision was. The feature list not only dictated the design and development, but also became our guide to describing ImThere to others. We were in trouble.

The good news was that it was easy to see everything we had done wrong:

  • ImThere was built and designed around a feature list
  • Aesthetics were the focus of the design, with little thought put into actual usability
  • Coding the high-concept back-end consumed nearly all of developer time
  • We tried to do too much for a version 1.0 website, and didn’t have the focus to pull it off
  • We never really tried using the website before launch, due in part to its incompleteness

Taking those missteps resulted in a myriad of problems:

  • ImThere felt one-dimensional and lacked continuity, preventing it from being useful or fun
  • The purpose of ImThere was unclear to users
  • Users would have to adapt to using the website since few things were intuitive
  • Much of the advanced back-end was left unexposed in the front-end

Our brand new website was fatally flawed. It just felt wrong and no amount of Band-Aids could fix it. Furthermore, in the meantime, a number of other social event services launched. When ImThere was originally envisioned, none existed. Now, in addition to problems with the website, much of our originality was lost. Our next move was obvious.

We had to scrap it.

That was remarkably hard to do after putting so much effort into something that had barely seen the light of day. We knew we would have to reinvent and completely rebuild ImThere, while being cautious not to repeat the same mistakes. Of course all websites iterate and iterate, but we had to do it in an extreme way. And do it we did.

Getting it Right

Before telling the team to scrap everything they had coded and designed, we first wanted a plan that was solid, realistic, and fully thought out. We began by focusing on the useful and fun qualities, which fortunately came together quickly. Our efforts also focused on overcoming the limitations of launching city-by-city, which our initial plan called for. A solution did come to us, and ended up being the cornerstone for the new ImThere. We would support “locationless” events in addition to local ones, which could include things like movie premieres, the release of the iPhone, Talk Like a Pirate Day, and even virtual events. These events could be relevant to anyone, allowing a ‘net-wide launch and providing ImThere an identity distinct from our new competitors.

Feeling confident about our refined and solidified vision, we set out to really plan it. This time we were determined to avoid the same traps. We locked ourselves in 24-hour coffee shops for a couple of weeks and extensively planned out every page. We would keep sketching out each page until we had it just right, and flesh out wireframes in the fantastic OmniGraffle application.

The First ImThere Wireframe
The First ImThere Wireframe

A big theme for the new website was reusability. Many elements like feeds, content streams, listings, and timelines were shared on pages throughout the website. Our event, venue, artist, and user pages shared the same base which was then tweaked for their individual needs. Other pages worked similarly; determine the necessary elements, and then tweak the page for its specific purpose. This process allowed the developers to perfect common elements and rapidly build out pages. It also allowed us to reduce the number of interfaces a user had to become familiar with.

Throughout development, we anticipated the various ways a user might use ImThere. For each page and feature, we thought about how a user would discover it, use it, and continue on through the website. When we were done, ImThere felt fluid, open, purposeful, and fun! We went from thinking “we want to use a service like ImThere” to “we want to use ImThere.” It provided reassurance that we were doing things right this time.

The differences were obvious; this time we had:

  • Developed a complete idea, not just a list of features
  • Wireframed every page of the website, forcing us to work through the flow and usability
  • Took development time into consideration and found ways to avoid spending months on just the back-end
  • Took a step back before development started to make sure this we had what we really wanted

We had to build the first version of ImThere to know to do these things. The lessons we learned were worth every second spent and the new ImThere could not exist without them. Looking back can be tough, but you later realize you had to take the steps you did. Fortunately, we realized our mistakes quickly enough to have the time to take our next step.

Take Two

Next came getting the team onboard with the new vision and getting their feedback. Their opinions were extremely valuable, especially since it was completely fresh to them. Everyone on the team was on the same page and embraced the opportunity to have a second shot at making ImThere the service we all wanted.

Both design and development went dramatically smoother the second time around. It was more clear what needed to be built which sped everything up and made for more realistic scheduling. Wireframes allowed for more design time to be spent on usability and less time on what needed to go where. Once the look and feel of the website was nailed down, the remaining pages went through relatively few revisions compared to pages for the first website. We were able to do this not only due to the wireframes, but also to sharing elements across pages. Towards the end of development, we even had the luxury of tweaking the design, which we had no time for even after launching the first ImThere.

Revisions of the New Main Page
Revisions of the New Main Page

Visual results began shortly after coding. We were able to carry over some back-end code, reducing the time it took to start on the front-end. This allowed us to start using the website very early on, which had been one of the biggest problems before. For the first time we could find out what worked and revise what didn’t. On the first version of ImThere we weren’t even able to add events until the last week of development, but now we could begin adding, modifying, and interacting with content months before launching the new ImThere. Around this time a bug tracking service called Lighthouse was released, which made reporting bugs enjoyable and manageable. It allowed us to report, prioritize, and track every little thing that wasn’t quite right.

From 0 to 3 Weeks
From 0 to 3 Weeks

We ended up launching this past June, which was later than we had hoped. However, it was to allow us to add little features we wanted and polish the website, not to develop rudimentary functionality. About a month prior to launch, we let a variety of people in for a private beta. This was something we hadn’t even dreamt of doing with the first version. During the final month, we fixed all known bugs, finished the last of the features planned for launch, and tweaked and tweaked everything.

Once Lighthouse reported 0 remaining pre-launch tickets, we launched the new ImThere—the ImThere we all wanted.

Easing it Out the Door

After pushing the elusive launch button and drinking the obligatory champagne, we found ourselves on our laptops, sitting around a table at one of our developer’s houses. We weren’t frantically fixing bugs to keep the website from crashing, nor were we trying to code last-minute features. We were simply using ImThere and enjoying it.

As the first batch of users rolled in, we interacted with them and watched how they were using the website. They filled out their profiles, commented on events, sent messages, just explored around. No one left right away. From a statistical standpoint, our pageview to unique ratio was very favorable. That is a good sign, because even without stellar uniques, having people stick around means you are doing something right. All in all, our launch went as well as we could have hoped, and it seemed that we were finally on track.

Getting the User Page Right (old -> wireframe -> new)
Getting the User Page Right (old -> wireframe -> new)

We quickly got off our post-launch high and went back to work. For the first time, we had a solid base to build upon and could begin making forward progress. Our work over the next few months consisted of:

  • Gauging initial user response and improving the areas that needed it
  • Building the features we had put off until after launch
  • Evolving our existing features to make them more useful
  • Getting the word out to start building up our userbase

As we worked we would frequently take a step back to ensure we were on track and sticking to our vision. After our first time around, it was very important to make sure we didn’t waste a second working on the wrong thing. We were now focusing our work on strengthening the identity of ImThere, something we had failed to accomplish before. Since ImThere was designed in an open way to support a broad scope of content, it was challenging to make the value of the service immediately apparent to users. That concern drove our early focus on building utility-based features, like an invitation system, so prospective users could quickly find value. The hope is that once they sign up and begin using ImThere, they will see the big picture.

With a few post-launch months under our belt, ImThere was ready for the masses, and our next set of big ideas.

Where We Are Now

Over two years later we finally have the fundamentals in place and can enjoy making ImThere great. We are now faced with a new set of obstacles: reaching more users and demonstrating the value of the service to them. We also must keep looking into the future for ideas to maintain ImThere’s uniqueness and rapidly develop those ideas into realities. No matter how satisfied we are, standing still can never be an option.

Redesigned Signup System Based on User Feedback
Redesigned Signup System Based on User Feedback

The team is already working hard to evolve the very essence of ImThere. At the center of this evolution is the one key idea still missing from the original vision. Implementing this idea couldn’t have happened or even re-entered our minds without building the open, community-driven service we have now. With those fundamentals in place, the idea that began our journey returned, and proved to be a solution for our current obstacles.

ImThere Today
ImThere Today

This further demonstrates that if something isn’t working, you need to look back and figure out what got you excited in the first place. That is how we put ImThere back on track and why we have full confidence that it will soon be a success.

Continue reading 1

Sign Up to our Newsletter

Enter your e-mail address below to receive regular updates on web design, web development and web business. Subscribe today and receive a free 44 page PDF "Designing Web User Interfaces" by Ryan Singer of 37signals.

Subscribe to the Think Vitamin articles RSS feed

CSS3 Online Conference March 22nd 2010

News

Twitter

Follow us on Twitter

Subscribe

Article Subscribers

Feedburner blog subscriber indicator

News Subscribers

Feedburner blog subscriber indicator

Subscribe by Email

You can receive Think Vitamin updates via email. Just pop your email address in the box below and click the arrows.

Subscribe by RSS

You can also receive new Think Vitamin posts via your RSS feed reader

Subscribe RSS Think Vitamin is a proud member of the Smashing Network

Ads Via The Deck