Re: Re:feedback/features/new loopers...

["Kris Hartung" <khartung@cableone.net>]

Yes, I realize the obvious fact that LD is the best source of information 
on
what the most important features would be for a new looping unit, and that
is what I was alluding to, but I was suggesting that this data mining occur
with a formal process, and one that ends with a prioritization from a good
portion of the members. I've been to the Looperlative forum too...it's a
great start, and Bob has been amazing in responsding to questions, 
including
my own.

It's probably too late to act on my suggestion, given that Bob already had
the feature set locked for the release, but in hindsight, if I had been the
program manager for the development of the unit, I would have done what any
program manager in marketing would have done with the development of a new
product, namely conducted a series of focus groups and use various data
collection tools to understand what the most important features are to
customers, and how they prioritize them. And then I would have shared this
with them with a confidentiality agreement.

Maybe Bob did this...I don't know. I'm sure he's talked to a lot of people
and has been taking note of many discussision in LD regarding desireable
features. I'm suggesting something more formal. I'm sure that in the end 
the
LP1 will be a superior unit, and I'm not trying to bash Bob or how he is
going about developing this project. If anything, I'm recommending a 
process
that generally makes development easier. A formal process might make 
getting
there more timely and cost effective. This is one way to address limited
time from a developer.

Kris



----- Original Message ----- 

> >>>What would be nice is if Bob had someone create a web-based
> survey of all the available features on the LP1, first release, along 
>with
list of
> possible features, and have us prioritize the entire list. In other
> words, let the potential buyer define the feature set.<<<

> It's already there... it's called Looper's Delight. Bob's been a
> subscriber and poster here for years. his understanding of looping
> requirements is pretty well tied in with the nature of discussions
> here. the reason for having beta testers is to check whether the
> software works and to have people try out all the stuff that loopers
> are likely to want, most of it based on discussion on here. And also
> to have people to interact with on the process rather than spending
> all day every day fielding requests/complaints/demands from people
> who aren't a committed part of the project. the LD community can be
> pretty damn demanding when it comes to things like this, and Bob
> clearly has a limited amount of time to field this stuff given that
> it's just him (I don't work for Looperlative, I'm just doing the beta-
> testing, and am an endorsing artist of the box) - I'm sure Bob would
> have been answering all this himself, but he's off work on holiday at
> the moment... ...which means that all of this stuff is my thoughts,
> not official company policy. :o)
>
> Oh, and there is a looperlative forum if you want to post questions/
> comments/ideas already. If you have some feature that would been the
> deal breaker in you buying one, post it on the forum. I'm sure Bob
> knows about it already from here, but it can't hurt. ;o)
>
> cheers,
>
> Steve
> www.stevelawson.net - site
> www.stevelawson.net/store/ - shop
> http://steve.anthropiccollective.org - blog
>
>
>
>