Searching...
13 results for “product development”
...of product development. And I had a I think I had a knack for all of that and kind of integrating it all into a package.
12:41 / 13:46
from transcript12:41 – 13:46
...product. And so this way, you can get your answer, but then in order to be able to plug it to the to the broader product, you need to do some work. Do you think it's important to ship fast and be imperfect or to make sure that that gap between protot
29:11 / 30:28
from transcript29:11 – 30:28
...for most most products and most enterprise teams is you you wanna make sure you're testing this way, like, much more often with with kind of expanding circles. What have been the biggest mistakes you made in user testing or biggest mistakes you see o
36:00 / 37:04
from transcript36:00 – 37:04
...products. That is how you demotivate your whole team because no one wants to be just stuck in what they're, you know, the specific, you know, section. And so the biggest thing when you've when you've written a PRD is get everyone in a room who's gonn
29:59 / 31:04
from transcript29:59 – 31:04
...so I think the development process just accelerates a bunch. You mentioned the one pager there.
10:29 / 11:31
from transcript10:29 – 11:31
...products to learn necessarily because a couple of them really resonate and they're gonna go explore those first. When you think about those four new products, do all of them work? If you place forward three years, do those four products will still ex
42:00 / 43:08
from transcript42:00 – 43:08
...a product team to be creative, ambitious, hungry, excited when it's a little bit formulaic? Yeah. That's certainly happened. You know, sometimes it can happen because you just have this very hard problem that you've been banging your head against the
45:41 / 46:48
from transcript45:41 – 46:48
...that is production ready. Because the prototype, if you did it well, it's inexpensive. And so it means that it lacks a lot of the things that make it production ready. It's basically a probe to some extent. We call it a probe. It's
28:23 / 29:35
from transcript28:23 – 29:35
...development process. Right? Like we talked about, as you discover, as you test different options, as you iterate, you're gonna gradually come to a picture of whether the product is a hit or or or not. In vast majority of cases, it's it's over a perio
26:09 / 27:16
from transcript26:09 – 27:16
product decision that I made that didn't work is how we built DAISY, like the v one. We took a breadth first approach. The consensus view is, you know, start narrow, point solution, land and expand. It's the wedge, that sort of thing. What we set out
14:06 / 15:18
from transcript14:06 – 15:18
a company we work with told us that, you know, they're sort of like a build contract build company. They said they will get off the phone from a pitch, and in four hours, they would have a prototype. And so the question is, like, what is a PM doing?
9:00 / 10:05
from transcript9:00 – 10:05
...step change improvements. And then there is, if you have existing products, already your company with multiple products already, there's obviously maintenance of those products or also known as KTLO and internal productivity. So those are the three m
28:04 / 29:35
from transcript28:04 – 29:35
...process, again, coming from design, I kind of view everything through that lens, is very similar. Instead of making an observation, you define a problem. You observe a problem that's happening, something that people are dealing with that's making the
19:29 / 20:30
from transcript19:29 – 20:30
Have a podcast?
Run your podcast through Clypt
Get ranked clips, hooks, and ready-to-post copy from your own episodes. Free to try.