Friday Bonus: 2012 *IS* the Year

January 13, 2012

Ground Zero for PowerPivot Going Critical?

Today’s Scene  (Just add a Foot of Snow)

An obsessive and intrusive habit

Quick anecdote.  For a couple of years now I have been accosting people in public places when I see them using Excel.  On an airplane?  In an airport?  In a doctor’s office waiting room?  You aren’t safe in any of those places.

If you’re using Excel, some weirdo is gonna walk up to you and ask you two questions:

  1. Do you use PivotTables?
  2. (If Yes) Do you use PowerPivot?

The first answer tends to be “Yes” about a third of the time.  That’s disproportionately high relative to the broader population, in which only about 5-10% of people use pivots.  There’s a selection bias in play here of course, because someone who uses Excel enough that it’s on their screen when I walk by is more likely than average to be an Excel pro, and therefore more likely than average to use pivots.

But for two years the second answer has always been “no.”  I then explain that they should be, they express shame, they promise to check it out.  Sometimes they even get a demo.

Until Today!

Recall that just a few days ago, I predicted this would be the year where we start running into PowerPivot via random personal connections and conversations.

This morning, at 10:15 eastern time, at the Starbucks on Cedar and Fairmount in Cleveland Heights OH, I noticed a well-dressed man sitting with his laptop, engrossed in Excel 2007 or 2010 (couldn’t tell, just saw the Ribbon).

Being a “work from home day,” I took stock of my own ensemble:  Unshaven?  Check.  T-shirt and tennis shoes under a coat covered in dog fur?  Check.  Beanie-style snowboarding hat with a pom-pom ball on top?  Check.

Perfect.  I moved in for the kill.

I’m positive he thought I was going to ask him for money or something, and the smile that came over his face when he heard the pivot question was one of sheer joy and reliefSmile

OK, so “yes” he uses pivots.  Now for the second question, the one that engenders shame when the person has to say “no” to a question that so clearly, I think they should say “yes” to… 

ME:  “Do you use PowerPivot?”
HIM:  “No, I don’t, but my team does.  We use a lot of SharePoint.”

Quite the rollercoaster in that sentence.  In sequence, my brain flashes the following reactions:

  1. “He said no.  Yep, just like every other random sample to date.”
  2. “Whoa, his team does???  Wait, he doesn’t know what PowerPivot is does he?  He’s bluffing!”
  3. “Hold it hold it!  Anyone who follows up a PowerPivot question with a SharePoint reference actually DOES know it.  And quite well!”

Fantastic.  I let him get back to work rather than chatting him up.  Took some serious willpower.


In the Browser, Aesthetics Yield a Greater Return

January 10, 2012

 

A PowerPivot Doc in the Browser is an Application   
A Spreadsheet in Excel Services Is No Longer a Document,
It’s an Application

I thought today was going to be a “handful of mini posts” kind of day but then this post blossomed into a bit more than I thought it would, which is a good thing.

Normal Spreadsheets are Usually Ugly and That’s OK

It’s true:  most Excel pros are not artists.  I certainly am not.  We’re number folks first and foremost, and our jobs haven’t historically placed top-level emphasis on aesthetics either.  So we don’t spend much time on it, typically.

Besides, Excel itself isn’t pretty.  Back in the 80’s or 90’s, even if you made a spreadsheet look fantastic, well, it was still loaded in Excel.  So you got all those lovely “battleship grey” toolbars, the title bar, etc.:

Spreadsheets of Yore Were Also Made Ugly Just by the Excel Frame

Spreadsheets of Yore Were Also Made Ugly
Just by the Excel Frame Itself

I want to be clear:  This is NOT a post that is going to encourage you to run out and start putting lipstick on all of your spreadsheets. 

Instead, I am going to make the case for why the game changes significantly (for the better too) when you switch to using a server (or a cloud hosting service like ours) to share your work.

The “Excel Frame” Has an Enormous, Underappreciated Impact

Hey, you might say that the old-style Excel screenshot above is an unfair example, since Excel 2007 and 2010 replaced menus and toolbars with the Ribbon.  But in a crucial way the Ribbon is NO different really – the point is that either way (ribbon or menu/toolbars) the Excel frame is NOT YOURS.  It belongs to Excel.  And no matter how much work goes into the document itself, the user of that document still thinks you made them a document.

Let that sink in for a minute.  Because the user of your spreadsheet thinks they are “using Excel” and not “using an application built by my favorite Excel pro,” you are receiving a hidden benefit AND a hidden penalty:

  1. There are many things you will never be blamed for as long as the consumer thinks of Excel as the application.  Hey, the overall experience just feels kinda clunky.  “No big deal, that’s just how Excel docs always are.”
  2. But you also don’t get nearly enough credit, psychological impact, or perceived importance that your work deserves.  Seriously, your work drives your organizations.  If everyone thought of you as a programmer (which you are, even if you don’t write macros), you’d be viewed differently.  But people who produce documents are often viewed as “Excel Monkeys.”  Honestly I think Excel pros are, for the most part, underpaid relative to their true importance.

When you switch from mailing spreadsheets around to publishing spreadsheets on SharePoint, well, both of those go out the window.  Well, if you do it right, anyway.

SharePoint Brings Its Own Frames!  Ack!

OK, so you switch over to using SharePoint as your publishing mechanism.  Does that get rid of the Excel frame?  Well not really.  It just gives you a new Excel frame in your browser:

See all of those highlighted elements?  Just another Excel frame, ported to the browser.  Complete with File tab, toolbar, the .XLSX extension blazoned across the top, and even a warning bar.

Not to be left out, SharePoint adds some of its own at times:

So, you gotta get rid of those.  And that means customizing SharePoint.  If you’re a SharePoint pro that’s mostly not too difficult, but even then it likely will take you some time to get it tuned just right (we’ve been making tweaks now for two years).  And if you’re not a SharePoint pro, well, you are going to need one.

(For more info on the details of these SharePoint elements and what we’ve done to modify/suppress them, see this post and this post).

Going Frameless Turns “Document” Into “Application”

In our Hosted PowerPivot offering, we’ve got all of that suppressed, and the only “frame” you see is just the browser and a typical web header.  An example:

PowerPivot Application Built by Pivotstream

The Consumers of This Application Neither Know NOR Care that it Was Built in Excel

The idea for this post struck me yesterday as I was putting together this sample workbook (based on Microsoft’s AdventureWorks data set) that we are going to start including in all of our HostedPowerPivot sites as a tutorial:

Sample Hosted PowerPivot Workbook

Sample Workbook v1 For Hosted PowerPivot

Or try this humorous example (based on real data) that examines UFO sightings – click image to view the application on Mr. Excel’s HostedPowerPivot site.

Live PowerPivot Application on HostedPowerPivot

Click Image to View the Live APPLICATION

Completing the Illusion:  A Few Simple Steps

Once you’ve gone frameless, there are a few simple things you can do to complete the transformation from document to application.  Neglect these and your “frameless” would-be application screams “spreadsheet” to the audience.  Follow them, and even if you’re not terribly artistic, your work will be perceived very differently:

  1. Turn off gridlines and headers.  It’s not hard.  Two checkboxes on the View tab of the ribbon, but do that for EVERY sheet the consumer sees.  Every single one.  Crucial.
  2. Hide or delete all sheets you don’t want them to consume.  Don’t leave extra blank tabs in there named “Sheet3” OK?
  3. Insert some images.  So important!  Your company logo.  Your client’s logo.  Something.  And make sure you use the Insert ribbon to do this!  Simple copy/pasting an image into a worksheet, in my experience, seems to result in that image NOT showing up in the browser.
  4. Line up slicers, charts, and tables.  Takes just a minute or two to make sure the top of your slicers are even with the top of your chart, etc.
  5. Don’t neglect number formatting.  If something is a currency, format it as a currency.
  6. Use conditional formatting.  No need to overdo it, but conditional formatting turns a boring black and white grid (a pivot) into an inviting surface that is actually fun to look at.  Plus, trends, patterns, and outliers jump off the page much more readily.  I’m especially fond of data bars, color scales, icon sets, and when I have the time, sparklines.
  7. Create a Menu sheet (Table of Contents), and use hyperlinks for navigation.  Yes, the sheet tabs are visible.  But why force people to use them?  There are a million reasons why sheet tabs are disproportionately old fashioned and cognitively difficult.  When it comes to navigating around a web application,  nothing comes close to a hyperlink. 

“I’ll Take ‘Hyperlinks Between Sheets’ for the Win”

Let’s focus on that last one.  Did you know that you can hyperlink between sheets in a workbook?  I worked on Excel for years and never really realized this.  Our CEO at Pivotstream pointed that out to me, and it works on the server too.

Hyperlinking Between Sheets in Excel

Hyperlinking Between Sheets in Excel

This lets you create menu sheet like the AdventureWorks sheet above, as well as this one at the beginning of the post:

This Is Actually a PowerPivot Menu Sheet aka Table of Contents

This Is Actually a PowerPivot Menu Sheet (aka Table of Contents)

Cool huh?  Those chart thumbnails are IMAGES.  The hyperlinks above them take you to the full-page interactive sheets that host each of those chart views.

Formatting Macros

I have a number of macros that help me do some of this stuff, and in an upcoming post I will share some of them, once I have time to organize them a bit.

In the meantime, here’s a real simple one whose intent should be obvious:

Sub HideGridAndHeadersOnAllSheets()

    Dim oSheet As Worksheet
   
    For Each oSheet In ActiveWorkbook.Worksheets
        If oSheet.Visible = xlSheetVisible Then
            oSheet.Activate
            ActiveWindow.DisplayGridlines = False
            ActiveWindow.DisplayHeadings = False
        End If
    Next

End Sub

How many of you use macros, by the way?  I’m really curious.  Drop me a comment if you would and just say yes/no.  I will also put up a survey at some point if I get industrious.

Conclusion

I know that not everyone who has embraced PowerPivot for Excel has started using PowerPivot for SharePoint yet.  That’s changing, but it takes time.

For those of you who are starting that transition, I’m very excited for you.  I know it sounds weird.  But you cannot appreciate how much more impactful your work “feels” as a web application until you see it in action.  And this post is aimed at helping you reap that benefit.

For those of you who are yet to start down that path, file this one in the back of your mind for later.


Welcome to 2012: the Year of PowerPivot Everywhere

January 3, 2012

 
PowerPivot

Coming Soon to an… Everywhere Near You Smile

(OK so I said this post was coming on January 2nd, but really I meant the 3rd since today is Tuesday.  Apologies for being so late in the day though). 

Well it’s been a refreshing holiday season.  I actually did a lot less work than I planned.  That’s mostly a good thing, but I committed to a bunch of new things too, so I better have fully-charged batteries rolling into the new year.

So, why do I think 2012 will be the year of PowerPivot?  Well, the first reason is that…  2013 isn’t here yet Smile.  Because I am quite certain that every year will be a bigger year for PowerPivot than the previous.  For a long time.

But 2012 will be the first year where we all start running into PowerPivot in places where we weren’t looking for it.  I certainly see plenty of PowerPivot adoption in places that we all might consider “unlikely,” but I find out about those cases because those people reach out to Pivotstream for assistance.  It’s not like I’m stumbling on it.

But I think that changes in 2012.  I think we will start running into PowerPivot through random personal connections, because its adoption has just reached that point.

I’m increasingly meeting “High Priests” coming downstream while I am paddling upstream.  Lately I keep finding myself on so-called “sales” calls with people who have been using PowerPivot for awhile and glimpsing its potential, and THEY start telling ME why they think PowerPivot is a game-changer.  Not only that, but their reasons, their “talking points” if you will, are as crisp as anything I have ever captured on the blog.  That certainly gets my attention.

Reason #1:  My Uncle-in-Law Savvies the PowerPivot?

A funny thing happened over the holidays.  My wife and I were visiting her family in Chicago, and the usual “so what are you up to these days” type of holiday party chatter ensued.  Her uncle owns his own video editing business, and when he heard the word “PowerPivot,” he said:

         “Hey I edited a video on PowerPivot last year!”

I am not accustomed to this sort of thing yet.  People who aren’t spreadsheet or SharePoint or BI pros really have no reason to know about PowerPivot at this point.  So my response was naturally something like “are you SURE it’s PowerPivot?  Was it computer related?”  Turns out, it was an Intel video from TechEd 2010, which I even attended:

image

Not the best video in terms of content, but the editing is SUPERB

OK, yeah, it’s from a year and a half ago, so it’s not exactly a sign of a recent tipping point. 

But it’s still my first-ever completely random, “normal, non-number-crunching-person has a connection to PowerPivot” moment.  I expect to have many more of these in 2012.

Reason #2:  Blog Stats on the Rise, with an Exponential Flavor

PowerPivotPro.com enjoys a decent page ranking in the search engines, as evidenced by a quick google of the term “PowerPivot.”  As such, I tend to regard traffic here as a decent indicator of overall PowerPivot adoption and awareness.

I’ve guarded these stats closely for a long time now (mostly out of insecurity, and not knowing what counts as “good” traffic for a blog).  But the trend I have been watching is interesting, and I want to provide some detail.

The blog had its first full month in November 2009, about 6 months before PowerPivot v1 was released.  Here is a graph of total page views per month going back to the beginning:

PowerPivotPro Monthly Blog Views Since Inception

PowerPivotPro Monthly Blog Views Since Inception

Notice how the little orange trendline doesn’t actually keep pace with the recent traffic numbers?  That’s because we’ve seen an inflection point this Fall.  A sharp rise.

Curious as to what this would look like just over the last eighteen months, I filtered it down:

PowerPivotPro Monthly Blog Views Since PowerPivot V1 Release Date

PowerPivotPro Monthly Blog Views Since PowerPivot V1 Release Date

That’s probably a better indication of trend, since those 18 months roughly correspond to the time since PowerPivot v1 was released.

Now if we extend the trendline out another six months into the future, we see that we’re trending toward 35,000 a month by June, about 3x what it was the same time in 2010.

Same as Previous Chart But Projected Six Months Into the Future

Same as Previous Chart But Projected Six Months Into the Future

Lastly, it’s instructive to look at the data in “year over year” fashion:

PowerPivotPro Monthly Blog Views Since Inception, Year over Year

PowerPivotPro Monthly Blog Views Since Inception, Year over Year

See how the gain from is bigger from 2010-2011 than it was from 2009-2010?  That’s an example of exponential growth:  the audience is growing at a rate that is proportional to the existing size of said audience.  

One of the hallmarks of exponential growth is that it tends to seem slow at first, because the size of the population is also small at that point.  Later, once it has a good foothold, it surprises you with startling increases in a short period.  This is literally the way that viruses and bacteria multiply, and when something spreads “virally,” it follows this sort of a curve.

For examples of this, see my reference to the “magic eyedropper” story near the end of a previous post, and here’s an article that explains how plants/gardens follow the same sort of growth curve.

Typical Example of Linear vs. Exponential Growth:  Seemingly Slow, then Explodes

Typical Example of Linear vs. Exponential Growth:
Note How the Exponential Curve Seemingly Goes Nowhere for Awhile,
Then Starts to Pick Up, Then Goes Literally “Viral”

Reason #2a:  A Past Observation by Bill Baker

I was at a TDWI conference in San Francisco about seven or eight years ago where I attended a panel discussion.  Bill Baker was one of the three panelists.  Bill was asked if he thought a particular technology (I think it was web services like SOAP) was going to be a big deal or a one-hit wonder.

I really liked his answer, which was to point out that we often tend to OVER-estimate a new technology’s impact when we look ONE year into the future, but we tend to UNDER-estimate its impact FIVE years in the future.  In other words, “hot” technologies tend to “disappoint” at the one year mark, but by the five year mark, they often have quietly popped up everywhere.

Today, it struck me that Bill’s answer is really just the anecdotal way of describing exponential growth:  something that spreads by word of mouth, by example, by experimentation, and by proving itself the hard way, rather than being adopted on command.  I’m pretty sure Microsoft wishes it could command this one, but it won’t have to.

OK, on Thursday we have a killer new post by the esteemed Mr. Churchward.  Stay tuned Smile


Why PowerPivot is Better Fed From a Database, Pt 1

November 22, 2011

An Excel Pro’s Two Year Journey in Database Land

In a post last week I mentioned that when you use a real database as a source for PowerPivot, a number of unexpected doors open up.  As a longtime Excel pro who has spent the past two years working closely with a database team, I can tell you that it’s been an eye opening experience.

So I have been advocating to Excel/PowerPivot pros for quite some time that they cozy up to their database teams (if they have them).  Of course, this works both ways, and I have also been advocating to Database/BI pros that they embrace and cooperate with Excel/PowerPivot pros.

Awareness, Flexibility, and Sometimes…  Outright Resistance

It’s an interesting ambassadorship.  On one hand, Excel pros are often accustomed to doing everything on their own, with no external help whatsoever, and so it’s mostly a matter of opening their eyes to benefits they’ve never imagined. 

But the other camp often doesn’t expect to learn anything new and relevant about the role of Excel, that unruly little brother of “real” BI.  In conversation, that camp splits into two subgroups rather quickly – one that is willing to consider new ideas and possibilities, and another that regards Excel as the devil.  Interactions with that second group can get ugly.  I also tend to fear for them a bit.

Today, I’m going to focus on the Excel crowd and explain why a db pro can make a huge difference in their lives.  While I have danced around the topic for two years on the blog, this will be my attempt to provide a definitive list of the benefits.

And you die-hard Excel haters out there, don’t worry, I’m coming back around to you soon Winking smile

Benefit #1:  Data Shaping is Easier in Databases.  MUCH Easier.

Hey, Excel is just a collection of individual cells when you come right down to it.  Cells go into formulas, and cells come out.  But turning a wide and short table into a tall skinny table (or vice versa) for instance can consume the better part of an Excel pro’s day in some cases.  That same operation might take a db pro 5 minutes or less.  And even better, the next time might take them no time at all…

Benefit #2:  Auto-Refresh!

Once the db pro has a script in place (or query or view or sproc or whatever it is that they deem best), it can now be run automatically in response to your refresh request from PowerPivot. 

If you are running PowerPivot on your desktop, hey, now it’s just one click (refresh) to pull in the latest, properly-shaped data.  But even better, if you have access to a PowerPivot-enabled SharePoint server, you can put your workbook up there and schedule it to refresh itself!

Even if the manual shaping that you do today only takes you a few minutes each time, it’s still worth it to outsource it to a db.  The SharePoint option means you don’t have to do anything each day to merely update the reports, and the difference between “small” and “nothing” is huge.  Like, “you can go on vacation without repercussions” huge.  Or “you don’t have to come in early each day” huge.

Benefit #3:  Quality

Did you know there are entire conferences devoted to the topic of spreadsheet errors?  Spreadsheet errors are a fact of life in traditional spreadsheets, but they are primarily due to specific problems that a good PowerPivot “ecosystem” eliminates.  One is the lack of convenient named reference – “what did D$14 refer to again?” crosses the inner monologues of Excel pros worldwide millions of times a day.  PowerPivot fixes that – everything is referenced by table/column/measure name.

But raw repetition is the real killer.  If you perform the same spreadsheet task every day for a year, pure statistics tells us you will make mistakes.  And if the task is tedious, you will make even more.

The lack of “portable formulas” in traditional spreadsheets is an underappreciated source of repetition.  Even a single iteration of a reporting task explodes into repetitious subtasks and provides lots of opportunity for error.  (PowerPivot fixes that one too).

So we are left with raw repetition – performing the same task every day – as our primary source of error.  Once you have PowerPivot, data shaping is the biggest source of repetition.  Outsourcing that shaping logic into a database, then, doesn’t just save time.  It prevents mistakes. 

Why?  Because the db logic is written only once, and it doesn’t change no matter how many times you run it.  Even if there were mistakes made in the db logic, you will catch them sooner or later (usually immediately), and once you fix them, they stay fixed.

Come back Thursday for part two, with items four through seven.


Comparing Access to PowerPivot

November 17, 2011

 
I don't think the artist had data apps in mind, but this pic rocks!

Here’s a question that comes up with increasing frequency:  “PowerPivot seems kinda similar to Access in many ways, what’s the difference?”

Why Does the Question Come Up?

Some of you are thinking “yeah, I can see why people would ask that.”  And others of you are thinking “WHAT???  That questions makes ZERO sense, they are NOTHING alike!”

You are both right.

The biggest reason why the question comes up, I think, is the longstanding symbiosis between Access and Excel – Access as data source, Excel as analysis tool.  Remember, Excel used to be limited to about 64,000 rows of data.  And many Excel pros learned to import large data sets into Access rather than Excel, manipulate and prep the data in Access, and THEN import from Access into Excel for PivotTables, charting, etc.

With Excel expanding from 64k to 1M rows in 2007, that tradition has already begun to fade, to an extent.  But even for data sets that fit into Excel, there is still a good reason that drives Excel pros into Access:  VLOOKUP is slow.

VLOOKUP = Excel Acting Like a Database, and Driving Folks to Access

Even for large data sets, arithmetic calculations in Excel can be blindingly fast.  After all, Excel is designed for that.  But VLOOKUP, and its more advanced cousin INDEX/MATCH, is not arithmetic.  It’s a search – “go find me a value that looks like X, and when you find it, return value Y from the same row.”

Even when you’re dealing with row counts merely in the thousands, that can get slow in Excel.  Because “search and retrieve” is what databases are designed for.  And Excel is not a database.  When it comes to finding values, Excel isn’t terribly more efficient than Word.  (A risky thing for me to say, I expect to be corrected in three…  two…  )

But since many data sets inherently “arrive” as multiple separate tables, you can’t avoid trying to splice them together, and that means VLOOKUP, or using a real database product.  I know the SQL snobs will say that Access doesn’t qualify, but Access IS a real db.

An Understandable Question

With that in mind, it’s easy to see why longtime Excel pros see their first PowerPivot demo, and come away asking this question.  At a high level, this is what they see:

Access Versus PowerPivot

OK, so what’s the answer?

PowerPivot Does Things That Access Will Never Do

You had me at DAX MeasuresThe first time you write a “Sort By Slicers” or an “Iffer-Blanker” or  a Set of Greater/Less Than Slicers or a Custom Calendar Running Total or even just worked with ALL(), you know this isn’t Access.  Oh, and you are doing that in Excel pivots, not in a separate window.

There are other benefits of course, for sure, but DAX Measures are a gamechanger.  Let’s leave it at that for now.

And Yes, You Can Replace “Access as Data Source” With PowerPivot*

The two biggest reasons that drove Excel pros into Access in the past are in fact alleviated with PowerPivot.  No 64K row limit in PowerPivot.  No 1M row limit either.  I commonly demo a 300M PowerPivot row workbook on my laptop!  You can load a lot more data into PowerPivot than you can into Access.

And VLOOKUP isn’t something you even need anymore in PowerPivot.  Got multiple tables?  Fine!  Leave them as separate tables, link them via relationships, and you are done.  That’s not even just a convenience – leaving them as separate tables is actually even just better, for many reasons.

All of that “go find me a match in another table” stuff is taken care of by PowerPivot.  Lightning fast in fact.

But whoa there, I put an asterisk on that statement above.  For good reason.

PowerPivot Goes Better with Databases!

image

Database –> PowerPivot –> Excel = Happy Happy

Fact is, if you work in an organization that uses SQL Server or another industrial strength database product, you are better off connecting PowerPivot to that db.

Or more accurately, you will get even more out of PowerPivot if you have the cooperation of a database professional.

Why is that?  I can (and will) write many posts on that.  For now let’s keep it simple and just point out two reasons:  1) Databases are inherently a very good place to do data “shaping,” which is not something you can do at all in PowerPivot.   and 2) Databases are great places to perform complex row-wise and cross-row business calcs.  They centralize those calcs for re-use, often take the db pro 5 mins to do versus much longer for you, and result in faster and more compact workbooks than if you use calc columns.

I’m not saying you need a db pro to get amazing things out of PowerPivot.  But there’s another level even beyond amazing, and it opens up when you cooperate with a db pro.

Final Note:  Be Thankful PowerPivot Wasn’t Built By Office

I say this because it would have been questioned to death.  It’s hard to imagine, but as a product like PowerPivot is taking shape at Microsoft, no one is really sure how to describe it yet, or even what it’s going to turn out to truly be.  A hundred people in the Office org would have had the same question – are we cannibalizing the Access business, and there would have been as much time spent answering that as designing the actual product.

Now, in hindsight, no one in Office is worried about that.  Access always had a much bigger mission than carrying around data for Excel.  And Access’s current mission has evolved quite a bit from what it was even a few years ago.

But those inevitable nagging questions early on would have saddled PowerPivot with a number of “thou shalt not cross this line” concessions.  Concessions which ultimately were not needed, and that would have hurt the product.

Gives new meaning to the term “Office Politics.”


Six Observations from the 2011 PASS Keynote

November 10, 2011

The PASS Summit tends to be one of  Microsoft’s favorite venues for unveiling big news in the BI space.  As you may recall, the 2010 Summit revealed some amazing things for the PowerPivot world.

Yes, I know that the 2011 Summit was weeks ago, and I’m overdue on my observations.  And no, I did not attend in person this year.  But the keynote tends to be the vehicle for the big news, and it was available via streaming.  So I watched it later the same day.

It’s a couple hours long, vast stretches of it are dry wooden rhetoric, you can’t really fast forward it, and I don’t recommend watching the whole thing even though the highlights were worth it.  I’ll share those here to the best of my ability.

Point 1:  Denali Release Date “First Half of 2012”

OK, this means we will get the final production version of PowerPivot v2, the new Tabular BISM, and Crescent in first half of 2012.  I was kinda expecting them to say first quarter of 2012, so I was a little surprised.  I guess this means there is still time to get real feedback submitted Smile

Points 2-4:  Cloud and Big Data

A very distinctly “cutting edge” feel to this year’s keynote.  And honestly, there appears to be substance to it, not merely hype.  I would say that the SQL team is one of the most nimble orgs at Microsoft, and one of the most responsive to changing customer needs.

2) “The cloud world is a hybrid of your data center and the cloud”
      -
SQL VP Ted Kummert

image

This was a very deliberate and prominent statement.  It’s very interesting (and encouraging) that they said this – a sharp contrast to the MS reputation of “our offerings are the only things in the universe and are only designed to work with themselves.”  (BTW – that reputation, while deserved, derives from the academic mindset of MS employees rather than from arrogance, but at times that’s a fine line).

The meaning here is that we will be able to opt in “a la carte” rather than being forced to convert completely to Azure in order to make use of service X.  I like that a lot, because I expect some services to mature faster than others.

OK, maybe that’s not a big deal.  That’s just good business strategy and perhaps obvious.  But there’s a big difference between them stating this as a prominent theme (as they did) versus mentioning it as a detail, or merely bringing it up in Q&A (which is often the case).  They were NOT saying this last year.  So I call this a very positive development.

3) “Reporting Services Will Be Available in Azure Sometime Next Year”
      
(…and then nothing was said about Analysis Services)

I forget who said this – it was either Ted or Amir, or maybe both.

The real information for me here was what was NOT said.  They said nothing about Analysis Services (SSAS), and the omission simply cannot be an oversight.  It was too obvious, the void in the next sentence was tangible.

That means they either already know that it will be 2013, or they are trying for 2012 but aren’t sure enough yet to promise it.  Either way, we can safely assume we won’t see SSAS Azure until late 2012 at the earliest.

Since PowerPivot is built on Analysis Services, that also means we won’t see any PowerPivot in the cloud until late 2012 at the earliest.  Furthermore, Office 365 won’t support PowerPivot until late 2012, or probably 2013.  That’s not a fact, but it’s a very safe guess.

4) Hadoop Support in PowerPivot!

PowerPivot and Hadoop:  Sounds Like Chocolate and Peanut ButterDo you use Hadoop?  I don’t either, at least not yet, but a number of our clients at Pivotstream do.  So my ears definitely perked up when they said that we will soon have an ODBC driver that connects directly to Hadoop sources.  And as a bonus, our boy Denny Lee got some stage time giving the demo.

Seems like a natural fit – PowerPivot’s ability to crunch large volumes of data coming together with the world’s most popular system for collecting massive amounts of web data.  And again, a departure from the MS norm.  I would typically expect MS to hastily invent a Hadoop competitor and rush it to market, then take five years to make it a credible competitor.  Maybe that’s still a long term goal, but to embrace something with open source and Google roots like this so prominently is again a very novel and mature move that we should salute.

I’m actually getting a more in-depth demo and update today, so I hope to report back with more detail soon.

5) Introducing Data Explorer!

image

How often do we get something 100% brand new?  Data Explorer allows you to take basically any collection of data sources – like an Excel file on my desktop, a sales data set in SQL Azure, and a demographics data source on DataMarket – and mash them together into a single table.

Even better, it then allows me to publish the resulting data set, in Azure, so that others can consume it.

I have a LOT of questions about this new offering, but very little time to explore it.  I have asked a member of the Data Explorer product team if I can interview them on the blog.  If that doesn’t work out, maybe one of you out there would like to investigate it and submit a review to the blog.

Point 6:  Crescent is now named Power View

image

Just like PowerPivot was known as Gemini until late 2009, we knew Crescent would eventually get a real name.  And that real name is Power View.  Yes, the space is official.

Point 6a:  Live interactivity in PowerPoint (yes, the slides app) is going to be included in the Denali release after seeming like it was going to get cut.  Pretty cool.

Point 6b:  Purely my opinion, but Power View seems aimed at putting a more glamorous face on traditional BI scenarios – it’s a very “field list oriented” tool which in my experience means that only “data people” will take to it initially.

But I also DO believe that as Excel pros get more and more comfortable with publishing PowerPivot models to SharePoint, they will start opportunistically exploring what Power View can do for them, since Power View can be connected directly to a PowerPivot model and used as an alternative front end (or complement to) Excel Services.


What if spreadsheets were invented today?

November 1, 2011

 
Time And Punishment

Homer Creates a Perfect World… 
Except it Has no Donuts

Imagine a modern world without spreadsheets

Here’s a story I find myself telling a lot these days:  imagine a world in which all of today’s technology exists except spreadsheets.  In that world, we have all of the computing hardware, software, and networking of 2011, but for some reason, spreadsheets have just never been invented.

That would be a very interesting place, and very different from our world.  The evolution of the spreadsheet and the evolution of the PC are largely the same story in our world – they both spread in parallel, starting in the early 1980’s.  It took about 10 years for both to become common in the workplace, with each one driving adoption of the other.

Release the hounds (of Excel 2000)!

Now imagine that suddenly, Microsoft released Excel into that world.  (Or Lotus released 1-2-3).  And not version one of Excel, but something like Excel 2000 or later.

Here’s what I think would happen:

1) It would take time for spreadsheets to reach broad adoption.  People would need to hear about this new invention.  They would need to comprehend the value they offer.  They’d need to overcome their natural skepticism about the latest “next best thing.”  And they’d need to learn how to use them.

2) But it would NOT take as long as it did in the 1980’s.  Remember, the PC itself wasn’t widely adopted when spreadsheets were first invented, and that was a big impediment to their adoption.  But in our 2011 imaginary world, the PC is already everywhere – a world primed for more rapid adoption.

3) The early adopters would enjoy a tremendous advantage.  It would seem like magic to them.  Their competitive advantages would dwarf those enjoyed by the early adopters of the 1980’s.  The CPU and RAM of 2011 desktop hardware combined with the advanced feature set of even Excel 2000 would deliver a transformational capability.

OK, so what’s the point of this thought experiment?

PowerPivot’s Release in 2010 is Just as Impactful

The #1 reason why I’ve been telling that story above is this: I think PowerPivot’s impact on today’s world will eventually be judged to be as every bit as big as the invention of spreadsheets themselves.

Now, as Vincent Vega would say, that’s a bold statement.  But you have to consider the source here (me) – I’m not a Microsoft fanboy.  My employment at Microsoft over 13 years jaded me more than stoking my religion.  In fact, in the “ask the experts” session this weekend at SharePoint Saturday, I was clearly the most cynical panelist.  (Come see me in person to see what I’m talking about).

So when someone like me says something bold like that, I encourage you to pay attention.  I was NOT saying (or expecting) that degree of impact when I was at MS, and I was not saying it when I started this blog.  It’s really just been the past year – after many months of seeing it for myself.

The Magic Eyedropper:  How PowerPivot is Spreading

How about speed of adoption?  I think it’s going to be just like Excel 2000 landing on our imaginary world.  There’s another relevant thought experiment that I love, but I didn’t come up with this one.  Here it is, copy/pasted from another website:

Suppose I had a magic eye dropper and I placed a single drop of water in the middle of your left hand. The magic part is that this drop of water is going to double in size every minute.

At first nothing seems to be happening, but by the end of a minute, that tiny drop is now the size of two tiny drops.  After another minute, you now have a little pool of water that is slightly smaller in diameter than a dime sitting in your hand.  After six minutes, you have a blob of water that would fill a thimble.

Now suppose we take our magic eye dropper to Fenway Park, and, right at 12:00 p.m. in the afternoon, we place a magic drop way down there on the pitcher’s mound.

To make this really interesting, suppose that the park is watertight and that you are handcuffed to one of the very highest bleacher seats.

My question to you is, “How long do you have to escape from the handcuffs?” When would it be completely filled? In days? Weeks? Months? Years? How long would that take?  I’ll give you a few seconds to think about it.

The answer is, you have until 12:49 on that same day to figure out how you are going to get out of those handcuffs. In less than 50 minutes, our modest little drop of water has managed to completely fill Fenway Park.

Now let me ask you this – at what time of the day would Fenway Park still be 93% empty space, and how many of you would realize the severity of your predicament?

Any guesses? The answer is 12:45. If you were squirming in your bleacher seat waiting for help to arrive, by the time the field is covered with less than 5 feet of water, you would now have less than 4 minutes left to get free.

I’ve recently seen traffic to this blog jump to double its longstanding average.  I’ve seen the post frequency on LinkedIn quadruple.  Incoming requests for HostedPowerPivot have also quadrupled.  Every metric like that is telling a similar story.

Is it 12:45 yet?  Probably not.  But I’d say it’s around 12:30.


PowerPivot ROI Comparison: CIMA Part Three

October 6, 2011

 
PowerPivot ROI Comparison

CIMA Part Three:  PowerPivot ROI Comparison
CLICK IMAGE TO VIEW ARTICLE

It’s that time of the month again folks…  you know… for the next installment in my series for CIMA Insight! 

The overwhelming request from the CIMA crowd after they read Part One was to ask for proof of ROI.  These are accountants, after all, and it’s a fair question.

Some of Pivotstream’s customers would be the most “neutral” source for this kind of evidence, but it is difficult to convince folks to take time out of their day to explain to the world what a great competitive advantage they have discovered Smile 

So I think we are going to explore some additional joint case studies with Microsoft, including a more vivid writeup of the Duane Reade case study (Pivotstream and DuaneReade  jointly authored a 25-page whitepaper jammed with quotes, images, and a specific focus on PowerPivot, and the MS marketing machine distilled it to…  something I don’t even recognize).

So Part Two, and now Part Three, are still very much informed by my experiences with all of our clients, but is grounded specifically in a project I have implemented both the traditional way and the PowerPivot way, which is, of course, The Great Football Project.

CIMA readers, I’m very hungry for feedback on part three – particularly on the topic of “should I continue  with more ROI detail in part four, or should I start explaining the basics of how to quickly get started, from an Excel veterans’ point of view?”

Leave comments, send me email, whatever you are comfortable with.  I want to know what would be the next best step, the most useful material for you.


CIMA Part 2 – The Hidden Costs of Traditional BI

September 13, 2011

 
Finding an image for "dark matter" should have been more challenging

“Requirements transmission is the ‘dark matter’ of BI Projects.”

-Me, SQL Saturday Cleveland (in one of my wittier moments)

I’ve always loved the concept:  we know the universe is essentially a lot “heavier” than all the things we can see.  There’s a lot of mass out there that we just can’t see – so-called dark matter.

On paper, BI projects seem pretty simple.  What kind of data do you collect.  What are the kinds of questions you need to answer.  Simple, we draw a line from A to B and off we go.  But then the project runs for a very long time – where does all the time go?

I’ve mentioned this before – the time vanishes in communication, and it vanishes in “ok now that I have what I want, I realize I don’t want that.” 

But in my second post to CIMA Insight, I explain in a bit more depth where and how time and budget manage to disappear in traditional BI projects.

Of course, it’s no surprise that the NEXT part explains how that is greatly reduced with PowerPivot.  I originally planned to include that in the current installment, but those folks at CIMA are strict about that 750 word limit Smile

And yes, the next part ALSO explains how I think traditional BI pros are going to become even more important than they are today.  So if you read this one, traditional BI pros, and want to come rip my head off, please wait until next month Smile

image

From the article:  Diagramming some of the hidden costs

Click Here to Read the Article


Value Proposition of PowerPivot (in CIMA Insight)

August 3, 2011

 
A few days ago I mentioned I was writing a series of posts for CIMA Insight, which is the monthly web magazine of the Chartered Institute of Management Accountants – an audience that knows Excel quite well but probably has yet to discover PowerPivot.

Given that this series is starting from scratch, with an introductory post, it is mostly “old news” for readers here.  But there are perhaps some high level explanatory points that are new.  For instance, this diagram I sketched to explain the traditional tradeoffs between spreadsheets and formal BI: – a decision that results in impractically high costs sooner or later:

Spreadsheets vs Formal BI

PowerPivot, of course, provides a curve that shares the low startup costs of spreadsheets AND the long-term maintainability and robustness of formal BI.  Literally, PowerPivot is the end of that “damned if you do, damned if you don’t” situation.

To read the whole (brief) part one of the series, please click here.

As always, I’m interested in your comments.