Nalpeiron analytics introduction webinar
Two part series explaining the benefits and pitfalls of Software Analytics. Join Jon Gillespie-Brown, CEO of Nalpeiron and an Angel Investor, as he presents the latest insights on this topic. You will learn more about:
- How to fully understand your product lifecycle from download/signup all the way to end of life
- How customers discover and use product features to drive improved adoption
- How features operate in complex, real-world configurations to reduce support headaches
- The biggest take-aways from two essential books on the topic: Lean Analytics & Consumption Economics
Great user understanding through analytics leads to better software, happier users, higher adoption, and more revenue.
Published on: Mar 3, 2016
Transcripts - Nalpeiron analytics introduction webinar
Turn Data into Useful Insight
The Software Analytics Playbook (Part 1)
About your Host
• Jon Gillespie-Brown
• Angel Investor – focus SaaS Software/Internet
• Author of “So you want to be an Entrepreneur” (wiley)
• Stanford and UC Berkeley lecturer
• CEO, Nalpeiron
– 20 years in software licensing/analytics
– Analytics solutions for desktop/enterprise
• Ask questions as we go along within the system
• Give us your feedback as we go along
• 10 minutes Q&A at the end
• Watch this on demand after the end anytime
• This webinar is 30 minutes long
Contents of this Webinar
• Why use Software Analytics?
• Today’s leaders in Software use
• Build it and they will come…(not)
• Challenges for most Software
• Trying to get user insights the old way
• Nalpeiron (example data sources)
• Complex and fragmented data
• What is Software Analytics?
• What are the Analytics choices?
• Which organizations needs Software
• How does Software Analytics help?
• Why use Analytics in your
• Avoiding feature bloat with Analytics
• How it works – Desktop Software
• Data collection and the Law
• A final word…Just do it!
• Get a Free Book
• Q & A
Management Guru and Author Peter Drucker famously observed
“If you can’t measure it,
you can’t manage it”
Why use Software Analytics?
Organizations that apply analytics to their business
outperform their peers:
*Source: “Outperforming in a data-rich, hyper-connected world,” IBM Center for Applied Insights study conducted in cooperation
with the Economist Intelligence Unit and the IBM Institute of Business Value.
2.5X stock price
Today’s leaders in Software use Analytics
Today’s leader doesn’t have all the answers.
Instead, today’s leader knows what questions to ask.
Build it and they will come…(not)
Go lean: Use Analytics for “validated learning”
Challenges for most Software Developers
Decisions are based on “gut feelings” => risky strategy
Trying to get user insights the old way
Getting “real” and useful data is time consuming and hard
Lots of data, in many systems, in many formats
Nalpeiron as example
Complex and fragmented data
What is Software Analytics?
Error reporting User ecosystem
What are the Analytics choices?
Simpler Web Apps
e.g. Google Analytics, Kissmetrics
e.g. Flurry, Keen
e.g. Nalpeiron, Redgate
e.g. Nalpeiron, Trackerbird
Types and providers
Which organizations needs Software Analytics?
Internal teams developing
Software for non-
• Reducing waste, improving user
satisfaction and software quality
Teams at Open Source
Developers & Embedded
• Different business model,
software quality and legal
• Accountability, optimum
development processes, better
Teams at Independent
Software Vendors (ISVs)
• Commercial success,
engineering focus and risk
How does Software Analytics help?
• Lower Support
Why use Analytics in your development cycle?
• Fully understand your product lifecycle
• Learn how customers discover and use
• Understand how features operate in
complex, real-world configurations
• Learn about error conditions to improve
customer satisfaction and software quality
• Understand how well marketing
promotions are working to focus resources
• And so much more…
Copyright: Ben Yoskovitz
Avoiding feature bloat with Analytics
1. Why Will It Make Things Better?
2. Can You Measure the Effect of the Feature?
3. How Long Will the Feature Take to Build?
4. Will the Feature Overcomplicate Things?
5. How Much Risk Is There in This New Feature?
6. How Innovative Is the New Feature?
7. What Do Users Say They Want?
“Save millions in development costs as you stop the feature overshoot”
How it works – Desktop Software
Retro-fit Collect Insight
Data collection and the Law
• Be aware if you collect any
data you will be subject to
• Be sensitive and transparent
• Managing the data you
collect from “people” is
Copyright: MicrosoftAsk Nalpeiron for their extensive whitepaper on the topic
A final word…Just do it!
• Most developers operate in the “dark”
– It’s fast and easy to avoid these risks
• It requires planning and forethought to get value
• It’s all about asking “questions” and testing, not data
• Modern organizations use Analytics to avoid “waste”
• Todays leaders need a “data-informed” mindset to succeed
• Choosing the right partner/fit will save a lot of time
The first step is to give it a try, its low risk and high reward…
Get a Free Book…with a Trial
Learn more at: www.nalpeiron.com
Sneak peak of the next Webinar: Advanced Analytics
• More details on metrics and dashboards
• Working through the challenges of using Analytics
• Using KPIs and the lean Analytics cycle
• Analytics for Product Manager and the Engineering team
• More about data collection and the law
• More specific use cases for desktop/enterprise Software
Q & A
• Lean Analytics: Use Data to Build a Better Startup Faster by
Croll, Alistair; Yoskovitz, Benjamin
• Consumption Economics: The New Rules of Tech by J. B. Wood,
Todd Hewlin, Thomas Lah
• Web Analytics 2.0 by Avinash Kaushik
• Segment.io analytics academy
• Seth Godin