Quote:
Originally Posted by Brian
However, when we do a new release - whether it's a new product or a point release to an existing one - our goal isn't to ship something that's useful to everyone we think might conceivably be interested. Instead, our goal is to ship something that's useful to a lot of people as early as we can manage to ship it.
|
Hi Brian. I agree with everything you say on a "policy" level, but the reply above illustrates my point perfectly I think.
The mistake I think you've made this time around is
not in leaving out feature X, Y or Z; there will always be features that some people want but that don't make it into version 1, and your policy is the only sensible way to deal with that. The mistake is in leaving out ANY way for people who need to share projects outside of their own organisation, or inside it if Omniplan isn't 100% adopted, and thinking that that leaves you with a product that is useful.
This is the point you haven't answered. The remark I've quoted above suggests that you think export/sharing is a nice to have that will only be useful to a (small?) subset of your users. Yet I'd suggest that thinking that is a massive mistake, unless your target market is people planning a house move rather than serious PM's; i.e. the people who will never buy Omniplan for Mac anyway. As I said before, I can't think of any way for a serious PM to use PM software that won't let him share his plans, because sharing is core to project planning, and the chances of those he needs to share with also using Omniplan are, sadly, almost nil.
So agreed, you can't ship something that will be useful to all users, but I don't believe you've met your own goal of shipping something that's useful to a lot of them.
If I've got that wrong, can you please explain the workflow you had in mind when you released an app that will ONLY share with Omniplan (and Omniplan 2 at that), into a market that unfortunately has not adopted Omniplan as it's de-facto file format?