We could not find the article specified.

We're sorry, but this resource is no longer available.

You may also be interested in:

Innovation: Five Signs You Might Be Faking It

Every company wants to be a leader in innovation, but how can you tell if your company is really innovating or just going through the motions? See the 5 signs you might be faking innovation and what to do if you are.

Assessing the Five Styles of Enterprise Business Intelligence

The world of BI and analytics has evolved. Discover the five styles of reporting and analysis, and learn the pros and cons of each in an enterprise scenario.

11 Proven Ways to Turn Your Culture into a Culture of Innovation

Learn the 11 proven strategies that you can implement quickly to get every employee innovating and contributing to the growth of your company.

Spigit's 2018 State of Crowdsourced Innovation Report

A rigorous analysis of how the world’s largest brands – representing 21 different industry verticals – leverage their innovation programs to solve problems and surface opportunities, and the key role crowdsourcing plays in their success.

Data From 3.5 Million Employees Shows How Innovation Really Works

Analysis of how 3.5 million employees using Spigit ideate proves innovation is a science, and can be measured.

How to Improve Customer Experience in an Era of Choice

Customer experience is quickly becoming the de facto differentiator between successful businesses and the ones that fail. Download this ebook to learn how some of the largest companies in the world are driving better customer experiences.

Selling Data and Decisions to your Team

Gathering support for a product feature or enhancement is a critical skill for Product Managers. Talking to customers, working with key stakeholders in the business and convincing development that a feature is necessary can be a daunting task. Join Product Management expert Cait Porte as she covers how to sell your ideas internally by leveraging data to drive decision making.

Agile Metrics for Team and Product Progress

You’ve seen team metrics like velocity. Velocity is not an accurate measure of a team's progress towards "done." So what should you use instead? Join Johanna as she discusses the measures that are actually useful in understanding what your team does, where the work is, and how long the work really takes - and in addition, we’ll examine what it takes to explain the team’s progress to others in terms of the product backlog burnup chart, ways to talk about what’s done and not yet released, and how to show others working product.

Connecting Analytics to Strategy - Keeping Your Corporate Objective In Sight

Data analytics has transformed the way many product managers approach product enhancements, creating strong demand for product managers with skills and expertise in defining and analyzing product metrics to make more valuable product decisions. But there is one essential element that is often left out of the conversation, and that is strategy. How does my product decisions support the overall strategy of the business, and am I tracking the right metrics based upon that strategy?

Mixing Qualitative & Quantitative Data with Storyboarding

Qualitative vs. Quantitative is a silly argument. Qualitative data from UXers should not compete against the quantitative data product owners need for their business model. Both are necessary to have a complete understanding of where the desirability of the product meets the viability of the business.

Creating the "Right" Product Roadmap With Data

Data can be qualitative or quantitative, and comes from multiple sources: customer interviews, product usage & funnel analytics, company financial performance, and internal stakeholders. How do you use that data to create a product roadmap that is aligned with your organization’s business needs?

Living With Technical Debt: Balancing Quality and Perfection

As a Product Manager, you probably have to deal with technical debt. Regularly. Whether you like it or not - because it can’t be avoided. Unexpected details pop up, as small as UX that needs clean-up, and as big as a previously unforeseen flaw in the infrastructure of a project. We have to accept that nobody gets away without some technical debt. And of course, the longer you take to deal with your technical debt, the more difficult it becomes to address fully. Feeling frustrated? Fortunately, we can take a step back, gain clarity, and see how the decisions we make impact our technical debt. Then, we can make decisions about how we want to balance technical debt with other priorities. Are we willing to live with some level of technical debt in order to ship product and meet deadlines? Can we mitigate technical debt to get to an MVP faster?