(Updated) Sending a Link to Google Slides in Presentation Mode

Update 9/12/17 - It seems that Google has disabled this functionality. But, here's another method that I found while searching for solutions. 

Copy the share url (click on the Share button and click 'get shareable link') and update like shown in the sample below: 

Original link: https://docs.google.com/presentation/d/1234567890/edit?usp=sharing
Update to: https://docs.google.com/presentation/d/1234567890/present?usp=sharing

When deploying changes to Salesforce, part of my process involves creating documentation and tutorials to explain the changes to users.

I've found Google Slides to be very useful for this purpose. I create a short slide deck with an overview of the changes, along with screen captures so they'll know exactly what to expect.

I generally send a link to the shared slide deck, but I realized recently that my recipients might not be sure what to do with that link, or how to view the presentation in an easily navigable format.

My previous method involved sending a link to the presentation, which opened in this preview mode.

So, to make the process easier, I've started sending a link to the slides in presentation mode.

To do this, I click on 'Present in new window' under the Present button dropdown, and then copy the url in the new window that opens.

Now, when I share the link, the slide deck will open in presentation mode and the viewer can use the arrows on the keyboard to navigate.

I'm always looking for ways to streamline and improve how I support end users. Have suggestions or ideas to improve the process I've described above? I'd love to hear them in the comments!

Salesforce Admin Journal: Teaching a Man to Fish.... or at Least to Create a Report

I regularly receive requests from users to create a specific report. Often these are reports that no one else needs access to.

We are trying to cut down on the number of reports in the 'Unfiled Public Reports' folder. So, I'm encouraging users to save reports that they may need in the future to their 'My Personal Reports' folder.

I'm also working on teaching them how to create reports on their own. As I mentioned in this post from last year, I think it's important to educate people whenever possible rather than just doing something for them automatically because 'it will take me less time.'

This method doesn't just benefit me by reducing the number of request I will receive in the future. It also helps my users become more self sufficient and capable.

Today, a user chatted me a report request. In response, I recorded a one minute long tutorial that will help him learn the basic skills needed to prepare the report himself.

Here's the response I received:

That was totally worth the few extra minutes it took me to record the tutorial using Jing.

Teach, Don't Just Do | Tech Support & Boiled Eggs

I'm going to just ignore the fact that I haven't posted anything in four months. (Four months, really!?) I'm going to pretend that my website wasn't down for a few weeks because I totally forgot to renew my domain while I was planning my wedding. Just smile and nod and proceed to the next paragraph. Please. For me. 

Earlier this month, a coworker emailed me with some questions about basic Salesforce functionality. I didn't have time to do a GoToMeeting to train him (I always get sidetracked with demonstrating functionality that they don't need to know but is just so stinkin' cool... and I didn't want that to happen).

It would have been easy to just do the tasks for him and reply 'done.' 

But, I recalled a conversation with my boss, likely during my employee evaluation. While it might not be the easiest or quickest route, we discussed the benefits of training people rather than just doing something for them.  In addition to benefiting them, it helps you (or me) because the next time they need assistance with something similar, they'll be better equipped to handle it themselves.

When I was growing up, my mom never taught me to cook (or do laundry or start a lawnmower). She would say "Oh, just let me do it!" when I didn't catch on quickly. She didn't have the patience to let me fumble a bit and learn. (This is why I had to call her when I moved out in my early 20's to find out how to boil an egg. No joke.)

So, with a little life experience and encouragement from that conversation with my boss, I wrote out a tutorial with screencaptures (uh, got Clarify? It's awesome.) and sent it to him. I told him that if he needed further help, I was available.

I expected a response something like this: "I'm-too-busy-to-following-your-numbered-directions! I-have-so-many-things-to-do-because-I'm-an-important-sales-guy!! My deals-are-worth-more-than-you-make-in-a-year!"

But this is what I received instead. 

Good technique on your part - provide instructions and let me do it - that's the best way to learn.

That totally made my day.

I know that not everyone is going to respond this way. And that's okay. This experience reminded me that the effort I put forth to help other people become geekier is worth it. I'm going to do my best to provide support that will help my coworkers get something done and build their skill set. 

The moral is this: go forth and do. But also take the time to teach.

Jenna Baze is a rather geeky girl with average social skills and an affinity for: Google Apps, Salesforce.com, Pinterest, natural light photography and finding creative ways to avoid doing dishes (which includes updating a handful of blogs).
Email: rathergeeky@gmail.com | Twitter: @RatherGeeky  | Facebook: Rather Geeky Tips