Laura’s Winning Ideas

Yup. I was certainly skeptical of how you could use Twitter or Facebook to move forward an engineering proposal. Well, these fine folks are doing the best job I’ve seen in harnessing the power of the crowd to move their technology into the flow of funding.

I heard about them this morning when someone in my Facebook network posted this video to their page:

Transfer from Asphalt to Solar Roadway

After watching the video, I was happy to click out to vote for them. They are in a competition at the GE Challenge to win a portion of the $220 million being offered in their Ecoimagination Challenge grant program.

From there, I looked at a couple of other submissions. Only this one caught my attention so I voted for it as well:

Wind capture that avoids open blade windmill issues

Then I clicked back and voted for the other two proposals Solar Roadways has at GE:

Solar Roadway Wants to Win GE Grant!

And finally, on the Profile for the engineer/founder, I clicked out to watch a TED presentation he made in June 2010:

Endearing story about the genesis of this company

I haven’t looked yet, but I’ll bet they are on Twitter. AND I know the folks at ARPA-e must be watching this to track their progress.

I want to buy stock in this company. In the meantime, I’m stealing every good idea to help clients understand how to use Social Media to Win Work!

Every proposal gets a debrief and I like to have our debrief meetings the morning after delivery of the proposal.

I use a quad diagram for this meeting. Easy to put up on a board or on a webinar screen.

Celebrate: The first and most important. What went right? Who was our hero? How did we make something special of the proposal that just went out? If someone outside the team should be celebrated, who gets to work on the Thank you. Will it be a note or a gift?

Fix: That went wrong? What is the timeline to fix this so it doesn’t happen again? Who will work on this?

A printer ran out of toner? Buy a backup, or get a key to the storeroom where replacements are kept.

Improve: What did we notice that “but for” could have been a serious problem? Is it in our realm of influence? If not, can we bring in the folks responsible to team with us on a prevention? How much time will we budget to fix this? When is it due back?

We had a production problem with the print shop. When we pulled the printers in, they suggested we send our files in a different order, and that made all the difference, erasing the slow down we’d suffered.

The Red Team review wasn’t successful, making changes that should have been made earlier, during the storyboard review. We needed to add some training. So, we developed a mini-course on Storyboards and recruited folks used for Red Team to attend these brown bag sessions. We also created an instruction sheet for Red Team Reviewers and packaged the pre-review packet with the storyboards used to create the proposal so they’d be reminded of the instructions driving the proposal development.

Ignore: Some issues can’t/ should’nt /won’t be fixed and don’t endanger delivery of a winning proposal, so we’ll spend a moment griping about them and then decide to ignore it.

Amazingly, we put very little in this box. New trainees would feel that everything was outside our control, but more experienced folks knew we had more tools than you might suspect and would figure out ways to nibble away at issues.

For example, resume updating was always behind.

• Our best writer took over the quarterly reminder message and made it a hilarious literary gem folks looked forward to receiving.
• Our best technical person brought in a friend who was programming the new management system and figured out how to grab data being used for billing to automatically update each person’s resume with the jobs they’d billed to. With the minutia already written (account number, client, project title), it was trivial to jot down a note about what you did on the project.
• Candidates for a plum assignment had to be identified quickly. We developed a list of candidates for the President based on the data in the resume database, and we made sure folks knew that the shortlist was created from the resume database.

These systems didn’t happen overnight. We tackled issues as we became aware of them, and bit by bit, built a monster proposal machine. Small disasters were a gift because they gave us the data to know what we had to fix to be ready for a bigger disaster.

We lost power for two hours one day. That got us thinking about what we would do if power were out longer and we had a proposal due. Over the next few months we whittled away at a list of issues until we had a disaster plan. It didn’t get a chance to gather dust.

A few months later, a transformer went out, taking down our entire campus and all our servers. Our group gathered up their supplies, headed for home, got on-line, created a network in the cloud, and were working within 45 minutes. The proposals underway were delayed by only a few hours as we transferred work to other team members and protected our critical path of proposals nearing deadline. We looked like geniuses. The rest of the firm took a pretty big hit in productivity that month with two days lost.

As the team leader, I would look at the issues raised and think about whether the correct place for prevention was actually farther upstream than it might appear. For example, we had a problem printing an odd file and were investigating other ways to print these particular files. However, the better solution was to ask for these files (data output from a proprietary system) a few days earlier than Red Team and produce them ahead of time. The data in these files would not change based on review comments, so there was no reason to delay production of those files until the rest of the document was ready. If we tried to fix this problem on the back end, during production, we had to convert the files and lose resolution, which was not necessary if we re-arranged the production schedule earlier in the process.

I never run out of things to fix, but it stays interesting because we don’t spend time repeating the same problems in the same boring ways.

The jury is still out on whether Engineers and other technical service providers need a presence on the Social Media sites. The most progressive firms are dabbling in LinkedIn, Facebook and MySpace. Most are still sitting on the sidelines.

However, individuals in your firm are on these sites. So every firm needs a social media policy if you don’t already have one.

TRUE STORY:

When the World Wide Web was brand new, the firm I worked for didn’t have a website yet. Only a few of our competitors had websites up, and everyone was fumbling around. We found some good ideas (posting a website and getting in the category for your business with Yahoo and the other directories)  and some bad ideas (posting graphics that were too big to load in less than two minutes!).

Our proposal team was the defacto marketing division since the only other “marketing” department was the graphics team. We took up doing vanity searches of our corporate name just to keep up with what was being said about us out in the ether.  Our employees were also dabbling on the internet, posting personal pages and fooling around with HTML.

Unfortunately, some of those personal pages were objectionable but also mentioned our firm as their employer. Search for our firm and you could get some pages of porn and pages with generally unacceptable lifestyle choices. Maybe you’d get a page that reflected well on our business, maybe not.

We suggested a corporate-wide policy be created to cover how and when the corporate name and/or logo could be used. You would think this wouldn’t have to be written down and disseminated to everyone, but common sense ain’t so common.

Same goes today, only moreso. Some managers worry about social media impacting work productivity. I worry about social media impacting your brand and your firm’s ability to qualify for and win work. A simple set of rules and cautions is all it takes to make folks understand they should avoid implicating the firm in their personal adventures.

Have you Googled your key personnel being proposed for the first time to a client? Don’t you think clients do that?  Add a step in your proposal process to Google all the key people during a review cycle, just to be sure you don’t get any surprises. If it turns out someone with the same name and profile that could be mistaken for your employee has unsavory posts that turn up too high in the search results, 1) coach your person to post their own profile to a few social media sites, especially LinkedIn and Facebook, and 2) consider using their middle initial or otherwise modifying their name to minimize the unsavory hits from matching.

I go one step further and contact many of the folks with my same name. I trade links with them and send traffic their way when it gets misdirected to me. Luckily none of them are strippers, neo-nazis or drug dealers, at least not so far!

One part of my process is to get everyone’s complete contact information at the beginning of the proposal. I want:

• all their phone numbers (work, home, cell),
• all their email addresses (work, and  home) and
• street addresses (work, home, girlfriend) suitable for overnight delivery of documents.

Folks would tease that I kept a “little black yellow pages” with all the personal contact information for so many folks in the firm.

You never know when you’ll need to reach someone and proposals are too time sensitive to wait for the next business day.

< my excuse > I was brought in to help with a proposal underway and did not have the authority nor buyin to use my usual process.< /my excuse >

Sure enough, we go into our crunch weekend, and discover that no one has the home number for the keeper of the cost section. There was a problem, we’d called in a consultant to figure it out, but when he was ready, the cost person was AWOL. Friday night. No response to office voicemail messages nor emails. Great. That cost extra since the consultant had to work blind. With a 5 minute phone call, he’d have finished in minutes. But without his questions answered, he needed more time to work on his own, write out complete instructions, and discuss all possible answers to his questions. Luckily we had until Sunday morning to finish the cost section.

Saturday we meet, but the files are not available. Some of the firm’s servers are down and the internal team members can’t communicate. However, we don’t know this because we don’t have alternative email addresses that could be used to alert everyone. And we don’t have an alternative repository (I use Dropbox, so copies of everything would have been on all our hardrives in a case where the server had gone down.) so we waste time sending files to alternative home email accounts once we get together by phone.

Sunday, we need final approval and the signature of a principal of the firm. You guessed it, no one had the guy’s home phone number. The files couldn’t be emailed earlier because the servers were off line. He was carrying a blackberry so we could communicate with him, but he wasn’t close to a fax machine, and couldn’t open documents.

I abhor heroic efforts to do what should be effortless. I save the heroics for legitimate emergencies, and manage with a process designed to avoid details tripping up progress.

Example of a Legitimate Emergency:

True story: It’s final production on a proposal after hours, and the proposal person is packing proposals in a box. He looks out the window when he hears some commotion. A moose has ambled into the parking lot and walks over his car, smashing the roof in, and breaking all the windows. (Evidently moose aren’t too smart nor delicate.) This is a good reason to have home phone numbers in case you can’t get a taxi in time to get you to the last courier drop.