APMP Study Guide

https://www.apmp.org/

Get Started. It's Free
or sign up with your email address
Rocket clouds
APMP Study Guide by Mind Map: APMP Study Guide

1. Part 1: Introduction to the Business Development lifecycle

1.1. The business development Lifecycle

1.1.1. is about winning business.

1.1.2. A clear business development process based on best practices can help organizations to:

1.1.2.1. identify opportunities and

1.1.2.2. win bids in a repeatable, sustainable way.

1.2. Increasing the Probability of Winning

1.2.1. A key goal of any business development team is to advance a business opportunity and move toward being in a "favored" position from the customer's perspective

1.2.2. Positions

1.2.2.1. Unknown position.

1.2.2.2. Known position.

1.2.2.3. Improved position.

1.2.2.4. Favored position.

1.3. Phases in the Business Development Lifecycle

1.3.1. Untitled

1.3.2. 1. Market Identification

1.3.2.1. helps organizations ensure that they spend marketing budgets and resources on the most likely targets for profitable business opportunities.

1.3.2.2. The market risk assessment

1.3.2.2.1. is highest for opportunities with new customers and new products;

1.3.2.2.2. is lowest for opportunities with existing customers and existing products.

1.3.2.2.3. Market and Customer Match Matrix

1.3.2.3. Organizations must constantly

1.3.2.3.1. assess and reevaluate their markets,

1.3.2.3.2. identify new market segments

1.3.2.3.3. validate current markets.

1.3.2.4. Assessing whether to enter a specific market is a key decision gate at this phase of the business development life cycle.

1.3.3. 2. Account Planning and Positioning

1.3.3.1. Account planning

1.3.3.1.1. involves "long-term positioning" with a potential customer and is an "ongoing activity" across the business development lifecycle.

1.3.3.2. Account plan consists of

1.3.3.2.1. Historical account information,

1.3.3.2.2. Buying history

1.3.3.2.3. Strategies for penetrating or growing an account.

1.3.3.2.4. Key customer personnel and decision makers,

1.3.3.3. An account plan often feeds into an opportunity plan when specific opportunities are qualified.

1.3.4. 3. Opportunity Assessment

1.3.4.1. Bid / no-bid Decision

1.3.4.1.1. A key decision gate at the opportunity assessment phase of the business development life cycle is a preliminary bid/no-bid decision on a specific opportunity.

1.3.4.2. Sales opportunities➢ Organizations can identify sales opportunities through many channels, including

1.3.4.2.1. Marketing campaigns

1.3.4.2.2. Social media efforts

1.3.4.2.3. Lobbying strategies

1.3.4.2.4. Traditional prospecting

1.3.4.3. Opportunity tracking programs

1.3.4.3.1. Many successful organizations use third-party sales opportunity tracking programs (subscriptions) to track and monitor future bidding opportunities, especially in regional and national markets.

1.3.4.3.2. These programs can help identify upcoming opportunities based on specific filters used during opportunity searches.

1.3.5. 4. Opportunity Planning

1.3.5.1. Opportunity Planning

1.3.5.1.1. This process does not always go in this order; the qualification decision may need to be revisited as you learn more about the customer and the opportunity.

1.3.5.2. Critical aspects of "opportunity planning"

1.3.5.2.1. 4 C's

1.3.5.2.2. Portfolio management.

1.3.5.3. Regardless of the size or complexity of an opportunity, a Sales or Opportunity Manager should take time to plan. The plan's level of detail will depend on the opportunity, including complexity and dollar value

1.3.6. 5. Proposal Planning activities

1.3.6.1. Migrating

1.3.6.1.1. data from the opportunity plan to a proposal plan or to proposal planning tools

1.3.6.2. Extending

1.3.6.2.1. the opportunity strategy into the proposal strategy.

1.3.6.2.2. A proposal strategy consists of

1.3.6.2.3. Organizations can capture this transfer the preparing a draft executive summary.

1.3.6.3. Engaging

1.3.6.3.1. the right staff for the proposal team and securing the right executive support

1.3.6.4. Refining

1.3.6.4.1. the solution and price-to-win

1.3.6.5. Holding

1.3.6.5.1. a proposal kickoff meeting to share planning activities with the proposal team

1.3.7. 6. Proposal Development

1.3.7.1. Stop bid planning activities

1.3.7.1.1. At this stage, bid planning activities, shoud stop including

1.3.7.1.2. Ongoing changes result in wasted time and resources and can lead to a mediocre proposal that is frustrating to prepare.

1.3.8. 7. Negotiation and Post-Submittal Activity

1.3.8.1. Submittal of a proposal does not signal the end of the business development lifecycle.

1.3.8.2. On the contrary, this is the phase where business decisions become intense and real.

1.3.8.3. Organization's strategy should be:

1.3.8.3.1. To respond fully to customer questions and concerns

1.3.8.3.2. To reinforce a customer's trust in its solution and organization

1.3.8.3.3. To optimize the deal to the benefit of bidder and customer

1.3.8.4. Lessons-learned

1.3.8.4.1. Conducting a lessons-learned review on each major bid opportunity is a critical best practice.

1.3.8.4.2. Lessons learned should be well documented and stored for others to access and reference on future sales opportunities.

1.3.9. 8. Delivery and Ongoing Customer Relationships

1.3.9.1. Effective business development activities continue throughout the solution delivery phase

1.3.9.2. Winning the contract is an opportunity to prove value and position your organization for additional opportunities.

1.3.9.3. Apply account management techniques, such as

1.3.9.3.1. Regular customer contact,

1.3.9.3.2. product demonstrations and upgrades,

1.3.9.3.3. social marketing,

1.3.9.3.4. and participation in relevant industry and trade events.

1.4. Common Pitfalls and Misconceptions

1.4.1. Necessity of business development process

1.4.2. Importance of bid decision gates and positioning

1.4.3. Importance of early customer involvement

1.4.3.1. Many companies believe that a compliant, responsive, and well-done proposal will win the contract. On the contrary, a proposal is often the final step in confirming a customer's buying decision. Effective marketing, positioning, and selling are critical to winning business-the proposal then verifies the winning solution.

1.5. Summary

1.5.1. Defining, documenting, and implementing an effective business development lifecycle is a core part of stra­tegic planning for any business.

1.5.2. Organizations must remember to

1.5.2.1. Scale and tailor the cycle to specific markets and competitive positions.

1.5.2.2. Clearly define roles and responsibilities within the cycle.

1.5.2.3. Secure leadership buy-in and support for implementing the cycle.

1.5.2.4. Document all successes and failures to learn from experience.

1.5.2.5. Enhance the customer relationship across the cycle at each phase and as part of each activity.

1.6. Terms to Know

1.6.1. Market Identification

1.6.2. Opportunity Plan

1.6.3. Price-to-Win

1.6.4. WOT

2. Part 1: Focus on the Customer

2.1. 1. Compliance and responsiveness

2.1.1. Introduction

2.1.1.1. Compliance

2.1.1.1.1. Compliance is the act of

2.1.1.1.2. Examples of compliance include:

2.1.1.2. Responsiveness

2.1.1.2.1. Responsiveness goes beyond compliance. it address:

2.1.1.2.2. Examples

2.1.1.3. Notes

2.1.1.3.1. It is possible to be compliant without being responsive. as well as responsive without being compliant. The best proposals, however, are both.

2.1.1.3.2. Compliance is not enough

2.1.2. Best Practices

2.1.2.1. 1. Begin to cultivate responsiveness Long before RFP release

2.1.2.1.1. If you are beginning to think about responsiveness at RFP release, you are too late. The customer's hot-button issues are often not stated in the solicitation.

2.1.2.1.2. To be responsive, you must know your cus­tomer beyond the written requirements.

2.1.2.1.3. Starting early means you can help shape the request for your specific response.

2.1.2.1.4. Building a trusting relationship with your customer and understanding your customer's underlying con­cerns takes time.

2.1.2.1.5. Bid Managers and sales professionals must begin gathering this customer intelligence early in the business development lifecycle and continually build upon this relationship through RFP release

2.1.2.2. 2. Thoroughly review and clearly understand the customer's bid request.

2.1.2.2.1. Prior to the kickoff meet­ing read the RFP

2.1.2.2.2. After reading (and rereading) the RFP, ensure that you clearly understand what is required. identify anything that is unclear and could impact your response.

2.1.2.2.3. Consider seeking clarification from the customer,but be sure to complete with the instructions for submitting RFP questions.

2.1.2.3. 3. Prepare a comprehensive compliance matrix for every bid request

2.1.2.3.1. The compliance matrix is a must-have planning document. Always create a compliance matrix when a customer has provided requirements, regardless of the bid size or timeline.

2.1.2.3.2. For unsolicited proposals, white papers, and RFI responses, use the followings to demonstrate your understanding of requirements and compliance.

2.1.2.3.3. Create your compliance matrix early in the planning process, before writing begins, and update it throughout the proposal process, following solicitation amendments, customer responses to clarifica­tion questions, and proposal outline changes.

2.1.2.3.4. A compliance matrix is a powerful tool used by different proposal team members in different ways:

2.1.2.4. 4. Submit a response matrix with your proposal

2.1.2.4.1. You must make the proposal evaluation process as easy and efficient as possible

2.1.2.4.2. Prepare a clearly written and arranged proposal that is easy for evaluators to compare to their RFP requirements.

2.1.2.4.3. A response matrix

2.1.2.5. 5. Maintain a customer focus

2.1.2.5.1. When you understand and have a trusting relationship with your customer, you will be prepared to write a customer-focused proposal

2.1.2.5.2. Demonstrate that you understand the customer by citing its vision and hot-button issues in your executive summary and then weaving corresponding theme statements throughout your proposal.

2.1.2.5.3. A customer-focused bidder

2.1.3. Summary

2.1.3.1. Winning proposals ore not only compliant, but responsive to the customer's underlying issues.

2.1.3.2. Compliance and responsiveness ore two different, but equally crucial elements.

2.1.3.3. It is possible to be compliant without being responsive and vice verso. Winning bidders ore both.

2.1.3.4. Before beginning any work, you should thoroughly review and clearly understand the customer's bid request.

2.1.3.5. You should prepare a compliance matrix for every proposal that contains requirements, regardless of size or timeline.

2.1.3.6. Make it clear that your proposal is compliant by submitting a response matrix with your proposal.

2.1.3.7. This will also ensure that your proposal con be easily evaluated.

2.1.3.8. Developing responsiveness begins in the early stages of the business development lifecycle and continues throughout.

2.1.3.9. Responsiveness can vary greatly across different markets, groups, and cultures.

2.1.4. Terms to Know

2.1.4.1. Benefit

2.1.4.2. Clarification

2.1.4.3. Compliance Matrix

2.1.4.4. Compliant versus Responsive

2.1.4.5. Customer Focus

2.1.4.6. Customer Issues

2.1.4.7. Customer Requirements Feature

2.1.4.8. Hot Buttons

2.1.4.9. Non-Compliant Bids

2.1.4.10. Protest

2.1.4.11. Response Matrix

2.2. 2. Customer Analysis and Competitive Intelligence

2.2.1. Introduction

2.2.1.1. Customer and competitive intelligence

2.2.1.1.1. Requires researching what your customers need and what your competitors can offer.

2.2.1.1.2. Provides the data you need to create effective strategies and compelling proposals.

2.2.1.1.3. Is a key part of opportunity planning and can help organizations develop winning proposals.

2.2.1.1.4. Allows you to present solutions that overcome competitor weak­nesses

2.2.1.1.5. Enhances narrative development,

2.2.1.1.6. Strengthens your value proposition,

2.2.1.1.7. highlights your strengths that complement your cus­tomer's priorities and RFP requirements.

2.2.2. Best Practices

2.2.2.1. 1. Understand the importance of customer and competitive intelligence.

2.2.2.1.1. Customer intelligence

2.2.2.1.2. Competitive intelligence

2.2.2.1.3. Customer analysis and competitive intelligence work together to drive the strategy. They are critical to the

2.2.2.2. 2. Foster information sharing among all members of your extended organization

2.2.2.2.1. The best sources of competitive intelligence data may be your colleagues.

2.2.2.2.2. Opportunity planning teams should take time to build information networks with colleagues

2.2.2.2.3. Application of customer analysis and competitive intelligence helps focus your opportunity planning and proposal writing in two critical ways

2.2.2.3. 3. Leverage public sources of customer analysis and competitive intelligence data

2.2.2.3.1. Employees:

2.2.2.3.2. SMEs engaged by your company

2.2.2.3.3. Customers' websites

2.2.2.3.4. Competitors' websites

2.2.2.3.5. Trade/industry association websites

2.2.2.3.6. Social media: Facebook, Linkedln, Twitter, etc

2.2.2.3.7. Publicly available information: government agency reports, industry/trade publications, webinars

2.2.2.3.8. Trade shows/conferences

2.2.2.3.9. Annual reports. onclusts' reports, and other SEC reports

2.2.2.3.10. Subscription services: OneSource, Hoovers, Dun & Bradstreet, GovWin, Gartner, PWC, etc.

2.2.2.4. 4. Use a bidder comparison matrix (CM) to identify your key competitors' strengths and weak­nesses

2.2.2.4.1. Capturing a true picture of the competitive field for any proposal will add dimension to your writing . It also directs your writing to requirements from the customer's perspective, complemented by a discussion of your own company's strengths and discriminators.

2.2.2.4.2. The matrix clearly shows the strongest competitor and highlights strengths and weaknesses of others.

2.2.2.4.3. Figure

2.2.3. Common Pitfalls and Misconceptions

2.2.3.1. Belief that competitive intelligence data collection is a covert activity

2.2.3.1.1. Competitive intelligence is an ethical business practice guided by written rules from the association of Strategic and Competitive Intelligence Pro­fessionals (SCIP).

2.2.3.2. Difficulty obtaining competitive intelligence data

2.2.3.2.1. You can find the majority of the competitive intelligence data you need among colleagues and online

2.2.3.2.2. With so many resources readily available, it is relatively sim­ple to find most of the data needed for an effective proposal narrative.

2.2.3.2.3. Proprietary company data, however, is not always available. In these cases, teams may have to derive information from available data and make assumptions.

2.2.4. Summary

2.2.4.1. Customer analysis and competitive intelligence uses research to understand customer needs and competitor strengths and weaknesses.

2.2.4.2. An important source of competitive intelligence data is information shared by colleagues. Proposal teams should work to gain information from others in their organizations.

2.2.4.3. Gathering competitive intelligence is an ethical activity; most sources of information are publicly and readily available.

2.2.4.4. This knowledge helps proposal writers show a company's own value proposition in the best possible light .

2.2.4.5. Organizations can use a bidder comparison matrix to showcase their own capabilities in comparison to their competitors.

2.2.5. Terms to Know

2.2.5.1. Competitive Intelligence

2.2.5.2. Customer Intelligence

2.3. 3. Executive Summaries

2.3.1. Introduction

2.3.1.1. Must be clear and persuasive to grab customer attention.

2.3.1.2. is a concise, informational, persuasive piece of writing.

2.3.1.3. It is generally a standalone section at the front of a proposal.

2.3.1.4. If the customer's instructions do not allow for an executive summary, then include this content as part of the cover letter or first-page introduction.

2.3.1.5. it is a sales document that shows that you:

2.3.1.5.1. Grasp your customer's vision

2.3.1.5.2. Understand the customer's explicit and implied needs

2.3.1.5.3. Offer better value than any competitor

2.3.1.5.4. Have built a solution that satisfies those needs

2.3.1.6. Aim the executive summary at senior-level decision makers in your customer's organization

2.3.1.7. Write the executive summary in the opportunity planning phase, before a kickoff meeting. Then, as appropriate based on value and strategic importance, review it early with management based on decision gate criteria.

2.3.2. Best Practices

2.3.2.1. 1. Keep executive summaries customer-focused.

2.3.2.1.1. A customer-focused executive summary:

2.3.2.1.2. Organize your executive summary around the answers to seven key questions:

2.3.2.1.3. Define a structured approach for your executive summary

2.3.2.1.4. If customer instructions or procurement rules disallow an executive surnrnary

2.3.2.2. 2. Write and review early.

2.3.2.2.1. Preparing executive summaries early promotes clear alignment for the pursuit.

2.3.2.2.2. This ensures that every individual, from the proposal team to senior executives, conveys the same message to your customer.

2.3.2.2.3. Drafting your executive summary early allows you and your team to:

2.3.2.2.4. If you are not prepared to write the executive summary early you probably are not ready to bid and should consider a no-bid.

2.3.2.3. 3. Use your executive summary to make an impression.

2.3.2.3.1. As a sales document, your executive summary helps to advance the sales process to the next stage.

2.3.2.4. 4. Clearly indicate your proposal's responsiveness and compliance.

2.3.2.4.1. Tailor your executive summary to match the priorities of key decision makers:

2.3.2.4.2. Clearly show that you have validated needs with the customer.

2.3.2.4.3. Make it clear that you comply with the client's requirements.

2.3.2.5. 5. Assign writing and review responsibilities strategically.

2.3.2.5.1. Use a clear, easy-to-read writing style.

2.3.2.5.2. The ideal author for your executive summary is

2.3.2.5.3. When choosing reviewers for your executive summary, make sure you have a good mix of

2.3.2.5.4. Use a professional proposal editor for edits. This may be the Proposal Manager or an Editorial Specialist on the proposal team, depending on the size of your team and organization.

2.3.2.6. 6. Mirror your executive summary themes in the proposal cover, title, and cover Letter

2.3.2.6.1. When preparing these aspects of a proposal, consider the following:

2.3.3. Common Pitfalls and Misconception

2.3.3.1. Including irrelevant information in executive summaries

2.3.4. Summary

2.3.4.1. 1. A good executive summary provides a value proposition that helps evaluators choose you.

2.3.4.2. 2. Always include an executive summary as a standalone document unless the proposal is very short. Follow instructions if provided.

2.3.4.3. 3. Write a draft executive summary before kickoff and get it approved early. Use it as a briefing tool to drive the direction of the proposal team. Allow time for changes and be sure to do a final proofread, while keeping production schedules in mind .

2.3.4.4. 4. Plan before writing. Adapt your approach to the time available.

2.3.4.5. 5. Write executive summaries for nontechnical, upper-level decisionmakers.

2.3.4.6. 6. Tie major discriminators explicitly to customer issues.

2.3.4.7. 7. Match the goals and priorities of the evaluators. Give them good reasons to select you by showing them the unique value of your solution with relevant proof points.

2.3.4.8. 8. Mention the client first and benefits before features. Show your solution's compliance.

2.3.4.9. 9. Use a clear writing style and include graphics to add emotional appeal. Avoid too much technical detail. Include high-level pricing and related value propositions unless prohibited or irrelevant.

2.3.4.10. 10. Ask the salesperson (or Opportunity Manager) who knows the client best to write the draft executive summary. Enlist a proposal editor for final edits and a mix of client, technical, competitor, executive, and proposal skills for reviews.

2.3.4.11. 11. Keep your executive summary short. Use a structure that works. Each executive summary differs for each opportunity because the client, evaluators, competitors, and solution are all different.

2.3.5. Terms to Know

2.3.5.1. Bidder Comparison Matrix

2.3.5.2. Executive Summary

2.3.5.3. Hot Buttons

2.3.5.4. SWOT

2.3.5.5. Win Themes

2.4. 4. Strategy and Win Themes

2.4.1. Introduction

2.4.1.1. Strategy and win themes play an evolutionary role in the development of an opportunity.

2.4.1.2. As intelligence improves,

2.4.1.2.1. strategy evolves and

2.4.1.2.2. competitive focus matures, driving improved win themes.

2.4.1.3. Proposal strategy statements are tools to verbalize your win strategies in a way that helps everyone on your team understand how the bid will succeed

2.4.1.4. Strategy is inextricably linked to the

2.4.1.4.1. customer,

2.4.1.4.2. competitor,

2.4.1.4.3. bidder capability assessments developed in the opportunity plan.

2.4.1.5. As you move from the opportunity planning phase to the proposal planning and development phases of the business development lifecycle:

2.4.1.5.1. Opportunity strategies will influence proposal strategies, and

2.4.1.5.2. win themes will influence proposal themes

2.4.1.6. Each time those assessments are updated, strategies and associated win themes must be reassessed.

2.4.1.7. A win strategy

2.4.1.7.1. Your win strategy is the collection of win themes and actions you develop after a pursuit decision to win a bid.

2.4.1.7.2. It is documented in the opportunity plan you develop to win a specific opportunity.

2.4.2. Best Practices

2.4.2.1. 1. Develop opportunity strategies and win themes early.

2.4.2.1.1. Using a bidder:

2.4.2.2. 2. Identify a "killer" opportunity strategy and refine it as intelligence improves.

2.4.2.2.1. The litmus test of the very best opportunity strategy is that if it were revealed to the competition, it would damage your chances of winning.

2.4.2.3. 3. Use the following to focus your strategies and win themes

2.4.2.3.1. Opportunity plan review

2.4.2.3.2. Competitor review feedback

2.4.2.4. 4. Build proposal strategies for anticipated response requirements.

2.4.2.5. 5. Design a proposal cover and key graphic that reflect your overall offer and overarching theme.

2.4.2.5.1. Earlier in the process, You chose a one- or two-word theme that was the basis of your elevator speech.

2.4.2.5.2. If you have not already done so with early marketing activities, create a customer-focused cover for the proposal and a key graphic that summarizes your offer.

2.4.2.5.3. The process of representing your concepts visually will help you further sharpen your message. In addition, visuals will kick-start your executive summary mock up and transition of opportunity plans to proposal plans.

2.4.2.6. 6. Monitor transition of strategy and win themes to:

2.4.2.6.1. -Proposal content/Final proposal response,

2.4.2.6.2. -Contract negotiations.

2.4.2.6.3. The best-laid opportunity plans are not always transitioned into proposal plans, Avoid this by carefully mapping strategy statements and win themes all the way through to technical management, and price solutions at contract negotiations.

2.4.3. Summary

2.4.3.1. Strategies and win themes must evolve from positioning actions and statements to solution strategies and themes based on the entire opportunity environment.

2.4.3.2. The litmus test of the best opportunity strategy is that if it were revealed to the competition, it would damage your chances to win.

2.4.3.3. Review and repeat SWOT analysis to confirm that your strategy statements are still aligned as the requirements and competitive field change.

2.4.3.4. Translate win themes to proposal themes for each major section of the proposal.

2.4.3.5. Communicate and ensure understanding of your strategies and themes through the proposal all the way to contract negotiations.

2.4.3.6. Use quantified benefits statements in customer-focused themes.

2.4.4. Terms to Know

2.4.4.1. Bidder Comparison Matrix

2.4.4.2. Competitor Review

2.4.4.3. Elevator Speech

2.4.4.4. Executive Summary

2.4.4.5. Ghosting the Competition

2.4.4.6. Opportunity Plan

2.4.4.7. Opportunity Plan Review

2.4.4.8. Opportunity Strotequ

2.4.4.9. Proposal Strategy Statement

2.4.4.10. SWOT

2.4.4.11. Theme Statement

2.4.4.12. Win Strategy

2.5. 5. Value Propositions

2.5.1. Introduction

2.5.1.1. Value proposition

2.5.1.1.1. Offers clients something they want

2.5.1.1.2. Gives them a good reason to choose you over your competitors.

2.5.1.2. In the executive summary and in your full proposal, as well as in any other customer interactions, communicate a strong value proposition that matches your client's needs and demonstrates your unique offer.

2.5.2. Best Practices

2.5.2.1. 1. Sell the value based on client benefits.

2.5.2.1.1. People make decisions based on

2.5.2.1.2. Salespersons should not sell features, but rather positive discriminators that deliver benefits that matter to the client.

2.5.2.1.3. Selling on value helps to organize your proposal strategy.

2.5.2.1.4. A good value proposition

2.5.2.2. 2. Link benefits to your unique selling points.

2.5.2.2.1. Making your value proposition the foundation of your executive summary gives evaluators a reason to select you, even before they read your proposal

2.5.2.3. 3. Use effective price-to-win methods.

2.5.2.3.1. You don't have to offer the lowest price to win a deal.

2.5.2.3.2. The role of the Proposal Manager is to maximize the difference between the value the client gets and the price paid.

2.5.2.3.3. Use price-to-win methods to arrive at a winning price, the following can help you do this:

2.5.2.4. 4. Quantify the payback

2.5.2.4.1. Quantify the payback.

2.5.2.4.2. Use proof points to further convince the customer. This is far more persuasive than making vague claims about the value clients will gain.

2.5.2.5. 5. Make it visual.

2.5.2.5.1. Using pictures to explain your value proposition helps clients understand your value faster and remember it longer. It also adds emotion to persuade.

2.5.2.6. 6. Structure your value proposition in a logical, orderly way.

2.5.2.6.1. Follow the SMART approach:

2.5.2.6.2. According to Tom Sant, a value proposition can be presented in three parts:

2.5.2.7. 7. Focus on the right kind of impact.

2.5.2.7.1. The return your client wants might not only be financial. clients might seek the following kinds of impact:

2.5.2.7.2. Look for impact that is measurable, linked to your products or services, and proportional to the fees you will charge.

2.5.3. Common Pitfalls and Misconceptions

2.5.3.1. Common obstacles to using value propositions include

2.5.3.1.1. Lack of awareness

2.5.3.1.2. Poor information about clients or competitors

2.5.3.1.3. Fear of mentioning specific results

2.5.4. Summary

2.5.4.1. Failure to sell on value will result in the client choosing on price or doing nothing.

2.5.4.2. Overcome obstacles to using the value proposition to increase your chances of winning.

2.5.4.3. A value proposition offers clients something they want and gives them a good reason to choose your organization rather than your competitors.

2.5.4.4. The value proposition forms the foundation of the executive summary.

2.5.4.5. You don't have to offer the lowest price to win a deal; you must show more value than your peers.

2.5.4.6. Quantify the payback using a measure of time, rate, or value.

2.5.4.7. Make the payback visual and add emotion by including a graphic, even when the value is intangible.

2.5.4.8. There are many ways to structure a value proposition; choose the method that works for your organization and the proposal you are working on .

2.5.4.9. Focus on the right kind of impact, which may not necessarily be financial.

2.5.5. Terms to Know

2.5.5.1. Intangible Value

2.5.5.2. Price-to-Win

2.5.5.3. Proof Points

2.5.5.4. SMART

2.5.5.5. Value Proposition

2.6. 6. Proposal Theme Statements

2.6.1. Theme statements

2.6.1.1. Link "customer benefits" to the "features" of your offer.

2.6.1.2. communicate your discriminators, making evaluators' decisions easy.

2.6.2. Introduction

2.6.2.1. Proposal theme statements are

2.6.2.1.1. section-

2.6.2.1.2. topic-

2.6.2.1.3. or paragraph-level elements

2.6.2.1.4. offering the key points you want the customer to remember

2.6.2.2. If win strategies are the things you plan to do to win, theme statements are the things you say about those strategies.

2.6.2.3. The best theme statements tie benefits to features and address customer issues. Often highlighted or incorporated into callout boxes.

2.6.3. Best Practices

2.6.3.1. 1. Build a proposal theme outline against the structure of the response and flow themes into content plans

2.6.3.1.1. Proposal themes should flow from:

2.6.3.1.2. Develop feature/benefit pairs that reflect the executed opportunity strategy

2.6.3.1.3. Start with the highest level of the outline

2.6.3.1.4. and create a statement that:

2.6.3.1.5. When you have completed the top levels of your outline, flow related themes to the indented sections of the outline. .

2.6.3.1.6. This exercise will identify areas needing further information to showcase benefits.

2.6.3.2. 2. Use theme statements consistently.

2.6.3.2.1. If you place themes inconsistently, evaluators may become confused or annoyed.

2.6.3.2.2. Be sure to format all theme statements in the same way.

2.6.3.2.3. If themes do not have the same font, color, size, and design, evaluators may miss them-and you may miss an opportunity to score points.

2.6.3.3. 3. Maintain customer focus.

2.6.3.3.1. Customer-focused writing is key in developing proposal themes.

2.6.3.3.2. Placing benefits before features and tying them to customer issues,

2.6.3.3.3. and naming the customer first and more often than you name yourself will sustain the attention of evaluators and communicate a reduced sense of risk.

2.6.3.4. 4. Read your theme statements out Loud

2.6.3.4.1. Did you need to take a breath to finish it?

2.6.3.4.2. Did it make sense, or did you stop yourself and start over with new words?

2.6.3.4.3. Does it sound believable?

2.6.3.4.4. Does it sound Like something a normal person would say?

2.6.3.5. 5. Test the impact of your theme statements and improve them accordingly.

2.6.3.5.1. The litmus test for a good theme statement is twofold:

2.6.4. Common Pitfalls and Misconception

2.6.4.1. Writing proposal sections before themes are identified and reviewed

2.6.4.1.1. This can lead to lack of alignment between themes and proposal content.

2.6.4.2. Failing to provide adequate proof

2.6.4.2.1. Evaluators will not believe your proposal themes unless you use sufficient, quantifiable, and verifiable proof

2.6.4.3. Focusing on features over benefits

2.6.4.3.1. For theme statements to be effective, you must clearly and tangibly show customers how they will benefit.

2.6.5. Summary

2.6.5.1. Theme statements tie benefits to features and address customer issues. They should be woven throughout your proposal.

2.6.5.2. Build an outline for proposal writers.

2.6.5.3. Ensure that theme statements focus on your customer, not on your organization.

2.6.5.4. The litmus test of a good proposal theme is that competitors cannot believably make the same claim and that evaluators could cut and paste it into their evaluation to justify your high score.

2.6.6. Terms to Know

2.6.6.1. Best and Final Offer (BAFO)

2.6.6.2. Content Plan

2.6.6.3. Customer-Focused Writing

2.6.6.4. Discriminator

2.6.6.5. Elevator Speech

2.6.6.6. Opportunity Strategy

2.6.6.7. Theme Statement

2.6.6.8. Win Strategy

2.7. 7. Features, Benefits, and Discriminators

2.7.1. Introduction

2.7.1.1. customers are sold on benefits, not features

2.7.1.2. Deep understanding of the followings allows you to communicate compelling, substantiated benefits to buyers

2.7.1.2.1. your customer's needs,

2.7.1.2.2. competitors' offerings and discriminators,

2.7.1.2.3. and your own capabilities (features)

2.7.1.2.4. and unique characteristics (discriminators)

2.7.1.3. simplified way to think of features, benefits, and discriminators:

2.7.1.3.1. Features= What?

2.7.1.3.2. Benefits= So What?

2.7.1.3.3. Discriminators= Why Us? (and why it matters to you)

2.7.2. Best Practices

2.7.2.1. 1. Understand your customer's needs.

2.7.2.1.1. Advantages

2.7.2.1.2. In your written offer, document the confirmed benefits in feature/ benefit tables.

2.7.2.2. 2. Develop and evaluate competitive intelligence.

2.7.2.2.1. To develop features, benefits, and discriminators, you must gather and analyze data about

2.7.2.2.2. Competitive intelligence is a key element of developing effective features, benefits, and discriminators.

2.7.2.2.3. It can be gathered by competitive intelligence professionals inside an organization or consultants outside of it.

2.7.2.2.4. When you have completed this analysis, take the intelligence you have developed and complete a bidder comparison matrix that scores the capabilities of all significant bidders against the "what" and the "why" of the requirements.

2.7.2.2.5. The next step is to document the strengths and weaknesses of each player using a SWOT analysis. Many strengths and weaknesses will surface during the bidder comparison exercise to justify the scores

2.7.2.3. 3. Determine your discriminators.

2.7.2.3.1. Maintain a clear focus on the customer's perceptions when determining your discriminators.

2.7.2.3.2. Relying on your brand as a discriminator is a common mistake in this area.

2.7.2.3.3. Your past performance may support your claim, but it is the people, processes, and tools applied to successful customer engagements that ore the discriminators, not your brand.

2.7.2.3.4. Figure

2.7.2.4. 4. Use feature/benefit tables.

2.7.2.4.1. Figure

2.7.2.5. 5. Quantify the potential value of benefits.

2.7.2.6. 6. Apply the "So what?" Litmus test.

2.7.3. Common Pitfalls and Misconceptions

2.7.3.1. Mistaking features for benefits

2.7.3.1.1. Applying the "So what?" litmus test can help proposal developers distinguish features from benefits. How­ever, this requires writers to detach themselves from a solution and look at a proposal from the customer's perspective.

2.7.3.1.2. Sellers, particularly incumbent contractors, also fall into the trap of thinking they know what the customer really wants, which may be different from what they have requested.

2.7.4. Summary

2.7.4.1. Features are your organization's capabilities. Benefits result from features and are solutions to customer problems. Ultimately, customers buy benefits, not features.

2.7.4.2. Determine your discriminators by assessing what the customer needs that you can offer better than any other competitor.

2.7.4.3. To ensure that you have distinguished correctly between features and benefits, apply the "So what?" test. Benefit statements should provide clear answers.

2.7.4.4. When possible, quantify the value of proposed benefits.

2.7.5. Terms to Know

2.7.5.1. Advantage

2.7.5.2. Benefit

2.7.5.3. Bidder Comparison Matrix

2.7.5.4. Differentiator

2.7.5.5. Discriminator

2.7.5.6. Feature

2.7.5.7. SWOT

2.7.5.8. Value Proposition

2.8. 8. Proof Points

2.8.1. Proof points, drawn from past performance and experience, give tangible evidence that builds confidence in your solution's features and benefits.

2.8.2. Introduction

2.8.2.1. Proof points often describe performance on similar past efforts. They can be

2.8.2.1.1. project data,

2.8.2.1.2. case studies,

2.8.2.1.3. customer quotes or testimonials,

2.8.2.1.4. awards or recognition earned

2.8.2.2. Crafting effective proof points requires understanding your win strategy before the RFP is released and conducting a data call to gather data.

2.8.3. Best Practices

2.8.3.1. 1. Understand your win strategy and corresponding win themes.

2.8.3.1.1. Effective win themes must contain

2.8.3.1.2. A win strategy

2.8.3.2. 2. Get started before you have an RFP.

2.8.3.2.1. The Proposal Manager should partner with the Opportunity Manager to understand the win strategy and the proof points you need

2.8.3.2.2. The Opportunity Manager should provide the following information

2.8.3.2.3. Customer Debriefs

2.8.3.3. 3. Conduct data calls before and after RFP drop, both internally and from teaming partners.

2.8.3.3.1. Pre-RFP, the Opportunity Manager and Proposal Manager should determine:

2.8.3.3.2. Post-RFP, the Opportunity Manager and Proposal Manager should analyze the solicitation to determine

2.8.3.3.3. Proposal proof points should be presented for both the prime contractor and any proposed teaming partners

2.8.3.3.4. Data calls are requests to members of your company and teaming partners for data to be used to build proof points.

2.8.3.4. 4. Maintain a repository of proof point data.

2.8.3.4.1. Know whom to ask for various sources of proof point data. Some examples of data and POCs for data sources include the following:

2.8.3.4.2. A proof points tracking checklist is provided among the tools and templates for this section in the APMP BOK. You can use this checklist to inventory and maintain a repository of reusable proof points.

2.8.3.5. 5. Ensure that proof points are persuasive, tangible, and credible

2.8.3.5.1. Proof points must be persuasive by substantiating features and benefits that meet or exceed customer objectives and requirements

2.8.3.5.2. Proof points must also be tangible by providing quantitative facts and figures

2.8.3.5.3. Proof points must be credible by providing verifiable information

2.8.3.6. 6. Verify accuracy of proof points.

2.8.3.6.1. The customer must be able to verify the proof points. Therefore, the proposal should identify data sources where possible and provide specific customer references and quotes

2.8.3.6.2. Some potential sources include:

2.8.3.7. 7. Aggregate and interpret data.

2.8.3.8. 8. Use the standard APMP proposal and business development roles to guide responsibilities for development of proof points.

2.8.3.8.1. Opportunity Manager

2.8.3.8.2. Knowledge Manager

2.8.3.8.3. Proposal Coordinator, Facilitator, or Specialist

2.8.3.8.4. Proposal Desktop Publisher

2.8.3.8.5. Proposal Manager

2.8.3.8.6. Proposal Writer

2.8.3.8.7. Project Manager

2.8.4. Common Pitfalls and Misconceptions

2.8.4.1. Waiting until the RFP drops

2.8.4.2. Relying on features to sell the company

2.8.4.3. Believing that benefits are enough

2.8.4.4. Assuming that general statements are acceptable

2.8.4.5. Putting proof points only in callout boxes

2.8.5. Summary

2.8.5.1. Proof points assure the proposal evaluator that features and benefits claimed are real, verifiable, and achievable.

2.8.5.2. Assembling, analyzing, and presenting proof points requires time.

2.8.5.3. Gather data early to substantiate proposed features and benefits.

2.8.5.4. Conduct data calls with your team and partner contractors to collect data needed for persuasive, tangible proof points.

2.8.5.5. Establish a repository of reusable proof points and continually update it based on lessons learned.

2.8.5.6. Effective proof points reduce the customer's risk perception because the data provided substantiates claims made in the proposal

2.8.6. Terms to Know

2.8.6.1. Benefit

2.8.6.2. Data Call

2.8.6.3. Discriminator

2.8.6.4. Feature

2.8.6.5. Hot Buttons

2.8.6.6. Proof Points

2.8.6.7. Win Themes

2.8.6.8. Win Strategy

2.9. 9. Persuasion

2.9.1. Summary

2.9.1.1. People make decisions using either

2.9.1.1.1. Central Processing

2.9.1.1.2. Peripheral Processing

2.9.1.2. Social psychologist Robert Cialdini identified six Weapons of Influence that can be used to persuade. They are reciprocity, consistency, social proof, liking, authority, and scarcity.

2.9.1.3. Writers should never misuse principles of influence. The principles should be used to highlight true benefits, never to deceive.

2.9.2. Introduction

2.9.2.1. Research shows that people can be persuaded to act in universal, predictable ways.

2.9.2.2. When making contract decisions, decision makers rarely apply cold, hard logic and exclude all other considerations. Many factors influence decision-making, including

2.9.2.2.1. the content of a presentation,

2.9.2.2.2. the relevancy of a product

2.9.2.2.3. and even a proposal's font.

2.9.2.3. proposal developers must successfully apply the principles of influence

2.9.3. Best Practices

2.9.3.1. 1. Understand how central and peripheral processing affect decisionmaking.

2.9.3.1.1. Elaboration Likelihood Model,

2.9.3.1.2. Proposal readers use both central and peripheral processing in their decisionmaking processes.

2.9.3.2. 2. Use the six Weapons of Influence to structure your argument effectively.

2.9.3.2.1. Reciprocity

2.9.3.2.2. Consistency

2.9.3.2.3. Social proof

2.9.3.2.4. Liking

2.9.3.2.5. Authority

2.9.3.2.6. Scarcity

2.9.4. Common Pitfalls and Misconceptions

2.9.4.1. Overuse of persuasive techniques

2.9.4.1.1. Writers shouldn't load proposals with all of the tools of influence they can find

2.9.4.1.2. What is the right amount of persuasion to use?

2.9.5. Terms to Know

2.9.5.1. Central Processing

2.9.5.2. Peripheral Processing

2.9.5.3. Principles of Influence

2.10. 10. Price-to-win

2.10.1. Price-to-win combines customer and competitor intelligence with careful attention to the balance of capabilities and cost.

2.10.2. It is an assessment that helps vendors arrive at prices that customers will value

2.10.3. Introduction

2.10.3.1. Price-to-win is a process for analyzing competitor and customer data to determine how other bidders are Likely to position their solution and bid price with their understanding of the customer's budget and their assessment of value.

2.10.3.2. It is an assessment that shows how competitors' pricing is Likely to be derived.

2.10.3.3. Price-to win is an external examination that defines where your business should target your offering.

2.10.3.4. Price-to-win analysis is used to develop winning bid strategies.

2.10.3.5. following relationship must be true: Customer Perceived Value >= Customer Budget >= Your Price >= Your Cost

2.10.4. Best Practices

2.10.4.1. 1. Understand the characteristics of a mature, successful price-to-win capability.

2.10.4.1.1. What makes price-to-win successful?

2.10.4.1.2. Successful price-to-win activities share several additional key elements:

2.10.4.2. 2. Engage price-to-win as early as possible and update as new information comes to Light

2.10.4.2.1. Price-to-win is used to identify what kind of solution your team should offer and the price point at which you should offer it.

2.10.4.2.2. it should be engaged as early in the proposal process as possible before a solution is developed.

2.10.4.2.3. Price-to-win is needed for effective best value solution development.

2.10.4.2.4. Price-to-win activities are a continuous process, extending throughout the opportunity phase through post-award

2.10.4.3. 3. Employ information systems and analysis tools.

2.10.4.3.1. A customer relationship management (CRM) system and an internal knowledge base are important to mature organizations for

2.10.4.3.2. The most useful analysis tools for price-to-win analysis are custom built using spreadsheets

2.10.4.4. 4. Gain as much customer intelligence as possible.

2.10.4.4.1. In the commercial environment, you wouldn't quote a price without knowing whether it was available winning price.

2.10.4.4.2. The best intelligence sources are people, especially those in your own organization. Customer intelligence can be obtained from

2.10.4.4.3. Intelligence about the customer's authorized funding and what it is able to spend on the project is vital.

2.10.4.4.4. Other important information about the customer might include:

2.10.4.5. 5. Gain as much competitor intelligence as possible.

2.10.4.5.1. Competitive analysis can help establish what your competitors' bid and actual award prices would be based on prior similar contracts.

2.10.4.5.2. Other sources of competitive intelligence include:

2.10.4.5.3. Consider previous contracts awarded to likely competitors and the budgets for those acquisitions. Use findings to estimate where competitors might position their offers on the current opportunity. Similar contracts awarded by other customers may serve as additional data points.

2.10.4.6. 6. Maintain strong opportunity activities parallel to price-to-win analysis.

2.10.4.7. 7. Focus pricing on value to the customer.

2.10.4.8. 8. Align pricing strategy with your sales strategy.

2.10.5. Common Pitfalls and Misconceptions

2.10.5.1. Belief that price-to-win is an externally set parameter

2.10.5.1.1. Price-to-win

2.10.5.2. Failure to embrace price-to-win concepts

2.10.5.2.1. Misunderstanding the importance of price-to-win leads many companies to "lose on price. "

2.10.5.2.2. Many companies think price-to-win is the lowest price they can set after examining their own bottom-up costing. This is not true and can lead to a loss.

2.10.6. Summary

2.10.6.1. Getting to a price-to-win target range is an iterative process that begins early in the procurement cycle and continues throughout the life of the opportunity and beyond to lessons learned after the win.

2.10.6.2. Information obtained about:

2.10.6.2.1. the customer,

2.10.6.2.2. the competition,

2.10.6.2.3. one's own organization

2.10.6.3. Custom spreadsheets and market intelligence gathering are important tools for assessing price-to-win.

2.10.6.4. All things being equal, a winning price must offer value to the customer. It is up to offerors to learn from their customers what constitutes value to them.

2.10.7. Terms to Know

2.10.7.1. Pricing, Bottom-up

2.10.7.2. Pricing, Top-down

2.10.7.3. Price-to-Win

2.11. 11. Teaming

2.11.1. Introduction

2.11.1.1. Teaming with other businesses can help companies fill competency gaps and increase their wining probability. To succeed, however, recruitment and management of teaming partners must be approached with care.

2.11.1.2. The larger and more complex a contract opportunity, the more likely it is that prime bidders will need to form teams of multiple companies to provide the resources and solutions required in an RFP

2.11.1.3. There is a complicated, delicate balance of strategy and tactics required to assemble a winning team.

2.11.1.3.1. Effective teaming strategy can significantly improve a bidder's win probability.

2.11.1.3.2. Poor executed strategy can create serious performance, reputation, legal, and financial problems.

2.11.2. Best Practices

2.11.2.1. 1. Determine objectively whether teaming is needed to strengthen a win strategy or a competitive position.

2.11.2.2. 2. Identify, evaluate, select, and recruit teaming partners.

2.11.2.2.1. Teaming partners should be selected primarily on their ability to increase win probability and secondarily on their ability to work cohesively with the team and customer under the conditions of the proposed contract.

2.11.2.2.2. Fill out a bidder comparison matrix. Use data to identify an optimum mix of teaming candidates that strengthen your weaknesses and improve your score based on expected evaluation criteria

2.11.2.2.3. If you don't have a relationship with the company, then reach out on a peer-to-peer basis (business development, C-level, operations, etc.) to have the same discussion.

2.11.2.3. 3. Select the most appropriate team structure.

2.11.2.3.1. Traditional prime/subteam.

2.11.2.3.2. Joint venture team.

2.11.2.3.3. Partner arrangement.

2.11.2.3.4. Prime contractor with subcontractor pools.

2.11.2.3.5. Mentor-protege arrangements.

2.11.2.3.6. Company-specific versus integrated project teams.

2.11.2.4. 4. Negotiate and document effective teaming agreements and subcontracts.

2.11.2.5. 5. Optimize and strengthen the competitiveness of the team.

2.11.3. Common Pitfalls and Misconceptions

2.11.3.1. 1. Automatically teaming with strategic partners

2.11.3.2. 2. Delaying senior management approval

2.11.3.3. 3. Miscommunications related to teammates' price/cost

2.11.3.4. 4. Data and intellectual property rights

2.11.4. Summary

2.11.4.1. 1. Objectively assess your company's resources and capabilities to identify gaps and deficiencies compared to the customer's expectations and competitors' capabilities.

2.11.4.2. 2. Determine if teaming with selected companies could create a winning bid.

2.11.4.3. 3. Choose teaming partners based on their ability to increase the win probability and ability to work cohesively with the team and customer under the conditions of the proposed contract.

2.11.4.4. 4. Assemble your team by recruiting the selected companies, clearly negotiating defined roles and responsibilities, and codifying the arrangements in legally binding teaming agreements.

2.11.4.5. 5. Optimize and manage the team to maximize your competitive position and win probability.

3. Part 2: Create Deliverables

3.1. 12. Compliance Matrix

3.1.1. Introduction

3.1.1.1. The compliance matrix is a tool for managing response preparation and demonstrating compliance to the customer

3.1.1.2. A good compliance matrix also serves as a plan of action for writers

3.1.1.3. You also can-and should-use a compliance matrix to make the evaluator's task easier. even when it is not specifically required.

3.1.2. Best Practices

3.1.2.1. 1. Prepare a comprehensive compliance matrix for every bid request

3.1.2.1.1. Introduction

3.1.2.1.2. Submittal instructions

3.1.2.1.3. Requirements

3.1.2.1.4. Internal compliance It can also be used by proposal team members in different ways, such as:

3.1.2.2. 2. Build the compliance matrix early.

3.1.2.2.1. preparing a compliance matrix saves time by reducing mistakes and rework. It helps teams break down requirements and bunch them into bundles appropriate for different sets of stakeholders

3.1.2.2.2. The compliance matrix also goes a long way toward preventing the big mistake that can sink an otherwise potential winning bid: an overlooked requirement.

3.1.2.3. 3. Shred the RFP Line by Line.

3.1.2.3.1. Resist the urge to save time by shredding RFP requirements only by section or paragraph

3.1.2.3.2. Separate every requirement (e.g., every "shall," "will," "must") into separate rows within your compliance matrix.

3.1.2.4. 4. Tailor the compliance matrix for your customer and setting.

3.1.2.4.1. Customize the content of your compliance matrix to the situation and team needs. A basic compliance matrix starts out with the following:

3.1.2.4.2. If you plan to extend your compliance matrix to provide guidance to writers , you can include information such as:

3.1.2.5. 5. Create your compliance matrix using a spreadsheet application.

3.1.2.5.1. The sorting function also enables users to toggle between ordering the compliance matrix by proposal section or RFP section. This can be a big time saver

3.1.2.5.2. Spreadsheet programs also enable the Proposal Manager to quickly and easily hide columns for different users.

3.1.2.6. 6. Follow the customer's Lead.

3.1.2.6.1. Follow the numbering system used in the RFP in your compliance matrix and in your proposal.

3.1.2.6.2. To increase your customer focus, use the customer's words and phrases in the compliance matrix.

3.1.2.6.3. Do not paraphrase or substitute your own preferred terms

3.1.2.6.4. Begin each item with the action verb used in the bid request,

3.1.2.7. 7. Keep the compliance matrix up to date throughout the proposal process.

3.1.2.7.1. Building the compliance matrix is part of proposal planning, but it must be continually updated throughout the proposal process.

3.1.2.8. 8. Submit a response matrix with your proposal.

3.1.2.8.1. A response matrix is a simplified version of your compliance matrix.

3.1.2.8.2. It is a derivative of the compliance matrix that shows where a given requirement is answered.

3.1.2.8.3. It serves as a roadmap for elevators to easly connect each proposal section to its respective compliance items. This matrix identifies where in the proposal you have addressed the solicitation requirements.

3.1.2.9. 9. Enhance compliance with responsiveness.

3.1.2.9.1. Before completing a compliance matrix, carefully review all "partially comply" and "non-comply" responses against customer requirements. If possi­ble, update responses to comply as closely as you can.

3.1.2.9.2. "Nice to haves" are additional requirements that are usually important for only a part of the customer's organization.

3.1.2.10. 10. Use the compliance matrix as a selling tool.

3.1.2.10.1. RFPs typically don't specify a compliance matrix format. (If they do, follow it explicitly.) This means you can use the compliance matrix as more than just an index-you can use it to sell.

3.1.2.10.2. Construct a compliance matrix that doesn't merely state the requirements and directions to the response (more work for the evaluator), but contains a brief statement of the proof of the compliance (less work for the evaluator) that also reiterates a win theme or discriminator (selling the solution).

3.1.2.10.3. Make the layout of the compliance matrix as user-friendly as possible. Having requirements and responses in separate columns can result in hard-to-read layouts, especially if the requirement is long and detailed. One way to work around this is to design a table that lines up the Requirement in one row and Response in the row below, then shade the response a different color than the requirement. Make it easy to read, and make the summaries brief and concise.

3.1.3. Summary

3.1.3.1. A compliance matrix is both a guide to the evaluator and a checklist for the Proposal Manager to make sure every requirement is answered.

3.1.3.2. Compliance matrices can also serve as a guide to writers. They should be created early in the proposal process, before writing begins.

3.1.3.3. The compliance matrix also serves as a response assignment matrix for the Proposal Manager to effectively manage and follow up on responses from different stakeholders.

3.1.3.4. A good compliance matrix ensures that all customer requirements have been answered and provides the customer an easy guide for understanding the response.

3.1.3.5. A compliance matrix should always be used in any proposal in any industry.

3.1.3.6. Proposal developers can develop a compliance matrix by shredding an RFP line by line.

3.1.4. Terms to Know

3.1.4.1. Compliance Matrix

3.1.4.2. Compliant versus Responsive

3.1.4.3. Response Matrix

3.2. 13. Proposal Organization

3.2.1. Introduction

3.2.1.1. Proposal evaluators often scan rather than carefully read proposals to find the answers they need. For this reason, information should be easy to locate and understand.

3.2.1.2. Proposals that are well organized and easy to understand have the following attributes:

3.2.1.2.1. They provide a roadmap to how the proposal is organized.

3.2.1.2.2. They make key points for evaporators to identify and understand.

3.2.1.2.3. They are written from the customer's point of view, evidenced in the organization scheme.

3.2.1.2.4. They tell customers what is important to them.

3.2.1.2.5. Theu use multiple highlighting techniques (headings, roadmaps, graphics, etc.) to enable evaluators to scan the document and locate the information theu need.

3.2.2. Best Practices

3.2.2.1. 1. Plan content before you write.

3.2.2.1.1. Content plans are essential in team writing efforts. Use key team members to build the content plan.

3.2.2.1.2. Content plans help writers plan and structure their thinking before beginning to write

3.2.2.1.3. It also captures proposal strategies and shows writers where and how to include the strategies in written content

3.2.2.1.4. Carefully planning can ensure you have clearly communicated your win themes and are on track to producing a compliant, consistent proposal

3.2.2.1.5. Draft value propositions and include these in content plans.

3.2.2.1.6. A few common planning tools are

3.2.2.2. 2. Organize your bid or proposal according to the customer's instructions.

3.2.2.2.1. Use the exact headings from the bid request. and include all sections that the customer requires.

3.2.2.2.2. Prepare a top-level, topical outline that follows the prospect 's organizational priority

3.2.2.2.3. Mimic the numbering system, naming conventions, and order listed in the bid request.

3.2.2.3. 3. Make information easy for evaluators to find.

3.2.2.3.1. The introduction to the proposal and all subsequent sections should provide a roadmap for what follows. Plan summaries at all levels of the proposal to reinforce key information

3.2.2.3.2. Headings are a key way to direct evaluators to information. They clearly mark when you are moving from/to the next key point. Use headings to organize and announce content.

3.2.2.3.3. Use both telegraphic headings and informative headings throughout the proposal

3.2.2.3.4. Executive Summary

3.2.2.4. 4. Use a structure that Layers information for the reader.

3.2.2.4.1. For responses in which you have some flexibility, structure your points in a way that "layers" information for the reader

3.2.2.4.2. Begin by introducing a topic (e.g., your solution) and explaining it at a high level.

3.2.2.4.3. Gradually add to your explanation with supporting facts and claims

3.2.2.4.4. (these could be the features and benefits of your solution).

3.2.2.4.5. Next, give proof for your claims with examples, case studies, and other details (e.g., descriptions of your past performance).

3.2.2.4.6. Finally, write a conclusion that summarizes your main points and reinforces your position.

3.2.2.5. 5. Group similar ideas and avoid redundancy.

3.2.2.5.1. To limit confusion, examine an RFP before writing and use content plans to help writers identify and group similar ideas.

3.2.2.5.2. If an RFP does not require a particular structure, group similar ideas together and eliminate redundancies.

3.2.2.5.3. If the RFP has specific instructions for response structure, use the following guidelines:

3.2.2.6. 6. Put the most important points first.

3.2.2.6.1. This technique helps busy proposal reviewers, who want to get to the heart of your solution as quickly as they can.

3.2.2.6.2. The faster you can give them a compliant response, the faster they can score the question and move on.

3.2.3. Common Pitfalls and Misconceptions

3.2.3.1. Writing before planning

3.2.3.1.1. Ideally, teams should plan proposals using a content planning tool to organize their most important points.

3.2.3.1.2. Only when a solution is fully planned, organized, and illustrated should the team begin to write.

3.2.3.1.3. Content planning doesn't have to be complicated-it simply means thinking before you write.

3.2.4. Summary

3.2.4.1. Content planning matters because proposal evaluators are short on time. The more easily they can get the information they need from your proposal, the better.

3.2.4.2. Proposals should be organized with customers in mind, following their requirements and making navigation simple.

3.2.4.3. One way to make reviewers' jobs easier is to put the most important information first, followed by less critical information.

3.2.4.4. Content planning should always precede actual writing. In fact, the writing stage should come last.

3.2.5. Terms to Know

3.3. 14. Persuasive Writing

3.3.1. Introduction

3.3.1.1. Well-written proposals draw on the techniques of persuasive writing.

3.3.1.2. Proposal writers and managers can Learn and apply persuasive writing techniques to win business and build partnerships.

3.3.1.3. Persuasive writing is:

3.3.1.3.1. Personal.

3.3.1.3.2. About probabilities.

3.3.1.3.3. Conclusive.

3.3.2. Best Practices

3.3.2.1. 1. Know your audience so you can use the right techniques to match their perspectives.

3.3.2.1.1. Persuasive writing is all about the audience.

3.3.2.1.2. Be specific.

3.3.2.1.3. Make it personal.

3.3.2.1.4. Find common values.

3.3.2.2. 2. Apply the traditional rhetorical principles of argument.

3.3.2.2.1. your proposals will be more persuasive if you build them in a logical sequence

3.3.2.2.2. The rhetorical structure makes perfect, logical sense:

3.3.2.2.3. Establish the validity of your proposal with Logic

3.3.2.2.4. Appeal to the emotions of your audience

3.3.2.2.5. Figure

3.3.2.3. 3. Anticipate your readers' questions so you can remove reasons for rejection.

3.3.2.4. 4. Apply Cialdini's Weapons of Influence to hone your arguments with Lessons from modern behavioral science.

3.3.2.4.1. Persuasion is presenting a case in such a way as to sway the opinion of others, make people believe certain information, or motivate a decision.

3.3.2.4.2. Influence is having a vision of the optimum outcome for a situation or organization and then, motivating people to work together toward making the vision a reality."

3.3.2.4.3. Weapons of Influence

3.3.2.4.4. Figure

3.3.2.5. 5. Use graphics and multimedia to immerse your audience in the potential of your solution.

3.3.2.5.1. Graphics are powerful tools for persuading audiences. Graphic design influences:

3.3.3. Common Pitfalls and Misconceptions

3.3.3.1. Importance of asking for what you want

3.3.4. Summary

3.3.4.1. Persuasive writing is completely about the reader. Craft every strategy, theme, section, and line with the reader in mind.

3.3.4.2. Rely on the classic techniques of persuasion and adapt and enhance them using research in human behavior.

3.3.4.3. innovatlvely apply sound graphical design and multimedia technologies to persuade tech- and media savvy audiences.

3.3.4.4. Adapt your use of persuasive techniques to match the cultural backgrounds of your audiences.

3.3.5. Terms to Know

3.3.5.1. Principles of Influence

3.3.5.2. Rhetoric

3.4. 15. Writing Clearly

3.4.1. Introduction

3.4.1.1. If your writing is clear, your readers probably won't notice

3.4.1.2. The root cause of unclear business communication is style, not form or grammar.

3.4.2. Best Practices

3.4.2.1. 1. Tell stories.

3.4.2.1.1. "Storytelling is fundamental to human behavior. No other form of prose can communicate large amounts of information so quickly and persuasively."

3.4.2.2. 2. Write Like you talk.

3.4.2.2.1. Use simple words with precision

3.4.2.2.2. Use jargon only when it's clearly to your advantage to do so

3.4.2.2.3. Build intimacy with your reader through personal pronouns.

3.4.2.2.4. Use contractions as needed to create an informal, friendly tone

3.4.2.2.5. Use a variety of punctuation to engage readers.

3.4.2.3. 3. Write tight.

3.4.2.3.1. State your idea up front and make sure everything else relates.

3.4.2.3.2. Provide a point statement for a powerful takeaway.

3.4.2.3.3. Keep paragraphs short.

3.4.2.3.4. Tie your sentences together to make unified paragraphs.

3.4.2.3.5. Use only the words your readers need.

3.4.2.3.6. Watch out for Long strings of nouns in succession, or "noun stacks."

3.4.2.3.7. Use concrete images and precise measures.

3.4.2.3.8. Be consistent when using technical terms.

3.4.2.3.9. Stay positive.

3.4.2.4. 4. Show your document's structure

3.4.2.4.1. Write informative headings.

3.4.2.5. 5. Plan to revise.

3.4.3. Common Pitfalls and Misconceptions

3.4.3.1. Using proposals as technical references

3.4.3.1.1. Many proposal contributors and even some proposal managers think that proposal content must be the dense, complex, and jargon-ridden prose of technical manuals because technical experts compose the primary audience or are the key influencers for decisions.

3.4.3.2. Writing proposals in objective, formal language

3.4.4. Summary

3.4.4.1. Follow the principles of clear writing and plain language to improve your chances of winning business.

3.4.4.2. Understand that all readers appreciate clear writing, even technical experts, keeping in mind that teams of analysts from a variety of backgrounds and expertise assess proposals.

3.4.4.3. Investigate ways to incorporate modern multimedia techniques (video, animation, interactive demonstrations) to keep up with communication trends.

3.4.4.4. Analyze and understand your readers so you can anticipate their needs, write to their expectations, and accommodate their communication and cultural preferences.

3.4.4.5. Revise your work to reduce the cost of rework, to test the validity of your ideas revealed by plain language, and to ensure the integrity of your content.

3.4.5. Terms to Know

3.4.5.1. Active/Passive Voice

3.4.5.2. Nominalization

3.4.5.3. Noun Stack

3.4.5.4. Style Sheet

3.4.5.5. Transitions

3.5. 16. Headings

3.5.1. Introduction

3.5.1.1. Headings help evaluators quickly understand your proposal's organization and key points.

3.5.1.2. Effective headings

3.5.1.2.1. Give readers an overview of the story of your proposal and can help you earn higher evaluation scores.

3.5.1.2.2. Effective headings highlight your solution's benefits and discriminators.

3.5.1.2.3. Should convey a clear message,

3.5.1.2.4. Capture the reader's attention,

3.5.1.2.5. Address evaluators' hot buttons or specific requirements.

3.5.1.3. Headings accomplish the following goals:

3.5.1.3.1. Break large amounts of text into smaller, more manageable sections

3.5.1.3.2. Make important information easy to locate

3.5.1.3.3. Simplify complicated information

3.5.1.3.4. Make your proposal easier to score

3.5.1.3.5. Guide readers through your "proposal story

3.5.2. Best Practices

3.5.2.1. 1. Follow exact bid request instructions for proposal headings, including heading content, numbering scheme, and heading Levels

3.5.2.2. 2. Use an informal table of contents.

3.5.2.2.1. Including an introductory paragraph at the beginning of each section aids clear responses and gives evaluators an idea of what information to expect in the section that follows.

3.5.2.2.2. Proposal professionals refer to this paragraph as an informal table of contents or section introduction.

3.5.2.2.3. Review this introductory section every time you edit a section or heading in the proposal content. Ensure omissions or additions to the write-up are reflected in the informal table of contents.

3.5.2.2.4. Example

3.5.2.3. 3. Use headings to convey key benefits and discriminators.

3.5.2.4. 4. Use informative and telegraphic headings as appropriate.

3.5.2.5. 5. Use verb headings to convey action and noun headings to demonstrate your purpose.

3.5.2.5.1. Verbs

3.5.2.5.2. Noun

3.5.2.6. 6. Create a clear hierarchy of information.

3.5.2.6.1. Numbered headings help evaluators find responses to requirements in longer proposals (more than 10 pages). However, headings with more than three levels can create confusion.

3.5.2.6.2. After level three, use run-in headings to give a similar effect to a new subheading without creating additional heading levels. A run-in heading may be in boldface or a large font; text follows after a period or a colon and a space.

3.5.2.7. 7. Maintain consistency throughout your document.

3.5.2.7.1. Headings can be aligned right or left, centered, indented, or presented as run-in headings. No matter what style you choose, ensure headings at the same level are consistent throughout your proposal.

3.5.3. Summary

3.5.3.1. Effective headings attract readers' attention, tell them what to expect in subsequent sections, and help evaluators find responses to specific questions easily.

3.5.3.2. Where possible, use the exact headings listed in the RFP, especially i n government proposals.

3.5.3.3. The most effective headings are informative, numbered, and consistent in structure.

3.5.3.4. Verb headings express action and noun headings state a purpose.

3.5.3.5. Make your subheadings identical with the topics listed in your introductory sections. Review the listed topics every time you modify your text.

3.5.3.6. Consistency in heading styles is critical; proposal producers should create their own libraries of heading styles.

3.5.4. Terms to Know

3.5.4.1. Benefit

3.5.4.2. Discriminator

3.5.4.3. Feature

3.5.4.4. Hot Buttons

3.5.4.5. Informative Heading

3.5.4.6. Telegraphic Heading

3.5.4.7. Value Proposition

3.6. 17. Graphics and Action Captions

3.6.1. Introduction

3.6.1.1. Graphics and action captions make complex content easier to understand and remember.

3.6.1.2. Clear, compelling, audience-focused graphics and action captions improve win rates.

3.6.1.3. Visual aids are 43 percent more persuasive than those that do not.

3.6.1.4. Research shows:

3.6.1.4.1. Graphics lead to a more profound and accurate understanding of presented material.

3.6.1.4.2. Graphics grab our attention and may influence how (and whether) we attend to the rest of a story.

3.6.1.4.3. Graphics enhance or affect emotions and attitudes, and emotions influence the very mechanisms of rational thinking.

3.6.1.5. The combination of graphics and words has a communicative power that neither singularly possesses

3.6.2. Best Practices

3.6.2.1. 1. Know when, where, and why to use graphics and action captions.

3.6.2.1.1. It's best to create graphics and action captions before you write a proposal

3.6.2.1.2. Begin with an action caption, then create supporting graphics

3.6.2.1.3. .. then, use the graphics and captions as a roadmap for writing.

3.6.2.1.4. Making graphics first ensures the team is on the same page,

3.6.2.1.5. There are three situations in which proposal graphics are especially important:

3.6.2.1.6. To improve your likelihood of winning, make your proposal easy to review and evaluate. Here are a few ways to do this:

3.6.2.2. 2. Write action captions and conceptualize graphics before rendering.

3.6.2.2.1. Your action caption should be the message you want your graphic to convey and should be no longer than one sentence.

3.6.2.2.2. The simpler you can make an action caption, the better.

3.6.2.2.3. Actions captions are composed of three parts:

3.6.2.2.4. Avoid graphic reuse unless on existing graphic is consistent with

3.6.2.2.5. The Four Steps for Developing Successful Proposal Graphics

3.6.2.3. 3. Understand and use basic design principles.

3.6.2.3.1. Color.

3.6.2.3.2. Style.

3.6.2.3.3. Consistency.

3.6.2.3.4. Grid.

3.6.2.3.5. Balance.

3.6.2.3.6. Shapes.

3.6.2.4. 4. Use templates.

3.6.2.4.1. A graphic template is a key ingredient to quickly developing quality graphics.

3.6.2.4.2. The resulting graphics demonstrate that the solution provider is acting as a team with one consistent vision

3.6.2.4.3. Your template should take into consideration the following variables:

3.6.2.5. 5. Objectively validate your graphics against

3.6.2.5.1. Content:

3.6.2.5.2. Aesthetics:

3.6.2.6. 6. Understand copyright Law.

3.6.2.6.1. If you do not hove permission from the owner of an image, you cannot legally use that image in your proposal.

3.6.2.6.2. Copyright low stipulates that once on image is created, the owner holds the rights to that image.

3.6.2.7. 7. Know the differences between graphic file formats.

3.6.2.7.1. Proposal graphics ore usually at a print resolution of 150 to 300 dots per inch, or DPI.

3.6.2.7.2. Some file formats allow image compression (e.g. , JPG). Compression decreases file size by lowering image quality. Avoid heavy compression when possible.

3.6.2.7.3. Some file formats allow image compression (e.g. , JPG). Compression decreases file size by lowering image quality. Avoid heavy compression when possible.

3.6.3. Common Pitfalls and Misconceptions

3.6.3.1. Using more detail than needed

3.6.3.1.1. A visual becomes too complicated when the author attempts to convey too many messages in one graphic or includes too much detail. This typically results from a poorly written or missing action caption.

3.6.3.2. Failing to explain yourself

3.6.3.2.1. An unclear graphic, due to lock of identification and/or explanation, happens when the author erroneously assumes that the customer understands the subject matter on the some level that he or she does.

3.6.3.3. Making design mistakes

3.6.3.3.1. Poorly rendered graphics result from a lock of design skill . These graphics ore homogeneous at best and unprofessional at worst.

3.6.4. Summary

3.6.4.1. Write customer-focused action captions before conceptualizing and rendering graphics.

3.6.4.2. Create graphics before writing your proposal.

3.6.4.3. Start with a graphic that summarizes your entire proposal (e.g., executive summary) and use it as a roadmap during proposal development.

3.6.4.4. Use on objective, repeatable process and graphic templates to ensure consistency, lower cost, and improve win rotes.

3.6.4.5. Know when and when not to use graphics.

3.6.4.6. Ensure that all aesthetic decisions hove a clear purpose that is consistent with the RFP, audience, and message.

3.6.4.7. Track graphics development to effectively schedule and staff graphics support for future proposals. Understand that the style and professionalism of your graphics reflects your company culture, the professionalism of your company, and the quality of your solution.

3.6.5. Terms to Know

3.6.5.1. Action Caption

3.6.5.2. Aesthetics

3.6.5.3. Balance (Visual)

3.6.5.4. Graphics Template

3.7. 18. Page and Document Design

3.7.1. Introduction

3.7.1.1. A proposal's visual presentation is nearly as important as its content.

3.7.1.2. Application of design principles, combined with clear production timelines, can help you create a compliant and consistent document.

3.7.1.3. The overall design and layout of your proposal documents is critical for

3.7.1.3.1. communicating your information,

3.7.1.3.2. making on impression on reviewers and evaluators

3.7.1.4. For starters, documents must:

3.7.1.4.1. Follow instructions or guidelines from your customer, your company, and/or your writing outline

3.7.1.4.2. Be aesthetically appealing in on appropriate and professional way

3.7.1.4.3. Use design techniques to highlight specific text and information

3.7.1.4.4. Be produced efficiently using the tools and resources available

3.7.2. Best Practices

3.7.2.1. 1. Understand the desktop publisher's role.

3.7.2.1.1. creating and implementing a document template that is compliant with instructions and applied consistently over all pages or files of a proposal submission

3.7.2.1.2. insert, label, and number graphics within a document

3.7.2.1.3. implement a list of figures and tables;

3.7.2.1.4. coordinate with editors, writers, and graphic designers to ensure consistent style

3.7.2.1.5. interface with any physical production, including printing and creation of electronic files.

3.7.2.2. 2. Choose the right tools.

3.7.2.3. 3. Create a document template to ensure compliance and consistency.

3.7.2.3.1. A document template must first be compliant:

3.7.2.3.2. Second, a document must be consistent.

3.7.2.3.3. A document template includes

3.7.2.4. 4. Schedule effectively using metrics.

3.7.2.4.1. Documents may be formatted in parallel to writing/editing

3.7.2.4.2. Formatting should align with major review cycles and may require reformatting or rechecking of formatting

3.7.2.4.3. Documents are often formatted several times throughout a proposal review cycle before final formatting,

3.7.2.4.4. Successful teams track productivity metrics over time

3.7.2.5. 5. Prepare for production.

3.7.2.6. 6. Use graphic elements to create emphasis and guide readers.

3.7.2.6.1. Beyond being consistent and compliant, proposals should be easy to understand and evaluate

3.7.2.6.2. This top - down reading or viewing is interrupted by items that contrast with the rest of the page, including items that are

3.7.2.7. 7. Apply six design strategies to create effective Layouts.

3.7.2.7.1. Contrast

3.7.2.7.2. Proximity

3.7.2.7.3. White space

3.7.2.7.4. Consistency

3.7.2.7.5. Balance

3.7.2.7.6. Alignment

3.7.3. Common Pitfalls and Misconceptions

3.7.3.1. Presumptions about staffing and resources

3.7.3.2. Inconsistency in document formatting

3.7.4. Summary

3.7.4.1. Ensure your entire team understands that effective, consistent application of page design is critical for improving readability and understanding of information.

3.7.4.2. Always schedule appropriate time for formatting and desktop publishing using metrics and based around major reviews.

3.7.4.3. Develop a document template based on customer requirements and corporate brand standards with defined and repeatable processes/procedures early, and communicate templates clearly to your team.

3.7.4.4. Train your team and stay up to date on software/application trends; don't expect teammates to understand how a piece of software works simply because it is on their computer.

3.8. 19. Cost and Pricing Data

3.8.1. Introduction

3.8.1.1. Cost and pricing data are developed based on past performance and customers' perceptions of value.

3.8.1.2. Cost and pricing are highly dependent on the setting

3.8.1.3. Pricing may differs between government and commercial settings because bids for government agencies often have strict regulations regarding pricing data.

3.8.1.4. Before you consider bidding for a government procurement, be sure you understand acquisition rules and regulations

3.8.1.5. Showing what your price comprises demonstrates your logical approach and gives credibility to your proposal

3.8.2. Best Practices

3.8.2.1. 1. Distinguish between price, value, and added value.

3.8.2.1.1. Price is what you charge a customer for a product or service.

3.8.2.1.2. Value is what your customer perceives your product or service is worth.

3.8.2.1.3. Added value is defined as the difference between the customer's perceived value of a solution and the price they pay , plus any implementation costs

3.8.2.1.4. The following is usually true of winning prices

3.8.2.2. 2. Present cost and pricing data in a summary form

3.8.2.2.1. Presenting a cost section executive summary is essential to gaining credibility and making your value proposition a complete circle with the technical proposal.

3.8.2.2.2. In your summary, make sure you reach as many of these objectives as possible:

3.8.2.3. 3. Use graphics to clearly convey value.

3.8.2.3.1. Use graphics, tables. and charts to quickly give the reader a snapshot of the message you are delivering.

3.8.2.3.2. suggested methods to present cost and pricing data

3.8.2.4. 4. Quantify all claims with measurable data

3.8.2.4.1. To substantiate your cost or pricing data, you must present facts.

3.8.2.4.2. Your facts not only validate what you are claiming and lend credibility to your organization

3.8.2.4.3. Justify and build your case for your costs with your past performance historical information.

3.8.2.4.4. Bottom-up Pricing

3.8.2.4.5. Cost analysts rank estimated rationale in the following order, from most to least reliable:

3.8.3. Summary

3.8.3.1. Cost and pricing data must be based on facts rather than judgment.

3.8.3.2. To add value, you must know what your customer considers valuable. Use customer intelligence to shape your proposal pricing.

3.8.3.3. A quick and easy way to convey value is by using graphics. Choose the right graphic for the data you need to display.

3.8.3.4. The cost executive summary is crucial to gaining credibility with the evaluator and making your value proposition sell.

3.8.4. Terms to Know

3.8.4.1. Cost Section

3.8.4.2. Pricing, Bottom-Up

3.8.4.3. Pricing, Top-Down

3.9. 20. Proactive Proposals

3.9.1. Introduction

3.9.1.1. Proactive proposal(s)

3.9.1.1.1. are submitted without a formal customer request. Vendors can use them to address unmet customer needs

3.9.1.1.2. generated after an informal discussion with a customer, such as a sales visit or phone call

3.9.1.1.3. might be disguised as

3.9.1.2. Other terms for a proactive proposal are

3.9.1.2.1. sales letter

3.9.1.2.2. sales

3.9.1.2.3. commercial

3.9.1.2.4. unsolicited

3.9.2. Best Practices

3.9.2.1. 1. Confirm customer interest in your solution.

3.9.2.1.1. Preparing and submitting an unsolicited proposal has about the same probability of success as a mass or bulk mailing (near zero).

3.9.2.1.2. However, a proactive proposal might be a best practice under the following conditions:

3.9.2.2. 2. Determine your objective and design your proposal around achieving it.

3.9.2.2.1. To develop the most effective proactive proposal possible, you must define your objective more precisely.

3.9.2.2.2. If your objective is to persuade this customer to forgo competitive bidding, then focus on the opportunity cost of delayed implementation.

3.9.2.2.3. If your objective is to persuade this customer to meet, then proposing a complete solution is premature

3.9.2.3. 3. Organize according to the customer's hot-button issues, without customer direction.

3.9.2.3.1. Address these fundamental elements of persuasive writing in your proactive proposals:

3.9.2.3.2. Consider two organizational patterns:

3.9.2.4. 4. Use graphics with action captions to differentiate your proposal.

3.9.2.5. 5. Limit attached or appended materials.

3.9.2.5.1. Attached information dilutes your message and discourages readers confronting what appears to be a Large document.

3.9.2.5.2. Instead, List additional materials that are available and explain how they can be viewed or obtained.

3.9.3. Summary

3.9.3.1. Confirm a customer's interest before determining whether to prepare and submit a proactive proposal. Limit your proposal to the content necessary to advance this sale.

3.9.3.2. Adopt a customer-focused document organization, either as requested or according to the customer's hot-button issues.

3.9.3.3. Use graphics with action captions to convey persuasive information efficiently and effectively.

3.9.3.4. If content does not directly support your objective, eliminate it, either reserving it for a subsequent client request or noting where customers can access supporting material at their convenience.

3.9.4. Terms to Know

3.9.4.1. Action Caption

3.9.4.2. Benefit

3.9.4.3. Compliant Versus Responsive

3.9.4.4. Customer Issues

3.9.4.5. Feature

3.9.4.6. Graphics

3.9.4.7. Hot Buttons

3.9.4.8. Informative Heading

3.9.4.9. Persuasive Writing

3.9.4.10. Proactive Proposal

4. Part 3: Manage Processes

4.1. 21. End-to-end Process

4.1.1. Introduction

4.1.1.1. An end-to-end process is a systematic series of actions or steps directed toward a specific end.

4.1.1.2. Organizations that consistently follow a defined business development process:

4.1.1.2.1. win more business

4.1.1.2.2. and use fewer investment resources

4.1.1.3. The impetus to reengineer an organizations BD process often stems from situations such as:

4.1.1.3.1. Merged or restructured organizations

4.1.1.3.2. Changes in management

4.1.1.3.3. Sale of the organization

4.1.1.3.4. Failure to meet sales or win-rate goals

4.1.1.3.5. Loss of key customers or contracts

4.1.1.3.6. Staffing fluctuations

4.1.1.3.7. Maturing markets

4.1.1.3.8. Analysts' concerns affecting stock price

4.1.1.4. There is no one-size-fits-all process model

4.1.1.4.1. Due to the variability of the buying-selling cycle in various markets, there is no one-size-fits-all process model.

4.1.1.4.2. What works for a complex, multisector company may not work for a company whose proposal department consists of only one or two people

4.1.1.5. Every organization should design its own end-to-end BD process suited to its organization and customers-and gain senior executive support.

4.1.1.6. Generalized BD process

4.1.1.6.1. Common features that will pertain to most end-to-end processes include:

4.1.1.6.2. BD Phases

4.1.1.6.3. Figure

4.1.1.7. Bid Decisions.

4.1.1.7.1. Progressing from one phase to the next is determined by bid decisions, sometimes referred to as gate decisions.

4.1.1.7.2. These decisions are led by executives and address business and strategic issues.

4.1.1.7.3. Their primary purpose is to help teams make decisions regarding allocation or withdrawal of BD resources.

4.1.1.7.4. Disciplined bid decisions reduce BD costs by avoiding investment in low-probability opportunities.

4.1.1.7.5. The most successful organizations tend to bid less and win more

4.1.1.7.6. The major questions considered at each decision point are listed in the table below.

4.1.1.7.7. major questions considered at each decision

4.1.1.7.8. Figure

4.1.1.8. Team Reviews.

4.1.1.8.1. Team reviews are aimed at improving the quality of thinking and documentation of a pursuit.

4.1.1.8.2. The team reviews and expected outcomes

4.1.1.9. Outputs

4.1.1.9.1. Outputs are developed in each phase and become inputs to the next phase.

4.1.1.9.2. Beware of outputs required for no justifiable reason. If an output does not contribute to advancing the effort, you should eliminate it.

4.1.1.9.3. Outputs and their contents

4.1.1.10. Additional Elements on end-to-end BD process

4.1.1.10.1. The customer's buying process

4.1.1.10.2. Notional timeframes for phases, decisions, reviews, and outputs

4.1.1.10.3. Defined goals for each phase

4.1.1.10.4. Critical business decisions for each phase

4.1.1.10.5. Listing of activities embedded within each phase

4.1.1.10.6. Indication of accountable roles for all activities

4.1.1.10.7. Listing of tools, templates, and other aids associated with each activity

4.1.1.10.8. Notation of changes to pipeline status, CRM, or other tracking systems

4.1.2. Best Practices

4.1.2.1. 1. Create a documented, unified process.

4.1.2.1.1. BD-CMM

4.1.2.1.2. Organizations with a defined end-to-end BD process realize significant benefits:

4.1.2.1.3. In the absence of a defined BD process,

4.1.2.1.4. To achieve the second level of maturity (Repeatable), the organization must at least have a repeatable process for response generation.

4.1.2.1.5. At level three (Defined), a defined BD process allows teams of business developers with organizational competencies to focus on developing a winning solution guided by a shared understanding of process and roles.

4.1.2.1.6. When the BD process has been fully integrated with corporate operations, the benefits of levels four (Managed) and five (Optimizing) maturity can be realized.

4.1.2.2. 2. Align with the customer's buying cycle.

4.1.2.2.1. The customer's interests, priorities, and accessibility vary across their buying cycle

4.1.2.2.2. Create phases in the BD process that include activities responsive to the customer at each phase

4.1.2.2.3. Generic buying cycle:

4.1.2.3. 3. Make the process flexible and scalable.

4.1.2.3.1. The end-to-end process provides a baseline for designing a BD process tailored to any organization.

4.1.2.3.2. Tailoring begins by determining who the primary customers are. Are they governmental bodies (business-to-government) [B2G]) or other companies (business-to-business [B2B])?

4.1.2.3.3. A flexible process implies that phases, bid decisions, and team reviews are included based on the opportunity categories.

4.1.2.3.4. Commercial Business Development Process

4.1.2.4. 4. Clearly define roles.

4.1.2.4.1. Distinguish between roles and positions.

4.1.2.4.2. Identify supporting organizations.

4.1.2.5. 5. Develop needed staff competencies.

4.1.2.5.1. Rely on the competencies for "Proposal Managers" and "Opportunity Managers" identified by APMP as a baseline for establishing a training plan.

4.1.2.6. 6. Ensure consistent, disciplined use.

4.1.2.6.1. Designing and developing an end-to-end BD process is a straightforward task that most organizations can accomplish relatively quickly.

4.1.2.6.2. Even smaller organizations can adopt an existing process rather than continuing with ad hoc operations.

4.1.2.6.3. implementing and sustaining an effective BD process requires management focus and continuous effort.

4.1.2.6.4. Barriers include to BD is

4.1.2.6.5. To succeed, the launch of a new BD process must include a change-management plan. This plan must take into account the predictable stages that most individuals experience when faced with change.

4.1.2.6.6. Change management is a significant challenge and those attempting it should take advantage of guidance from experts in the field.

4.1.3. Common Pitfalls and Misconceptions

4.1.3.1. Lack of discipline and accountability

4.1.3.1.1. an organization must have the discipline to "walk the walk" and not just "talk the talk."

4.1.3.1.2. This begins with executive leadership

4.1.3.2. Lack of support with tools and training

4.1.3.2.1. The very best BD process will not be successful if it is not supported with appropriate tools and training.

4.1.3.3. Corporate inertia and changing priorities

4.1.4. Summary

4.1.4.1. A defined end-to-end BD process is critical to achieving high levels of BD capability. It is composed of a series of phases, decisions, reviews, and outputs.

4.1.4.2. The generic end-to-end process introduces the principles and best practices common across selling environments.

4.1.4.3. Organizations must develop tailored end-to-end processes that best support their company and their customers.

4.1.4.4. For an end-to-end BD process to be successful, a proactive change-management plan must support its implementation.

4.1.5. Terms to Know

4.1.5.1. Best and Final Offer (BAFO)

4.1.5.2. Bid Decisions (General)

4.1.5.3. Bid/No-Bid Decision

4.1.5.4. Bid Pursuit Decision

4.1.5.5. Bid Validation Decision

4.1.5.6. Business Case Review/Senior

4.1.5.7. Management Review

4.1.5.8. Business Development Phases

4.1.5.9. Competitive Intelligence

4.1.5.10. Competitor Review

4.1.5.11. Content Plan

4.1.5.12. Delivery

4.1.5.13. Executive Surnmoru

4.1.5.14. Final Document Review

4.1.5.15. Lessons Learned Review

4.1.5.16. Market Identification

4.1.5.17. Market Strategy

4.1.5.18. Opportunity Plan

4.1.5.19. Opportunity Plan Review

4.1.5.20. Opportunity Qualification Decision

4.1.5.21. Pricing Strategy

4.1.5.22. Proposal

4.1.5.23. Proposal Development

4.1.5.24. Proposal Outline

4.1.5.25. Proposal Planning

4.1.5.26. Proposal Responsibility Matrix

4.1.5.27. Proposal Strctequ Review

4.1.5.28. Response Matrix

4.1.5.29. Reviews (General)

4.1.5.30. Role (Relationship of Roles to Job Titles)

4.1.5.31. Style Sheet

4.2. 22. Gate Decisions

4.2.1. Introduction

4.2.1.1. A disciplined gate process is required to make effective decisions on whether to compete for business and can help organizations increase their win probability.

4.2.1.2. Bid decisions ore aimed at eliminating opportunities or soles leads with a low win probability, thus permitting stronger focus on opportunities with a higher win probability.

4.2.1.3. organizations should only pursue opportunities with a reasonable probability of win.

4.2.1.4. These important concepts drive successful gate-decision processes:

4.2.1.4.1. Organizations view gate decisions as critical to

4.2.1.4.2. Decisions to continue pursuits or to abandon opportunities are made at the gate-decision reviews.

4.2.1.4.3. Opportunities are qualified by

4.2.1.4.4. Gate decisions have a regular schedule on the organizational calendar that people understand and adhere to.

4.2.1.4.5. A formal team is established and tailored to the value and risk of the bid.

4.2.1.4.6. All gate decisions focus on answering three basic questions about a business opportunity:

4.2.2. Best Practices

4.2.2.1. 1. Make a series of gate decisions.

4.2.2.1.1. Gate decisions must be organized to achieve organizational objectives related to winning business and managing the cost of winning business.

4.2.2.1.2. Gate decisions ore normally organized around the following milestones related to business opportunities:

4.2.2.1.3. Gate decisions

4.2.2.2. 2. Standardize company templates and schedules.

4.2.2.2.1. Standardized templates and schedules promote effective decisionmaking. Meeting dates are known, expectations are set, and information to be presented for the decision is defined and understood.

4.2.2.2.2. In large organizations, gate decisions are generally scheduled for a consistent day, time, and location.

4.2.2.2.3. An opportunity plan template is used both for developing the opportunity plan and making gate decisions.

4.2.2.3. 3. Set expectations for information maturation across the gate-decision cycle.

4.2.2.3.1. Organizations must set reasonable expectations for information quality and maturity at various gate decisions.

4.2.2.3.2. As the opportunity matures, more information is expected

4.2.2.4. 4. Determine bid and proposal investment.

4.2.2.4.1. Gate decisions often focus on "is it worth it?"

4.2.2.4.2. Cost should always be determined based on what it will cost to win, not what it will cost to bid

4.2.2.4.3. Cost should include labor, other direct costs (consultants), travel, and incidentals required to develop and submit a winning bid.

4.2.2.5. 5. Establish company-appropriate decision criteria.

4.2.2.5.1. Most organizations develop first-order decision criteria to enable the rapid elimination of opportunities that do not contribute significantly to the organization's annual and strategic business objectives

4.2.2.5.2. Examples of these first-order metrics include:

4.2.2.6. 6. Determine probability of win and probability of go.

4.2.2.6.1. Probability of win and probability of go are broad-based calculations of an organization's likelihood of winning an opportunity.

4.2.2.6.2. They are generally expressed as

4.2.2.6.3. Probability of win

4.2.2.6.4. Probability of go

4.2.2.6.5. Industry-standard calculators can help with these analyses and are available from multiple sources.

4.2.2.7. 7. Understand who is responsible for gate decisions.

4.2.2.7.1. The leadership and presentation role changes at gate decisions as the opportunity progresses.

4.2.2.7.2. For the pursuit, the assigned Opportunity Manager assumes the lead and generally maintains it through the final review.

4.2.2.8. 8. Follow up on action items related to gate decisions.

4.2.2.8.1. Successful gate decisions depend on recording and following up on action items that fall out of gate decision reviews.

4.2.2.8.2. This affects opportunities receiving a "proceed" decision at the gate

4.2.2.8.3. Overview of gate decisions and the end-to-end BD process.

4.2.3. Common Pitfalls and Misconceptions

4.2.3.1. All opportunity information is known at the beginning of the cycle. → Set information maturity expectations for each review.

4.2.3.2. Strategy should remain static throughout decisions. → Win strategy is key and should be reassessed at every review.

4.2.3.3. You can't win a Low probability of win deal if you start early. → The right actions can make low probability of win deals high probability of win deals.

4.2.3.4. You can't Lose a high probability of win deal if you start Late. → A late start equals lower probability of win.

4.2.3.5. Probability of go has no value in the decision to pursue or not. → If a bid does not generate revenue, you cannot gain ROI.

4.2.3.6. Resourcing is unimportant in probability of win calculations. → Subpar teams do not often win.

4.2.3.7. Gates can be treated as reviews rather than decision points. → Deferring decisions wastes time and money.

4.2.3.8. Gate-decision quality is not indicative of probability of win → Strategy rules. Bad strategy is often associated with low probability of win.

4.2.3.9. Price-to-win can come Late in the gate process. → Competitive pricing strategy must come early to match the solution presented.

4.2.4. Summary

4.2.4.1. Gate decisions are a key component of the business development lifecycle.

4.2.4.2. Gate decisions prevent businesses from unnecessarily expending resources on bids they have a low probability of winning.

4.2.4.3. Consistent decision criteria can help organizations make decisions effectively.

4.2.4.4. Two important criteria are probability of win and probability of go, or the likelihood that a customer will actually proceed with a funded program upon making an award decision.

4.2.5. Terms to Know

4.2.5.1. Bid Decisions

4.2.5.2. Probability of Go

4.2.5.3. Probability of Win

4.2.5.4. Win Rate

4.3. 23. Kickoff Meeting Management

4.3.1. Introduction

4.3.1.1. Kickoff meetings are a team's introduction to a proposal effort.

4.3.1.2. A successful kickoff sets the stage for a successful proposal response.

4.3.1.3. A kickoff meeting is an early, major milestone in a proposal response.

4.3.1.4. It is included in the proposal management plan and should take place after RFP release.

4.3.1.5. The Proposal Manager generally leads kickoff meetings, supported by the Opportunity Manager.

4.3.2. Best Practices

4.3.2.1. 1. Understand when and why to conduct kickoff meetings.

4.3.2.1.1. Schedule kickoff meetings about 15 percent into the response timeframe

4.3.2.1.2. Plan the meeting using

4.3.2.1.3. The salesperson should explain

4.3.2.1.4. At this meeting, distribute a draft executive summary.

4.3.2.1.5. Kickoff meetings should be

4.3.2.1.6. Kickoff meetings have the following objectives:

4.3.2.1.7. A sample checklist can be used to plan a successful kickoff meeting.

4.3.2.1.8. Figure: The Goals of a Successful Kickoff Meeting

4.3.2.2. 2. Develop necessary materials prior to a kickoff meeting.

4.3.2.2.1. Documents that must be in place in advance of a kickoff meeting:

4.3.2.2.2. Materials that should be included in a kickoff meeting.

4.3.2.3. 3. Include all team members.

4.3.2.3.1. This includes

4.3.2.3.2. The kickoff meeting is when lines of authority are established and roles and responsibilities defined and shared

4.3.2.4. 4. Stick to a schedule

4.3.2.4.1. The first part of the kickoff meeting is an overview of the program

4.3.2.4.2. The second half of the kickoff meeting is delivered by the "Proposal Manager"

4.3.2.4.3. Participants should walk away from this meeting with a complete understanding of the time frame and how this response will be completed

4.3.2.4.4. Sample Kickoff Meeting Agenda with Roles and Responsibilities

4.3.2.5. 5. Adjust operating procedures for virtual kickoff meetings

4.3.2.5.1. Pay additional attention to planning the kickoff call.

4.3.2.5.2. Confirm understanding and commitment with the team after each schedule item. Be sure every participant understands his or her role and tasks.

4.3.2.5.3. Check progress more frequently than you would with a co-located team. You need to replace your physical presence with both individual and group support. Use email, calls, and quick check-ins.

4.3.2.5.4. Your collaboration system can give you alerts, but will not provide the coaching and hands-on support to keep morale high and fix issues

4.3.3. Common Pitfalls and Misconceptions

4.3.3.1. Confusing kickoff with initial planning meeting

4.3.3.1.1. The kickoff meeting should not be confused with the initial planning meeting.

4.3.3.1.2. An initial planning meeting should be an internal meeting with core team members immediately after the RFP is released

4.3.3.1.3. The outcomes and directions of this initial planning are the inputs to the kickoff meeting.

4.3.3.2. Not allowing sufficient time to plan a kickoff

4.3.3.2.1. Considerable time needs to be spent preparing for the kickoff.

4.3.3.2.2. Having a kickoff meeting as quickly as possible after the release of the catalyst documents can set the team up for failure if key information and guidance is missing

4.3.4. Summary

4.3.4.1. A successful kickoff meeting is the cornerstone for a successful proposal response.

4.3.4.2. Kickoff meetings are a team's introduction to a project. They provide team members an overview of

4.3.4.2.1. Strategies to accomplish the mission,

4.3.4.2.2. Infrastructure for efficiency in sharing content.

4.3.4.2.3. Solution

4.3.4.3. Meetings should be attended by all proposal contributors, including a C-level sponsor.

4.3.4.4. During the meeting, several key documents should be shared and presented, allowing all members to start from the same page.

4.3.5. Terms to Know

4.4. 24. Daily Team Management

4.4.1. Introduction

4.4.1.1. Day-to-day management

4.4.1.1.1. is the engine at the center of all successful proposals.

4.4.1.1.2. helps everyone focus on what is important

4.4.1.1.3. keeps the entire team moving towards the ultimate objective: delivering a winning proposal.

4.4.1.2. The Proposal Manager

4.4.1.2.1. Has to walk the line between injecting structure and formality where it is needed

4.4.1.2.2. Know when to allow the proposal to run on its own

4.4.2. Best Practices

4.4.2.1. 1. Make sure that daily activities are consistent with a written proposal management plan.

4.4.2.1.1. A Proposal Management Plan

4.4.2.1.2. Each proposal activities must relate to the proposal management plan.

4.4.2.1.3. The Proposal and Opportunity Manager have a responsibility to make an up-to-date version of the plan available to everyone on the team.

4.4.2.1.4. Adherence to a plan ensures that everyone on the team moves in the same direction

4.4.2.2. 2. Conduct a short, daily stand-up review or call.

4.4.2.2.1. The participants in the review should include team members with accountability for proposal sections and functions, as well as the support team.

4.4.2.2.2. Proposal and Opportunity Manager

4.4.2.2.3. Use a standard stand-up meeting agenda to keep meetings on track

4.4.2.3. 3. Identify roadblocks on the daily stand-up or call, but resolve them outside of the daily review in a smaller meeting.

4.4.2.4. 4. Track actions with imminent deadlines or long lead times on the daily stand-up and track other actions outside of the stand up.

4.4.2.4.1. The proposal schedule and the proposal management plan together drive daily priorities,

4.4.2.4.2. but day to day activities should be driven by near-term interim deadlines

4.4.2.4.3. For smaller, embedded sub-tasks or action items that ore not milestones in and of themselves, but ore on the critical path, use a written action-item tracking matrix to document progress and close out

4.4.2.5. 5. Listen for potential problems that are not always articulated clearly.

4.4.2.6. 6. Clarify roles and responsibilities to avoid duplication of effort and ensure complete coverage of all proposal functions.

4.4.2.7. 7. Track activities enough to be able to show progress, but not in so much detail that the tracking interferes with the development of content.

4.4.2.8. 8. Use appropriate techniques to keep the team motivated and productive.

4.4.3. Common Pitfalls and Misconceptions

4.4.3.1. Overreliance on virtual communication

4.4.3.2. Failure to ask questions of team members

4.4.4. Summary

4.4.4.1. The daily discipline of tracking of progress and escalating problems is critical to completing a winning proposal on time and within budget.

4.4.4.2. Use and update a proposal plan to guide teams' activities.

4.4.4.3. Conduct daily stand-up reviews to assess team members' progress against assigned tasks.

4.4.4.4. Adjust the specifics to suit the particulars of the environment and the proposal, but maintain consistency and transparency.

4.4.4.5. day-to-day team management entails not just tracking the status of tasks but also prioritization based on an understanding of the big picture.

4.4.5. Terms to Know

4.4.5.1. Daily Stand-Up Review

4.4.5.2. Proposal Management Plan

4.5. 25. Review Management

4.5.1. Introduction

4.5.1.1. Structured and timely reviews throughout the proposal process ensure

4.5.1.1.1. compliance

4.5.1.1.2. completeness

4.5.1.1.3. higher probability of winning bids.

4.5.1.2. Good reviews result in actionable improvements that increase probability of win on opportunity pursuits.

4.5.2. Best Practices

4.5.2.1. 1. Use appropriate reviews to improve the quality of your bid.

4.5.2.1.1. Reviews

4.5.2.1.2. A key element of the BD process is a series of appropriately timed reviews

4.5.2.1.3. Figure: Matured BD reviews.

4.5.2.2. 2. Set up each review to answer a series of key questions.

4.5.2.2.1. Figure: Team Reviews and the BD Lifecycle

4.5.2.2.2. Competitor Review

4.5.2.2.3. Opportunity Plan Review

4.5.2.2.4. Proposal Strategy Review

4.5.2.2.5. Final Document Review

4.5.2.3. 3. Adhere to the following guidelines for more effective review management.

4.5.2.3.1. Standardize company review templates.

4.5.2.3.2. Establish review teams early.

4.5.2.3.3. Select the right review team Lead.

4.5.2.3.4. Keep the same core team throughout the review cycle.

4.5.2.3.5. Incorporate teammates into reviews.

4.5.2.3.6. Use consultants in reviews as needed.

4.5.2.3.7. Conduct effective review kickoffs and debriefings

4.5.2.3.8. Record comments and decide which to incorporate.

4.5.2.3.9. Use subreviews effectively.

4.5.2.3.10. Debrief management on review results.

4.5.3. Common Pitfalls and Misconceptions

4.5.3.1. Reviews are just a "check-the-box" exercise.

4.5.3.2. Little value comes from reviews.

4.5.3.3. Reviewing late in the proposal cycle is all right

4.5.3.4. You can cut review time to gain time for authors.

4.5.3.5. Reviews can be planned quickly and easily.

4.5.3.6. Anybody can be a good reviewer.

4.5.3.7. The Proposal or Opportunity Manager should lead the review.

4.5.3.8. Executives should not be part of the review team.

4.5.3.9. Subject matter experts have more important things to do than review.

4.5.3.10. You don't need to review price proposals as carefully as other volumes

4.5.4. Summary

4.5.4.1. Reviews should be timed appropriately to allow sufficient time for proposal team members to incorporate reviewers' comments.

4.5.4.2. All reviews should have a review team lead who understands the customer and can keep team members on track.

4.5.4.3. Organizations should keep the same core team throughout all functional reviews, adding team members with subject matter expertise as needed.

4.5.4.4. Most reviews are associated with corresponding bid decisions.

4.5.5. Terms to Know

4.5.5.1. Functional Reviews

4.5.5.2. Review Team Lead

4.5.5.3. Subreviews

4.6. 26. Production Management

4.6.1. Introduction

4.6.1.1. Production management is the process of getting a proposal formatted, published, and delivered to a customer.

4.6.1.2. Although it occurs at the end of a proposal process, teams should begin planning for production as soon as preliminary production needs are known

4.6.1.3. Although production activities require significant time, effort, and attention to detail, their ultimate success depends on the planning activities initiated long before proposal writing and functional reviews begin.

4.6.2. Best Practices

4.6.2.1. 1. Begin planning for production during the pre-RFP stage.

4.6.2.1.1. Be sure to:

4.6.2.1.2. Use the production, editing, and printing checklists included as tools and templates for this section in the APMP BOK

4.6.2.1.3. Allow approximately 10 percent of your available proposal development time for production efforts,

4.6.2.1.4. Carefully read and reread RFP instructions. Confirm instructions and any relevant amendments prior to production

4.6.2.1.5. Planning for production activities early in the proposal lifecyle allows you to identify gaps or shortcomings in your team's production capabilities, tools, equipment, facilities, and personnel,

4.6.2.2. 2. Assign responsibilities for key roles involved in proposal production early.

4.6.2.2.1. Proposal production requires

4.6.2.3. 3. Scale your proposal production plan based on proposal size and complexity and on your organization's size and capabilities.

4.6.2.4. 4. Consider outsourcing proposal production.

4.6.2.5. 5. Carefully plan contingencies to mitigate risks for final delivery

4.6.2.5.1. Always plan to submit a day early, and train your management to understand the need for this schedule.

4.6.2.5.2. Be sure to implement

4.6.2.6. 6. Maintain senior management visibility to ensure support throughout the production process.

4.6.2.7. 7. Ensure version control in all phases of the proposal development Lifecycle.

4.6.2.8. 8. Do not make Last-minute changes to your proposal.

4.6.3. Common Pitfalls and Misconceptions

4.6.3.1. Failure to plan adequately

4.6.4. Summary

4.6.4.1. Begin planning for production during the pre-RFP stage. The more time and attention you pay early on to planning for proposal production, the more smoothly and professionally your proposal productions will run.

4.6.4.2. Assign proposal production resources early, including people, facilities, and equipment.

4.6.4.3. Scale your production plan based on proposal size and complexity, as well as your organization's size and capabilities.

4.6.4.4. Ensure that the proposal complies with stipulated font size and formatting instructions.

4.6.4.5. Make contingency and backup plans for all aspects of your proposal production efforts.

4.6.4.6. Maintain version control of all proposal text and graphics. Not doing so can completely derail your production effort, jeopardizing compliant and on-time proposal delivery.

4.6.4.7. Make no last-minute changes to a proposal unless not doing so would cause you to deliver a non compliant product and thereby lose the proposal.

4.6.5. Terms to Know

4.6.5.1. Contingency Plan

4.6.5.2. Functional Reviews

4.6.5.3. Production Manager

4.6.5.4. Proposal Coordinator

4.6.5.5. Proposal Desktop Publisher

4.6.5.6. Proposal Development

4.6.5.7. Proposal Editor

4.6.5.8. Proposal Graphic Designer

4.6.5.9. Proposal Management

4.6.5.10. Proposal Manager

4.6.5.11. Teaming Partners

4.7. 27. Virtual Team Management

4.7.1. Introduction

4.7.1.1. Virtual teams

4.7.1.1.1. are those that interact through electronic means.

4.7.1.1.2. can also include peripheral team members, such as SMEs, and team members from partner companies.

4.7.1.1.3. Although they have the same governing principles, their effective management requires special consideration.

4.7.1.2. Advantages

4.7.1.2.1. Can use time differences to be productive during other team members' downtime

4.7.1.2.2. Provide flexibility and increase knowledge sharing; organizations have more resource options when they can include anyone in the world

4.7.1.2.3. Increase productivity

4.7.1.2.4. Are cost effective

4.7.1.2.5. Meet green initiatives

4.7.1.3. Disadvantages:

4.7.1.3.1. Feelings of isolation and restlessness

4.7.1.3.2. Cultural clashes

4.7.1.3.3. Loss of team spirit

4.7.1.3.4. Overwork

4.7.1.3.5. Lack of

4.7.2. Best Practices

4.7.2.1. 1. Create a virtual proposal center.

4.7.2.1.1. The first step to take before you hold a proposal kickoff meeting is to evaluate the RFP.

4.7.2.1.2. Next:

4.7.2.1.3. A good virtual proposal center is easy to use, access, and administer. It push information such as:

4.7.2.1.4. Tools may include:

4.7.2.2. 2. Set a foundation for clear communication. Ask all team members a few critical questions, including:

4.7.2.2.1. What version of software do they run

4.7.2.2.2. What is their technology Level/experience?

4.7.2.2.3. What are their vacations/holiday schedules?

4.7.2.2.4. What hours will they work?

4.7.2.2.5. What is their preferred form of communication?

4.7.2.3. 3. Communicate clearly by email and phone

4.7.2.3.1. To improve email communication:

4.7.2.3.2. Use these techniques include to strengthen communication and build rapport among teams.

4.7.2.4. 4. Conduct virtual reviews

4.7.2.4.1. Kickoff Meeting

4.7.2.4.2. Daily Stand-Up Review

4.7.2.4.3. Document Reviews

4.7.2.5. 5. Close out projects upon completion.

4.7.3. Common Pitfalls and Misconceptions

4.7.3.1. Insufficient infrastructure and communication

4.7.3.2. Failing to build rapport among team members

4.7.3.2.1. Be sure to regularly acknowledge all team members. Otherwise, they may feel their contribution is not sufficiently valued, which could, in turn, affect the quality of the finished bid.

4.7.4. Summary

4.7.4.1. In leading a virtual proposal team, build trust and rapport through regular communication and interaction.

4.7.4.2. Picking up the phone and speaking to people is ideal. Encourage contributors to do the same, using their contact list.

4.7.4.3. Virtual teams have the same goals and are governed by the same principles as traditional proposal teams. What differs is simply the ways in which they communicate.

4.7.4.4. A virtual proposal center provides a central "hub" where your team can access and share project information.

4.7.4.5. Other digital tools, such as screen sharing and video conferencing, can facilitate communication among team members.

4.7.4.6. Proposal Managers should keep in mind considerations such as differing time zones, software compatibility issues, and team members' familiarity with various technologies when managing virtual teams.

4.7.5. Terms to Know

4.7.5.1. Daily Stand-Up Review

4.7.5.2. Kickoff Meeting

4.8. 28. Lessons Learned Analysis and Management

4.8.1. Introduction

4.8.1.1. Lessons Learned are gathered from your team and your customer after an award decision has been made.

4.8.1.2. They are a way to improve your team's strategies and processes in response to wins and Losses alike.

4.8.1.3. Producing winning bids requires a willingness to learn from experiences, both positive and negative.

4.8.1.4. Debriefing

4.8.1.4.1. The internal debriefing should be held soon after bid submission, you can learn:

4.8.1.4.2. The customer debriefing should be held after the customer has made a final award decision, you can learn:

4.8.1.5. Lessons-learned reviews

4.8.1.5.1. should be held on all major engagements soon after they are submitted. The depth and frequency of reviews should be tailored to the setting and organizational maturity.

4.8.1.5.2. should typically be gathered and applied in the following order:

4.8.1.6. Organizations that learn from their previous pursuit experiences see more wins in the marketplace

4.8.2. Best Practices

4.8.2.1. 1. Conduct an internal Lessons-Learned review to determine how to improve opportunity planning and proposal development processes.

4.8.2.1.1. Your review team should answer the following questions:

4.8.2.1.2. For participants to provide constructive feedback, create an atmosphere devoid of blame; focus on the project, not the people

4.8.2.1.3. An Opportunity Manager or Bid/Proposal Manager should lead and facilitate the internal lessons-learned review.

4.8.2.1.4. During the review, solicit feedback from all internal personnel who supported the entire BD effort, including:

4.8.2.2. 2. Conduct a customer-focused lessons-learned review to determine how well you understood the customer's perspective.

4.8.2.2.1. The purpose of the customer-focused lessons-learned review is to determine whether your organization effectively captured the customer's perspective in the opportunity planning phase and converted that assessment into the final proposal for the customer.

4.8.2.2.2. During this review, focus on how to improve collection and analysis of opportunity-specific information and how to incorporate that information into a proposal

4.8.2.2.3. This review should begin with a customer debriefing.

4.8.2.2.4. A face-to-face or phone debriefing with the customer should be led by the sales executive in charge of the opportunity. Follow these tips for effective debriefings:

4.8.2.2.5. Follow up the customer debriefing with an internal analysis of the feedback and a lessons-learned session focused on the results of the analysis. This session should answer the following questions:

4.8.2.2.6. The following members of your team should attend the customer-focused lessons-learned review:

4.8.2.3. 3. Use a structured approach to conduct and follow up on Lessons-Learned sessions.

4.8.2.3.1. Give participants advance notice.

4.8.2.4. During the session, the session leader should:

4.8.2.4.1. Encourage all participants to provide constructive feedback along with appropriate solutions.

4.8.2.4.2. Allow all voices to be heard. If feedback starts getting personal, the leader should step in and ensure that all feedback is issue based. not personality based.

4.8.2.4.3. Ensure that the team reaches consensus on the lessons-learned based on feedback.

4.8.2.4.4. Document lessons learned and provide them to the bid process owner.

4.8.3. Common Pitfalls and Misconceptions

4.8.3.1. Misunderstanding the purpose of Lessons Learned

4.8.3.1.1. Some people think that lessons-learned reviews are for identifying individuals who did not perform well. But this isn't the case.

4.8.3.1.2. They are about the

4.8.3.1.3. Others believe that lessons learned are just for the "big team." However, lessons learned should begin when the opportunity is first identified and a pursuit decision is made, and they should continue throughout the entire BD lifecycle.

4.8.3.2. Failure to apply Lessons Learned

4.8.3.2.1. Organizations should have a plan to harvest and track lessons learned so they are communicated to the responsible stakeholder to promote continuous improvement. Learn to view both wins and losses not as isolated events, but as opportunities to improve.

4.8.4. Summary

4.8.4.1. Organizations that invest in lessons-learned sessions tend to see more wins in the marketplace.

4.8.4.2. Conducting lessons-learned reviews both internally and with your customer can help you understand what went well and what you can improve.

4.8.4.3. Using a consistent post-award debriefing protocol provides valuable trend analysis for what drives wins and losses in your market.

4.8.4.4. Lessons learned are not about dwelling on the past but about winning the next opportunity conditioning the customer and your organization for the future.

4.8.5. Terms to Know

4.8.5.1. Customer Debrief

4.8.5.2. Lessons Learned Review

5. Part 4: Use Tools and Systems

5.1. 29. Opportunity Plans

5.1.1. Introduction

5.1.1.1. Opportunity plans

5.1.1.1.1. are useful tools for sellers to improve customer positioning, They document:

5.1.1.1.2. begin by identifying an opportunity,

5.1.1.1.3. followed by a making a bid pursuit decision

5.1.1.1.4. and assigning an Opportunity Manager

5.1.1.1.5. will

5.1.1.1.6. do

5.1.1.1.7. approached by

5.1.1.1.8. Includes the following topics

5.1.1.2. Potential bidders who use opportunity planning may ultimately decide that a favored position is either not possible or not desirable, prompting a no-bid decision long before resources are committed and consumed in preparation of a proposal

5.1.1.3. The Opportunity Manager

5.1.1.3.1. builds a team appropriate for the bid.

5.1.1.3.2. can have a variety of titles depending on the setting:

5.1.1.4. For major procurements, opportunity planning could begin 2 years in advance or more.

5.1.1.5. In the case of recompetes of existing contracts, opportunity planning begins at award. A mid-term review is a perfect trigger for in-depth opportunity planning for the next award.

5.1.2. Best Practices

5.1.2.1. 1. Gather and analyze intelligence about the customer and the competition.

5.1.2.1.1. It is not enough to know:

5.1.2.1.2. When you have completed this analysis, take the intelligence you have developed and complete a bidder comparison matrix.

5.1.2.1.3. The next step is to document the strengths and weaknesses of each potential bidder. The best-known way to do this is using a SWOT analysis, but other techniques, such as gap analysis and the chain of differentiation, can be useful in certain situations.

5.1.2.2. 2. Work collaboratively with the customer to craft a solution addressing explicit requirements and hot buttons.

5.1.2.2.1. The period before the RFP drops is also the time to develop pricing:

5.1.2.2.2. At this stage, your solution is notional, but should reflect the intelligence developed to date and hopefully position your offer positively with the customer.

5.1.2.3. 3. Develop program, opportunity, and proposal budgets.

5.1.2.3.1. The strategic importance of the opportunity and your company or team's resources will affect the levels of resources and budgets committed.

5.1.2.3.2. it may be a good idea to no-bid, or consider switching to a subcontractor position with another firm acting as prime contractor If your company is unable to provide the necessary resources

5.1.2.4. 4. Initiate teaming and make/buy decisions.

5.1.2.4.1. You can improve your competitive positioning by cementing good partnerships early

5.1.2.4.2. Teaming can also facilitate make/buy decisions.

5.1.2.5. 5. Conduct opportunity plan and competitor simulation reviews.

5.1.2.5.1. Opportunity plan reviews and competitor reviews focus on quality improvement. Make certain that reviewers can offer different perspectives on the customer, competitor, and solution.

5.1.2.6. 6. Mock up an executive summary.

5.1.2.6.1. it serves as a valuable aid to drive transition from opportunity planning to proposal planning

5.1.2.6.2. Key proposal graphics, such as

5.1.2.7. 7. Guide transition of opportunity plan elements to the proposal plan.

5.1.2.7.1. A current, up-to-date opportunity plan and mocked-up executive summary effectively front-load proposal planning, saving time and helping you establish a consistent message early.

5.1.2.7.2. The more you can shorten the final proposal planning timeframe before kickoff, the more time you will have to develop a winning proposal.

5.1.2.8. 8. Develop and Lead decision gate reviews.

5.1.2.8.1. The number and focus of decision gates depend upon the complexity of the opportunities and company governance processes, but will always include at least a bid/no-bid decision.

5.1.2.8.2. Good decisions that avoid a bias toward always going forward should be the goal.

5.1.3. Common Pitfalls and Misconceptions

5.1.3.1. Focusing on the plan rather than the customer

5.1.3.1.1. Opportunity plan must be developed collaboratively with a customer.

5.1.3.1.2. Interacting with the customer during opportunity plan development benefits your company in the long run.

5.1.4. Summary

5.1.4.1. Use opportunity plans to document your work, inform your organization, and facilitate reviews.

5.1.4.2. Tailor and scale opportunity plans to match the opportunity.

5.1.4.3. Start early: "front-loading" proposal planning can give you more time to develop a winning proposal.

5.1.4.4. Remember to do the work, not just "fill out" the opportunity plan. This means working closely with customers to understand their needs.

5.1.4.5. Keep completed opportunity plans for reuse on future deals.

5.1.5. Terms to Know

5.1.5.1. Bid/No -Bid Decision

5.1.5.2. Bidder Comparison Matrix

5.1.5.3. Competitor Review

5.1.5.4. Customer-Focused Writing

5.1.5.5. Customer Positioning

5.1.5.6. Executive Summon,

5.1.5.7. Hot Buttons

5.1.5.8. Opportunitu Plan

5.1.5.9. Opportunitu Plan Review

5.1.5.10. SWOT

5.1.5.11. Win Strategy

5.2. 30. Proposal Management Plans

5.2.1. Introduction

5.2.1.1. Proposal management plans, or bid plans, are used to

5.2.1.1.1. allocate effort,

5.2.1.1.2. structure work,

5.2.1.1.3. and ensure adherence to timelines throughout the proposal development process.

5.2.1.2. This planning is increasingly focused on two key documents:

5.2.1.2.1. Opportunity plan

5.2.1.2.2. Proposal management plan (PMP)

5.2.1.3. Plans are now tailored by industry sector and bid size and type.

5.2.2. Best Practices

5.2.2.1. 1. Prepare the PMP before the kickoff meeting, using the opportunity plan as a starting point.

5.2.2.1.1. The PMP is an evolution of the opportunity plan.

5.2.2.1.2. In many cases, more than half of an opportunity plan will appear in its corresponding PMP, with the key additions of:

5.2.2.1.3. Always follow your opportunity plan, unless capture is not used

5.2.2.2. 2. Use plan templates when appropriate.

5.2.2.3. 3. Ensure executive buy-in and support of plans. There are a few ways to foster and support buy-in:

5.2.2.3.1. Explain to stakeholders how plans can benefit them

5.2.2.3.2. Ensure respect of plans by all members of the lead organization and any other key bidding partners, especially senior staff (key staff will help set an example for the rest of the team).

5.2.2.3.3. Clearly identify the owner and updater of the plan (a senior bid team member).

5.2.2.3.4. Clarify the process of conducting signoffs and sharing changes.

5.2.2.3.5. Ensure that bid leads and key staff refer to and use plans regularly and visibly

5.2.2.4. 4. Carefully plan and organize content.

5.2.2.4.1. Use OVERVIEW PLANS to map content at a high Level

5.2.2.4.2. Use DOCUMENT-BASED PLANS to organize key resources.

5.2.2.4.3. Use ACTION-BASED PLANS to visualize the proposal process in detail.

5.2.2.4.4. Use CONTENT PLANS to develop ideas before you write.

5.2.3. Common Pitfalls and Misconceptions

5.2.3.1. Allocating too Little time for plan development

5.2.3.1.1. Bid operations invariably benefit from extra care taken in planning phases.

5.2.3.1.2. Good plans often require more time than is allocated to be researched and produced in a user-friendly format.

5.2.3.2. Misunderstanding of plans' role

5.2.3.2.1. A plan should be followed as closely as possible, but must not become an end in itself.

5.2.3.2.2. The existence of a plan does not mean that it will be followed. Refer to your plan regularly to be sure you are on track toward reaching your goals.

5.2.4. Summary

5.2.4.1. A bid or proposal of any size is a complex project with many tasks to be completed by a strict deadline. These projects benefit from plans that clearly define the schedule and effort needed to complete tasks.

5.2.4.2. Choose the plan type that best fits the opportunity and your organization.

5.2.4.3. Ensure that the plan is owned, understood, and approved by all key proposal personnel.

5.2.4.4. Follow the plan, but not to the exclusion of common sense; allow for modifications as needed.

5.2.5. Terms to Know

5.2.5.1. Opportunity Plan

5.2.5.2. Proposal Management Plan

5.3. 31. Content Plans

5.3.1. Introduction

5.3.1.1. Use content plans to create consistent, compliant, well-organized proposals.

5.3.1.2. Teams should not start writing until there is a clear and shared view of what the finished product will look like.

5.3.1.3. Without a clear specification of what needs to be created, the finished products will be inconsistent, incoherent, and low quality.

5.3.1.4. The approach is no different from best practice on any project or development effort. Plan, define quality criteria, and then execute.

5.3.2. Best Practices

5.3.2.1. 1. Implement a systematic approach to designing content.

5.3.2.1.1. Follow a simple, clear, and requirements-driven process to design content

5.3.2.1.2. The term content plan embraces a wide range of techniques such as:

5.3.2.1.3. The time invested in content planning should match the likely ROI. There should be a surplus of benefits over costs.

5.3.2.2. 2. Adapt the approach to each proposal's situation.

5.3.2.2.1. Content planning offers the following benefits:

5.3.2.2.2. No benefits are achieved without costs. The main costs of content planning are the time and effort of

5.3.2.2.3. the appropriate amount of planning will be determined by the nature of the proposal solicitation and the required response, check attached table

5.3.2.2.4. Figure: Determining Level of Planning Needed

5.3.2.2.5. In other situations, the return from detailed planning is determined by the sales situation, Check Figure: Determining Level of Planning Needed

5.3.2.3. 3. Build and manage a requirements baseline for each proposal.

5.3.2.3.1. To document requirements, use

5.3.2.3.2. For

5.3.2.4. 4. Create a robust topical outline.

5.3.2.4.1. Start the content planning process by building a robust topical outline for the proposal

5.3.2.4.2. Making your outline consistent and compliant

5.3.2.4.3. Making your outline robust

5.3.2.4.4. Figure: A Robust Outline

5.3.2.5. 5. Annotate the outline to provide guidance to authors.

5.3.2.5.1. Provide guidance to contributors by annotating the outline. Annotation can be added in-line to text or in a list

5.3.2.5.2. Annotation should include

5.3.2.6. 6. Develop detailed content plans for important sections.

5.3.2.6.1. Apply the "just enough planning" principle.

5.3.2.6.2. The test of a good content plan is to ask, "Could I give this to the responsible author and expect him or her, using only what is in the plan and the kickoff briefing, to create compliant, responsive, focused content?"

5.3.2.6.3. For

5.3.2.6.4. There are many ways to plan detailed content, including:

5.3.2.6.5. Templates

5.3.2.7. 7. Involve your writing team in content plan creation.

5.3.2.7.1. If section content plans are to be used, the Proposal Manager, with the support of the proposal team, should develop initial section content plans before kickoff.

5.3.2.7.2. The Proposal Manager should agree to and sign off on content plans before writing starts.

5.3.2.7.3. The completed section content plan will provide a "contract" between the Proposal Manager and the contributor, defining what is to be developed.

5.3.2.7.4. Like outline annotations, sample content plans provide quality criteria for acceptance of all finished content.

5.3.2.8. 8. Review content plans before starting to write.

5.3.2.8.1. Where time and budget allow, schedule a review of the completed section content plans before writing starts.

5.3.2.8.2. The content plan review should include all internal stakeholders in the proposal, including:

5.3.2.8.3. Team review of content plans helps

5.3.2.8.4. Review Types

5.3.2.8.5. Consolidate review comments before ending the review meeting so that participants are clear what changes, if any, they should make to their plans.

5.3.2.9. 9. Integrate content plans into the proposal development plan.

5.3.2.9.1. The outline is the basis for planning proposal development activities.

5.3.2.9.2. For each unique assignable item in the outline, allocate a responsible developer.

5.3.2.9.3. From the outline and page budget, decide how many pages and graphics are required for each outline item.

5.3.2.9.4. Identify how much of the content can be created bid adapting reusable content

5.3.2.9.5. Use historic metrics collected from previous pursuits to estimate the time and effort required.

5.3.2.9.6. Metrics

5.3.2.10. 10. Use content plans to monitor quality and progress.

5.3.2.10.1. Extend the proposal responsibility matrix to show additional details such as

5.3.2.10.2. Use the resulting product status register to monitor progress and status

5.3.3. Common Pitfalls and Misconceptions

5.3.3.1. Not enough planning

5.3.3.2. Introducing new techniques without training and support

5.3.4. Summary

5.3.4.1. Compliant, responsive, focused proposals do not happen by accident. Proposal content must be specified before it is created, and a wide range of techniques is available to support this process of specification.

5.3.4.2. Proposal managers should select and use techniques appropriate to the proposal environment. At a minimum, a robust topical outline should be created as a basis for checking compliance and planning writing tasks. Use more detailed approaches where the opportunity is complex or important.

5.3.4.3. Focus on complying with customer instructions and achieving a clear brief for proposal contributors so that requirements are not missed or duplicated.

5.3.4.4. Set clear writing criteria for authors so they can create winning content that is "customer ready" from the first draft.

5.3.5. Terms to Know

5.3.5.1. Annotated Outline

5.3.5.2. Content Plan

5.3.5.3. Kickoff Meeting

5.3.5.4. Mock-Up

5.3.5.5. Proposal Outline

5.3.5.6. Win Themes

5.4. 32. Knowledge Management

5.4.1. Introduction

5.4.1.1. Knowledge management

5.4.1.1.1. is getting the best knowledge to the right person at the right time

5.4.1.1.2. For proposal management (PM) and business development (BD) professionals, this means:

5.4.1.1.3. is less about technology (storing and retrieving knowledge using databases and search engines) and more about the processes of

5.4.1.1.4. and more about the processes of creating, classifying, sharing, and improving what we know about what we do.

5.4.1.2. By adopting and applying KM principles, BD and PM organizations can:

5.4.1.2.1. Convert tacit knowledge into explicit knowledge people can find and use when they need it.

5.4.1.2.2. Turn disorganized information into reusable knowledge objects classified under a useful taxonomy.

5.4.1.2.3. Learn how to share know-how, know-why, and know-what with others to improve performance.

5.4.1.2.4. Distribute knowledge objects as valuable assets that improve efficiency and effectiveness.

5.4.1.3. Three keys challenges of successful KM, especially in the BO and PM worlds, are:

5.4.1.3.1. Choosing the most relevant knowledge from the sheer volume of information available

5.4.1.3.2. The variety of tools to manage that information

5.4.1.3.3. A cultural bias against knowledge sharing

5.4.1.4. To successfully implement KM, you should first distinguish between:

5.4.1.4.1. KM principles (the guiding concepts crucial to KM success)

5.4.1.4.2. KM tools and systems

5.4.1.4.3. KM processes (the tangible assets that make KM work)

5.4.2. Best Practices

5.4.2.1. KM Guiding Principles

5.4.2.1.1. 1. Gain top-management commitment and sponsorship

5.4.2.1.2. 2. Start small with quick, Low-cost knowledge management initiatives.

5.4.2.1.3. 3. Assess your knowledge status through external benchmarking and internal knowledge audits.

5.4.2.1.4. 4. Establish or join communities of practice for knowledge management.

5.4.2.1.5. 5. Create a culture that rewards knowledge sharing and transfer.

5.4.2.1.6. 6. Create standards that promote knowledge re-purposing.

5.4.2.2. KM Systems, and Processes

5.4.2.2.1. 7. Build the following knowledge management tools, processes, and systems

5.4.3. Common Pitfalls and Misconceptions

5.4.3.1. Falsely equating KM with IT

5.4.3.1.1. Some erroneously equate KM with IT. Although KM is greatly enabled by database, communication, and computer technologies, KM will not succeed through technology alone.

5.4.3.1.2. KM is

5.4.4. Summary

5.4.4.1. Knowledge is

5.4.4.1.1. is "understanding gained from experience."

5.4.4.2. KM is

5.4.4.2.1. getting the best knowledge to the right person at the right time.

5.4.4.3. Both tacit and explicit knowledge are best stored, managed, and delivered when converted to discrete digital objects.

5.4.4.4. BD and PM organizations of any size, in any business setting, anywhere in the world can benefit from application of KM principles.

5.4.4.5. Most KM tools can be scaled or enabled by technology to meet the needs of all BD and PM professionals.

5.4.4.6. KM is more about change management than IT.

5.4.5. Terms to Know

5.4.5.1. After-Action Review

5.4.5.2. Benchmarking

5.4.5.3. Change Management

5.4.5.4. Community of Practice (CoP)

5.4.5.5. Content Management System (CMS)

5.4.5.6. Expert Locator

5.4.5.7. Explicit Knowledge

5.4.5.8. Fundamental Knowledge Object (FKO)

5.4.5.9. Knowledge Audit

5.4.5.10. Knowledge Base

5.4.5.11. Knowledge Cafe

5.4.5.12. Knowledge Management

5.4.5.13. Knowledge Management Heuristic

5.4.5.14. Knowledge Manager

5.4.5.15. Knowledge Map

5.4.5.16. Knowledge Repository

5.4.5.17. Knowledge Sharing

5.4.5.18. Lessons Learned

5.4.5.19. Tacit Knowledge

5.4.5.20. Taxonomy

5.5. 33. Scheduling

5.5.1. Introduction

5.5.1.1. Effectively allocating time and resources across multiple tasks-and communicating and enforcing milestones are essential parts of proposal management.

5.5.1.2. The basic principles of proposal scheduling are consistent with those of good project management.

5.5.1.3. Careful project schedule development and management is the only way to ensure on-time delivery

5.5.1.4. Contingency planning, based on the specifics of the organization, the proposal, and the team, is an essential component of schedule management.

5.5.2. Best Practices

5.5.2.1. Schedule backward, starting with the proposal due date and time.

5.5.2.1.1. Start with the due date and time.

5.5.2.1.2. Estimate the total proposal development effort, then schedule delivery and production before scheduling tasks that occur earlier.

5.5.2.1.3. When you have built in enough time for delivery and production, make a list of the other tasks and subtasks, using as menu levels as necessary to describe the work in detail.

5.5.2.1.4. Develop realistic time estimates for specific tasks and record these in a proposal resource schedule

5.5.2.2. Allocate time for proposal planning and for establishing the proposal infrastructure

5.5.2.2.1. Setting up a proposal infrastructure and creating realistic plans are critical to a smooth proposal process.

5.5.2.2.2. They also decrease the overall effort required

5.5.2.2.3. The planning process, including

5.5.2.3. Minimize sequential tasks and maximize parallel tasks

5.5.2.4. Clearly explain the start and end date for each task as well as the expectations associated with completion of the task

5.5.2.5. Break Large assignments into short, manageable pieces.

5.5.2.6. Make sure the schedule drives the priorities for daily activities.

5.5.2.7. Avoid scheduling weekends and holidays.

5.5.2.8. Allow sufficient time for proposal reviews.

5.5.2.9. Plan for production time conservatively.

5.5.2.10. Change the schedule only if it absolutely has to be changed, and be sure to communicate changes clearly to all involved.

5.5.3. Common Pitfalls and Misconceptions

5.5.3.1. Rigid adherence to allotted timeframes

5.5.4. Summary

5.5.4.1. Even if everything else is functioning, scheduling mistakes can threaten quality, compliance, and on-time delivery of a proposal.

5.5.4.2. Base the schedule on metrics collected from previous proposals and make a single person accountable for completion of each task.

5.5.4.3. Use interim deadlines to keep tasks on track and provide feedback early.

5.5.4.4. Look for tasks that are independent of one another that can be completed in parallel. carefully plan tasks that have multiple dependencies.

5.5.4.5. Leave enough leeway in schedules for time off on weekends and holidays, multiple review cycles, and potential RFP changes, as well as for unexpected setbacks

5.5.5. Terms to Know

5.5.5.1. Project Schedule

5.5.5.2. Proposal Management

5.5.5.3. Proposal Resource Schedule