Showing posts with label Best Practices. Show all posts
Showing posts with label Best Practices. Show all posts

Friday, April 18, 2014

Three Common Mistakes to Avoid with Charts & Graphs

Charts are charts, right? Wrong.

You have a lot of decisions to make when creating a chart, most of which seem benign. But some of those decisions can make a critical difference between providing insight into the underlying data and causing the reader to draw the wrong conclusions.

To illustrate just three of the ways charts can be made to be misleading, check out Ravi Parikh post on How to Lie with Data Visualization over at Heap's Data Blog.

Tuesday, November 8, 2011

Nice Call

Global Equity Organization's call for their annual conference really stands out for its clarity and conciseness. Our favorite part? The "What Happens After You Submit Your Proposal" section. Check it out at http://www.globalequity.org/geo/node/3265 and see if you agree.

Thursday, September 1, 2011

Crowdsource, Curate, or Combo?

The most common model for selecting presenters for educational conferences is pretty straightforward:

  1. Announce a call for proposals (or call for papers, call for abstracts, call for speakers, etc.)
  2. Collect proposals
  3. Have a committee of volunteers review the proposals
  4. Select presentations based on the reviews
  5. Build a session program that accommodates the selections

Although the process works for the vast majority of meetings, it's hard to argue that it can't be improved.

One suggestion we've noticed recently is to open the process up to crowdsourcing. Basically, the idea is to leverage the power of social media by turning over the selection (and possibly scheduling) tasks to attendees. For a more detailed explanation, see Michelle Bruno's post at TSNN.

Another suggestion, seemingly at odds with crowdsourcing, is to have a curator manage the selection and scheduling tasks. The idea here is that conferences, like museum exhibits or other curated collections, are far more effective if the content is carefully selected and organized to "tell a story" to attendees. For more information, see Jeff Hurt's post on Velvet Chainsaw's Midcourse Corrections blog.

So which is it? Crowdsourcing obviously works for larger conferences, like SXSW, but does it also work for smaller meetings with more focused content? And how about curating? Does it work for every type of conference or only for those that can be organized around a clear theme? How about a hybrid? Is it possible (or even desirable) to combine the two into a single model?

Monday, March 28, 2011

Strategies for New & Return Attendees

Jeff Hurt recently posted something on Velvet Chainsaw's Midcourse Correction blog that caught our attention. Basically, he points out how past attendees and prospective attendees employ different criteria when deciding whether to attend your conference and recommends unique marketing strategies for the two groups.

Past attendees are already biased in your favor (assuming they found your event valuable). They know what your conference is all about. You just need to remind them of the experience and demonstrate how the next conference can build on it.

Prospective attendees, on the other hand, are typically biased against you. They need to know why your event is different from other conferences competing for their time and money. Your challenge with them is trust. And who better to build trust than past attendees? Make your previous attendees your "salespeople" by giving them the tools they need to promote your event and ways for prospective attendees to connect with them.

Something similar could be said of presenters. You have two audiences—past presenters and prospective presenters—with distinct sets of needs. Your communications strategy should reflect those needs.

Past presenters already understand the value of presenting at your conference. You don't need to sell them on the benefits. They are more concerned with the process. Make it clear to them that the process will be as easy—or easier—than the last time.

Prospective presenters don't care so much about the process. They don't have a point of reference, so it's all new to them. For them, your focus should be on the benefits of presenting.

You already understand that attendees and presenters have different needs and tailor your marketing and communications strategies accordingly. So why not do the same for loyal and prospective participants? Their needs may overlap, but they are not identical. As Jeff puts it, "Segmented marketing strategies work."

Tuesday, July 13, 2010

Why a hard deadline is better than a soft deadline

We argued previously that a soft deadline for submissions is better than a hard deadline. Now we're going to argue the opposite: that a hard deadline can be preferable to a soft deadline. We're not doing this to confuse you, we're just trying to point out that each has its own benefits and that your choice should depend entirely on your own unique situation.

Unlike a soft deadline, which is nothing more than an initial target for authors to shoot for, a hard deadline is the absolute final date and time you will accept submissions. You always have the option of accepting late submissions on a case-by-case basis, but as a general rule, authors who miss a hard deadline are out of luck—at least until the next call.

A hard deadline is better than a soft deadline because:

  • It avoids confusion. You can publish one deadline and authors won't have to figure out if it has passed or been extended.
  • It forces authors to budget their time for unforeseen problems, which can lead to earlier submissions.
  • It shows you mean business. A hard deadline lets authors know that you are serious about the organization and planning of the conference.
  • It lowers your stress. Once the deadline has passed you no longer have to worry about submissions.

The key to a hard deadline, of course, is that you never extend it. Otherwise, you've just created a soft deadline.

Also, when setting a hard deadline, be painfully precise about the exact date and time of the deadline. It's true for any deadline, but especially true for hard deadlines: include a time—and time zone—along with the date. And if you're going to set your deadline for noon or midnight, don't use "a.m." and "p.m.".

Tuesday, July 6, 2010

Why a soft deadline is better than a hard deadline

One of the most basic decisions about any call is whether to set a soft or hard deadline for submissions. Unlike a hard deadline, which is carved in stone, a soft deadline provides authors with a target date to submit their work, with the understanding that the deadline will be extended.

A soft deadline is better than a hard deadline because:

  • Authors get a date to budget their time for, while also getting a cushion in case of unforeseen problems.
  • You can get a gauge of the quantity and quality of submissions and fine-tune the call if needed.
  • The extension can be used to promote the call to authors who may have missed it the first time.

A soft deadline is set under the assumption that you will eventually extend it, so don't forget to budget for the additional time. Also, soft deadlines work best when you don't publicize the fact that they are soft deadlines. People often produce their best work when crunched for time, so don't ruin your authors' creative edge by hinting the deadline will be extended.

Lastly, don't confuse a soft deadline with accepting late submissions on a case-by-case basis. A soft deadline should be applied to everyone equally, regardless of their circumstances. If you're leaning instead toward accepting late submissions on a case-by-case basis, be sure you have clear criteria in place for determining which submissions qualify for an extension. (But that's a topic for another post.)

Thursday, June 10, 2010

What to include in every call

Wondering what information you should include in your call? Here's our checklist of the key pieces of information every call should have. (You can really never have too much information, though, so consider these the minimum.)

  • Submission deadline (Yes, we have seen numerous calls that neglect to mention the date submissions are due. If you don't have one, set one. People need to know how much time they have or they may never even begin to work on their proposals.)
  • Purpose / theme (Don't assume everyone knows exactly what the call is about. Assume instead that this is their first time to hear about it. At a minimum, give them a general description of what you're looking for. If possible, provide a list of specific topics.)
  • Qualifications (Let people know up front if there are any requirements they must meet—like being a member of your association—in order to respond to your call. If the call is open, be sure to mention that, too.)
  • Contact information (There will be questions. Don't make it difficult for people to get answers. Always include contact information so they can easily reach you with questions, comments, or concerns.)
  • Examples (This isn't absolutely necessary, but examples of previous submissions are a terrific way to show people what works—or doesn't work.)

For conferences, you should also include the conference dates and location. That way, people can determine whether they can attend.

Lastly, if the information for your call is on your Web site (which it should be), try to keep it all on one page. Not only does it make it easier to find information, it also makes it easier for people to print it all out.

Friday, June 4, 2010

Word's Hidden Costs

You should never distribute your call as a Word file for people to fill out and send back to you. It might seem like a fast, easy solution—especially for smaller calls—but it will end up costing you more than you think.

Here are just some of the challenges you face using Word:

  • Although Word is ubiquitous, different versions and platforms mean you can't be certain everyone who downloads your file is going to be able to open it, edit it and send it back to you without compatibility issues.
  • You can include pages of instructions and use highlighting and colorful text to draw attention to required fields, but you're still going to have to review every submission to make sure it was filled out properly.
  • You'll need an iron-clad organizational plan to track every submission you receive, including revisions.
  • Most authors expect an acknowledgment that their submission made it safely into your hands. You'll need to send a confirmation email for every submission you receive.
  • Any file you get back could be carrying something you don't want on your computer. You'll need to make sure you scan every submission for viruses and other malware.
  • You'll need to back up every file you receive on a regular basis in case something bad happens to your computer or network.

Using Word to distribute your call might make sense because it's easy to use, readily available and basically free (if you've already got a license). But once you start to receive submissions, the costs—especially time costs—really start to add up.

Wednesday, May 12, 2010

First Impressions

How many times have you heard someone say (or have said yourself): "This food is terrible. Try it."?

Well, that's the impression we got when we came across a recent call for abstracts that included 25 pages of instructions explaining how to use their online submission system.

Think about the message that sends to potential submitters. How many are going to look forward to submitting an abstract when they're being told—quite clearly—that not only is the first bite going to be hard to swallow, but that if they're selected, the rest of the process is probably going to be just as bad?

No submission process should require reams of instructions. But that's beside the point. The real point is this: Your call is often your first impression with potential submitters. Don't waste it turning people off.

Monday, May 3, 2010

4 Tips for Getting Announcement Emails Noticed

The most important part of any email is the subject line. Think of it as the "packaging" for your message. Not only should it summarize the contents, it must also pique the recipient's interest enough to make him want to open the message to find out more.

So why do so many conferences send out call notices with uninteresting subject lines like "Annual Meeting Call for Speakers Now Open" or "Call for Speakers - Annual Meeting"? Are call announcements an exception to the rule? Of course not. While it may be easy to get people who are already excited about speaking at your conference to open up an email from you, those aren't the people you need to worry about. They've already committed to action. Instead, you should be focused on people who don't know about your conference or who might be on the fence about responding to your call.

Here are some tips for engaging those people:

  • Keep it short. The more words you use, the more likely your message will be muddled. Keep the details for the body of the message.
  • Define value. Tell the recipient up front what he gets out of opening the message.
  • Convey urgency. People are far more likely to act when there's a deadline.
  • Personalize. Keep the focus on the recipient.

Friday, April 30, 2010

How Not to Write a Call for Papers

Dr. Jody Byrne has received quite a few calls for papers over the years. One he received recently, however, really caught his attention... for all the wrong reasons.

As Dr. Byrne points out, "Calls for papers are supposed to inspire, encourage and explain. All this one does is bombard you with jargon, vague descriptions and non-explanations and then give you a bit of a headache."

Have you ever received a particularly bad call for papers? What stood out about it? What could have made it better?

Wednesday, December 30, 2009

The Reviewer's Golden Rule

Here at ProposalSpace we not only want to make peer review easier, we also want to provide a venue where best practices for peer review can be developed and promoted. As a first step, we want to pass along Dr. Stanley S. Siegelman's "Golden Rule" for reviewers from the February 1988 issue of Radiology:

"Most reviewers are also active authors. Referee the manuscript as you would like to have your own papers treated. Be thoughtful and helpful. Offer fair, thorough, and constructive criticism. The reviewer's tone should be friendly and supportive, never harsh or adversarial. Avoid derogatory, potentially offensive, or demeaning comments. We don't want to dampen the enthusiasm of budding young academicians. Test your critique for fairness and objectivity by asking yourself if you would be willing to sign it and send it to the author."

Reviewers in ProposalSpace are not only able to score proposals, they can also attach comments to them. The call administrator determines whether those comments are restricted (made available only to review chairs and administrators) or revealed to the proposal's authors. Regardless of how comments are handled, Dr. Siegelman's advice provides valuable guidance for making the most of every reviewer's effort.