Office 2016 review: The same old Office, but now with more collaboration - http:/
More bandwidth, please #netlit
1 min read
Yes- MT @RoyAtkinson A6: Yes. But...: Complexity drives channel choice. When it’s a complex issue, people want phone, chat or F2F. #custserv
— Bruce Waltuck (@complexified) September 9, 2015
I often think about channels in terms of the bandwidth they afford. As Bruce tweeted, when dealing with complexity, additional bandwidth is desired because we want to take advantage of the additional communications cues they enable.
Different channels fall along a continuum face-to-face -> video conferencing -> audio-only -> real-time text -> asynchronous text, For the most effective collaboration, we need to choose the appropriate form of communicating for the given situation.
Email frequency
1 min read
The surprising data about how often to send promotional emails - Campaign Monitor
Before you send an email, ask yourself, “what value does my subscriber gain from receiving this message?” and “How can I provide the most value to the subscriber by making this relevant to them?”
Great explanation of Slack by Thomas Vander Wal (@infocloud) - #netlit
Admitting You Don’t Know, When You’re the CEO - https:/
Montana / Yellowstone 2015
1 min read
Took Ethan to Montana and Yellowstone - I was at Big Sky, MT for the National Extension Technology Conference (#netc2015). I managed to give a few presentations and attend a bunch more...when I wasn't playing!
Toolbox too big???
1 min read
I'm working on a project looking at the integration of Qualtrics survey software with our Salesforce CRM platform. One of the questions that keeps coming to mind, is what problem will it solve that I can't solve with tools we already have, like Form Assembly. I was hoping it would enable offline data collection, but that feature appears to be incompatible with the Salesforce integration. I like that Qualtrics allows our end users to collect information, but I'm not sure they will be comfortable with connecting to Salesforce - several hoops to jump through.
This got me thinking about how various technologies have given us multiple ways to solve each problem. Finding the right solution is highly dependent on the particular use case, the comfort level of the user, cost, etc.
I think folks get irritated when I offer multiple ways to address an issue, they want one blanket recommendation or "best practice." Too bad there isn't one...
