CDFAM NYC 2023 · New York · 14–15 June 2023

Computational Design Ops

Listen as a podcast

Abstract

Ronnie Parsons, a renowned figure in computational design operations from Mode Lab, shares valuable insights on the topic of ‘Computational Design Ops’. In his presentation, Parsons dives into the principles and practices that shape computational design operations, providing a roadmap for integrating computational design strategies to streamline processes and enhance efficiency in various domains. Drawing from his vast experience at Mode Lab, Parsons explores the practical applications of these operations, elucidating how organizations can leverage computational design tools and methodologies for improved operational performance and innovative problem-solving.

This presentation is primarily targeted at professionals, researchers, and academics in the fields of computational design, additive manufacturing, and operational optimization. Individuals looking to harness the power of computational design in operations management will find this presentation particularly beneficial.

Please note: The CDFAM Computational Design (+DfAM) Symposium serves as an esteemed platform for the exchange of knowledge among leaders in computational design and additive manufacturing. This recording is provided for educational and professional development purposes.

Transcript

From YouTube’s automatic captions, lightly cleaned; expect some errors. Each timestamp opens the video at that moment.

Read the full transcript · 2,723 words

0:05 Cool, all right, hey, good morning, see some familiar faces, so it’s very very cool, it’s been a minute since I’ve been back in New York, so glad to be here. Before getting started, just a quick show of hands, how many of you in the room are computational designers? Just put your hand up real quick, self-identifying, cool. How many of you in the room have used a computational design tool, maybe to create a product of some sort? Yeah. How many of you have built a computational design tool for someone else to use? Awesome, you can put your hands down.

0:46 All right, I’m Ronnie, thank you for the CDFAM team for putting the show on, right, and for the invitation to speak today. I’m a computational designer too, and I’m also the founder of Modelab, a sustainable innovation company based in Portland, Oregon. For the past two decades I’ve worked alongside visionary brands to scale the value and impact of computational design by focusing on two key issues, what products to create and how to create them.

1:21 So to start, let’s take a step back in time to a very interesting moment. In the 1960s computer technology began outpacing the speed of computer programming, the explosive growth of com, of this computing power, and sorry, in the 1960s computer technology began outpacing the speed of computer programming, the explosive growth of computing power and new languages presented opportunities that the emerging programming community was, will, was really ill-equipped to exploit. And it was such a threat that in 1968 the NATO Science Committee held the first International Conference on Software Engineering, where 52 global experts would come together for four days to talk about a really uncomfortable problem, right, and what are the solutions to sort of solve for it.

2:16 Douglas Douglas McElroy, who was a prominent mathematician, engineer, and programmer of the time, suggested a component-based development to speed up programming’s potential by making code reusable, thus make it more efficient and easier to scale. component-based development lowered the effort and increased the speed of software development, allowing software to utilize the power of modern computers more effectively. And in reflecting on this pivotal moment in time, Editor Dykstra would remark that “as long as there were no machines, programming was no problem, when we had a few weak computers, program, programming became a mild problem, and now that we have gigantic pro computers, programming has become an equally gigantic problem.”

3:05 This growing disparity between the hardware evolution and software stagnation of the time was not just a minor issue, it threatened to stifle the potential of computing. This existential threat would later become known as a software crisis. Now fast forward 50 years, and we’re experiencing a similar challenge, but this time in design. Computational design is struggling to scale up because it still operates in a bespoke fashion, we’re creating unique solutions for individual problems. And so today’s talk is about how to operationalize computational design to maximize its value and impact in this new technological era.

3:51 Now everyone in attendance is well aware that computational design has become a hot topic these days, right, and for good reason, computational design’s market presence is expanding, right, businesses across industries are investing in computational design, as it is clearly established that it enables a fundamentally different set of capabilities for design organizations, capabilities such as richer interactions between brands and consumers, data being infused throughout the product pipeline, and differentiation in the market through product innovation.

4:27 The trajectory of growth typically looks something like this, new roles are defined, new resources are added to a growing computational design team, the team becomes more embedded throughout the organization, typically servicing multiple groups and their product needs, and KPIs are defined and measured to evaluate the effectiveness of computational design efforts across products and platforms. But the reality of the environment we are working in is just way too challenging, right, the problems we’re solving are becoming more complex, we’re incorporating new materials, we have multiple manufacturing processes, and the there are evolving design requirements and kind of rigorous standards to hold up.

5:14 Rapid consumer demand, technological advancements, and environmental and regulatory requirements are, are bringing about tons of volatility, and there’s uncertainty everywhere, it’s stemming from potential supply chain disruptions, market shifts, and an evolving set of required skill sets to either learn or potentially be left behind. Lastly, there’s a growing disconnect between stakeholder expectations and what is realistically achievable given time, budget, and resource constraints. Organizations often struggle to unlock the full value of their investment in computational design, not because of a lack of product strategy or the computational designers they hired, but because computational design as a key organizational capability has not been set up for success organizationally.

6:08 That Modelab, we build systems that support computational design teams, the core of our work centers around integrating an operational layer within the enterprise, and we refer to this as computational design ops. So computational design ops systematically orchestrates and optimizes product, process, and people to amplify computational design’s value within fast changing organizations and markets. An analogous to how DevOps has revolutionized the development process through its agile and iterative approach, CD Ops empowers organizations to rapidly scale and make iterative improvements to computational design processes across teams.

6:53 And this computational design ops framework is experienced in the enterprise through the interaction between three integrated components, design systems, pattern language, and new practices and behaviors. A design system, a design system bridges the gap between the physical and digital domains of the solutions computational designers create, think of it as like the glue between what we’re going to make and how we’re going to make it. Design system is typically composed of things like principles, right, why we work the way we work, patterns, the articulation of the problems to solve and how to go about doing so, toolkits, reusable assets that a team who is not actually a computational designer or have that capability on the team can use, right, templates for having to not start a project from scratch every time, guidelines which loosely define the ways in which things should be created, team learnings and resources, and it can also include things like a lexicon of terms, helping to ensure that all stakeholders have a foundational understanding of computational design and its associated concepts.

8:20 We use design systems to increase consistency, efficiency, and scalability within the teams we work with, who are using these advanced capabilities that we’re hearing about today, right, to bring products to life. It serves to connect teams by providing a shared language and a reference point that spans teams. By systematizing computational design, design systems enable teams to work more collaboratively, it streamlines the design process, and it lessens the effort required to get started.

8:56 Now one of the key components within a design system is a pattern, okay, and a design pattern is the reusable form of a solution to a design problem, with ways, but the way that we typically provide an initial, initial structure to patterns is around four touch points. First, functional patterns relate to how a product should behave and how it should perform, perceptual patterns, which is the ethos of a product or the brand, depending how you think about a brand, and it forms the patterns that together shape how a product is perceived, platform patterns, which are the materials, the methods of make, the data models that you use to create products, and domain patterns, which are the categories of product, right, the types of products that you’re creating.

9:48 We’ve done a lot of work with Nike in the past, so I’m going to use a past project as a sort of an example of this thinking. So domain patterns, right, track and field, 100 meter race, functional patterns, we need to minimize weight, maximize stiffness, and tune flexibility, platform patterns, a data model center around a specific geometry kernel, method of make involving both rapid prototyping through additive manufacturing and injection molding, the materials that it is made of, and lastly perceptual patterns, like brand requirements needing to feel a certain way and having a certain kind of look.

10:38 These patterns extend beyond just the types of function that you might see on the surface of the product, but also the functions that live between products, right, things like incorporating sizing and how to grade computationally a product, so that it doesn’t just meet the requirements of one size and then get non-uniformly graded across all the size run, but each one can be unique to the unique functional requirements of that particular size. These functional patterns, when thought of in the context of a new domain, another category of race, are extensible, right, and they can be reused in order to be able to apply patterns that you’ve created within one product and one domain of use into new ones.

11:23 And working with patterns is a really interesting thing, right, because patterns, as you create them, they also have to live somewhere, right, and so a pattern library comes to life, where all of the ways that you’re solving things as a team go and live, and they evolve. And out of that pattern library, patterns are assembled into different new products, where each product will also yield additional patterns, right. In working with patterns a language will emerge that is the embodiment of an organization’s design patterns brought to life in the product context, and this language is an ownable asset in the market, it scales across product categories, seasons, right, and years upon years, right.

12:19 So don’t forget that a pattern for one thing is scalable within the context of other things, and as that happens there’s a new language that will emerge that you can own. So patterns define how you solve problems computationally, over time they form a design language for your organization, but the core of CD Ops, the experience that’s felt, really centers around a human element and a fundamentally different way to approach, approach the product creation process. We center this around two interconnected loops, one about launching products and one about landing products.

12:58 Right, at the start of a particular product we assess the product, what are its needs, and we try to identify the patterns that live within that product and the patterns that live beside or adjacent to that product, right, we map out of our pattern library the patterns that we can use, right, and reuse, thereby accelerating, right, our speed of innovation, allowing us to get further much faster, and we use those to then assemble and build first proofs of life, right, which then drive the development of the product. Over time, as we successfully land a product, right, we do another assessment of the product, we try to understand what patterns were born, in which we can publish and deploy, which then increases the scale and impact of the work that we are doing as a team.

13:57 So practices and behaviors define how a design system evolves and how teams experience this evolution over time. So CDOps provides a framework to create better products faster by making design reusable, and reusability is what makes scale possible, right, and a pro tip for you, if you’re already using a lot of cool software and really really deep in the process, this kind of thinking transcend software, right, it’s a framework that you can apply regardless of the tools you use, the industry you’re operating within, or the size of your team.

14:36 But a question that comes up a lot whenever, you know, we’re talking to brands about integrating this kind of a framework into the organization, is, you know, this sounds like a lot of process, you know, it sounds like a whole lot of stuff that’s not the product, and it’s concerning, right, I mean, of course everyone’s concerned about having too much to do when it’s not the thing you’re trying to actually create, right, it’s a, you know, a lot, a lot of debt in the workflow. But if you perform a product audit when you go back to the office, you’re going to come across a handful of tools that are similar, that you’re using a ton of permutations of workflow, depending on how many people are on the team that can be an order of magnitude greater, right.

15:21 And then if you multiply that by every product you’re supporting, right, you’ll realize how inconsistent and complete and difficult it is to maintain computational design within your organization, right, and so the thinking evolves from, rather than focusing on products, where the effort is always going to be the same and increasing over time, right, will be present and increasing, focus on systems, because there is an inflection point, right, where over time the effort is beginning, will begin to plateau, because of the reasonability factor.

16:00 So some things to consider, if this is at all something that sounds interesting to you, I want to share a couple of things about implementing CD Ops into your process. The first thing is patterns are everywhere, right, and so you really want to look somewhere unexpected. Okay, sorry, I’ve got a little notification pop up, try to look outside of the product, look at the user, look at the data, look at the assets that you already have within your team that you can leverage and integrate into the products that you’re creating, but also look adjacent to the product, right, look somewhere that is not the physical product, you know, look to nature, look in other areas, and try to use patterns that you find there to breathe new life and new ideas into the work that you’re doing.

16:56 Patterns are extensible, right, try integrating the patterns you’re creating across domains, right, beyond just sizing, try to take sizing, right, and then multiply that times category of use, right, thereby expanding the reach of the tools that you’re building and the impact you can have in the products that you’re creating. And your pattern language is an asset, right, you want to evolve it and you want to own it, right, so at the Olympics we use this type of thinking and these types of tools in order to not just bring one product to life, but to bring an entire, you know, smattering of products to life, and a fraction of the time that it would have taken to create just one, right.

17:43 But remember that pattern design systems are built for scale, right, and so the patterns that you’re creating you want to capitalize on that momentum, and the speed to market, right, that you now have possible through the use of this type of an operational framework is something that can leverage, you can be leveraged, on the success of a pinnacle event like the Olympics, driving the product then into market.

So in closing, I just want to throw out a quick four steps that you guys can take to start to integrate this thinking into your process, right, it’s it’s really pretty straightforward and pretty easy. The first one, bought it, take a look at what are the parts of that product, how do they work, right, and how were they defined computationally. Then take it, take a look at the computational product you created to support the creation of that, take a look at how you solve the problems, are you solving them consistently, is there anything you can reuse, define the pattern language that already exists within your organization and try to then identify ways that you can codify that, right, build a pattern library so you have somewhere to store all of this work, right, and be able to then reflect on its use through shared learnings to drive future pattern use and reuse.

19:10 So if you want to learn more about how to integrate CDOps into your process, you know, feel free to reach out, you can hit me up here, also I’m here for the next two days, so I would love to grab a coffee. Thank you so much, thank you.

More from CDFAM NYC 2023

Design Computation Human

Design Computation Human

Onur Yüce Gün · New Balance

Mud y Robots: Keynote Presentation

Mud y Robots: Keynote Presentation

Ronald Rael · UC Berkeley / Emerging Objects

Roadmap to Replicators

Roadmap to Replicators

Neil Gershenfeld · MIT Center for Bits and Atoms

Scaling & Standardizing Patient Specific Design

Scaling & Standardizing Patient Specific Design

Adam Wentworth · Mayo Clinic

Overcoming the Design Dilemma

Overcoming the Design Dilemma

Ryan Carter · Johns Hopkins APL

Generative Design & Digital Manufacturing at NASA Goddard

Generative Design & Digital Manufacturing at NASA Goddard

Ryan McClelland · NASA Goddard Space Flight Center

Digital Materials – Geometry and Data Combined

Digital Materials – Geometry and Data Combined

Marek Moffett · General Lattice

Ten Years Teaching Additive

Ten Years Teaching Additive

John Hart · MIT

10 Years of Applying DFAM

10 Years of Applying DFAM

Tim Simpson · Penn State University

MfAM Walks so DfAM Can Run!

MfAM Walks so DfAM Can Run!

Chelsea Cummings · The Barnes Global Advisors

Informatics and AI for Materials Development

Informatics and AI for Materials Development

Wes John Alder · Citrine Informatics

Predicting Fatigue Life in AM Metal Parts Using DigitalClone

Predicting Fatigue Life in AM Metal Parts Using DigitalClone

Behrooz Jalalahmadi · Sentient Science

Designing Material Properties with Advanced Toolpath Generation

Designing Material Properties with Advanced Toolpath Generation

Alex Roschli · Oak Ridge National Laboratory

Design Automation Using Machine Learning & Computational Design

Design Automation Using Machine Learning & Computational Design

Rhushik Matroja · Cognitive Design Systems

Learning to Generate Shapes

Learning to Generate Shapes

Karl Willis · Autodesk Research

Design for Artificial Intelligence

Design for Artificial Intelligence

Chris McComb · Carnegie Mellon University

Register for Updates and Discounts on CDFAM events.