Thank you to the many people who have been blog contributors to, and readers of ArtsBlog over the years. ArtsBlog has long been a space where we uplifted stories from the field that demonstrated how the arts strengthen our communities socially, educationally, and economically; where trends and issues and controversies were called out; and advocacy tools were provided to help you make the case for more arts funding and favorable arts policies.

As part of Americans for the Arts’ recent Strategic Realignment Process, we were asked to evaluate our storytelling communications platforms and evolve the way we share content. As a result, we launched the Designing Our Destiny portal to explore new ways of telling stories and sharing information, one that is consistent with our longtime practice of, “No numbers without a story, and no stories without a number.”

As we put our energy into developing this platform and reevaluate our communications strategies, we have put ArtsBlog on hold. That is, you can read past blog posts, but we are not posting new ones. You can look to the Designing Our Destiny portal and our news items feed on the Americans for the Arts website for stories you would have seen in ArtsBlog in the past.

ArtsBlog will remain online through this year as we determine the best way to archive this valuable resource and the knowledge you’ve shared here.

As ever, we are grateful for your participation in ArtsBlog and thank you for your work in advancing the arts. It is important, and you are important for doing it.

“In the report John Maeda makes the distinction between “classic” designer, the makers of finite objects for a select group of people (think graphic designer, industrial designer, furniture designer) and “computational” designers, who deal mostly in code and build constantly evolving products that impact millions of people’s lives.”

“Designers who can code and write have always been attractive to tech companies, but Maeda’s report foretells an inflection point for the field. As the distinction between engineering, writing, and design becomes blurrier, design’s role in technology only stands to become more ingrained in the product development process. In the end, design, as a singular field, could become less visible but more relevant.” [Wired, John Maeda: If You Want to Survive in Design, You Better Learn to Code]

The 2017 Report frames computational design as a key driver of accelerated growth, with inclusive cultures @work as vital for tech businesses hoping to lead in design. This report is the predecessor to the 2016 Report which showed peak growth in interest by venture capital firms in design, and highlight significant growth in the acquisition of design agencies by consulting firms like McKinsey & Co and Accenture. Google emerged as a new leader in design. And the 2015 Report which explained design’s rise in value to tech as due to mobile devices and the mass-consumerization of computing. We moved from “tech-led” to “experience-led” digital products as services on smartphones took over and gave access to everyone.

Report identifies and defines computational design as a key driver in the growth of tech businesses. Computational designers are those who deal mostly in code and build constantly evolving products that impact millions of people’s lives.

Report
Maeda, John
47
January, 2017
Publisher Reference: 
MaedaStudio
Research Abstract
Image Thumbnail of Pub Cover: 
2017