The year I discovered Sagmeister

Icon

Respect the Craft

Mind the Product event videos – not super recent but if you have great speakers who know their craft – much to takeaway: influencing processes, potentially implementation or just seeing how other teams do their thing.

Absolutely love Michelle You‘s presentation. Really open, honest and goes into great detail that allows a level of practical learning from her/Songkick product management process. (SK also have a blog – nice post on designing with data).

Some notes:

  • Modes: Optimising an existing product that’s live. Big bang product features or launches – shouldn’t happen that often. Brand new MVP discovery – you don’t know who your customer is and you don’t have a live product.
  • prioritisation and design-making get easier when goals are well defined. Most of the hard work….comes from breaking down a big..goal into smaller achievable sub-goals.
  • KPI can be broken down into themes or levers that influence that metric
  • Check the acquisition, activation, retention slide…
  • ‘Lean Analytics – Use data to build better start-up faster’: What makes up a good metric: Comparative – to be able to use the same metric for two sets of users, before and after or a/b test. Understandable – having it clear so it can be embedded in the team and easily referred to. Ratio/rate – so rather than total numbers of users, it is conversation rates or ratios – so that you can tell the difference between two things. Actionable – increase monthly users is not an actionable metric, it has got to be something that will change every day and will be sensitive to whatever you are shipping.
  • Example of this: Looking at your weight as a kpi – you want to lose 20lbs in 6 months as a long term kpi. But everyday you will be looking at how many miles you walked, how many calories you consumed – so things that you can control in the short-term that will impact into the longer term metric.
  • Process: take 5-10 themes for the main kpi. Discovery backlog – Experiment – Learning – Validated feature. Create the discovery backlog – idea generation – gamestorming format – use post-it notes (individually) then group them into categories or ideas. Work out the groups into an impact vs effort matrix – collaborative exercise (how much impact will it have vs expected effort involved)
  • Turn into an hypothesis – ‘if…then…because’ – ‘if we show you recommended concerts then you will more likely to buy a ticket because you will see more relevant events based on your tastes’ – So what we showed you before we showed everything in London if we personalise that list based on music you like then you will be probably be more likely to buy tickets.
  • Experimentation process: finding out if this what we should be building – so things like surveys, mock-up and click test, landing page tests, remote usability testing, user research. This will answer assumptions, prototypes, highest level of confidence that it will move the metric.
  • Use of split backlogs – validated features (70%), bugs, tech tasks/support (30%)
  • Meet once a week to prioritise for the next 2 weeks, tasks/stories from each board are selected to get moved into a main development board
  • Main dev board – Backlog: 2 weeks worth of user stories (always have some jfdi tasks). Next up: top 5 prioritised stories. In progress. Awaiting judgement – tests or features that need analysis on how it’s performed. Done.
  • Team dashboards – Review daily metrics dashboard every morning at stand-up. Weekly kpi email to the team tracking progress towards quarterly goals. Feature recap where we review the impact of individual features launched.

 

Filed under: Podcast / Seminars, UX design, , , ,

Pages

Archives