-
Creating Good Requirements
Good requirements share universal characteristics regardless of format. Here are the qualities every requirement should have, with a distinctly UX perspective.
-
Lost in Translation: User-Centered Design
The phrase “user-centered design” causes more harm than good. Designing for activities and goals produces better applications than chasing user preferences.
-
Barriers to SharePoint Adoption
Politics, culture, and technology create three distinct barriers to SharePoint adoption. Each requires a different strategy to overcome.
-
The Lie of Technology Agnosticism
Consulting firms that claim to be “technology agnostic” are selling a dangerous lie. Implementation expertise doesn’t transfer as cleanly as they pretend.
-
The Wireframe Audiences
Wireframes serve designers, customers, and project managers differently. The case for keeping them static and staying in your lane as an information architect.
-
The Four C’s to Sell MOSS
Selling SharePoint to management comes down to four words: communication, collaboration, consolidation, and consistency.
-
Harvest Reports WordPress Plugin
Harvest opened its API, so I built a plugin that shows freelance clients their pending charges inside the WordPress admin they already use. Requirements, and what it deliberately does not do.
-
The Value-Up Paradigm
Two ways of viewing the whole development process: the familiar work-down approach of ticking off requirements, and the value-up alternative. What each does to a project, whatever your methodology.
-
Engaging the Entire Development Team
Leaving college meant learning that large software is not built alone. On why specialists still need a general knowledge of what everyone else does, and what poor communication costs a team.