30. April, 2013
In some companies, a culture of “always on” has crept in. People are getting emails and phone calls in their spare time.
As a solution, add this to your contract: For every minute you spend on work related tasks in your spare time, you can log twice the time in your tracker. Tracking happens in 15 minute increments.
So if someone really needs to call your during the weekend to ask just a quick question, you can leave half an hour early on Monday. And if that question turns into a 4 hour monster, you have a whole day off (or eight hours overtime).
That way, there is a “price tag” on your spare time. People don’t have to feel that guilty for calling you but they are also aware of the cost when they do.
23. April, 2013
- Suddenly appear out of nowhere after longer periods of (felt) absence
- Create huge gusts of dust
- Make high and immediate demands for change
- Vanish as fast as they appeared
As a friend of mine once said, “managers are a service.” I don’t bother my manager with my daily work (that’s what I’m paid to do) but for things that I can’t solve myself. When I need feedback and someone else starves me. When I need a tool but the company doesn’t give me budget or the authority to sign it. Things like that.
Helicopter managers don’t help. Most of the time, you don’t notice that they’re there. When the suddenly jump to action, a lot of dust gets blown around. But dust isn’t important. Usually, you can safely ignore dust. Dust only becomes a problem when it’s disturbed. As soon as it gets airborne, it can blind or suffocate you.
Since the helicopter manager is always in a hurry, they don’t have time to see change happen. They just start it. But they’re not there when the flaws and shortcomings of the change become apparent.
When you suffer from one of those, always keep a bucket with dust around to clog their engines.
16. April, 2013
With the recent advances in 3D printing and robotics, there will be a time when traveling to conferences to meet people in person will work like this:
You send a 3D scan of your head and hands to a 3D printing service plus a set of clothes via normal mail. When the clothes arrive and the face has been printed, both will be dressed on an android frame.
The androids will then meet “in person” while you can safely stay at home.
12. April, 2013
A short summary of the presentation “UI Best Practices & Trends” held by Roland Studer of We Are Cube (slides).
- UIs are often bloated, confusing and frustrate users.
- A major factor is that features are often requested by people who won’t have to use the software later i.e. by (self) “important” managers. A variation of “Nothing is impossible if you don’t have to do it yourself.”
- “Don’t make me think” by Steve Krug (Amazon)
- “The interface is your product” (“Getting Real – The Book“). Customers don’t care about the code or the effort which went into the product, they only see what you show them on the screen.
- “Show me where I am”
– breadcrumbs, highlight tabs, use tree navigation
- “Use the F-Pattern”
– eyes travel left to right, top to bottom in Western cultures
- “Emphasize in Tables”
– gray out less important values, make important ones bold, group with color, use gauges instead of numbers
- “Affordance (sic): Show what’s interactive”
– Make it obvious for users to see where they can click
- “Make frequent uses accessible”
– Show only the most important actions as buttons (max. 5).
– Put the other, less signification actions in a popup menu.
- “Caution with icons”
– “A picture says more than 1000 words but which words exactly?”
– Icons can be confusing, hard to remember and they depend on culture/training.
– Offer at least user preferences to replace them with text or show text in addition to the icon or use tooltips.
- “Emphasize primary actions”
– Make the button stand out which the user most likely wants to click next or reduce visibility of less likely options (like “[Submit] [Cancel]”).
– Be careful that the visual cue doesn’t conflict with “this button is disabled”
- “Avoid OK / Cancel”
– Instead of asking “Is it OK to delete?”, ask “This object is still be used. [Delete Anyway] [Keep]”
- “Use undo if you can”
– Avoid confirmation dialogs. No one ever reads them.
– The user should never be able to do anything that isn’t reversible in some way.
– Allows users who got confused with an icon (see #6 above) to unto destructive action on touch screens.
- “Avoid left aligned form labels”
– The eye is only able to align elements when they are close enough.
– Right align labels, rely on browser search for locating elements if you have too many of them (which you shouldn’t)
– Or put the label on top of the fields (but this works better for forms where you have to fill in every single field)
- “Be nice to user input”
– Support “slang” like “next Tuesday” or “now” in date fields
– Keep illegal values so the user can edit them
- “Prevent errors”
– Calendar popups
– Offer a list of valid inputs in a drop-down list or use radio buttons
- “Instant Feedback”
– Show what has been entered correctly as well as what’s wrong.
– Display validation errors immediately (when the focus is lost) instead of waiting for the user to click on a “Submit” button
– Use tooltips on disabled buttons to explain how to enable them
- “Help users recover from errors”
– Avoid “There have been errors” dialogs; they aren’t useful in any way.
– Don’t tell what’s wrong, tell how to fix the error. If you don’t know how to fix it, will the user?
- “Responsive Web Design” – adjust the layout to available screen space. “Mobile first” helps to concentrate on the core features of your application. “Reduce to the max”, avoid distractions, show only the absolute minimum of data. Anything on the page begs to be noticed, so even if the user doesn’t read it, it will still take a tiny bit of concentration to ignore!
- There is a trend towards flat and minimal design. Example: http://basecamp.com/ where a lot of things on the page are interactive (i.e. responds to clicks) but almost everything looks like plain text.
- “Actions only on hover” – Show available actions only when the user hovers over some part of the page. Drawback: Doesn’t work on touchscreens since the user can’t “hover”
- “Implicit feedback” – Show a “saved successfully” message. Give hints in text fields.
Always keep in mind:
Developer != User
Product Owner != User
UI Guru != User
Do usability testing. If you can’t, try installing the product on a laptop and ask someone in the corridor to use it for five minutes. A little is better than nothing. You’re blind to your own prejudices.