
“So often, user-experience designers are held accountable for process objectives. A successful project is one that meets budgets, deadlines, and specifications.
There’s a problem with measuring success this way — process-objective metrics don’t really tell you how good you are at developing a strong user experience, only whether you completed the job specifications efficiently.
But what about the project itself? Was it chosen wisely? Was it grounded in user research and customer insight? What effect will it have on the business? ”
As Scott says, it is really important to define what you as user-experience designers will bring to the table. But it is equally important to note that most projects will still be measured using traditional metrics.
One of the best way to handle this is to define the user-experience design phase as a sub-project itself, so that it can be measured using independent metrics.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |
||||
![]() |
![]() |
![]() |
![]() |