Last Build Date: Fri, 23 Sep 2016 18:59:44 +0000
Fri, 23 Sep 2016 18:59:44 +0000[…] Bloggers: Are You Ready For Writer’s Block? […]
Sun, 18 Sep 2016 04:05:14 +0000[…] This article was originally published on InstigatorBlog. […]
Sat, 17 Sep 2016 07:05:09 +0000[…] This article was originally published on InstigatorBlog. […]
Mon, 12 Sep 2016 23:19:00 +0000Not at all. Totally understood what you were saying. It's hard to go from theory and "best practices" to implementation. That's where all the magic happens... :)
Mon, 12 Sep 2016 17:27:00 +0000Completely agree. I hope you didn't take my comment to mean that this isn't valuable information. The concepts are critical for effective product designers. I just wanted to point out that there seems to be a disconnect for many designers (and PMs) when it comes to implementation. Much in the same way teams get stuck with lean customer development.
Mon, 12 Sep 2016 16:55:00 +0000Thanks for the comment, Nickolaus. I agree that there's a difference between conceptual and delivery -- things in theory aren't always as effective in practice. This blog post didn't go into the experiment aspect of things extensively and how that should be done. There are some good frameworks out there as you point out. Implementing them is always a challenge...
Mon, 12 Sep 2016 16:00:00 +0000Great thoughts here, Ben. I'm a product guy with a background in UX design so I've seen both sides of the fence in practice. Conceptually, this all makes sense but I've seen things break down in the real world. I've struggled with finding a way to integrate the PM and designer work streams in a way that allows each role to contribute their best thinking without stepping on toes. It's not a territorial thing or a collaborative bottleneck, it's a tactical issue. I've found it quite difficult to develop a rhythm that allows both PM and designer the freedom to own their respective contributions while staying in sync and tracking toward common objectives. Sometimes, it's an issue of trust which is an entirely separate problem to solve. However, I think it's mostly a symptom of not having clear frameworks for defining assumptions, experiments and success. Most good PM/design teams I see are in tune with the collaborative approach to discovery and delivery. Many of those same teams are less clear about how to implement a reliable system that works. That is, a clear framework for experimentation that leads to trackable outcomes. I don't have an answer but I have had the most success (as a designer and PM) with a simple approach that clearly outlines the work in a way that the team can breakdown, visualize and manage. Tristan Kromer's experiment template (https://grasshopperherder.com/templates-suck-heres-our-lean-startup-template/) has been a useful way to document our assumptions and clarify the work ownership in a lightweight way that's still connected to success. Tristan Kromer (https://grasshopperherder.com/) and Teresa Torres (http://www.producttalk.org/) both have some great ideas on this topic.
Thu, 08 Sep 2016 18:48:55 +0000[…] For the comparison reasons, it’s also good to take some notes during the interviews. We also advise that you read Ben Yoskovitz’s case study for designing a successful interview process. […]
Thu, 08 Sep 2016 15:03:00 +0000this is really good news for lots of people,,, thanks a lot for this Billige Løbesko Mizuno http://www.skosportdk.com/mizuno-c-5.html
Mon, 05 Sep 2016 09:42:00 +0000Great one !