Sunday, October 14, 2018

When to Share a Draft With the Account Team

Published
Author
Comments
0

Updated September 2026: in 2018 I wrote about an account team that chased me by phone for updates before I had even reached the office, and how I finished my deck early but held it back until minutes before the call to avoid last-minute changes. I have rewritten it into advice on when to share a draft.

After an early call where I was not needed, I was getting ready for the office when the account team rang to ask whether I had arrived. I already had everything I needed from the previous day and planned to start once I reached my desk, but they chased every update. At the office I checked with the delivery expert, understood the expectations within minutes and got to work. I finished well before the deadline, but held the deck back and shared it only a few minutes before the call, because I expected the team to ask for unnecessary changes.

Why do people hold back finished work?

To avoid endless rounds of edits. If a team keeps changing things, sharing late feels like a defence. It often backfires: reviewers have no time to read, questions come up live, and trust drops.

When should you share a draft?

  • As soon as it is complete enough to review: with a clear label of what is final and what is not.
  • With a deadline for comments: "Comments by 3pm, please; after that I will lock it."
  • With a short summary: so reviewers know where to look.

How do you stop unnecessary changes?

Ask for comments in one list, accept those that improve the response, and explain briefly why others are not needed. A comment deadline does more to limit changes than sharing late.

How do you handle a team that chases constantly?

Send a morning note with what you will deliver and when, and a short update when it is done. Chasing usually stops when people can see progress.

What would I do now?

Share the finished deck early with a comment cut-off. It gives the account team confidence and keeps control of the changes.

Keep reading

Thursday, October 4, 2018

Closing Out a Bid Properly

Published
Author
Comments
0

Updated September 2026: in 2018 I wrote about finishing a weekend bid despite tool problems, then chasing the delivery expert for the final submitted deck, as my team's process required, and hoping for some recognition. I have rewritten it into advice on closing out a bid properly.

I worked from home over a weekend with my office Skype not connecting, signing in from my personal laptop and sharing screens over WebEx. I still finished the deck and met the onsite account team's expectations. It was submitted to the client early the following week. Our team's standard process was to get the final version from the delivery expert, so I asked him for it. Another weekend came, and he said he would send it then. I went to my home town and checked mail now and then, hoping for the final deck or some note recognising my work.

Why keep the final submitted version?

Because it is the version the client holds you to. If the deal is won, delivery will be measured against it. If it is lost, the final version is what you learn from. Drafts are not enough.

What should a bid close-out include?

  • The final submitted documents: stored where the team can find them.
  • Client questions and answers: as issued.
  • Key assumptions and estimates: with who approved them.
  • Short lessons learned: what went well, what to change.
  • Reusable content: added to the team's library.

How do you get the final version from a busy expert?

Ask the account team instead, since they submitted it. If the expert must send it, ask for a specific date and remind them once, briefly.

Should you expect recognition after a bid?

It is nice when it comes, but do not wait for it. Send your manager a short summary of your contribution after submission. That record is more useful than a hoped-for mail.

What does a good close-out save?

Time on the next bid for the same client, and arguments later about what was promised.

Keep reading