I don't think design-led organizations have become the norm....the only big tech company that is design-led is Airbnb (the founders are designers). It's safer to say that most companies are engineer-led. And it's also safe to say that more companies see the value and impact of design but we're far from leading companies and having a seat at the table.
Version control also does not improve my design instinct. I agree with what others have said regarding how design artifacts are pretty much garbage and have a short life span. I also fall into the camp of designers who just want the most recent up to date design. Sure it's important to know what were the reasonings that led to a design decision, but that's done at a high level. It's not like any stakeholder is asking why did we make iteration 3 like this (while we're on iteration 11).
This article comes across as very market-y. There's better ways to advertise your product, it doesn't have to be done by making outlandish claims that are not backed by designers outside of your organization.
Version control also does not improve my design instinct.
Agreed. It's a bit of a stretch.
I'm dubious about this article based on the very first sentence:
Design-led organizations have become the norm...
Tell that to every designer working outside of the tech bubble.
I'm also always a little wary of people that quote themselves.
Instinct transforms technical skill into artistry.
HEATHER PHILLIPS DIRECTOR OF DESIGN, ABSTRACT
As an individual contributor that does use Abstract, I'm very dubious about the claims here. I rarely, if ever, find value going down memory lane ala commits. The primary purpose for my usage of version control is so I can keep an archive in case of emergency and thus keep the current files as clean as possible. I could probably achieve a similar outcome with Dropbox and slightly more effort, but the result would be the same.
In other words, Abstract hasn't magically improved my "design instincts" in the slightest (although it may have for others, I don't know) but has certainly been a useful organization tool in my flow.
Most design artifacts are pretty much garbage as soon as they’re delivered and coded. Research done with users may be transferable, and I can see the need for tracking individual progress in larger teams but ultimately the coded thing IS the deliverable.
Tear downs, personas, jtbd, wireframes and even prototypes have relatively short shelf lives after release.
Version control always seemed like imposing github code methods on designers without a really strong reason. Most non-designers actually just want the link to the latest design with the recent feedback added. Abstract does help w that.
But improved instincts? Not buying it.