This content was created by GHION.AI . This content was uploaded by GHION.AI . This is a YouTube video titled "Customer-Centered Decision-Making" created on May 17, 2023. It features Julia Collins discussing decision-making frameworks at Planet Forward, focusing on design thinking and human-centered design for product development.
Chapters
Is there any frameworks you can share with us in terms of how you make decisions around the types of products that you would want to design for? Yeah, well, the decision making framework itself that we use at Planet Forward is pretty light, but it is important within teams to be able to signal where you are in the continuum of making a decision. Something that we say is, is this an idea, is this a proposal, or is this a decision? And that creates a lot of clarity within the team. Especially when you're brainstormin or you're working very quickly across multiple projects, it's important to be able to signpost and signal, oh, this is just an idea, I just want to get this out versus this is a proposal. I'd like for us to be able to price this and scope it, or in some cases this has been decided and I'm communicating it as a decision. In general, I think we are very inspired by design thinking when we think about the way to bring products to market. In particular, human centered design. Before we had any perspective on Moonshot as a cracker product or Planet Forward as a data and software platform, we just did a lot of listening. And by we, I mean the early team. So myself, one other MBA who I hired really just did a very like, methodical customer discovery, Sprint. We talked to 50 Chief Sustainability Officers working in companies to understand what their needs were, what their motivations were, what the incumbent solutions were. And we use that customer discovery to create sort of an initial perspective on what we could build. And then we did some really rough prototyping to be able to test it with real users. And so we used FIGMA and some other tools to be able to sort of create a sample product and then got that in front of users and had them tinkering with it. And then from that we developed sort of a quick application. So it was actual software, but again, we sprinted like maybe six weeks developing it. And then we figured out, would people pay anything for it? Would people pay even $1,000 for this solution? And so it was just really this. We've heard this framework a lot of times to test to rapid prototyping, testing and iterating. We very much did that. And I think that is the right way to build products.