I thought it came out pretty well, considering the circumstances. Years later, though, I can see a lot more flaws in the final result than I did at the time.

I’ll never forget this exchange from one of the many, many conference calls about the project:

Marketing Guy: “I want us to say that this technology will give a 10x performance improvement.”

Lead Engineering Gal: “Well , the main problem with that, is that that would be LYING.”

(I became her fan for life.)

I agree that the first thing they need to do is find a professional white paper writer.

If that is not an option, then they should designate one of their group to do the actual, physical writing. They can all brainstorm, decide on the outline, and then discuss edits together. But get them to decide who the best writer of the group is, and let him/her write the drafts.

I think it is hard enough to get four professional writers paddling together — four non-writers would just scoot around in circles unless they got very lucky.

But then if the goal is to get the project yourself, it might not be a bad idea to let them have at it for a while… (lol)

~Graham

I’ve had the experience more than once; with software engineers from several different companies, attorneys, industry analysts, and forensic specialists. I handled it by taking a different approach to the whitepaper.

First, I recognized that each of them had something of value to contribute to the whitepaper, and that it was important to document each of their “perspectives” (not opinions) on the project.

Second, I sent them an email explaining the theme, objective and purpose of the whitepaper, and attached three documents:

The first document was my standard audio recording release.

The second document was a form requesting their biographic information.

The third was a form requesting them to compose the five to ten questions they’d like to be asked about the project that would best express their knowledge of the project.

I also scheduled a recording date with them (via teleconference, so no one had to travel).

On the given date, I explained the nuances of making the recording, including what to do if they made a mistake or “misspoke.” By the time of the recording, I had organized the questions they provided in a logical progression, and added a couple of my own.

I edit the recording, and send it off to my service provider to have it transcribed.

While the recording is being transcribed, I compose an intro and an outro to the whitepaper. When the transcription returns, I perform a second edit, combine it with my intro and outro, and send it off for first draft review.

I’ve trademarked the approach: “Whitepapers and Case Studies – In Your Own Words™,” but that certainly doesn’t mean you can’t use it in your own work.

Hope this helps.