Toastmasters Pathways – an overview of the levels and projects

If you are in Toastmasters, you’ve probably heard that the education program is changing to Pathways. The new program has ten different paths each of which has three levels that you proceed through on your path. I started with the Presentation Mastery path as I expect that to be the most common choice in my club. You can read about my experiences in the Presentation Mastery path. It turned out to be less important than I expected in which path I choose for learning about the program. But more on that in a moment.

First lets start with some key references.

  1. District 57 (the home of Toastmasters) has a great Pathways site with lots of reference material.
  2. District 57 also has a 66 page PDF which lists:
    1. A paragraph description of the 10 paths
    2. A one page description of the projects and electives in each of the 10 paths
    3. A list of the requirements for each project
  3. A list of links to the evaluation sheets for all projects. In order for this link to work, you must already be logged into Pathways. (Don’t bother trying to login after clicking the link). This is useful if you are evaluating a member and they haven’t handed you the sheet.

Back to the paths. While the emphasis of each path varies, you have a lot of choices in common; especially in the electives. Also, the paths are mostly an equivalent amount of work. (Something that was not true of the old advanced communication manuals.)

I really liked the information in the 66 page PDF mentioned above. But I wanted to see in a view that let me compare paths. As a club officer, this is really helpful. So I made my own. I got permission from George Marshall to share my view and here it is.

This 12 page deck compares the paths level by level and gives you an idea of what to expect in each. If you are viewing this post from a corporate firewall, you may see a blank page here as this file is hosted at SlideShare. So try again from your personal computer.

Toastmasters Pathways – Evaluation and Feedback

See my main Presentation Mastery Pathways page for some context. You become eligible to start this project after completing your icebreaker.

About the project

After some background, you watch three video evaluations of the same speech. With a timer counter in the corner of the screen. They show why the evaluations are better as they go. Which helps give an evaluation to others.

I like that Toastmasters is encouraging members to become a speech evaluator once they have given three speeches. (the icebreaker and the two in this project.) I notice some members are afraid to give a speech evaluation at that point so this will be a nice nudge of encouragement.

I also like that this project gives you the choice of using feedback to improve the same speech or to apply it to a new speech. This project had a three question quiz at the end to review what you learned and reinforce the key messages. Like saying “I” instead of “you.”

One thing I found confusing was that the links to download evaluation guides and such were a screen after “complete your assignment.” With completing, I thought there would be nothing else needed to start. Like the Icebreaker, I like that they provide the PDF version of the whole project. It’s good for a reference. It’s also good for seeing what people who opted for paper instead of base camp get. (aka seeing the value of base camp!)

PDFs

Up until now, I had been using a scanner to create PDFs of my evaluation sheets. This time, I took a picture with my phone and converted.

Logging your roles

Also, this project is the latest you have done a meeting role. In addition to completing the project, remember to go to your base camp profile to indicate that you did the role. This needs to be done to log the date of the first time you do each of the following roles:

  • Ah-Counter
  • General Evaluator
  • Grammarian
  • Speech Evaluator
  • Timer
  • Toastmaster
  • Topicsmaster

To mark yourself off:

  • From the Base Camp home page, click “Settings”
  • Click “My Account”
  • Select the date you did the role
  • Click “Save”

performance tuning selenium – firefox vs chrome vs headless

I’m the co-volunteer coordinator for NYC FIRST. Every year we are faced with a problem: we want to export the volunteer data including preferences for offseason events. The system provides an export feature but does not include a few fields we want. A few years ago, my friend Norm said “if only we could export those fields.” I’m a programmer; of course we can!

So I wrote him a program to do just this. It’s export-vol-data at Github. And fittingly, he “paid” me with free candy from the NYC FIRST office. Once a year we meet, Norm gives his credentials to the program and we wait. And wait. And wait. This year NYC FIRST had more events than ever before so it took a really long time. I wanted to tune it.

Getting test data

The problems with tuning have been:

  1. I have no control over when people volunteer for the event. It’s hard to performance test when the data set keeps changing.
  2. The time period when I have access to the event is not the time period that I have the most free time.

Norm solved these problems by creating a test event for me. I started over the summer, but then got accepted to speak at JavaOne and was really busy getting ready for that. Then I went back to it and someone deleted my test event. Norm solved that problem by creating a new event called “TEST EVENT FOR SOFTWARE DEVELOPMENT – DO NOT ENROLL OR DELETE, please. – FLL”. And one person did volunteer for that. But not a lot so it helped.

Performance tuning

I tried the following performance improvements based on our experience exporting in April 2017.

  1. SUCCESS: Run the program on the largest events first. (It’s feasible to manually export the data for small events. Plus those have largely people who also volunteered at a larger event.) This allows us to run for the events with the most business value first. It also allows us to abort the program at any time.
  2. SUCCESS: Skip events and roles with zero volunteers. For some reason, it takes a lot longer to load a page with no volunteers. So skipping this makes the program MUCH faster.
  3. SKIP: Add parallelization. I wound up not doing this because the program is so fast now.
  4. FAILED: Switch from Firefox driver to PhantomJS. I knew the site didn’t function with HtmlUnitDriver. I thought maybe it would work with PhantomJS – an in memory driver with better JavaScript support. Alas it didn’t.
  5. FAILED: Try to go directly to URLs with data. FIRST prevents this from working. You can’t simply simulate the REST calls externally.
  6. SUCCESS: Switch from  Firefox driver to Chrome driver. This made a huge difference in both performance and stability. The program would crash periodically in Firefox. I was never able to figure out why. I have retry/resume logic, but having to manually click “continue” makes it slower.
  7. UNKNOWN: I added support for Headless Chrome in the program. It doesn’t seem noticeably faster though. And it is fun for Norm and I to watch the program “click” through the site. So I left it as an option, but not the default.

Results

Like any good programming exercise, some things worked and some didn’t.  The program is an order of magnitude faster now that at the start though so I declare this a success!