What about the users?!
User-centered design, a term that is found in more and more design discussions. The design of objects and systems that put the user first. At first it seems so obvious… of course we design for the user. We know what they want! Or do we?
User-centered design should be a foundational principle of your strategy, and from there flow into your User Requirement Specification. A URS is a document produced after research and consultation with real world users has taken place. This research can be a survey, a test group or even a discussion panel.
The Business Requirement Specification:
If you work for a government entity you are in the business of public service. It would seem natural that all systems built revolve around a User Requirement Spec of some sort? Unfortunately this is not always the case, let me introduce you to the Nemesis of the soft and fluffy URS, the dreaded Business Requirement Spec.
You’d be shocked to know that I’ve debated the importance of a URS with a Business analyst recently only to find out that they will ask the successful vendor to draw up the URS. Wait… What?
Let me explain the steps this project will unfold in..
1. A Business analyst will draw up the Business Requirement Spec.
2. The BRS will be handed to the Department and used for the Request For Quotation where the solution is described.
3. A vendor is selected that will deliver the solution
4. The solution starts getting implemented and then the actual USERS and their needs are identified.
5. The solution is rolled out and a usability unit needs to find ways to make it more user friendly.
6. User sits with a crappy product
7. Business ticks a box
Why does this happen?
The URS and BRS would live in happy matrimony if it weren’t for the way the system is set up. Unfortunately, government departments seem to only care about ticking boxes and building things that address their needs. There is also the issue on project funding where government departments (perhaps personalities) need to know how THEY benefit. A BRS is the easiest way for a Business Analyst to show Departments the internal value for the money to be spent.
I’ll sketch a version of a more ideal Project plan in a future post.
-AL-
No related posts.
