WASHINGTON TECHNOLOGY By By Lisa Pafe
“Federal government evaluators couldn’t care less about win themes. They are looking for Strengths, and if they do not find Strengths, they may instead find Weaknesses, Risks and Deficiencies.
“In the federal space, Strengths are features of merit with proven benefits that exceed requirements and/or significantly reduce risk in a manner the customer values.“
“We all know that, at a minimum, proposals must be compliant and responsive. If a proposal meets this minimum bar, the evaluator is likely to award it an Acceptable rating. But what if, despite several rounds of color team reviews, the proposal barely meets this mark?
A Mediocre Proposal
We can assume that an Acceptable proposal will not win in a federal government competitive best value trade-off, unless other bidders also submit Acceptable proposals, and price is the determining factor.
Under the Federal Acquisition Regulation (FAR), government evaluators must make an award based on benefits offered by the proposer. Those benefits may include features of the proposed offering with proven benefits, or a low price, or some combination of the two. Still, unless the win strategy is based on a low bid, the goal of our color team reviews is to improve proposal quality. As a result, we would hope that our proposal rises from merely Acceptable to Good or even Outstanding as we move from Pink to Red to Gold Team.
However, we encounter situations where despite the best efforts of reviewers and writers, the proposal never rises above mediocre. Why did this happen? In the case of some recent reviews we at Lohfeld Consulting joined as consultants, there were too many reviewers with no training or direction, too many comments and too little consensus, too little time to recover between reviews, and an ill-defined solution.
A Compelling Solution is Rich in Strengths
Writers cannot create masterful text with no direction. Communicating the win themes to writers is not enough direction. Writers need annotated outlines and/or content plans with Strengths mapped to evaluation factors.
If the capture team did not work with subject matter experts and solution architects to craft a solution of merit, and/or failed to vet potential Strengths with customers, then the writers will not write about Strengths. The reviewers will therefore not find any Strengths. The proposal will therefore remain mediocre.
Ten Lessons Learned
The lessons learned below assume that the team has developed and vetted a solution rich in discriminating Strengths. Assuming there is a well-defined solution, here are ten lessons learned our team identified to improve color team reviews and proposal quality.
- Types of Reviews: Not all color team reviews are created equal. Determine, up front, what type of color team reviews you will conduct and the purpose of each. We recommend that at least one group of reviewers act like a mock government source selection board to score and rate the proposal like the customer evaluation team. Every type of review should have discrete, well-defined roles that are clear and manageable.
- Team Composition: Get the right people committed early and get the reviews on their calendars. Keep review team membership consistent across reviews. Involve proposal professionals in the review to inspect for quality of proposal writing tradecraft (including graphics). Also, involve independent reviewers who know nothing about the opportunity.
- Training in the Art of Review: The right reviewers are trained reviewers. Make sure all the reviewers understand the proposal color team protocol. Set expectations for the reviews, provide agendas and scoresheets, and offer guidance/training on using automation, virtual proposal sites and/or evaluation tools.
- Team Size and Review Duration: Size the review team and review duration to the proposal size and complexity. Ensure each reviewer has adequate time to review assigned sections. A good rule of thumb is 25-30 pages per day per reviewer. Ideally, two or more reviewers will review each assigned evaluation factor or proposal section for a complete picture.
- Preparation: Ensure all review team members prepare in advance. Advance preparation includes reading the RFP, Q&A and amendments. The review team should also have access to the proposal manager’s compliance matrix and the capture manager’s win strategy. (If some reviewers are to act completely independent, do not provide the win strategy in order to see what a fresh pair of eyes finds).
- Horizontal and Vertical: Review horizontally for cross-section consistency. Review vertically to determine if the proposal is compliant and responsive (Acceptable) as well as persuasive and compelling (Outstanding). Do reviews at multiple entry points in case customer evaluators review only one section or one evaluation factor.
- Consensus: Review teams should have different roles. Some may be reviewing like a government evaluator. Others may be doing a compliance review. Still others may read the proposal for persuasiveness. No matter how you divide the roles, require each review team to provide a consensus out-brief including the proposal score or rating as well as perceived Strengths, Weaknesses, Deficiencies and Risks.
- High Level Out brief: Avoid time wasting, long-winded out briefs. Instead keep the group out brief under an hour with a focus on a prioritized set of recommendations for improvement. Save details for one-on-ones with authors to speed recovery and improve quality.
- Writer One-On-Ones: Too often, writers receive hundreds of comments and must fend for themselves during proposal recovery. Assign reviewers to fully brief the writers on consensus findings. Conduct iterative reviews before the next formal color team to ensure recovery is on track.
- Lessons Learned: After proposal submission, conduct an internal lessons learned using a standard template. Which review processes worked, and which didn’t? Do you need more training in proposal solutioning, writing, and/or reviews? Develop and implement corrective actions as needed.
It All Begins with a Solution
Just write and solution later is the worst way to develop winning content. Yet, too often, reviewers are expected to evaluate proposal drafts that reflect the lack of a compelling solution. If you want color team reviews that work, solution before you write. Give writers effective templates and fully developed content plans with Strengths mapped to evaluation factors. Then, implement the ten lessons learned above, and see your color team reviews improve and win rates soar.”