Questions part 4: Refining |
||
|
Most digital projects I’ve worked on treat user testing as a last-minute event, if it occurs at all. If I’m lucky enough to have time for problem solving before launch, I ask these questions. Part four of six. |
5 minutes to read. |
|
Questions part 3: Testing |
||
|
User testing can reveal funny (or disasterous) observations about a digital project. Accepting and dealing with the difference between expectations and reality requires a sense of humor and asking the right questions. Part three of six. |
5 minutes to read. |
|
Questons part 2: Design |
||
|
No two apps or websites, are the same. Neither are the roads between concept and first draft. But questions arise from wading knee-deep into code and pixels. Part two of six. |
5 minutes to read. |
|
Questions part 1: Concept |
||
|
How should one start a website or app? Everyone has different questions in the beginning. These are mine. Part one of six. |
5 minutes to read. |
|
Little rewards and fewer frustrations makes content management less of a chore |
||
|
Every website content management system lets people curate content. But I discovered that if the CMS itself is fun and painless, people are more inclined to update. |
5 minutes to read. |
|
A jQuery snippet to hide unnecessary support |
||
|
We had a list of links that wouldn’t sit still. The client would occasionally change the links, including some to PDF files. To accommodate users, we added a link to Adobe Reader. But when the list had no PDFs, the Reader link became superfluous. Conventional wisdom would have left the Reader link on the page [...] |
10 minutes to read. |
|
Using JavaScript to populate select lists through the ages |
||
|
When two different clients had the same problem, I knew a bit of portable code would solve both. But would it work next year? |
10 minutes to read. |
|