My company is currently looking into tools to manage use cases and
Since these terms can mean a wide variety of things I'll give an example of
how we're using them:
*Requirement:* The product should be secure and protect the safety and
privacy of the user.
*Use Case:* The user logs on to the system.
*Sub-use case/scenario:* The user has mistyped their password while logging
*Associated features: *Login screen, password security feedback, lost
password functionality, error feedback system.
*Associated users/actors: *Child, parent, administrator
Social apps are far more complex than single-user apps. I wonder to what
extent a lack of social psych research input into the design of these apps
-- the most popular ones having been designed by college undergrads -- is
causing their popularity to plateau? To me, this suggests a discontinuity
similar to the one that occurred when command line interfaces were displaced
by GUIs. Every GUI out there can trace its origins to the the
multi-disclipinary, thoroughly grounded research conducted at Xerox PARC. I
think it's possible to go only so far by the seat of one's pants.
*Another Blog Posting on Design Thinking & Management from Fast Company. *
"Is the Design Revolution Here? Can Designers get to the top of a publicly
In the past months I've read several articles and blogs about the
possibility that Jonathan Ive, SVP of Industrial Design at Apple, could
succeed Steve Jobs as CEO. As far as I can tell this is only a rumor, but it
prompts the questions: Is corporate America ready for the design revolution?
Can designers be CEOs?
Jason Santa Maria posted an excellent rant on his blog about the lack
of a solid design application for creating GUIs. Most of us jump
through hoops to accomplish our designs in traditional art programs
such as Photoshop or Illustrator.
Well its November and time to reorg the corporation again:)
We are looking at ways to integrate UCD with Business Development. Specifically we are looking at using methods such as K. Holtzblatt's Rapid Contextual Design to develop a new process, rather than a product, that creates a positive user experience for customers transitioning from a legacy application to a new generation product. We are thinking of doing contextual inquiry to understand the decision process customers go through so we can identify what makes them decide to transistion, what are the pain points etc.