"How to structure your input so it becomes a manageable scope?" - workshop by Artur Hebda

Artur Hebda ran a workshop on managing inputs when creating products during the Product Development Days in Krakow, Poland.

Transcript

1. How to structure your input so it becomes a manageable scope? Artur Hebda Railsware Labs
2. We build client and own products.
3. We build client and own products. Consultancy
4. We build client and own products. Consultancy Labs
5. We build client and own products. Consultancy Labs
6. We don’t do what client wants. We do what client needs.
7. Lead Engineer => Product Manager
8. Source: YouTube
9. Let’s get to know each other. Name? Role? Hope?
10. Agenda - Product structure discovery - Intro + Group work + Discussion of results - Structure-based input grooming - Intro + Group work + Discussion of results - Key takeaways - BONUS : How to go from pen and paper into digital toolkit? - Case study : JIRA
11. Where do you keep ideas/suggestions?
12. How many open tickets do you have in backlog?
13. Source: Ashim D’Silva Unsplash
15. Product structure discovery
16. Image: http://www.orlandospencer.com Product is a never consistent set of features
17. Split product into feature components Contextual, not functional Tree-like structure - divide & conquer
19. Source: Google Maps in Google Play
20. Source: Google Maps in Google Play
21. Contextual components - Map - Layers - Satellite - Terrain - 3D - Zoom - Road state - Area classification - Street View - Places - Points of Interest - Practical Information - Reviews - Areas of Interest - Your Places - Lists - Home - Work - Search - Directions - Traffic - Transit - Flights - Arrive on time - Navigation - ...
22. Functional labels - Design - Engineering - Architecture - Maintenance - Performance - Tech Debt - Back-end - Front-end - Marketing - Sales - Support - ...
23. Product is more... - Product Marketing - Market Research - Analytics - Customer Development - Experiments - ... - Product Development - Feature components... - Functional labels… - ...
24. Company is more... - Google Maps - Product Marketing - Product Development - ... - Google Translate - ...
25. Benefits of the structure - Improves communication - Common vocabulary - Reference points - Embraces deep focus & simplifies management - Context segregation - Responsibility split - Grows with us & supports step-by-step improvements - Restructuring is easy
26. Ex#1 Product structure discovery Context : Uber rides Time : 10 minutes Google Maps example ->> - Map - Layers - Zoom - Road state - Area classification - Street View - Places - Points of Interest - Areas of Interest - Your Places - Search - Directions - Traffic - Transit - Flights - Arrive on time - Navigation
27. Source: Uber in Google Play
28. Discussion of results
29. Structure-based input grooming
30. Working with inputs is hard...
31. https://goo.gl/Agc71c
32. Customer Feedback Public Private INPUT as a single source of truth
33. Customer Feedback Product Team Stakeholders INPUT as a single source of truth
34. The only effective solution we have found is to gather them in one place.
35. https://goo.gl/uKiGaV
36. That’s why you need structure.
38. Customer Feedback Product Team Stakeholders INPUT as a single source of truth
39. Customer Feedback Product Team Stakeholders INPUT as a single source of truth Context #1 Context #2 Context #3
40. Input types - Single context - Example : tech debt ticket - Example : bug report from user - => can be groomed right away - Multiple contexts - Example : bulk feedback - => has to be split first - Format and scope of information - #issue - #issue + #idea(s) - #dk (domain knowledge) - plain text
41. Three steps of grooming - Assign all inputs to a single most specific context - Split multi-context inputs into many single-context inputs - Optionally add functional label - Go through contexts to deduplicate inputs - Go through contexts to merge inputs into epics - NOTE: epics might span across contexts, but it’s not advised - Epics describe problem space and potential ideas - NOTE: structure might have to be changed, that’s OK!
42. Benefits of inputs - Single source of information - Simplifies prioritization - Streamlines content discovery
43. Benefits of inputs - Single source of information - Simplifies prioritization - Streamlines content discovery - Everyone can contribute and be heard - People have great ideas - Feeling of ownership - Tech debt becomes transparent
44. Benefits of inputs - Single source of information - Simplifies prioritization - Streamlines content discovery - Everyone can contribute and be heard - People have great ideas - Feeling of ownership - Tech debt becomes transparent - External memory for your brain - Capture thought, write it down as input, done - Get back to it when the right time comes
45. Ex#2 Structure-based input grooming Context : Uber rides Time : 30 minutes Three steps to grooming ->> - Assign all inputs to a single most specific context - Split multi-context inputs into many single-context inputs - Optionally add functional label - Go through contexts to deduplicate inputs - Go through contexts to merge inputs into epics - NOTE: epics might span across contexts, but it’s not advised - Epics describe problem space and potential ideas - NOTE: structure might have to be changed, that’s OK! - - P.S. If something bothers you about Uber, you can write and groom your own inputs :)
46. Discussion of results
47. Key takeaways - Structure - Improves communication - Embraces deep focus & simplifies management - Grows with us & supports step-by-step improvements - Input - Single source of information - Everyone can contribute and be heard - External memory for your brain - Grooming inputs - Assign input to the most specific context - Deduplicate inputs - Merge inputs into epics on per context basis
48. BONUS : How to go from pen and paper into digital toolkit? Case study : JIRA
49. 2 projects JIRA projects across entire Railsware : Input and Roadmap
50. 3 years Time we spent using and improving Input as an approach
51. 4500+ Created inputs
52. 825 Contexts
53. Input flow
60. Organisation Map
61. Context from OrgMap => component and quick filter in JIRA
63. Input Grooming GSheet App JIRA project OrgMap structure GSheet App Issues via Blockspring Tree of contexts via CSV Import Changed/new issues via CSV File Import
65. Thank you! Questions? Feedback: arturhebda.com
66. Thank you! Questions? Feedback: arturhebda.com
67. Thank you! Questions? Feedback: arturhebda.com