In the final discussion, we will run through several implementation strategies which customers can follow. We break down the development base on the area of expertise of the web developers. A proposal guidelines are included in the blueprint to make sure web developers who are reading it, understand what to deliver in their proposal.

The first draft of our web blueprint has been circulated to others to gather feedback, so that it can be finalised. After each discussion, the blueprint will be updated and made ready for final submission.

Web blueprint discussion

After the presentation of the revamp goals, what’s next?

Many vendors walk in and out with solution that over promises many features, which may not solve customers’ problems. Some vendors would present themselves as consultants and start describing how the future of the web would be, not unlike fortune-tellers.

After several rounds of interviews and extensive studies into existing process flows, we managed to ‘diagnose’ the goals to revamp their website and the various measurable performance indexes of their website. Yet, managing the client’s expectations, which includes how the website would function, the cosmetic issues, the usability issues will be very crucial and needs to be addressed before the first line of programming code is written.

To better communicate with the clients, the client would need to look at a prototype. It could be sketches, storyboards or designs of the system interfaces. While presenting the prototypes to the clients, the clients would be able to assist us in providing any feedback that was missed out from the earlier stages of discussions. These feedback are then collected before the interface design is finalized. The process flows of the proposed revamped are also determined at this stage to make sure that the newly revamped site achieves the objectives.

Sketches of user interface prototypes from an actual discussion, image intentionally blurred to protect the privacy of our clients ;-)

If you are a web developer and is interested to see how we can add value to your existing services, let’s meet up!

A web blueprint project is a huge undertaking that usually requires various kinds of expertise. The blueprint defines the goals that need to be achieved, and includes hand-drawn interface designs.

How can web developers and web-design freelancers participate in the web blueprint project?

Well, the project is carried out by web developers appointed by our web blueprint customers. Here is an outline of the types of expertise required from draft to interface design:

The deliverables in Stage 1 of the Web BluePrint is a presentation of our findings. The revamp goals are identified and the reasons behind their selection are also discussed. Once everyone agrees with the goals, we will start writing the blueprint.

Listing and prioritising of revamp goals

First, we will interview people in the management level, such as: CEOs, managers and heads of departments. It is important for us to understand what their responsibilities are in the company.

Second, we will meet up with staff who work in the front-line. They will have first-hand information on feedback from customers. We will then try to cover every region, since each of them will have their own work flow and tool preferences.

Lastly, we will approach their customers directly for feedback. We will also study the website statistics and enquiries submitted by visitors.

Have you read Eisen’s post “A Case for Your Web Development Project”? Well, we’re pretty excited to announce that we’ll be developing a comprehensive web revamp plan for one of the property developer in Malaysia soon! The entire process is expected to take at least 4 weeks.

For the revamp to be effective, a need-based study will be conducted to gather feedback and suggestions from their various profit and cost channels such as sales and marketing, showrooms, operations, management, information technology and clients.

Our information gathering methods will include brainstorming sessions, interviews, surveys, collection of website statistics and archives, and much more. The process can be detailed in two main stages:

Stage 1 (which will take approximately 14 days)

1) Listing and prioritising of revamp goals

2) Identifying the goal’s conversion rates and its measurables

Stage 2 (which will also take approximately 14 days)

1) Preparing the revamp blueprint document which outlines the project’s requirements, technical specifications, design guidelines, database, integration and other features that will help achieve the goals defined in Stage 1.

2) The materials in the blueprint will be used by appointed web developers as the guideline to execute the revamp. The blueprint can be given to any web developer for the actual site development, but it will create the same result, as planned.

Are you a web developers or freelancers? Register your profile

We took on a project to design a website for a public listed company called Wawasan TKH.

Wawasan TKH Revamp