Sean,
I disagree with your notion that adding hierarchy would improve the UI. I think
the single level provided by "group" is sufficient -- most jurisdictions only
have 10-75 service types. Having too many service types, too many groups, or
too many levels of groups makes a mess of the user experience. In our case, we
have over 200 service types for which we accept requests(!), but the top 25
service types account for more than 70% of our requests. With so many fairly
narrowly scoped service types I've seen customers become frustrated when they
can't find a service type that matches some narrow concern not clearly
described in the current set of service types.
Adding complexity to the spec would not just increase development/compliance
costs, but it would also encourage more service types and a more cluttered UI
and therefore hurt the user experience. Embrace the simplicity!
-Peter
From: Open311 Discuss [mailto:discuss@lists.open311.org] On Behalf Of barbeau
Sent: Friday, November 18, 2016 10:22 AM
To: discuss@lists.open311.org
Subject: Re: [open311 discuss] Revision to Services
Open311 Lists<http://lists.open311.org>
[Photo of barbeau]<http://lists.open311.org/p/BVbvv0dJVJ7tYpgRdHSOf>
Revision to Services<http://lists.open311.org/r/topic/5QgErpT9TZg5UrcMRTqpyT>
by barbeau <http://lists.open311.org/p/BVbvv0dJVJ7tYpgRdHSOf>
in Open311 Discuss<http://lists.open311.org/groups/discuss>
I disagree with your notion that adding hierarchy would improve the UI. I think
the single level provided by "group" is sufficient -- most jurisdictions only
have 10-75 service types. Having too many service types, too many groups, or
too many levels of groups makes a mess of the user experience. In our case, we
have over 200 service types for which we accept requests(!), but the top 25
service types account for more than 70% of our requests. With so many fairly
narrowly scoped service types I've seen customers become frustrated when they
can't find a service type that matches some narrow concern not clearly
described in the current set of service types.
Adding complexity to the spec would not just increase development/compliance
costs, but it would also encourage more service types and a more cluttered UI
and therefore hurt the user experience. Embrace the simplicity!
-Peter
From: Open311 Discuss [mailto:discuss@lists.open311.org] On Behalf Of barbeau
Sent: Friday, November 18, 2016 10:22 AM
To: discuss@lists.open311.org
Subject: Re: [open311 discuss] Revision to Services
Open311 Lists<http://lists.open311.org>
[Photo of barbeau]<http://lists.open311.org/p/BVbvv0dJVJ7tYpgRdHSOf>
Revision to Services<http://lists.open311.org/r/topic/5QgErpT9TZg5UrcMRTqpyT>
by barbeau <http://lists.open311.org/p/BVbvv0dJVJ7tYpgRdHSOf>
in Open311 Discuss<http://lists.open311.org/groups/discuss>