Five more random acts of kindness for readers

As I’ve mentioned, I’ve been reading and editing a lot of project reports and documents lately.  As I have, I’ve been keeping a running list of suggestions, errors and missteps to consider when embarking on a new writing assignment. Here are the latest additions. (Previous list is here.)  I’ll add to the list as my editing marathon continues.

  1. Define in your mind who your audience is and what you want them to do as a result of reading what you’ve written.  Consider making that definition a part of the document you’re writing to help readers better understand how they may benefit from or act upon what you’re written.
  2. Based on your intended audience, examine what you’ve written to determine whether an intended reader will know or understand every term of art or technical word/phrase.
  3. A declarative statement or editorial comment should be bolstered by proof points; without them, readers often judge such pronouncements as naive or obvious.
  4. When presenting  lots of information, think about using a matrix to organize and summarize material for the convenience of readers. 
  5. If you are discussing items in a series, present the same kinds of information for each item.  Deviations from item to item will stop readers in their tracks as they try to divine whether an omission is an error, an attempt to manipulate a conclusion or something entirely different.

Four ways to break up a coalition

If you’re in the business of building formal or informal coalitions to get things done, you know that you are going to run into people who are working just as hard to undo your good work.  As I’m currently working on a legislative initiative, I’m seeing that dynamic in action.  Here are just a few of the many potential ways that opponents try to peel away supporters (be on guard):

  1. Allege that the proposed action is insensitive at best, unethical at worst, while attacking the motivation of the proponents. Few people want to be evil, and this will cause supporters to at least temporarily question their involvement. Response: Make sure coalition front organizations are recognized positive advocates for change and that communication facts and analysis as to who is affected and how are bulletproof.
  2. Claim that the effort, while perhaps not unethical, is certainly illegal or unconstitutional, especially for obscure or highly technical reasons.  Leave a whiff of litigation threat in the air. People are so skittish about getting sucked into the American legal system that some will start to flee.  Response: Come prepared with legal precedents and analysis that the proposed change has/can withstand legal challenge.
  3. Suggest that the proposed initiative is unneeded because existing entities or organizations can make the changes under their current framework or rules/statutes.  Standing pat is a comforting position for many folks and will sap their drive, ignoring the fact that change wouldn’t be in the air if those groups had done something already.  Response:  Prepare timeline of worsening conditions and/or failed opportunities to previously address needed change.
  4. Agree that change is needed and then propose a complex administrative or funding scheme for making the change happen. The more intricate the problem-solving approach – often offered under the guise of “if we’re going to fix it, let’s get it right the first time” – almost always guarantees failure.  It ensures that the effort will likely collapse under its own weight and inertia. Or it creates a situation in which there are so many things, each hated by one person or group, that the coalition driving for change falls apart.  Response:  Stay focused on solving only the precipitating need and, to use the cliché, harvesting the low-hanging fruit first.  Further change can be pursued when successes have been established and everyone wants to be on the winning side.

10 random acts of kindness for readers (and editors)

I’ve been reading and editing a lot of project reports and documents lately, and as I have, I’ve been keeping a running list of common errors and missteps shared by many writers.  Here are ten in random order; I’ll add to the list as my editing marathon continues.

  1. Use the real state abbreviation when writing.  Postal codes – MO for Missouri – are only used in address blocks.
  2. Capitalize only first word and proper nouns in headlines.  Don’t cap every word or, god forbid, every letter; there’s plenty of research to show that landscape capitalization is far easier to read.
  3. Use “more than” or “less than” when talking about numbers or quantities, not over or under. More describes a numerical relationship; over a spatial relationship. 
  4. Scan the document – every occurrence of “to … ” signals an opportunity for using a more active voice. “The project will prompt economic growth”; not “the project is designed to prompt economic growth.”
  5. Lead virtually any organizational email, letter or document with a call to action, then build the case and context for taking the action, not the other way around. Doing so helps orient the reader and makes for more succinct, tighter writing. 
  6. Explain why you are introducing new information and why it matters.
  7. Link images with body text. Caption all images.
  8. If presenting a series of items, make clear whether it is a rank order list, alpha list or organized by some other principle, or if it’s a random list.
  9. Avoid acronyms.
  10. Construct bullets or lists throughout the document in a parallel fashion. Don’t start one bullet with a verb and the next one with a noun.  Pick one style and stick with it, as is the case with this list.

The 7-step quick-and-easy presentation outline

When consensus building, last-minute opportunities pop up to talk with specific interest groups and attempt to elicit their support.  Often these groups have such specific interests that a standard “stump speech” just doesn’t cut it in terms of content and focus. 

The time and effort involved in producing a tailored presentation for these groups can be reduced, however, by thinking about the mental map of those you are trying to reach.  That is, what questions will they have in mind as they decide whether to attend your presentation, pay attention and give you a fair hearing?

When faced with this kind of last-minute, one-off presentation situation, I think about how I will answer these questions that I believe most potential audience members have as they decide whether and when to pay attention:

  1. What’s the problem or opportunity generally speaking?
  2. Why should I care?
  3. Who are you that I should pay attention?
  4. What are the specifics of the issue/opportunity?
    1. Why is it a problem now?
    2. How much does it affect me?
    3. When will it affect me?
  5. What are the solutions?
    1. Why won’t the status quo handle the issue?
    2. What are the “easy” answers and why won’t they work?
    3. What/who will fix the problem and what are the pros and cons of each solution?
  6. What do I need to do?
    1. What are the specific things you want me to do, when and in what sequence?
    2. What resources are available to help me do this?
    3. How will I know when I’ve succeeded?
    4. Again, why do I need to do this as opposed to someone else?
  7. How will the world be different if I pay attention to you and do what you’ve asked.


Call me Bill

In the midst of myriad emails in which I was explaining the minutiae of passing legislation (and how support or opposition is built and expressed), a colleague complained:   “I don’t remember it being that complicated when the School House Rock video explained it.”  We can only wish.


Making the business case for dedicated truck lanes

Our project team, which has been studying the business case for designing and building dedicated truck lanes on 800 miles of I-70, have just  submitted our project nomination for a Transportation Planning Excellence Award.

This biennial awards program is sponsored by the Federal Highway Administration (FHWA) and the Federal Transit Administration (FTA), in partnership with the Transportation Research Board (TRB).

Our nomination is focused on the innovative planning goals and strategies we employed on the I-70 Dedicated Truck Lanes Feasibility Study, which was sponsored by Missouri, Illinois, Indiana and Ohio.

The Transportation Planning Excellence Awards (TPEA) Program recognizes outstanding initiatives across the country to develop, plan, and implement innovative transportation planning practices. Winners represent a variety of planning organizations from across the county, and will be published in an Excellence in Transportation Planning resource report for their peers.


Changing my mind to avoid changing my shirt

Back in June, I started running again after a layoFFFF of many years.

My clever use of a visual representation of the Doppler Effect may have left you with the impression that I run like the wind, despite having only picked back up in June.  That would be a misapprehension. 

I’m what’s known in running circles as a Clydesdale, both because of my size and lack of whippet speed (the term for lean, fast runners, by which I mean Kenyans).  All I can say is:  no one has ever cried over a Christmas commercial of whippets pulling a wagon through freshly fallen snow nor laughed at one in which they kick a field goal.

‘Nuff said.

Health scare … mid-life crisis … nostalgia for the athletic stud I once was (at least in anecdote); none of these factored into my decision.  Instead, running again was the price of admission to something I’ve always wanted to do – run the bulls in Pamplona.  That’s right. I’m a clichéd Hemingway wannabe who wants to dash into the ruedo in my white linen shirt and pants, my red sash blowing in the wind behind me. However, in the 34 years of life with Linda, I could never get her to see the wisdom and allure of this … until in a moment of weakness and drink, she said: “Sure, if you run a half-marathon first.”

She may have been laughing up her sleeve when she said it, but that stopped when she sobered up.  And to our mutual surprise, five months later I finished the Waddell & Reed Half Marathon here in Kansas City. Didn’t run it in the fasted time ever, but I did run my first half marathon fifteen minutes faster than NBC Chief Meteorologist did, to which I say: “Suck it, Al Roker.”

During that time, I also was busy researching and planning my 2012 Pamplona bull-running trip.  And I mean planning.  Working with engineers over the past five years has really stoked my love of Excel spreadsheets, critical paths and key dependencies. I had pulled together an action plan for getting there and, more importantly, how to sprint the 903 yards to the ring and survive. I knew everything. How they had put down non-skid surfaces at Dead Man’s Turn so that the bulls wouldn’t slip and could keep accelerating after the Euro-trash that deserved what they got. How they keep goring stats so you can schedule your run on a day less likely to end in injury or death.  And mucho, mucho mas!

But here’s the thing.  The more I researched, the more Pamplona videos I watched, the more I learned an important lesson about myself (and not the one people kept trying to teach me, that bulls can kill you). What I learned was that I’m just too damn old to stand in a Plaza with 10,000 youth of the world projectile vomiting from chugging cheap two-liter bottles of sangria.

I’m happy to risk getting gored.  But I don’t want to be vomited on. And I don’t want to be jammed, jostled and generally pawed by thousands of sweaty, pukey twenty somethings. (Hey, I veered away from the High Five Squad at mile six of the half marathon because I didn’t want to touch hands that had patty-fingered 11,000 other runners.)  So I’m not going to Pamplona. 

But at least I’m still running.  So join me for the next outing – the Dec. 4 Great Santa 5K –  No bull. No sangria. No puking up.