Recommended
More Related Content
Similar to 2014 MicroStrategy at Netflix (MicroStrategy User Group)
Similar to 2014 MicroStrategy at Netflix (MicroStrategy User Group) (20)
More from Albert Wong
More from Albert Wong (7)
Recently uploaded
Recently uploaded (20)
2014 MicroStrategy at Netflix (MicroStrategy User Group)
- 1. MicroStrategy at Netflix MicroStrategy SF Bay Area User Group Los Gatos 2/19/2014
- 2. Reporting Platform Reporting Platform Manager http://linkedin.com/in/albertcwong albertcwong Sting Albert Wong
- 9. Tell vs Ask
- 10. “It may well be the most important document ever to come out of the Valley.” - Facebook COO Sheryl Sandberg
- 12. Photo References • Open door: http://depositphotos.com/8198593/stock-photo-Open-white-door-to-meadows.html?sst=100&sqc=0&sqm=20529&sq=2uc2st • Control key: http://depositphotos.com/37981071/stock-photo-Control-key-on-Keyboard.html?sst=&sqc=2&sqm=4639&sq=2ublpd • Speedometer: http://depositphotos.com/5801166/stock-photo-Speed.html?sst=&sqc=9&sqm=192933&sq=2ua6wr • Garbage truck: http://depositphotos.com/31100689/stock-photo-Garbage-truck-isolated.html?sst&sqc=41&sqm=752&sq=2ubrnx • Culture deck: http://jobs.netflix.com/
Editor's Notes
- Welcome Delighted to be hosting Get a sense of MSTR at NFLX Hope u walk away with something useful 5 speakers instead of 4
- MSTR – main reporting tool emailing out reports, embedded or attachments Justin will go through one of our most widely viewed emailed reports We also use it for guided analysis – e.g. curate, throw into mem, put a visual discovery layer on top and allow for users to explore, find insightful information laura will go over an example of that Spy on each other Tableau – complements mstr, easy access to data with less steps Excel on steroids Sting – web tool, less complex than either specialized in accessing cloud data Talk about why we need all 3 Lead in to how we use tools – focus on mstr
- We have this concept of being an open and enabling platform meaning Easy to access Should empower / enable users To get here, remove barriers
- Open access to everyone Remove ticket submission process – slow down No matter how quick we were, things slip through cracks Today – account created behind the scenes
- Another thing Remove restrictions Concept of tiers All web users have the full set of permissions (olap, documents, ds) Our devs in addition also architect Here users have great control
- One more thing We keep a quick dev -> production cycle In theory, gating this process, putting in lots of checks will reduce mistakes Get good developers to dev, less mistakes We can focus on getting really efficient at pushing out code Remove qa By reducing steps, we are able to do production pushes in minutes, sometimes less Today regularly pushing up to 100s/day
- Sounds like a fun environment to work in But not all is rosy Consequences of having this concept of such an open platform, but issues can be managed for the most part with proper planning and communication
- Main problem – things get messy Do expect things to get messy fast in an open environment when things are moving quick and users have a lot of control to do stuff Essential to stay on top of cleanup Anything and everything from unused accounts, reports, schema objects, Managed objects, old column aliases will accumulate and slow down your system Get aggressive and be relentless when it comes to getting rid of objects That aren’t needed
- Tip during routine cleanup People more likely to pay attention