
December 2019 | ISE Magazine 37
skills, working relationships and possi-
bly lessons learned and formal outbriefs
from prior proposal efforts.
Next, instead of filling in the puzzle
pieces inside of the outline, the team
should begin to fill in the outside and
add the branches to the picture (see Fig-
ure 1). Mind mapping is akin to putting
a puzzle together, though it is backward.
Instead of starting with the border piec-
es, the business development team puts
in the one known or decided factor in
the center at the start, whether it is a
market, customer or specific contract.
The pieces extend from the center and
should reflect information regarding
that centerpiece of the market, customer
or specific contract.
The organization’s goal or desired end
state for the mind map is to build a pic-
ture of the current state of play and de-
cide whether the business development
goal is worth pursuing as a prime or a
subcontractor to the best prime. This al-
lows an organization to use this knowl-
edge to examine the facts and choose to
take on or pass on the opportunity alto-
gether during the capture phase.
Capture leads are mind
mapping quarterbacks
The team, or capture lead, digs into
whatever information is available. For
example, in defense contracting, a team
could use GovWin (iq.govwin.com), in-
dividual company contract pages, Fed-
eral Business Opportunities ( fbo.gov)
or even LinkedIn pages to start build-
ing the most complete picture they can
of the current state, based on published
information. A mind map begins with
explicit knowledge to support fact-based
discovery.
The next step is to add the tacit knowl-
edge to the mind map, which at the start
may consist of previous relationships
through teaming or employment. As the
work to build the mind map continues,
knowledge will continue to come from
explicit and tacit sources as the capture
lead progresses its efforts, and more so
as the team gains a better understanding
of what knowledge it must contribute or
develop.
For example, if the center objective
is a market the organization is consider-
ing entering, the business development
team can build a mind map to provide
a picture of businesses that support work
in the desired market of interest. After
examination, team members may also
discover they are not qualified to work
in the market or find there is no room to
be in the market.
On the other hand, the team may find
an opening in the market it did not un-
cover during prior capture efforts. Once
completed, a successful mind map should
be easy to understand without too much
explanation by using standardized ter-
minology used by the business develop-
ment team and those making the deci-
sion to pursue the opportunity.
Six simple steps of the
mind mapping process
In support of capture efforts, here are six
simple steps to create a mind map, with
customization to the customer, market
or specific contract:
Step 1: Select a desired customer,
market or specific contract that the busi-
ness development team will focus on
for examination. Any more than one
customer, market or contract per mind
map will cause confusion. The explicit
and tacit knowledge should provide a
focus on the center effort of interest on
the mind map. The example in Figure 1
uses a desired customer.
Step 2: For the desired customer,
market or specific contract, use your ex-
plicit resources such as contract portals,
internet resources ( financial magazines,
news media sites, etc.) and contract pages
of expected competitors to search for
contractual relationships with the de-
sired customer as prime contractors. The
team may also find the subcontractors
(subs) as well through the associated press
pages and, at times, may find them on
organization charts, whether spelled out
or color-coded to indicate the source of
the worker. Since the mind map may get
busy if the customer has multiple primes
and subs, it is useful to use the customer’s
logo for ease of recognition.
Step 3: From the explicit knowledge
gained in Step 2, the team can discern
contract numbers, the period of per-
formance, total value and estimate the
anticipated requests for proposal (RFP)
date. When the team adds the informa-
tion to the mind map instead of listing
the explicit knowledge on a spreadsheet
or on the contractual information found
during the explicit knowledge research,
this information provides a mental pic-
ture of the current state and may also
provide areas worthy of research to
achieve the desired future state.
Step 4: This next step requires com-
munication with the team and person-
nel not on the team. After completion
of the initial explicit knowledge gather-
ing by the capture lead, the business de-
velopment team starts to gather its tacit
knowledge and should ask questions
such as:
• Have any of the team members sup-
ported this customer in the past? If so,
who was it? What were the experi-
ences of those team members?
• Of the organizations identified as
current prime contractors for the
customer, what is known about the
relationship between them? Is the
contractor happy with the work or
waiting desperately for the end of the
period of performance?
• Who knows someone outside of the
organization’s customer identified
during Step 2? What do they know
about that customer that could pro-
vide insight for future business?
• Who within the organization has
skills or experience that may support
the customer? Note that these skills
and experience may be absent from
the resumes and skill sets known to
human resources or management.
These questions are not all-encom-
passing of what may come up during
these conversations to build a complete