PowerPivot: Is MS allocating enough resources to make it a "slam dunk" winner in the BI market?

i relatively new user of powerpivot. biologist training, training in epidemiology , statistics well, not programmer or bi analyst.  have been involved in developing several successful data management systems, starting 20 or more years ago, classified simple bi efforts.  earliest 1 involved hiring outside database programmers, subsequent ones involved using combination of lotus @ first, excel, access, alpha5, supplemented custom programming.  involvement far powerpivot has been feed data tables either imported access or large tables of lab results available csv files. applications agriservice industry, small businesses ~100 employees or less.

i excited see powerpivot. makes data assessment more within reach of of not data analysts or mis professionals. find, however, seems despite resources ms seem able apply development of tool apparent great potential in apparently rapidly burgeoning industry, product seems must allocated limited resources ms. couple of reasons.

first, while usable non-programmers or non-specialists, not easy should be. full appreciation fact every software has learning curve. nonetheless, documentation , poor. have been spoiled perhaps, previous use of statistics program called stata, has outstanding files clickable on screen, , within files there hotlinks great documentation set.  marked contrast ms products use, documentation sparse if can found @ all, , 1 learns easier syntax or "how i..." type question doing web search using built in help.try looking dax function stdev.s , finding explanation there of how apply filters use, example.

second, seems potential power, taking long time powerpivot functional in public's hands. posted question on list how use stdev , rankx on subsets of data in table. got helpful responses, , have been able implement them, seems me need me raise questions 2 such basic functions reveals lack of resource commitment ms product. in first place, these newly implemented functions pp. seems alone bit of indictment, because these kind of functions serious analysis use regularly - doesn't make sense me why being added tool box, unless ms hasn't allocated manpower , resources pp in position jump out gate enabled complete set of features a) required analysts, , b) implemented such use end users facilitated. in response people responded post explained why thought implementation of these 2 functions subsets in table poorly facilitated in program.

finally, seems there explosion of software tools out there enabling bi non bi/mis specialists. while pp seems remarkable addition toolbox, looking @ other similar options such tableau. looking because while think pp great new addition, limited exposure of alternative software suggests ms not making equivalent efforts pp  facilitate users work. yes pp lot of job done, suspect there alternative programs facilitate experience more pp.  wonder sometimes, if ms developers ever take days , go visit users, , sit there , watch them work. useful experience them, think might insight how new tool working end users.  note on forum there approximately 1000 threads, 60% having answered questions, , 40% remaining unanswered. if ms, concern me. presumably of people find way forum potentially heavier users , more advanced users general user picks pp. if in suspect advanced audience there 40% unanswered questions, , if  software makes 1 jump through convoluted syntax apply simple statistical function query described, not seem bode slam dunk winning lions share of market.

that unfortunate. pp seems great addition bi toolbox. deserves, , think return in kind, high priority resources aimed @ making complete , facilitating use. appreciate efforts in bringing new tool users, encourage ms commit enough resources make slam dunk winner. evidence kind of commitment ongoing development of product seems questionable me.

---

buzz burhans

the bottom line microsoft cannot force users learn use tools supply full potential. however, believe corporate culture such promoting, teaching or providing quite low on priority list. appears me powerpivot viewed internally microsoft same way excel viewed, user tool , not development platform. begs question of why make complex (and fabulously good) , support fancy toy. excel developers have had live reality ever since old xlm macro language introduced. however, microsoft never "facilitated use" providing interface between corporate , (to use current paradiym) "self-service" application developers. now, have frustratingly pointed out, powerpivot may destined go down same path. hope not, , continue want reach potential, regardless of whether powerpivot same.

btw, microsoft eliminating twitter tag powerpivot, example of talking about.

david hager

excel fmvp

SQL Server  >  Power Pivot