Corti Designworks - Web & Print Design Services

CDW Approach to Web and Print Design

The first step to achieving any goal is to have both a clearly understood purpose and a well defined project plan.

Always keep the following keys to any successful project in mind: define, design, develop, test, deploy.

Each one must be clear before you plan, schedule, and initiate work. We approach our web and print project development in the following basic stages:

Stage 1: Project Requirements, Definitions and Expectations.
The most necessary, yet most often overlooked part of project development - the requirements document. It defines the user needs and functional requirements. It clarifies what is in scope and what is out of scope (perhaps deferred as a later project). Without it you are embarking on a journey without a map – you might get to your destination, but at what cost to you in terms of lost time, money, and effort.

Everyone on the project (e.g. graphic designers, developers, programmers, and project owners) must use the requirements document to develop the project. It must encompass business purpose, target user definitions, visual and contextual impact, and in the case of website design, various technical analyses such as detailed information architecture, use cases, workflow/task analyses and site flow diagrams.

Stage 2: Design/Develop/Production.
Armed with all the key requirements and directives, production can begin. Public relations campaigns, content, programming, graphic design, and marketing collaterals can then be developed concurrently. We believes that taking the time to create a working web comp (mock-ups, comps and prototypes are identical terms), developing a working conceptual version of the site or marketing collateral. and providing print comps accomplish these key goals:

It provides an interactive and realistic version of user requirements while working through the basic graph site design and programming directions.
It enables everyone to review the project progress .
It ensures client expectations and user requirements have been addressed before deployment.
It enables real time review and testing.
It provides an opportunity to reassess and refine some requirements.

Stage 3: Pre-press Deployment, and Pre-launch Evaluation and Testing.
There is no such thing as spending too much time on testing and reviews. Marketing collaterals must be error free before printing, therefore, pre-press proofs are a necessity. Websites must must function properly and be free of bugs before deployment. Making a text change to a website is a tiny effort, reprinting a job is a huge expense.

Stage 4: Website Go-live.
A website is an integral business and marketing tool. It’s imperative not to skimp on or ignore pre-launch sample testing and review, or post-launch feedback. Any necessary modifications must be made immediately.

Additional Information:

Keys to Success:

Start with a clear, well thought out objective.
Develop a realistic project plan.

Include time for delays, changes, and revisions.

Create a schedule and manage it.

Maintain your budget and expected delivery dates, by sticking to the initial requirements document .

Understand that if you constantly adjust the requirements document with modifications and"scope creep," you cannot expect to have the project delivered within the originally projected time frame or for the estimated cost.

Use the 80/20 rule wisely: Put 80% of development effort into perfecting 20% of the site that will be most used.

Involve target users testing for feedback and reviews.