Corporate Voice
333 Hudson Street
New York, NY 10013
phone: 212.629.4200
fax: 212.736.6172
Connect With Us!
|
|
 |


 |

The Deep Dive
We begin by becoming familiar with the client’s strategic, business, and technical requirements and objectives.
This can include interviews and audits with project team members.
Technical specifications are gathered and overall goals are developed.
We carry out a visual audit of current brand positioning, including reviewing
ongoing online or offline campaigns to help us formulate visual design criteria
and gauge the appropriate creative and brand positioning before
design begins. Information architecture and page specifications are
developed to plan and detail functionality and content requirements throughout the site.
The blueprint
Next, we start to create an overall visual brand interface and framework. Several
options are presented to the client for feedback. Concurrently, page content
development begins. Text and page architecture nomenclature is developed
into a consistent, engaging, visual and verbal voice to support the brand.
Following client modifications and approval, the accepted brand structure and
design candidates are translated into functional front-end models and posted to
a development center. Usability tests will confirm whether more complex
functionality or processes are required. Approved pages will be posted to a
staging server where the front and back ends will be combined into a working
model.
The build
Once the development environment is established, the technical development
phase begins. Database, application and legacy components are specified,
developed and integrated into a complete system.
This development cycle has four phases:
Proof-of-concept
Involves capturing business requirements, defining goals, producing a conceptual
system design and logic design and making recommendations.
First-build
Goals are defined for the first build, including producing system test plans,
evaluating the first build and making recommendations.
Second-build
Where we derive subsystem requirements, define goals for the second build,
produce a physical design, construct the second build, produce subsystem test
plans, evaluate the second build, and make recommendations.
And finally…
The big test
We complete the final design and its system requirements, then start on the final
build. This involves performing complete system and subsystem acceptance tests.
All components and functionality of the web site on both the client and server sides
will be tested. This could include testing for system functions, load, stress,
usability, security, unit and integration, regression, links, HTML validation, reliability
and recovery.
And it doesn’t end there.
As the site evolves over time, you need to ensure the continuity of its look, feel, tone
and overall quality. We develop site design guidelines to ensure the consistency of
a brand’s online presence even as its various components may evolve and change.
We offer training on any developed CMS and ongoing maintenance is available
beyond the life of the project. We also provide support in the development of emarketing
campaigns and statistical reporting on web site traffic, user patterns,
and conversion rates as they relate to online and offline initiatives. These reports
can be provided on a monthly or quarterly basis at additional cost.
|
 |
 |
|
|