Wireframes
topic on 4 shows · 8 statements across 6 episodes
Startups For the Rest of Us
We Live to Build
Lenny's Podcast
the Startup Ideas Podcast
8 statements about Wireframes, every show
Isenberg: Mid-fidelity wireframes are bad; use low-fi or high-fi instead
“Mid-fi wireframes are bad. You know, I think that you want to start with low-fi or go high-fi. You know, you can't be half pregnant. You don't want to go mid-fi.”
Weisbrot: Comprehensive product and technical documentation makes startups scalable and acquirable
“Having all of, you know, the users, the user speech feature future documentation, the technical documentation, the QA documentation, The wireframes, all of these things combined makes this a sellable, a scalable business and a sellable business.”
Barnard: Low-fidelity wireframes drive better engagement with product developers
“Having these kind of sketchy, low fidelity artifacts, which is what wireframes are, they're kind of like a digital version of a napkin sketch, was really a great way to get more engagement with the people who are actually having an effect on the product.”
Barnard: High-fidelity mockups often lead to misaligned developer implementations
“Often better just to have something low fidelity and then have a conversation around it because you can hand off something that looks final and get something back that's totally different because you didn't specify how it should be on mobile or how, how it sho…”
Barnard: Wireframes have no standalone value because they never ship
“The wireframe is just an artifact. It's just a tool. It's not really It doesn't add any value on its own because it's not something that ships to the customer. So it's really what they can be used for.”
Foster: AI generation of interactive wireframes from user stories is already solvable
“I think that by itself absolutely would. And I think that's a solvable, that is a solvable problem with the technology even as it stands today. So I do think those kinds of things are going to be out there”
Wodtke: Creating wireframes is an ineffective use of design time
“I know designers spend all this time making wire frames, and I'm like, that's the lamest use of time ever. Just get some whiteboards, go into the room with your engineers, and start making some marks together, and that just works better.”
Mehta: Strategy docs require wireframes because words alone cause misinterpretation
“Oftentimes when you talk about strategy in words alone, everyone takes away a different interpretation of that strategy. Whereas when you actually can show people wireframes of what the product will look like when that strategy Is implemented. It creates much …”