Revised May 15, 2006
best one. The introduction should be kept short and sweet; generally try to
keep it less than two pages.
Technical approach
This section allows you to reinforce your authority as an expert by laying
out a sound technical plan for the project. The technical approach must
demonstrate that you understand the problem and have a methodology for
resolving it. This is the time to introduce innovative ideas or solutions.
Your impact will be greatly lessened if the plan is fuzzy or general in
nature, as invariably happens if you haven't taken the time to thoroughly
research the subject. The methodology must be described, including the
resources that will be required.
The more professionally you present the technical approach, the more
competent you will appear and the more confidence the evaluator will
have in your proposal. Brainstorming with some of your best technical
experts is a useful way of giving an understanding of the problem and
developing a sound methodology. Innovative approaches should be
sought and any unique selling points that your team can bring to the
project should be highlighted.
A task must be measurable and assignable. That is, you should be able to
assign a single person, the task leader, to be responsible for its
execution, although other staff may also contribute to it. Each task should
have a definite outcome, a budget, and duration. In other words, a task is
a work element that can be assigned, have its progress monitored, and
produce discreet deliverable components.
If the project is at all complex, a flowchart of the technical approach will
help the reader. It is a road map and should guide the reviewer through
the technical network of your proposed methodology. The flowchart is
often very helpful to you, as well, as its preparation forces you to analyze
the logical flow and interrelationship of the technical tasks that you are
proposing.
A section on anticipated difficulties is generally helpful as it shows you
have taken the time and interest to analyze potential problems and to
think of ways of overcoming them. If the project has a particularly difficult
schedule or budget to satisfy, then the effort you have invested in
recognizing these obstacles and thinking about their resolution will gain
the client's respect.
The technical approach is generally the longest section in your proposal
and should certainly be the one that consumes the deepest thought.
Page 5 of 36
Comentários a estes Manuais