This week in the ux-clinic discussion group:
- Signed, Cut-less in Chicago
This week in the ux-clinic discussion group:
Recently, I switched from working on consumer websites, to the more staid, practical, button-down world of accounting software. As in, accounting software for accountants. In reviewing all the usability classics, I’ve noticed how focused on the pick-up-and-play side of things most of it is.Aside from the odd mention of Fitts Law and the number of clicks required to perform a task, there’s little coverage given to designing for efficiency, especially expert efficiency, in interface design.Anyone have experience with designing for performance, not ease of learning, as job #1? What tips and/or references can the list offer that might help me adjust my mindset to this new set of demands? Is it even possible to make such data entry software a pleasure to use?- Working beyond don’t make me think
This week in the ux-clinic discussion group:
We’re a pair of UX folks (a designer and a usability engineer). We’ve teamed up to turn our team around, but despite our awesome talent combo, we’re spinning our wheels. The team had the good sense to hire both of us, but is fixated on tiny, short term, miniature UI developments. Big architecture work is added to the schedule easily, but all the UI bits are “tweak this”, “improve that”, or “provide a basic UI for new feature blah”.
Our team is smart and leaders are good – but they’ve never taken, or witnessed, a big bet on UI, despite the customer centric project goals. How do we use our powers, design or usability, to change our leadership psychology so that sizable UI/UX investments are part of the game?
– Superhero UX vs. the conservatives
This week in the ux-clinic discussion group:
I work for a large medical software company that attempts to follow a strict engineering process (partly for ISO certification). All logged bugs are supposed to be tied to a requirement (we use ReqPro), but managers aren’t sure what to do with “visual” bugs because visuals aren’t included in the official requirements docs.
So the big question is: What is the best way to fit the visual/UI deliverables into the engineering process?
Specifically:
- How best to deliver visuals? PDF? HTML?
- If designers don’t write the req documents, even if we wanted to, how do we get the designs into the requirements?
- How should visuals relate to the written requirements?
This week in the ux-clinic discussion group:
Right now, our company is growing by leaps and bounds and an initiative has been put forth to reduce the time it takes a new hire to become productive. My question really is what approach have others seen work when it comes to getting new hires (fresh out of college/grad school) up to speed as usability engineers or designers?
How long does it typically take a new hire in your company to be completing projects on their own? What topics are included in your training program and what format do those training sessions take (e.g., lecture style, one-on-one w/ a mentor, hands-on “lab” type training, etc.)?
This week in the ux-clinic discussion group:
While managing a small design team how does one manage both a strong design vision, and maintain a sense of collaboration and team ownership over that vision at the same time? How do you keep your team of real designers from becoming production crafts people when the design vision is quite strong from the beginning? Let’s assume for this thread that the strong vision is internal to the design teams and held and managed by the design manager.