Sylvia Pennington reports on the characteristics of the perfect boss. How does your boss stack up? Or if you’re the boss how do you stack up? The cheat sheet list is:
Clem Bastow writes a lot about women’s issues. In this piece from August 2012 she reflects on the name calling attributing to woman that perhaps is not bestowed on men displaying the same attributes. Food for thought.
The first Australian CXPA meet-up in Sydney (16/4/2013) was a breakfast session at Atlassian HQ with Cyrus Allen of Strativity as the MC. The special guest via a Google Hangout was CXPA and Temkin Group founder Bruce Temkin. He is also the creator of Forrester’s Customer Experience Index and Voice of Customer Award.
Time and again I see requirements mixed with specifications. The rule of thumb taught to designers is that requirements shouldn’t specify or suggest the solution.
While I was a student I worked in retail. At one store we were encouraged (forgive me if you hate sales assistants) to ask open questions to invite conversation. It’s harder that it sounds. Years later while being trained in user research we were encouraged to ask why. Not only why, but as many whys as we could … and you know why … to get to the root cause, that deep fundamental driver of behaviour. Of course this too is not as easy as it sounds. Unless you’re a charming 5 year old asking why can sound pretty obnoxious and being asked why can make anyone feel quite defensive. I’m guessing advice like this has its roots in the famous 5 Whys, which I take to be a tool of analysis, not a script. If you disagree with anything here, or have more to add please say so in the comments.