|
r
<br /> s
<br /> How We Work Together
<br /> Thank you for the consideration you've giuen;us`'Ve,',re;,anxious to start working together
<br /> to produce the results you desire ate know thatworf4mgwiith an organization like ours
<br /> for the first time often prompts a few questions:,Sometimes more than a few concerns,
<br /> too. How successful:will,we be in iriterpre;iing yoi;lr deeds? How can we do it most
<br /> effectively? How can.we.do it..;most e'.fficl;erit)y?';:';..,;
<br /> Laying The Foundation
<br /> Just as every architect knows.that a:buildings design-is no betterthan its foundation, we
<br /> know that no communications creativity,is:better than.tthe quality of the information it's
<br /> constructed around. This.is why we go to„g:re.at.lg.ngths.to get everything we need to
<br /> know to do the best possible job. The first:thing we do after being assigned a project is
<br /> schedule information-gathering meetings between ourvcreative team and your key staff.
<br /> We are interested not only.in scheduling, budget ehd fob specifications, but also in your
<br /> preferences, target audience and obje.ctive$ I,n additidh,, we will want to know all the
<br /> user features and benefits.of;the sub' t;wI ... GofnGnunicating. Although this
<br /> process is somewhat.time.-consuming:(we.dorl`t.aike retirnga any more than you do), it is
<br /> also crucially important. It will fielp you sharpen your project'focus and objectives, and it
<br /> will help us assure that what we produce is npt.only clreatiy,ely excellent, but strategically
<br /> targeted
<br /> Developing The Right Ideas
<br /> Despite popular misconceptions; good creativia.work{does.n't often come in a flash of
<br /> inspiration: usually it comes from lots of trial and,,e,rror;J: his'is why we also need to take
<br /> the time to consider several approaches'.(conce:pts):, work them through, try them out.
<br /> Then revise them. In addition, there .are.usually:some,:practical and functional ends we
<br /> need to tie up before submitting:our:i dews..sub Icb.ntractoravailability, scheduling
<br /> requirements, etc. All this, plu$;the.need tq'scf eduie;-Wr:.workflow in a businesslike
<br /> fashion, means that we normally askfo' Up,to•two.�weeks,;depending on the job's
<br /> complexity, before we.submit our rough,appCoaches,:(:corieepts) for your review. Of
<br /> course, if you have a rush proj.ect,.o.r':deadline;,;p,rag aure we adjust .our workflow and
<br /> timing accordingly. It is.our:experiende.that.it.'is,.°best if`we first present our rough
<br /> concepts to your project manager andv' . t one;:or two-others. This assures that we all
<br /> stay focused on the problem andare not distrac34d.by:too many personal opinions. Our
<br /> rough concepts consist of pencil sketches.or computer roughs. They are adequate to
<br /> convey what we believe is the best approach to.take;;teking into consideration your
<br /> budget, schedule, objectives and..preference.s::,On;:the;d.thI r hand, they are not so well-
<br /> developed as to have wasted time: and. effort if.we need'.a course correction. After
<br /> presenting, we'll sit back and,.ask for your.com"hts
<br /> The more objective and specific,you can be, thb:.b.etterwe will be able to respond.
<br /> Comments are the input for revising the rough concepts;into a,finished one. Revisions
<br /> normally takes us about a:week and we will schedule'a:>second presentation shortly
<br /> thereafter. From the input at this:second.presentatibn mai3ting further minor refinements
<br /> will be made as necessary. We,will,also:finalize'the,prptluction timetable, and the
<br /> scheduling of additional services.such as.engineer ng,. abrication and /or installation.
<br /> 90 39dd LZ ZT
<br /> 9NI AiIdNI9VWI 99Zb-Sb5-ZI9 966t/Ei/Z0
<br />
|