Notes

The particular UX Framework That truly Works When There's No Time for Research
Most design frameworks assume you have time. Time to research before you build, iterate before you ship, test before you launch. That assumption breaks down at most companies.
The sprint is planned. Developer capacity is allocated. The feature was promised to a customer on a sales call 3 weeks ago and is now in the contract. Research isn't off the table because nobody values it – it's off the table because 6 people have already made commitments based on the assumption that the design will be fine.
Working inside that constraint is a different skill than the one most design education focuses on. It's the constraint we work inside on most projects at UAREUX.
this article
Fast signal looks different from proper research but it isn't nothing. Four 20-minute calls with customers who use the relevant part of the product. A pass through 6 weeks of support tickets filtered by the feature area. Two hours of session recordings from Hotjar or FullStory on the flows you're about to touch. That's maybe 12 hours total. Not a research study. Substantially better than designing from memory.
Defensible decisions matter when you're moving fast. You can't always know the right answer, but you can document why you made the call – what signal you had, what you assumed, what you'd watch post-launch. When something doesn't work, that documentation moves the conversation from blame to learning.
Teams that ship fast and design well aren't skipping the process. They're running it in parallel with development rather than before it. The mindset shift is treating design as continuous rather than as a phase that has to complete before building starts.
That model is harder to maintain. It's also the one that survives contact with how product companies actually operate, which looks nothing like the double-diamond.

Homepage: https://uareux.com/blog/is-ux-design-oversaturated-or-just-the-same-portfolio/