View Single Post
ARJWright's Avatar
Posts: 861 | Thanked: 734 times | Joined on Jan 2008 @ Nomadic
#9
This thread is really important, but not because of the question the OP asked...

One of the hardest things for a user to tell me (I train and support folks with a current client and internally to a consulting firm) is what the problem is, or to specifically tell me what it is that should work. They really have a legit gripe about items, and in many causes I can emphathize with their experiences, however, that only goes but so far. Most of my time with them is spent asking questions towards how they use something, what are their expectations, and doing my best to simplify the problem into things that can be managed by any attending developers or others responsible. When I can get the conversation to that point, the user usually feels heard and respected, and will usually think a bit more detailed before they come to me again asking about an item (and they do come, again and again, but with much clearer goggles).

I am not a developer. I can prototype and wireframe pretty well though.

On the other side of those dealings with my client, I also interface with developers - who also happen to be client and internal. These persons care about hard data and requirements. They want to know the value of what they code/create and how it will translate into a normob/business user understanding what it is they go thru. They don't deal well with ambigious requirements, and many like a hard deadline - even if its unrealistic - vs no deadline at all. In my dealings with them, there are some more complicated concepts and discussions, but always the same point as it is with the end-use - to identify the problem and correctly nail the opportunity.

So to the original post and some of the resulting comments...

To say that the N900 doesn't meet your business needs is something that cannot be debated. There are indeed many holes in the OS, 3rd party applications, and overall user experience. These are noticable more in your business context, hence why you came here to air them.

This isn't a business device.

Therefore what you construe as an issue will eventually either fall towards something to be improved (see the Mail for Exchange issues) or fall off the map completely (see some items that were in Brainstorm). Reason is that there are only so many ways to make a non-business device fit your business needs. And at the same time, you not airing what you feel is missing is a problem. You need to speak up, you must.

So what should you do as a business user whom this device is falling short, and you don't have the time/ability to code a solution? Simple really, be as detailed as you can about the use case where the device is failing, and offer to test a solution when/if it becomes available.

What you can't or shouldn't do is be ambigious towards the issue. And yes, you do feel like you are being detailed when you say things like "the calendar should work like a business calendar." But you aren't. You are overgeneralizing - the same sin you are lamblasting the Maemo platform for. You have to say things like, "I expected that this calendar would be as featured as the ones used on previous mobile devices that suited my business needs with features such as XYZ and ABC, but am finding that either this feature isn't here, or that I'm really overlooking it. Is there a developer or two who would like to assist me in making the calendar better usable by adding these features XYZ, ABC, etc. And can someone with an understanding of the core OS at Nokia speak towards why these features may have been left out?"

When you come at it from that end, you are not only more likely to get a positive response, but things like Bugzilla and Brainstorm really begin to shine because they can be used to isolate bugs and features, and then the community-led development approach that's meant to happen, is allowed to happen.

So again, I don't want to discourage you from posting, but I do want to make it clear that much like a statement of work, business use needs to be detailed to the context of use. Otherwise, the non-business ears around here will not hear what needs to be heard, which is that there are more than just non-business persons who have vested interest in this platform prospering.

Kind regards
 

The Following 2 Users Say Thank You to ARJWright For This Useful Post: