Creative Fuel

When is a website “done”? Is it ever? One of the great things about working in web design is that we have the power to endlessly edit, change, update, and improve our sites. While some may complain about this so-called “constant state of beta”, I see this process as an opportunity because it encourages an active dialogue between user, client and designer, ensuring that we are addressing priority concerns.

The Issue with the Traditional Development Process

The traditional model for project development involves clients approaching designers with a project plan that includes detailed specifications. The designer designs and develops the site and has a brief period of testing and QA before the site goes live. While this is a straightforward process,it disregards the fluid and evolving nature of the internet. The issue with the traditional development process is that it is static; and it is more difficult to address user needs, because there are fewer opportunities to solicit feedback. Often user feedback cannot be addressed until the next time the designer is called in to update or upgrade the site.

The Internet is an interactive, evolving platform; a landscape that keeps us upgrading, downloading, rebooting, updating, and redesigning to suit industry needs, trends, and changes. When we design a site, we need to know that the product is one that meets not only the client’s needs, but the needs of whoever they are serving. The stakes for this can be high--and are often reliant on the feedback we get during the development process.

Taking Advantage of the Evolving Nature of the Internet

We prefer to approach the process from the customer’s point of view. What product or service is the customer looking for? What might have brought them to the site? How can we ensure that we are delivering what they want in the simplest way? What techniques can we use to promote the site, its products, and the client we are serving?

To address these needs, we borrow a practice from application development called Agile development. We develop the core features to 80% of their capability, then release them to gather customer feedback. We solicit reviews, address new concerns, and test and refine site features. In essence, we repeat the development cycle, redevelop according to user and client feedback, and build out the site in such a way that truly represents the client’s needs and answers customer questions.
Visit our Development process page for more information on our process.

Agile Development or a Constant State of Beta

As designers and developers, we need to be in constant conversation with our clients. At Creative Fuel, we see the “constant state of beta” as an expression of our commitment to excellence. This is why we maintain our client relationships beyond the go-live date: we know that websites, like any product or work of art, are ceaselessly editable; they’re never done. Even after you go live, there are always more changes to make.
View our portfolio page to view some of our recent projects.

The good news is, we’ll be there with you, ready for that next big change.
Contact us to start your project.