Showing posts with label user experience. Show all posts
Showing posts with label user experience. Show all posts

Monday, April 21, 2014

The Making of a Cue Sheet, Feedback

The post on how to create a cue sheet generated some feedback, some of which I'd like to share with you.

First, from Susan Otcenas:
"Had a conversation about cue sheets with some Canadian and US riders. One small item they seemed to feel differently about from your procedure. General consensus was that they want cue sheets to read left to right. As in Proceed 0.1 miles to mile 159 and turn right at River Rd."

So I thought about it, and modified my copy of cue sheet for the upcoming brevet.  Now, for ME, the most important thing on the cue sheet is total distance, because that is what is displayed on my bike computer as well!  Given that, I had the leg distance first, but in a slightly smaller font, and the total distance boldface font, same font size as everything else.  That way, I could quickly focus on total distance.  Looked like this:

Leg distance given first
Worked out well, so I will carry this format forward

Additionally, from Mark Thomas:
"FYI. I've had pretty good luck with a slight variation of this method. I put additional information (like your 10a stuff) into the cue sheet entries in RwGPS. It ends up in the same place after you do the CSV export / open in Excel, but then you have the information available in the RwGPS file as well."

The way to do this is to select the Add to Cuesheet option over on the right side, then click on the route where you want the control.  Then type in any information you want for the cues sheet CSV export.
Add to Cuesheet dialog box

Your notes added to the cues for the route, plus the mileage; nice!
When you export, there it is:
Already in your preliminary cuesheet
The only drawback I see to this is that the cues you add to the route do not show up as icons on the route map.  You would still need to add a POI (Point of Interest) for the viewer to see them called out on the map.

(Updated after more feedback from Mark) As well as adding cues for controls, this also works for useful bits of information such as summits, dangerous railroad tracks, or other.  In addition, existing cues can be improved with clearer navigation information, and adding SS and/or T (stop sign, t-intersection) or any other useful navigational aids.  And this is all stored in the RWGPS file, so you don't have to re-add it should you need to regenerate the cue sheet, and others have access to the information from the RWGPS link.

Monday, April 14, 2014

The Making of a Cue Sheet

Update: I received feedback on this, and ended up with an even more usable cue sheet layout.  So read this for the study and conclusions, and then read this posting for my preferred cue sheet layout.

About 5 years ago, I did a survey on what riders considered the most usable cue sheet format.

Basically, the most important bits of information were:

  • Turn
  • Road (description)
  • Cumulative distance, and
  • Leg distance

Everything else was less important, and, indeed in some respondents' eyes, "too much information".  That can be interpreted as distraction, or hiding the important information in too much text and numbers.

Not to mention that the cue sheet should be accurate!

Note: it is considerably harder to describe this process than to actually do it.

My process to generate a cue sheet for randonneuring is as follows:

Prerequisites: working knowledge of Excel or similar spreadsheet program

1) at least have ridden on the roads in question.  Mostly.  Or gather information from those who have.

2) map it out in Ride With GPS.  I like this mapping program best.  It is free, uses Google Maps data (which seemingly the entire world is buying into), and generates a wonderful starting point for the cue sheet.  I also find it easiest to use of all the programs out there.  I like it so much that I have calibrated my bike computer to match up with it.  If there is going to be a One True Distance, might as well be the one most people use and have easy access to. Yes, I know there are many truths, but if my bike computer and the cue sheet agree, that is a truth I buy into.

3) Verify that map.  Sometimes little side turns sneak in when plotting.  Edit them out (drag the route). Make sure the distance is what it needs to be.  Sucks to have to find a couple hundredths of a mile to get the route to the required distance later on.

4) Save the route, then export it to .csv format.  Looks like this:

Ride With GPS .csv output

5) The distance is way over on the right, so I move that column to be the first column. 

6) Best now to make a copy of this worksheet, so you will have the original handy.  Delete the elevations column if you don't want them.

7) Now, go through that cue sheet with the map handy, and tidy it up.  There will be extra turns in the original that don't apply in real life; delete them.  In addition, maybe a turn is missing, because the plotting program didn't think it needed to be included.  Also verify that all the rights and lefts are correct.  Save your file :-)

8) Now, remove all the extraneous text.  I make use of the Excel Replace All function, doing things like replacing "Turn right onto " with nothing, and so on.  Actually, I got tired of doing it over and over, and created a macro* to do it all for me.  After I clean up all the descriptions, I then replace all the "Right" with "R", "Left" with "L" and "Straight" with "CS".  After all that, I scan through the cue sheet again, manually fixing the ones that weren't zapped by the macro.
  • Don't forget to include the trailing space when replacing the text!
The Excel CTRL-H function.  Removing the trailing space makes the cue sheet look nicer.
9) Starting to look like a usable cue sheet!

10) Put in all the controls.  For controls where the rider just stops along the route and continues, I preface them in the Turn column with Stop.  If they are to turn around and go back, the Turn column contains "U" (U-turn).  You can find the exact mileage for the control, if it isn't at a turn, by putting your cursor on the exact spot on the map, and seeing the distance readout below in the elevation graph.
  • If you need to add a row, use the "Insert Row" function in Excel.  Newer versions let you choose to add a row above or below the currently selected row.
  • Tell the rider what to do AFTER the control.
10a) Add in useful information, like what town the location is in, and where convenience stores, food places, and groceries are located.  Also things like SS (stop sign), SL/TL (stop/traffic light), T (T intersection), are really nice; gives the rider another hint about the turn.
  • ex: "Netarts, groceries, taco truck, 3 Capes CafĂ©, Schooner Inn".  I italicize information that is useful, but not needed for route navigation
  • If a road changes names, I put that on a single line if there are no turns: "Bridge St, bc NE Abbey Rd"
11) now that you know the distance for all your controls (I work in miles; others choose to start in km), you can get the control times from the proper RUSA calculator.  RUSA certified events have different time windows than ACP certified events...
  • ex: "OPEN CONTROL: Tillamook, Main St (US 101)    Open/Close (8:44/12:12)"
12) are you happy with the cue sheet?  All turns correct?  Controls added?  Time to add the intermediate distances (legs), distance in the other (km or mi) reckoning, and format it!

13) insert a column between the total distance and the turn.  This is your Leg column.  The convention here is to have the Leg distance be how far one has to go before the turn (yeah, weird, but we are used to it), so, the entry in the row is the total distance in that row minus the total distance in the previous row.  You could just as easily do it the other way, next row minus this row.  But make sure everyone understands what is going on, although a quick glance at the cue sheet would make that clear.  So, do the formula and fill the column with that formula.  If there is a total distance in every row in the Total Distance column, all will be good.  If not, there will some funny numbers, so please go through and verify.  Save the file.
  • Leg formula, assuming Column A is Total Distance and Column B is Leg Distance, filling in row 3: "=A3-A2".  Copying this down will make the correct formula for each row.
  • Why I start with Total Distance and calculate Leg Distance - the imprecision of each Leg Distance will lead to Total Distance inaccuracies which compound through the cue sheet.  Using Ride With GPS, I can always find the total distance at any point, if things change.
14) now for the other distance reckoning.  I put those over on the right side.  Too many columns of numbers all clustered together is a recipe for a rider to read the wrong one at night when they are tired.  Make two columns, Km and Leg.
  • Total Km formula is: Miles*1.609344
  • Leg Km formula is the Leg Miles *1.609344
Again, create the first formulas, then drag down to fill the columns.

15) Formatting.  I understand some of this is regional preference, but this is how I do it:
  • Now is the time to reduce the number of digits to the right of the decimal point to just one.  Excel has a handy little control to do just that.  Note that this changes the DISPLAY FORMAT of the number, but not the underlying value.  This is a good thing.

    Reducing displayed decimal places
  • Font is something easy to read, Arial, Calibri.  NOT Times New Roman or Comic Sans!
  • Starting font size is 11, but I always save my cue sheets such that riders can download and edit them for their preferences.  Like bigger font :-) if they need it.
  • Control rows are boldface text and yellow background
  • The Turn column is centered and boldface text
  • The Total Distance column is sometimes boldface text.  I am liking that and will probably adopt it.
  • Borders - the outside borders and the horizontal (row) borders are black.  The internal vertical (column) borders are Darker 35% Gray.  Subtle, but the eye will track across a single row better, if some divisions are less emphasized.
  • All those useful bits, like a legend to the abbreviations, and who to call if you abandon should be added at the bottom.
  • Legend I use: L (left), R (right), CS (continue straight), VL/VR (veer left/right), X (cross), U (u-turn), Stop (stop), Immed (Immediate, like Immediate L or R)
  • Most of us use the front bags with map holder, which fits 8.5" width paper, so I don't do anything special, except to ensure that the cue sheet will fit to 8.5" printout.
16) Save it.  Now, follow it on the map one more time.  With any luck, you are all there, and can relax.  Or submit the route to the appropriate group for approval.

17) an option:  Remember "green bar" paper?  Easier to track across a line.  For my own use, I "green bar" my cue sheets, using the Excel table formatting function, with a very light green background on alternating lines.
Green Bar formatting

*macro - basically a recording of what you have done.  Start recording, go through all the Replace Alls, then stop it and save it.  You have to have "Developer" enabled in Excel, and you can find out how to do that online.  Out of scope for this posting.

Acknowledgement: my cue sheet formatting is based largely on the style developed by Susan France, Oregon Randonneurs RBA, with some additions.

Saturday, September 26, 2009

Number Four!

US Patents, that is. Really big grin here. We signed the invention disclosure for this one just a few days AFTER I had been subjected to a 7 hour deposition defending another patent. (We won.) I told the IP department that I just don't learn...

US Patent 7,593,814, Attaching measurement data to an area map

Here, if you want the details.

Wednesday, September 16, 2009

The Missing Scenario

(this would be a Usability/User Experience related post. If this doesn't interest you :-) that's entirely fine)

The scenario:

Prescription refill needed. Patient has new health insurance. The medication in question is one that is not normally stocked at a retail pharmacy, and, on top of that, needs preauthorization.

Patient, knowing all these things, brings it by a week in advance for the refill.

5 days later, patient hears nothing, not from doctor's office, pharmacy, or health insurance.

Health insurance hasn't gotten a preauthorization request, which comes from the doctor's office

Doctor's office hasn't gotten the refill request, which comes from the pharmacy

The pharmacy is called. They have new software, which does not even kick off the refill request until the medication is in stock. And there we have it.

Or, in my case, might not have it until a few days later than desired...

It is going to be a very low energy weekend.

Thursday, November 6, 2008

User Experience Professional At Large

That would be me. I was laid off on Monday, along with my manager, and most of our group. It took Monday and Tuesday to excavate my desk (30 years makes for a lot of stuff). As I had to turn in my badge end of day Monday, my (former) second level manager had to sign me in and get me a badge. While it said "Escort required", other than needing someone to open the outside doors for me, I had the freedom of the building. Excavated, visited around, etc.

Packing

30 years of stuff

I wouldn't say I'm in disbelief, although I still wonder at the logic of blowing away the corporate user experience group.

That said, I'm probably not going to seriously start looking for a job until at least after Thanksgiving.

However, if you know of anyone that needs someone to
  • elicit user requirements,
  • get an excellent understanding of the user's problem space from the USER'S point of view,
  • facilitate the formation of product requirements,
  • create user personas and scenarios,
  • design a user interface architecture, and then populate it with the details of a user interface,
  • as well as do iterative usability testing...
  • preferred in the Portland area
let me know!

In the meantime, I'm going to ride a permanent next Tuesday. 200km, Prairies and Wetlands.