When companies first start off-shoring, they usually send the “low level” implementation work overseas first, to work out the process kinks and manage risk. Over time, your valued, domain-aware developers will perceive a lack of career opportunities with this limited role. Naturally, you will want to consider sending design work offshore too. You can make it work. If you do it wrong, you’re toast.
Category Archives: Design
Measuring the ROI of Design
Measuring the return on investments in design may be the hardest ROI calculation you can do. It certainly is one of the rarest. To measure ROI, you have to be able to determine what would happen without the investment, and what happens with the investment. The difference between them is what happened because of the investment.
APR: Information Architecture – Faceted Navigation
In our previous article in the series on the development of nexus, we discussed navigation and information architecture. We identified the challenge of filtering articles by category and by level of experience (beginner / expert), while also viewing the articles along a characteristic (most-viewed, highest-rated, etc). Between both url-creation and visible site-navigation, the challenge we explored was how to present one facet or dimension as primary and others as secondary.
One of our readers presented a third alternative – faceted navigation.
APR: Thoughts on Ratings
Our agile project is to create a site that lets you rate articles. In our corporate goals, we defined the goal to make it easier for people to find and read great content. Last night I was doing some research on social networks and thinking about the nature of our ratings approach. In this article I share some of those thoughts, and the reason for changing the ratings approach relative to previous designs.
Posted in Design, Prioritization, Product Management, Requirements, Requirements gathering
Tagged brainstorming, collective intelligence, dumbness of crowds, eliciting requirements, idea seeding, managing data, passion of individuals, Prioritization, prioritizing requirements, requirements elicitation, Requirements gathering, wisdom of crowds
Leave a comment
Posted in Communication, Design, Prioritization, Product Management, ROI, Requirements, Software development, Usability, Writing
Tagged documentation, documenting upgrades, goal-driven documentation, managing data, passion threshold, prioritizing upgrades, software documentation, software upgrade, suck threshold, upgrade prioritization, upgrade priority, upgrades, user centric documentation
Leave a comment
Posted in Communication, Design, Interaction design, Requirements Models, UX, Use Cases, Writing
Tagged doc, documentation, help file design, Interaction design, interaction design and documentation, managing data, software doc, software documentation, structured requirements, structured requirements and documentation, use case analysis, Use Cases, use cases, writing doc, writing documentation
3 Comments
Latest Articles
Comments on all Articles
