• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Lean Operations
 

Lean Operations

on

  • 535 views

A Practical Guide to Delivering like a Startup in a Complex Environment

A Practical Guide to Delivering like a Startup in a Complex Environment

Statistics

Views

Total Views
535
Views on SlideShare
526
Embed Views
9

Actions

Likes
0
Downloads
5
Comments
0

1 Embed 9

https://twitter.com 9

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Lean Operations Lean Operations Presentation Transcript

    • Lean Operations: A Practical Guide to Delivering like a Startup in a Complex Environment Rob Keefer @rbkeefer Paul Spencer @spencepd
    • Big Idea Always know how the parts relate to the whole but don’t build the whole. Build HIGH Business Value components first, so you can live to fight another day. www.pomiet.com @pomiet @rbkeefer @spencepd
    • Getting to MVP MVP (Minimum Viable Product) Build something to get in front of customers for their feedback. www.pomiet.com @pomiet @rbkeefer @spencepd
    • Getting to MVP Define minimal application (across architecture) Maximize validated learnings Incremental business value Warnings: Not necessarily optimized for end users Business may want everything www.pomiet.com @pomiet @rbkeefer @spencepd
    • Getting to MVP Deciding exactly how complex an MVP needs to be cannot be done formulaically. It requires judgement ...When in doubt, simplify. - Eric Ries, Lean Startup www.pomiet.com @pomiet @rbkeefer @spencepd
    • Getting to MVP 1. Create goal statements 2. Prioritize goal statements 3. Map system dependencies 4. Develop architecture map www.pomiet.com @pomiet @rbkeefer @spencepd
    • Create goal statements I wish I knew ... We need to do ... www.pomiet.com @pomiet @rbkeefer @spencepd
    • Create goal statements View Claims Information View Health Information Validate/Edit Personal Information Compare Cost of Care Information Get Wellness Support Register to use the site www.pomiet.com @pomiet Compare Prescription Information Purchase Health Insurance @rbkeefer @spencepd
    • Prioritize goal statements www.pomiet.com @pomiet @rbkeefer @spencepd
    • Prioritize goal statements Compare Cost of Care Information Purchase Health Insurance Compare Prescription Information Register to use the site Get Wellness Support View Health Information View Claims Information Validate/Edit Personal Information www.pomiet.com @pomiet @rbkeefer @spencepd
    • Map system dependencies Validate/Edit Personal Information View Claims Information View Health Information Customer Info Customer Info Customer Medical Info Warehouse Payment ! X X X ! X Customer Medical Info ! Warehouse ! Payment Authorization www.pomiet.com @pomiet Authorization X X X X ! @rbkeefer @spencepd
    • Develop architecture map Validate/Edit Personal Information View Claims Information User Interface Business Layer Customer Info Customer Medical Info Warehouse Services Payment Authorization Critical View Health Information Architecture Layer www.pomiet.com @pomiet @rbkeefer @spencepd
    • Minimum Viable Product Statement We believe that creating < ... > for < ... > will achieve < ... > We will know it is true when < ... > www.pomiet.com @pomiet @rbkeefer @spencepd
    • Develop architecture map Validate/Edit Personal Information View Claims Information User Interface Business Layer Customer Info Customer Medical Info Warehouse Services Payment Authorization Critical View Health Information MVP Release 1 Release 2 Architecture Layer www.pomiet.com @pomiet @rbkeefer @spencepd
    • Minimum Viable Product Statement We believe that presenting claims information to customers will reduce customer service call volume. We will know it is true when call volume is reduced by 1%. www.pomiet.com @pomiet @rbkeefer @spencepd
    • Big Idea Always know how the parts relate to the whole but don’t build the whole. Build HIGH Business Value components first, so you can live to fight another day. www.pomiet.com @pomiet @rbkeefer @spencepd
    • Continue the Conversation Rob Keefer, PhD Rob.Keefer@pomiet.com Paul.Spencer@pomiet.com @rbkeefer www.pomiet.com @pomiet Paul Spencer @spencepd @rbkeefer @spencepd