Last Updated on 11 August 2019

Here’s a complete rip-off of today’s post from Seth Godin. Great to have Seth playing in my sandbox.

This is a special sort of get together, similar to the meeting where you organize people to figure out the best way to take advantage of an opportunity. In both cases, amateurs usually run the meetings, and the group often fails to do their best work.

Ignore these rules at your peril:

  1. Only the minimum number of people should participate. Don’t invite anyone for political reasons. Don’t invite anyone to socialize them on the solution because they were part of inventing it–people don’t need to be in the kitchen to enjoy the meal at the restaurant.
  2. No one participating by conference call… it changes the tone of the proceedings.
  3. A very structured agenda to prevent conversation creep. You are only here to do one thing.
  4. All the needed data provided to all attendees, in advance, in writing.
    At least one person, perhaps the host, should have a point of view about what the best course is, but anyone who comes should only be invited if they are willing to change their position.
  5. Agree on the structure of a deliverable solution before you start.
  6. Deliver on that structure when you finish.

I agree with Seth when running a problem-solving meeting, save for a few additions:
No. 5 – “Having a point-of-view about the best course” – The best course should be based on goals and constraints identified prior to the beginning of the meeting.

Goals such as: “In today’s meeting we want to conclude with five new potential names for the company.”
Constraints such as: “Names need to be real words. Need to align with our brand. Need to be easy to pronounce, etc…”

When it comes toward the end of the meeting, refer back to these goals and constraints as filters.