Proposal Land

Better RFP Responses & Management
 
Proposal Land

Term: SDRL

Leaving aside marine uses of this acronym (Sea Date Required to Load), a SDRL is a Data/Document Requirements List for a Supplier, Subcontract, or Subcontractor.  Pretty much all the same thing: data deliverables under a contract.

See also Contract Data Requirements List.

How to Foster Teamwork: Rule #8

Invert everything. (See the world through the client’s/user’s eyes.)
Rhys Newman and Luke Johnson

Seeing the world, or, at least, our service or product through the client’s/user’s eyes is obviously good for design, helping us give them what they want, not what we think they need.  That applies to proposal teams, too, which are (whether they realize it or not) designing a solution for the client and the eventual users.

But why is it good for proposal teamwork?

General Rules of Teamwork

Most teams go through standard stages, neatly if somewhat cutely named as follows:

  • Forming – coming together
  • Storming – fighting for power and over differences of opinion, style, and values
  • Norming – agreeing, at least implicitly, on how the team will function
  • Performing – doing the work assigned

How It Works on Proposal Teams

Limited by the hard deadline, proposal teams must go straight from forming to performing – but conflict doesn’t disappear magically just because the team is on the clock.  Instead, it emerges in other ways:

  • Interpersonal conflicts, as unacknowledged issues fuel snippiness
  • Professional conflicts, as undoubted experts dig in their heels on their approach/solution

How It Can Work Better

An external focus – trying to see our proposed solution through the client’s/user’s eyes – fosters proposal teamwork in two ways:

  • By fostering an overarching us/them mentality, increasing team cohesion and derailing the natural impulse to splinter into small, like-minded, and ultimately ineffective sub-groups
  • By establishing an objective and blessedly impersonal norm for resolving disagreements; to wit, “How would the client/user see this?”

 



Proposals are schedule-driven projects that require a strict project management discipline. Right? Partly right. In proposal terminology, I’d call that answer incomplete.  Proposals are projects, for sure, but they’re also the output of teamwork. I’ve recently been learning how much the design business has in common with proposals.

This post is one of a series on proposal teamwork, inspired by a fabulous article on Medium on design teams:
“No Dickheads! A Guide to Building Happy, Healthy, and Creative Teams.”

Term: Contract Data Requirements List

A Canadian and American federal government contracting tool (now not much used by the former) to capture all data deliverables (reports, plans, forms) for the contract in one place in the RFP (usually a SOW appendix). I’ve also seen this as “Contract Deliverables Requirements List”.  Although not standard usage, this is, nonetheless, perfectly clear and pretty much means the same thing.

Acronymized as CDRL: pronounced “sea-drl” or “sid-rl.”

During the response period, the CDRL is extremely helpful for bidders trying to gauge and cost the level of effort required to meet reporting and similar deliverables after contract award.

During the contract period, the CDRL is extremely helpful for the contractor and the contracting officer in meeting and enforcing contract requirements, respectively.

How to Foster Teamwork: Rule #7

Everyone leads at some point.
Rhys Newman and Luke Johnson

Proposal teams need proposal managers: I’m goodwith that.  They also need leadership.  What’s the difference?  Stephen Covey’s distinction can help us here:

Effective leadership is putting first things first.
Effective management is discipline, carrying it out.

It’s also expressed as the distinction between “doing the right things” and “doing things right.” Both formulations work.

Proposal Managers: There Can be Only One

Proposal managers are busy folks, doing all those standard management tasks related to doing things right:

  • Assembling resources, defining roles and responsibilities, supervising performance
  • Liaising with executives, teaming partners, and in-house resources
  • Overseeing requirements definition, solution development, proposal writing and review, and costing
  • Managing schedule, schedule, and (yes, again) schedule

And, as in “The Highlander” movie, there can be only one proposal manager.

Proposal Leaders: There Should be Many

By contrast, there can be (and should be) many proposal leaders, both formal and informal,  supporting the team’s quest to do the right things by making invaluable contributions:

  • Challenging assumptions
  • Broadening perspectives
  • Bringing focus
  • Resolving conflicts
  • Flagging priorities

Task-Focused and People-Focused Leadership

Like all work, proposals are about more than the task: They’re also about the people executing the task.  Depending on their skills and personalities, leaders can also help to maintain team morale and effectiveness:

  • Listening more than talking in meetings
  • Acknowledging contributions
  • Bringing in a new joke every day
  • Including everyone in social occasions

Staying on Track

Effective proposal managers create an open, respectful, and yet disciplined environment that fosters appropriate leadership from many sources, while never losing sight of their own management responsibilities — or the need to maintain schedule!


 Proposals are schedule-driven projects that require a strict project management discipline. Right? Partly right. In proposal terminology, I’d call that answer incomplete.  Proposals are projects, for sure, but they’re also the output of teamwork. I’ve recently been learning how much the design business has in common with proposals.

This post is one of a series on proposal teamwork, inspired by a fabulous article on Medium on design teams:
“No Dickheads! A Guide to Building Happy, Healthy, and Creative Teams.”

Term: Consortium

A gaggle of companies that have come together to bid on Work too complex or too large (or both) for any one of them to execute at an acceptable level of risk.

May consist of more than one joint venture with additional subcontractors and suppliers. Usually bound at the bid stage by an MOU or teaming agreement; after contract award, relationships are codified in contracts, subcontracts, and interface agreements.

Often necessary for complex projects; always difficult to explain to a client from a management perspective.