@zachlloydtweets Not settled, but we're testing "Footing": the share of a bet's risk that's actually been proven, against bars set before the test. Output is nearly free now, so evidence has to be the unit.
@michaelmiraflor 100 percent. There’s a human problem surfacing in AI-Native Product Dev. Someone spends a couple hours diving deep to understand a problem. Then someone else spends 30 seconds sharing what “their Claude” told them. Wrote a longer post here: https://t.co/RIlaoLy13u
Workplace failure mode: Someone in the room says "I asked my AI" and repeats what it said back to you like it's a rebuttal. They don't understand it. AI didn't kill critical thinking. It just made it optional, and made the absence of it very easy to hide.
@2sraval Could argue semantics but overall yes. Obviously depends on who the consumers are; builders or heavy practitioners in whatever field. Steeper climb at times for B2B to understand domains. Building within a legacy system is almost always true, especially in enterprise.
It's that confidence level propagates into the artifact's language. A roadmap built on thin evidence reads differently than one built on strong evidence. That distinction usually gets flattened the moment it hits a slide.
Every design system I've worked with assumes one product, one team, one codebase forever. Consultancies don't get that. Every project starts from zero, inheriting someone else's branding. Most tooling doesn't fit that reality, so we built our own.
@joshpuckett I agree with you fully. Is this a new title? New role? Or redefining what a designer does. The latter seems too much of an uphill battle to do. Seems like a good time to reset what an actual product designer does by shaping a new title?
@joshpuckett Unfortunately, it depends on who you ask. I think “perception of intention” is the bar for ALOT of non-designers.
If you’re tone-deaf, someone can sing flat for an entire song and it still sounds like singing to you.
@thenanyu@levie So that was my original thought. Do you think lots of companies will misalign to this in thinking that “oh this is obviously an engineer position”.
@jazer@jakek I agree that the cost of build has changed the role of planning. I’d say reducing uncertainty hasn’t disappeared, it’s shifted from “can we build it?” to “should we scale it?” And the fastest way to answer that isn’t more philosophy, it’s smaller, instrumented slices.
I feel like changing simplistic fonts and colors to mimic a current example isn’t… new right? Like the dropper interaction makes it feel more enjoyable but isn’t this not very “new” relative to other “make my design look like this example” things?
We made a tool that lets you absorb the vibe of anything you point it at and apply it to your designs
It's absurd and it just works
Style Dropper, now available in @variantui
@ryolu_@benjkowalski When you say “prototype,” do you mean a throwaway, iterative concept, or an actual branch of the application used to explore options? How does that work make its way back into the product? Is your branch, cleaned up, the actual work?
@vanschneider What’s being sold is “hey you can move fast, make the mistakes who cares bc you can scrap it and build it again so fast”. But nobody talks about the trust that gets broken and how frustrations turn people into anti-fans/users.