This is How Your Product Dies (and how to save it)

schedule May 29th 03:30 - 04:30 PM place Centennial A people 63 Interested

Product development is very much dominated by the idea of thinking forward. What are we doing next? What does next year's product roadmap look like? How many features are we launching in Q4? All good, valid questions for any software company.

However, this idea of always looking towards the "next thing" leaves little time for reflection during the product planning and development process and can often lead to products failing to reach their full potential.

By design, the 3 Panel Feature Evaluation is a super simple framework designed to help provide teams the ability to look at the feature area in question in three ways: before improvement, during improvement and post improvement. This 3 panel flow is designed to make sure that the user remains front and center during the planning and development process with an eye towards the pre and post experience that so often gets lost during development.

 
4 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

Learning Outcomes:

  1. The idea behind piecemeal refreshes
    1. This section will discuss in detail using real world examples, companies that failed to revise small product details and how that decision eventually caused their product to fail. We will look at examples both inside the tech industry and outside in order to provide a wide range of examples.
    2. After the real world examples of failure we will spend time answering the question: “why does a piecemeal refresh matter?”
      1. Examples of real world successful implementations of piecemeal refreshes will be used to back up the reasoning including those from my current company, Mavenlink, as well as my former startup, GoDesignerGo, and other outside organizations .
  2. How to implement a piecemeal refresh with your agile team
    1. Discussion will revolve around how to implement such a (potentially) disruptive set of changes without disrupting the agile workflow of your team.
    2. Examples of actionable best practices for how to implement these changes across a wide-ranging feature area will successfully prepare teams, team leaders and product stakeholders to work on multiple fluid areas of the product during one standard agile development cycle.
  3. How to review your success (or failure!)
    1. The final section of this presentation will go into detail on how to measure the success or failure of your piecemeal refresh and your team’s effort by using a super simple 3 step framework - the 3 Panel Product Flow
      1. We will go into detail about how the 3 Panel Product Flow is used to determine the qualitative and quantitative success of your piecemeal refresh by looking at three key areas.
        1. First panel: The product or feature area before the refresh. We will look at some common metrics you can look at here to get a workable baseline measure of where your product stands.
        2. Second panel: The product or feature area during the refresh. In other words, the changes you are making. We will look at the best ways to dictate which features to include in the refresh and how to prepare those features for successful metric measurement in the third and final panel.
        3. Third panel: The product or feature area after you have completed the refresh. This is where you will look back at the previous two panels to see your journey and make metric measurements towards the success or failure of your refresh. This where the main lessons are to be learned regarding incremental changes that need to be made to future refreshes and so forth.
  4. We will wrap up the talk with an overview of what we learned as well as some actionable questions to ask yourself and your team to see if a piecemeal product refresh will be the right fit you and your product. This talk is designed to provide you a new perspective on how to create product success in a growing company, not to force you into a new way of conducting development.

Learning Outcome

For attendees to come away with a new idea of how pre product development can affect the downstream pipeline and eventual feature success.

Target Audience

PMs, ICs, CSMs, Devs, Leadership

Prerequisites for Attendees

A desire to learn and a basic understanding of the Agile software development process.

schedule Submitted 6 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Dhaval Panchal
    keyboard_arrow_down

    Dhaval Panchal - Systems thinking for transformative change

    60 Mins
    Talk
    Executive

    Culture of an organization often gets blamed for lack of transformation success. This session takes a systems view to organization transformation. In organization systems, points of leverage are powerful because a small shift in one thing can produce big changes in everything. Consequently the higher the leverage point the more the system will resist changing it. Direct attempts at changing organizational culture do not work, they lead to many haphazard attempts at behavior change but do not result in lasting transformation within organization. Many leaders attempt to shift organizational behavior and neglect underlying structures that give rise to dysfunctional behavior. We compare and contrast different systems leverage points, to draw distinction between leaders actions and more importantly mindset towards organizational transformation. Introduction to various systems thinking models with colorful examples from real world coaching situations will help you to think through your transformation challenges and learn why culture change is free, when you replace willpower with knowledge.

  • Liked Andrew Elliott
    keyboard_arrow_down

    Andrew Elliott - Creating Product Success: Piece by Tiny Little Piece

    Andrew Elliott
    Andrew Elliott
    Mavenlink
    schedule 6 months ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    It is all too easy as a product manager to fall into the trap of new, new, new. New is fun. New is shiny. New is sexy. But as much as it pains us, new may not always be the best way to make move your product forward.

    In fact, small, incremental changes can have just as big of an impact on customer success and growth as shiny new features.

    In this talk I will present real life examples from my personal experience as a product manager and successful startup founder showcasing how piecemeal iteration refreshes can boost customer success metrics and increase overall growth within your product - whether you sell to enterprise or mom & pop shops.

  • Liked Andrew Elliott
    keyboard_arrow_down

    Andrew Elliott - Cultivating Product Success Within your Agile Product Development Team

    Andrew Elliott
    Andrew Elliott
    Mavenlink
    schedule 6 months ago
    Sold Out!
    60 Mins
    Talk
    Beginner

    In this talk we discuss three key areas required to cultivate a successful agile product development team: team development, communication and team responsibility. We will look at specific examples of how these three key areas are key to creating killer products, developing strong teamwork and enabling positive, forward-thinking workflows. Attendees will learn via real world examples and come away with new ideas and tactics they can implement with their teams. This talk will discuss team development in a way designed to provide value to Agile veterans and initiates alike.