Proposal Land

Better RFP Responses & Management
 
Proposal Land

Building a Brick Wall

“…the cognitive and emotional toll of repetitive tasks is real, even if doesn’t leave callouses.
The discipline is to invest one time in getting your workflow right
instead of paying a penalty for poor digital hygiene every single day.”

Seth’s Blog

As usual, Seth is onto something here. Proposal Land has many repetitive tasks:

  • Completing detailed time sheets that allow someone to estimate workload better next time.
  • Gathering current project data and kudos.
  • Building organization charts and tables and pull-out boxes  that are beautiful and clear.
  • Identifying the nits for the punch list.
  • Fixing the nits from the punch list.
  • Tracking where sections are: in whose hands.
  • Creating an editing control sheet in Excel or equivalent.
  • Formatting documents with defined styles (or without, yikes).
  • Checking every section for spelling and grammatical errors and format/layout funnies.
  • Sorting through endless emails for the ones you really need to see.
  • Printing and assembling documents for review and/or submission.

Most of these involve software tools; all involve workflow. In a schedule-driven environment, it’s easy to let “Just get it done” become our best practice. Instead, Seth argues that we should learn how to make our software tools sing and our workflow hum along.

Hacking your way through something “for now”
belies your commitment to your work and your posture as a professional.
Get the flow right, as if you were hauling bricks.

For the record, I was lousy at engaging with the software and pretty good at doing that vision thing on the process. Seth’s piece is a good reminder that what we do repetitively, we owe ourselves and our teams to do better.

 

No No No Yes Yes Yes

Style guides: Every proposal editor loves them, every proposal writer ignores them.

So. What to do?

Pick a few things you want the writers to do, or not to do, and give away the rest. “What are the few?” you ask. These are the first four that I ask for:

  • Active voice not passive
  • Future tense not present
  • First person not third
  • Benefits at the front, not at the end

But I’ve learned not to ask writers the same way I might ask another editor. Now I ask writers like this . . .

 

Term: Style Guide

A set of instructions for writers (and possibly for editors) specifying anything from formatting to punctuation to use of active versus passive voice and other stylistic elements.

Intended to efficiently increase the professionalism of the document; often used in conjunction with a terminology list specific to the opportunity.

Term: Stand-ups

Meetings of the proposal team, intended to be quick status checks and efficient communication mechanisms.

People literally stand up around a table or room or open area, or call in on a speakerphone if they’re off-site.

Held daily, semi-weekly, weekly, or as needed, depending on the size, duration, and stage of the proposal.

 

And just for something a little different, a story that illustrates the point, but from my first book . . .