Friday, May 9, 2014

Onboarding Class for Your New Job

I have worked a lot of places. A lot. And since I have clients instead of employers now, I get to see how many other types work as well. Corporate onboarding is always a waste of time, as it doesn't tell you how to be a useful, productive and most of all not an annoyingly bad member of the organization.

Here's your manual on being a good information worker in a modern, western office:

  1. When you are on a conference call, mute the phone when not talking. Ideally you plan conference calls like you plan to attend a real, in person meeting and you are awake, prepared, settled down with your coffee or water, on time and in a quiet place. But at least, mute so we don't hear you typing, or your dog barking, or your baby crying. 
  2. When the ask "How are you?" no one  really cares. Unless it will affect job performance in the immediate future, if you are sick or you may have to leave to pick up a kid from school, when people ask how you are doing always say "fine," or "great." Also, try to follow up with "how are you?" 
  3. Schedule meetings. Use the meeting organizer tool in the calendar. Fill out all the fields correctly. There's a place for each thing. Don't put the phone dial-in info in the title; you aren't being helpful; as everyone is used to finding it in the correct field. 
  4. If your meeting happens periodically, use the recurring meeting function in the calendar. Don't send out a meeting for each event. 
  5. When you host a call, and open the line, do not yell "hellooo" or any such variation. "This is Steven, who's on the call?" Better, to prevent people stepping one each other, is to look at who you actually invited, and conduct a real role call
  6. When you announce yourself on a call, at least until everyone knows who you are, explain yourself. "This is Steven from Corporate UX." 
  7. Be able to introduce yourself without saying "oh, what is it I do, hahaha?!" The first meetings with a project team will need that. "Steven Hoober, I am a contract designer for all mobile apps here at [client]. I work for [pointing] Carol, who runs the overall User Experience effort here. 
  8. When you run a meeting, take notes. Distribute the notes to everyone else at the end. 
  9. When you attend a meeting, take notes. Do what people told you to do. Cross off stuff when you finish the task. 
  10. When your boss comes by your desk and tells you to do something, take notes. Do what you are told you to do. Cross off stuff when you finish the task. 
  11. Schedule your work. I don't care if you put it on your calendar, make a to-do list or write it on the wall, but put all you work somewhere. Don't forget to do it. When it is due. 
  12. Tell everyone who cares when you finish your work. It's not really finished till it's delivered, and it's not really delivered until everyone knows it's on the share drive or whatever. 
  13. Don't steal other people's chairs. Don't be a thief in general, but we adjust our chairs to ourselves, and even if wobbly, get used to them. No, not all chairs are the same. Don't steal chairs and if you need it for a sudden executive meeting, note where they go and put them back! 
  14. Include subjects in the email subject line. Remember not everyone is on your project, and inboxes are sometimes narrow, so lead with something very short, like a project name abbreviation. Follow it with the briefest possible summary, and date it if you do this all the time so it's a unique email thread. "CTX - Updated designs, 9 May"
  15. Learn project names. Use the same name and abbreviation as everyone else. 
  16. Address emails in priority order. Put people who will care less as CC instead of TO. Some people filter emails like this. 
  17. Write emails for the least-informed member of the team. Don't assume everyone knows what you know about the project, or that they went to the last meeting. 
  18. Use the return key. Break emails into easily digestible pieces.
  19. Pull out tasks for individuals if you have them in the email. "John, I need you to..."but since it's rare that everyone must take action, don't usually put ACTION REQUIRED in the subject line. 
  20. Have a sigline. Really. For every email. In threads, it's hard to tell who wrote what without it, and often we don't know who you are anyway, or how to get ahold of you. Put your name, title, department, email, phone. 
  21. Reply properly. Use reply-all almost always. Unless you know the team hates conversations going on and on, copy everyone on the original email on the full conversation. 
  22. Reply with context. Copy the part you are replying to into your email, make it "quote" style or (if unavailable) make it gray and italics or something to make that clear, then put your reply under it. Do this point by point. Use color if needed to make it clear. 
  23. Put your vacations, doctor's appointments, etc on the calendar. Then, everyone knows you are not there and don't book meetings over times you are not there.
  24. Look at other people's calendars. You never need to send an email or call someone or take time on a call to say "what's a good time for everyone?" If they didn't update their calendar, that's their fault.
  25. How much do you need to complain about food, really? If the last three times you asked them to order vegetarian you didn't like it, can you instead just bring something, or suffer like we all do? We mostly all hate the pizza or sandwiches anyway, so you aren't unique. 
  26. Bring a pen. Pad of paper. Your computer. Your phone. A cup of water. Be prepared for meetings and so on. Don't spend time during the meeting going out to get stuff. 
  27. Know how company equipment works. If presenting, show up early, or the day before, or ask someone else how the projector works, for example.
  28. Get help. In a meeting, if you are showing off some work, have someone else take notes so you can focus on presenting, running the meeting, etc. and they don't all sit around staring at you slowly writing. 
  29. Sharing your screen on a Skype (or webex, or live in a room, or whatever), don't check your email, turn off your IM, etc. I like to actually quit programs I don't need, so reminders don't pop up. 
  30. Understand people are human. Don't schedule meetings over lunch without feeding, or a reasonable break so they can feed themselves. Don't have 3+ hour meetings, on the phone or in person, without bathroom breaks. 
  31. Tell people about meeting logistics. Don't make them assume or ask. 
  32. Never take the last [thing] from the fridge, snack basket, etc. I mean, unless you are hypoglycemic or pregnant, etc. Likewise, if present in your office, change the water bottle if you run it out, make more coffee if you have a group carafe and use it all, re-stock the pop from the cabinet if it's low in the fridge, etc. 
  33. Same for everything else. Paper in the printer, for example.
  34. Find out who orders office supplies. Be nice to them. Tell them when things are out. Actually, they often know or feel they should so don't tell, ask. "You know we don't seem to have any 11x17 paper, right?" 
  35. In big enough offices, you have a mail slot. Probably near the break room. Some day, something important will arrive there. Get used to glancing at it daily just in case. 
  36. Travel well, if you travel as a group. Never be exceptionally slow or annoying. Any trip under 3 days, for anyone at all, should not involve checked luggage. 
  37. If you drive, pretend you are hosting a meeting. Schedule, arrange, tell. The car is your conference room. Make it neat and organized, drive for the passengers. 
  38. Your corporate processes are stupid. Filling out the timesheet before the end of the month is nonsensical and maybe unethical or illegal. Who cares? Do it anyway so the whole team or department doesn't get an email that you've failed to fill out your time sheet. 
  39. First, do your work. Lunch with the team, leaving early for happy hour, going to the car show on the corporate campus, etc. is never a good excuse to miss a meeting or not get your work done that day. 
  40. If you can't do your work and have a life, for an extended period, complain. When they ignore you -- and they will -- start looking for a new job. 
  41. Don't quit. Look for a new job while you work. No one really knows what you are up to anyway, so you can slack off a bit and they won't notice. It keeps your options open, as the current job may get cool in the months it takes to find something better. 
What did I miss? 

Thursday, September 19, 2013

I Wish Those Who Ignored History Would be a Little More Doomed, Already

Every day I see three stupid tech bloggers, often for the Verge or Wired or someone formerly serious, totally ignore everything more than 18 months old. Here's a typical sort of comment:
Who would have predicted a decade ago that (smart)phones would offer constant access to the Web, to social networks and broadcast platforms like Facebook and Twitter, and to hundreds of specialized apps? Who could have anticipated the power of our everyday devices to capture our every moment and movement? Cameras, GPS tracking, sensors—a phone is no longer just a phone; it is a powerful personal computing device loaded with access to interactive services that you carry with you everywhere you go.
But what annoys me, is that this is from an ACM publication. A serious journal, where there is a long edit cycle and presumably reviewers and editors.

So, we've formally entirely forgotten that in 2003 there were phones that browsed the web, and I was improving the design of things like an app store that we'd had out for a while. Or that these phones had cameras, location (conflating GPS and location is a serious error in itself), etc. etc.

But no. Apple invented the smartphone. Unequivocally. No caveats that all others vaguely sucked despite Symbian being the largest smartphone platform for another 5 years. Forget that. Everything before iPhone was a "dumbphone" and just made phone calls. Apple won the mindshare war for all people who write.

Wednesday, September 11, 2013

M2M is Nice, but Don't Forget E2M

Or: "Your Favorite Pundit is Wrong: Moving Towards Hyper Toothpaste"

Every single article I have seen that talks about the sorta newly-announced Apple iBeacon is getting the point totally wrong. The continued lack of NFC, coupled with this "new" technology leads everyone to the conclusion that they are competitors, and Apple has made their stake.


iBeacons are, at their heart, based on BLE. That stands for Bluetooth Low Energy, and before we get any further "BTLE" doesn't stand for anything at all, so stop using the wrong abbreviation, right now. It's a standard, and indeed is an extension of the Bluetooth we all know and used all the time. Many devices support BLE, and have for a while. Not all phones, unlike what some stupid articles are reporting. But many, and more all the time. 

BLE is derived from Bluetooth which was the winner of a series of technologies called PANs, for Personal Area Networks. Like your connection to the internet is Wide Area, and your home or office has a Local Area Network, this is even smaller. Originally, just to get radio from the phone in your pocket to devices on your head or other pockets, or people you stand next to. 

They are most useful and designed as M2M or machine to machine networks, where your thermostat will send this very low-power, occasional, tiny bit of data to whatever device needs to know. Apple, and PayPal and soon even more, are trying to use these to end run location based services, so stores (for example) can discover (about) where you are as you walk around, or synch payment based on location. I expect much button pushing, and most data still goes over the mobile network (or WiFi), not over the BLE. That's just for handshake, discovery, and validation. 

For more, Matthew Lewis wrote the one and only explanation of iBeacon that isn't totally misinformed and misguided. 

These are supposed to kill NFC. That stands for Near Field Communications, and is a subset concerned with putting RFID technology into devices like phones. You have used RFID, if you have just waved a card at a pad by a door to get access to work, at a turnstile to get on the train, or at a payment terminal to, well, pay for things. 

And that explains why it's useful. What if you could stop carrying an ID badge, subway pass and credit card and just use your phone for that? Oh, and you can in some places, with significant limits. Nothing about the technology limits this, at all. In the US, contactless payment has been held back by... um, I forget. Some bullshit with banks and mobile operators and everyone else fighting over standards. 

When talking about mobiles, there is still button pushing or something else to validate it's you. The mobile network is used to transmit the data, and the NFC is just used to get this tiny amount of information, basically just a serial number (though other things like email addresses and http addresses can be embedded). The clever part to me is that (almost) any active NFC device can read passive devices. Once your phone replaces a credit card, it also can read stickers and posters and anything else a dirt cheap unpowered chip is embedded in. 

NFC is short, short, short range. Supposed to be millimeters or inches, and this is true aside from some hacking with directional antennas. Discovery is via stickers and so forth. You have to be told to tap your card/phone to activate it. Think of this in the same vein as barcodes, including QR codes. Passive, short range, limited in data. 

BLE is derived from Bluetooth which was the winner of a series of technologies called PANs, for Personal Area Networks. Like your connection to the internet is Wide Area, and your home or office has a Local Area Network, this is even smaller. Originally, just to get radio from the phone in your pocket to devices on your head or other pockets, or people you stand next to. Discovery of this is by the radio itself, which can be set to broadcast and discovery modes. BLE is active, longer range (small buildings, street corners), and supports very dynamic data. 

BLE connects the many little digital devices with intelligence and something to say. Over time, everything with power (your car, your thermostat, etc.) will be expected to get little computers, and little radios, so they can talk to each other and we can control them. 

NFC gives a voice to the remaining vast, vast number of passive, stupid objects the world is filled with. No tube of toothpaste is ever going to have a power source, radio, and sensors to tell you how much is left. But it can have an NFC tag which makes it hyper toothpaste. It becomes connected to digital products and the internet. 

You can conceive of an NFC reader in the medicine cabinet which knows what is in it, then that is part of the home automation and talks to a server somewhere via BLE to your phone to keep track of use rates and times, so it can tell if the kids brushed their teeth. Think of this as the real Internet of Things. NFC supports E2M, the Everything to Machine network of the future. 

The moral of this is that BLE and NFC are not competitors. Regardless of the choices Apple makes, and what the tech press is making of it, the world needs both of these types of standards.

Monday, September 9, 2013

Smart Watch Roundup and Some Thoughts

Boy there are a lot of smart watches and related connected devices finally coming out. No, I haven't used the majority of these. Partly as some are merely announced, and otherwise I mostly still have to buy my stuff instead of being cool enough to get things sent to me.

I have played with lots of other crazy devices over the years, and even some very old attempts to be smart watches so still claim to get the gist, though.

  • Samsung - It's practically a mini phone in itself, with the ability to install what seem to be fairly free-standing apps, a camera, voice input, and of course a fairly serious color touchscreen. 
  • Qualcomm - The Toq, which also seems to have an accompanying earpiece, uses a "new" display technology, and is trying to strike a more useful middle ground in the touchscreen control area, with much larger inputs. That might help, but it looks even huger than the others still. 
  • Sony - Rather similar in UI scale to the Qualcomm, if you are following links in order, and still too big a device. Proud of having gestures, like swipe to perform some actions. 
  • Smart Devices - Really not much about this, but it looks again to be a full color touchscreen with tediously tiny controls. 

Of course, most folks are comparing these to the Pebble. And not just the tech writers. Sales doubled on announcement of the Samsung device.

Despite my previous glowing review, it's not a perfect device. It's not ePaper despite their claims. I do wish it would shake to dismiss items, and was a little more clever about what it sent to the watch (most emails are useless, as the body is all this header info...), and i can just imagine having a few crazy features like a speakerphone so I can answer calls sometimes, but that is probably a step too far.

Overall, I have trouble like many commenters on why you'd want a smart watch, but only when I look at those with full color screens, touch targets that are far too small, and maybe as much as 1 day of battery life. Pebble, while in no way perfect, is the trend I still see winning, and maybe even the way these shiny, touchscreen watches will be used: as remotes for your mobile, pushing notices, giving almost-ambient information on weather and status and position and maybe even time. I don't see a lot of photos, note taking, voice response or gaming going on with your wrist.

Which brings me really to the last smart... thingy. Embrace + is a kickstarter I backed as I love, love, love the idea. It's a bracelet (okay, I won't wear it, but my wife might) that just glows and blinks. Truly ambient, very simple and unobtrusive, one-way only information.

Scott Jenson over the weekend said that "people are deconstructing the computer/phone into alternative configurations," which is a great way to say it. These device manufacturers are creating a new way for mobiles to work, and allowing customer choice again in an ocean of flat, fragile slabs of glass. But in a really interesting way, for the interactivity. You used to have the candybar vs. flip choice, with the rare pen/touch nerd, but now there is beginning to be the promise of making your mobile as intrusive, or not, as you want and as two way or not as you need at any moment.

Thursday, September 5, 2013

On Greek Yogurt, Into Darkness, and Platform Choice

I like yogurt. Especially with cereal. There wasn't a lot I could eat as a child, so I grew up on Dannon vanilla and Grape Nuts. Later and over time I have learned how bad 80s yogurt was, and for a while have been happy with much of the local, organic and otherwise real food trends. The health section at the local HyVee spoils me for choice.

Except, now things aren't always so rosy. The Greek yogurt craze has gotten entirely out of hand. When I travel, or try to get my old favorites at Costco, there is no normal yogurt. Nothing but Greek yogurt.

Oh, did I forget to mention I hate Greek yogurt?

See, this is why I consider the "well, just don't use/watch it if you hate it" comments to be the ultimate trolling. Greek yogurt is trying to ruin yogurt for me.

And J.J. Abrams has ruined Star Trek. Sure, I can just not go see the new films. But the way that works, there are (essentially) no new competing products in that universe. So my hate is not for the new, terribly property but that it eliminates something better from existing.

Or, to bring it back onto my day job, when you read a forum or posting that complains about some app only being on one platform it's a legitimate complaint. If I want to use the Fuel band then why do I have to buy an iPhone? Sure, there's some sector competition, like UP or FitBit, but why do I have to shop around for compatibility?

Sure there's other Sci Fi (for now!), and other food, but why do I have to change?

There's a larger point here, which maybe I'll work out sometime.

Friday, August 30, 2013

Gesture Deathmatch: Leap Motion vs… Galaxy S4?

Kinesthetics is awareness of the movement of your limbs, or learning based on physical movement. It is also coming to mean gestures that are not those you touch and swipe across the screen of your mobile phone. 

It’s no coincidence that one of the first kinesthetic gesture devices you used, the Microsoft Xbox Kinect is spelled that way. Yeah, the Wii also does this, but senses in a different way.

This is one of those technologies that is a bit like voice; it’s been the next big thing for a decade or two. Except that it’s also been sneaking up on us. Sensors have, for years now, been waking up your phone when you pick it up, or locking the touchscreen when it thinks you are putting it up to your head to talk.

But now, these sorts of gestures are becoming a bit more mainstream and general. You can consciously use them on, or with, several new devices.

Leap Motion

If you didn’t know, Leap is one of those popular but somewhat delayed Kickstarter products. I got mine the first few days they were shipping, and have been evaluating it for a couple weeks now.
It’s a tiny box that plugs into your computer via USB and then watches for movement. You set the box in front of your monitor somewhere, then when you wave your hands in front of the computer, it sees them. In some detail, when you run the demos at least, though real-world responsiveness is just okay.

Not that I use it much. Other reviews have complained about not having a consistent gesture library, for example. That didn’t stop touchscreen phones when they came out. It was a gripe, but one you could get over pretty easily.

When I ordered the Leap, and even when I saw other demos, I had visions of how it would work for me. Quite specific ones. I wanted to keep my right hand on my pen tablet (which has been my primary input method since 1993) and then be able to just put my left hand in front of the screen to manipulate the drawing area; open palm to scoot the screen area around, say, or pinch to zoom.

It doesn’t do that. At all. Not that it couldn’t I suppose, but they have gone far, far too much into the app store model. Software is piled on software and linked to websites. You have to install zillions of little apps and plugins. Many are paid. Almost all are very freestanding. Essentially nothing allows you to control an existing application with the Leap directly.

I don’t intend to change my whole way of working by having the one computer with a Leap using special Leap software. So 90% of the use has been me getting the kids out of my hair playing games and doing very cool looking educational, exploring things. It’s very cool, and the hardware is promising, but the integration fails me entirely.

Samsung Galaxy S4

Yes, the contender for today’s purposes is a completely-different device. Not a dongle to complete with the Leap on desktop, but a single, free-standing smartphone.

For a few generations now, Samsung has been adding human-facing sensors, and doing interesting things with them. Many of these have been somewhat secret. Not evil, just not very obvious, with the end goal being not very annoying. Their devices are a bit better at detecting when you are looking at them during a call for example. Yes, others (notably Apple) have a decent assortment of sensors also, but Samsung has really embraced this.

I've been trying out the Verizon version of their newest flagship model, the Galaxy S4, for a few weeks also. It has a few more sensors than the S3, I think, but most of all is using them more directly and is making it all quite obvious to the end user now.

There are a whole series of settings that turn on various UI features based on you waving at the phone, tilting it, or even just looking at it.

When I say they are being obvious, I mean that these features are front and center in their TV advertising. 
I should mention that while the sensing isn’t better than Leap, or sometimes really very good at all even, it’s quite good at mentioning when it sees you. My favorite is the eyeball scanner. It shows a little icon (oddly in the middle of the screen) which indicates it can see you, and where it thinks you are looking.
This feedback means you can adjust yourself. I think that’s one reason Leap fails. When in demo mode you are looking at your hands directly, and it’s amazing but when using it for what we have to consider real work, you have no feedback.

Building an Environment

Aside from niggling details of the UI and interaction, the biggest difference between the two, by far, is the way they work.

The Leap Motion has brilliant technology, and the concept of bringing kinesthetic gesture to the desktop is great, but is such an add on that it is of essentially no value to me. And actually, the kids have even gotten bored with it. They want to do much the same as me, and finger paint in my professional drawing tools, or use it to navigate the computer. Which it doesn’t really do.

Whereas the Galaxy S4 totally does this. The technology is not as flashy, and is actually maybe less reliable than the Leap. The eye tracker doesn’t work with glasses, for example. But what works, works in most every app. And pretty seamlessly. If you leave on the gesture scroll, then as soon as you aren’t confused by it, the page you are viewing just scrolls as you naturally want it to.

And this proves out actually using the devices. As I said, no one much uses the Leap Motion, but it’s hard to keep the kids away from the Galaxy S4. It’s not just the big, shiny, new phone in my collection. But also the one that has the features that automatically make it work easily.

I like to talk about how it’s our job to use the sensors and connections of the phone to create ecosystems, or environments that support the way the user works. This is another extension to that. And you don’t even have to spend the usual time to get used to it and set it up your way. Turn everything on and just let it try to automatically create an information environment around you, and for you.

Tuesday, August 27, 2013

Developers Misguided on App Platform Targeting

That could be the alternative headline for this article from TechCrunch. Let's look at a bit:
Forrester found that more than a third (35%) of respondents target iPhones as their first priority device vs less than a third (27%) who target Android phones first... ...For the time being, iOS continues to punch above its weight by being the platform developers tend to choose to launch apps on first. 
Um... sure. That's not at all biased. It's not "has closed to just a 7 point difference" or anything.   But I have another issue.

I speak not as the anti Apple fanboi, but from my experience working for a couple clients. In the last year I have worked on (if nothing slips my mind) five mobile apps. Some are multi-platform. ONE was first built on iOS. And that because... the app developer the client picked (before I got there) was comfortable on iOS. Insisted stuff that they wanted couldn't be done in Android "as easily." Stuff like connecting to Bluetooth devices. Sure. (They also decided design was hard so just sorta ignored what I got paid to do, and built something else.)

If we go back the previous year, I did another half dozen apps or app projects. 2/3rds of those did start on iOS. Here, again, because of the developers. They had a write-once (hybrid, apparently) platform and decided [a poorly conceived] iOS version was the baseline.

When marketing gets involved, without any whiny developers, they look at the actual data and pick platforms their target audience uses. And more often than not this actual data is right. They are happy, to have spent money on the most result first.

In all cases where multiple platforms were launched... it depends. Android was not always the clear winner. Sometime BlackBerry had surprising use rates (over 20% in some user groups*). The lesson is:

  1. Do some research, check your Web analytics, and target what your audience really uses and wants to use. 
  2. Stop asking developers what they prefer.
* Yeah, that was last year. BBOS has dropped off to nothing in most cases now.