Proposal Land

Better RFP Responses & Management
 
Proposal Land

The Entabulator

I’ve edited lots of technical-speak that read like gobbledygook to me. Most of it was just poor explaining, but I’ve always had a sneaking suspicion that some really didn’t make any sense.

If some or all of what you sell is highly technical, it’s worth spending some time and money outside the proposal cycle to get a description/explanation of it that a non-expert but non-stupid reader can understand. A reader like an editor. Or an evaluator.

I’m sorry to say that I think Bud Haggert is no longer available. H/t to Jim T. for the link.

“I shot this in the late 70’s at Regan Studios in Detroit on 16mm film. The narrator and writer is Bud Haggert. He was the top voice-over talent on technical films. He wrote the script because he rarely understood the technical copy he was asked to read and felt he shouldn’t be alone.”
– Dave Rondot

 

When?

I haven’t had a day off in six weeks.

When can we talk about our proposal processes?

Why do we always pull an all-nighter the night before our proposal is due?

When can we talk about our proposal processes?

The technical experts don’t know anything about writing; the writers don’t know anything.

When can we talk about our proposal processes?

Red Team just trashed our whole plan for service delivery. What now?

When can we talk about our proposal processes?

I know we have super examples of this exact same work for other clients. Why don’t we have snappy little write-ups on those? And pictures, dagnab it?

When can we talk about our proposal processes?

We never get useful feedback from our clients.

When can we talk about our proposal processes?

Well, in the middle of a proposal we don’t have time to talk about our proposal processes. And afterwards, we don’t have . . . what? Time? Motivation? Discipline? Imagination? The attention of executives and managers? Any belief that we can make it better?

It’s comfortable to ignore the system,
to assume it is as permanent
as the water surrounding your goldfish.
Seth Godin

As Seth notes, the systems we work in — including proposal processes — are not permanent. Unless, of course, we never talk about them and how they’re going wrong.

Pick your When, even if it *is* in the middle of a proposal. And then just do it.

 

A Man Walks Into a Bar – Riff #2

A synonym strolls into a tavern.

People whose last writing instruction was in Grade 9 are fond of telling me that adding synonyms to their writing makes it more interesting.

I am fond of telling them that our Grade 9 teachers are not working as proposal evaluators.

In Proposal Land, the rule is clear: For every significant concept, choose one word and use it without fail. Well, as close to that as you can get. Humans are not designed to achieve perfect consistency in anything.

Is it a little boring? Maybe. Clear? That too.

 

Read more here about Buddy & Me.

Term: Para-by-Para Response

A proposal methodology requiring responses to each SOW paragraph, rather than the production of plans and functional descriptions of how the Work will be done.

Excessively tedious to write, edit, review, and evaluate.

Not seen much these days in the sense of a formal requirement, but damnably difficult to get rid of at the informal level. Every executive or proposal-management consultant has a story about having been penalized by evaluators for *not* responding to every SOW line item, even when this was not specified. The low-risk approach is thus seen as responding para-by-para anyway, in addition to meeting the actual response requirement.

Clients have it in their hands to prevent this:

Simple, eh? But I’ve never seen it done . . .

 

Getting to Lovely

There comes a point on a proposal where an editor must settle for coherent . . .

The Operations Manager and Facilities Lead will interact with government, federal, provincial, municipal and territorial regulatory organizations, the Technical Authority, DND centres of expertise and functional authorities, building occupants, other service contractors, specialized services subcontractors, other authorities having jurisdiction, third parties, public service union representatives and stakeholders, as required, to continually improve operations and services for the buildings in the Contract.

But where’s the problem with settling? It’s lovely, yes? Well, good enough, no?

No. Don’t do this. (Except for the active voice. :-))

Don’t put a long list inside a sentence, thereby generating a hard-to-read and harder-to-remember paragraph. Instead, group the list in bullets with headings, like this:

. . . interact with:

    • Government bodies and agencies: federal, provincial, municipal and territorial regulatory organizations
    • Client representatives, agencies, and users: the Technical Authority, DND centres of expertise and functional authorities, building occupants
    • Contractors: other service contractors, specialized services subcontractors
    • Miscellaneous stakeholders: other authorities having jurisdiction, third parties, public service union representatives

  Now a reviewer or evaluator can scan the page to see what you’ve included.

⇒  Now *you* can see whether you want to add a whole category, like community organizations or technical associations.

Don’t use vague, high-falutin’ words like “interact.” Instead, use more-precise words, like this:

    • Meet with
    • Submit plans to
    • Report results to
    • Consult with
    • Advise of changes

⇒  Now the reviewer or evaluator knows what they’ll get.

⇒  Now your costers know what the work will cost, in time and money.

Don’t bury the benefit. Instead, lead with it, like this:

To continually improve operations and services for the buildings in the Contract, the Operations Manager and Facilities Lead will . . .

⇒  Now a reviewer or evaluator knows why they’re bothering to read the rest of it.

⇒  Now you know what you’re selling and can think about whether there are more points you should make, which leads to the last point . . .

Don’t stop at the bare minimum specified in the RFP. Instead, tell them what else you’ll do to achieve the benefit, like this:

To continually improve operations and services for the buildings in the Contract, the Operations Manager and Facilities Lead will deliver the following:

    • Compliance – By maintaining currency with regulations by consulting monthly with government bodies and agencies . . . (as above)
    • Communication – By meeting, on the schedule provided in Attachment 1, with client representatives . . . (as above)
    • Coordination – By meeting with other contractors . . .  (as above) . . . during project initiation to communicate site safety standards and to confirm that work schedules minimize disruption to client activities
    • Cost control – By implementing our 4-step facilities-inspection process, detailed in Attachment 2, which has cut annual operating costs by 23%  for a client with similar infrastructure (see project citation in sidebar)
    • Customer satisfaction – By surveying building occupants quarterly (see Attachment 3 for a sample questionnaire), a process which identifies customer priorities and which has allowed us to improve customer satisfaction rates by an average of 14% year-over-year on similar projects (see Table 1, below, for project list)
    • Verification – By commissioning BOMA-accredited inspectors to complete annual independent third-party audits of building condition and of our services
    • Quality control – By convening annual meetings with client representatives to discuss progress to date and areas requiring improvement

⇒  Now the reviewer or evaluator can see that you have a sensible plan for achieving their objective.

⇒  Now you can highlight the things you’re promising to do that your competitors might not be.

Does that content make real-world sense? Hey, don’t ask me: I’m the editor. Ask the technical expert. These are only for illustration.

But remember that while some of these changes can be handled by editors, some require technical and marketing experts to cough up more content, and all of them require proposal managers to set schedules that give time for revisions. Getting to lovely requires the whole team to work together.

Don’t. Settle.