Using OKRs (Objectives and Key Results) to focus on customer problems

I came across the post Using OKRs to focus on customer problems by Viktoras Jucikas. It is highly interesting and certainly practical, but to my mind it has a close similarity to Impact Mapping and even Management by Objectives. Still, however you may call it, it is a critical tool for product managers.

Roadmap Timeframes

Which timeframe should your roadmap have? The post The 666 Roadmap suggest having three different roadmap timeframes: 6 weeks, 6 months and 6 years. Others might call the 6-year roadmap a vision, but why not see the vision as a very high-level roadmap? 6 months is your current plan, the next features, releases, etc. 6 weeks are your current user stories and sprints that you actually work on and have a very deep understanding of.

User Personas: More thoughts

Every once in a while, I think about the best way to write user personas. The UX Lady wrote a nice post about how to write such personas and provides a template to do so, but my daily experience tells me that the usual templates contain way too much information. If you collect so much information about your users, that’s a great way to learn about them and segment them, but in order to use them in user stories, they contain more information than necessary. I usually constrain my user personas to the following:

  • Name
  • Picture
  • Quote
  • Short background description
  • Technical experience
  • Frustrations
  • Motivations
  • Ideal world

This is sufficient to effectively work with them.

Multi-screen insights from Google and Microsoft

The UX Lady summarized the insights from Google and Microsoft regarding multi-screen use. The companies made some findings that could have been found by applying common sense, but some ideas are pretty interesting. It is worth a read if you plan to offer your service on several platforms (and who doesn’t, after all?).